Tutorial Rework
Moderator: Forum Moderators
-
- Posts: 427
- Joined: May 10th, 2011, 7:20 pm
Re: Tutorial Rework
Ugh. Thank you, averyimaginativename.
Wait, it just dawned on me. WTH does the quintain have a magical attack? That just seems extremely stupid.rjaguar3 wrote:On line 388, I don't think it's a good idea to mention terrain defense at this juncture, since the quintain has magical attacks (rendering terrain defense superfluous in this circumstance). I do believe it is mentioned later (at line 1047); that, I believe, is sufficient instruction on how defense works.
Timshel
- averyimaginativename
- Posts: 245
- Joined: August 21st, 2010, 12:40 pm
- Location: /dev/null
Re: Tutorial Rework
From the WML:uncleshelby wrote:Wait, it just dawned on me. WTH does the quintain have a magical attack? That just seems extremely stupid.
This probably. 1 in 170,000 in a game as popular as Wesnoth - it's happened to somebody. 70% magical vs 60% normal makes it less likely.# There is a 1 in 170,000 chance that the quintain will miss on all
# 10 attacks. Ignoring that.
Force chance to hit might be a better option than magical attacks, though magical attacks are something that should be addressed in the tutorial at some point.
UMC Story Images web gallery
On an indefinite Wesbreak for health reasons - please only try to get my attention for UMC story images website issues.
On an indefinite Wesbreak for health reasons - please only try to get my attention for UMC story images website issues.
-
- Posts: 427
- Joined: May 10th, 2011, 7:20 pm
Re: Tutorial Rework
Hmm. I get it. But I think the quintains should be unable to kill Konrad/Li'sar in the first two turns. It's a tutorial. So, raise Konrad/Li'sar's life, or lower the quintain's attack power...
Any thoughts?
Any thoughts?
Timshel
- averyimaginativename
- Posts: 245
- Joined: August 21st, 2010, 12:40 pm
- Location: /dev/null
Re: Tutorial Rework
Code: Select all
hitpoints=32
I would use FORCE_CHANCE_TO_HIT with an attacker hits or attacker misses event. Set it to 100%, and remove it after the first hit (or leave it alone, and set it for the last hit).
UMC Story Images web gallery
On an indefinite Wesbreak for health reasons - please only try to get my attention for UMC story images website issues.
On an indefinite Wesbreak for health reasons - please only try to get my attention for UMC story images website issues.
-
- Posts: 427
- Joined: May 10th, 2011, 7:20 pm
- averyimaginativename
- Posts: 245
- Joined: August 21st, 2010, 12:40 pm
- Location: /dev/null
Re: Tutorial Rework
Something like this (untested)
Set your variables:
Force your chance to hit
increment your variable on the first hit:
[Edit - two edits already. Forgot filter, and used wrong IDs in FCTH]
Set your variables:
Code: Select all
[set_variable]
name=playerhit
value=0
[/set_variable]
Code: Select all
{FORCE_CHANCE_TO_HIT id=quintain id=Konrad 100 (
[variable]
name=playerhit
numerical_equals=0
[/variable]
)}
Code: Select all
[event]
name=attacker hits
first_time_only=yes
[filter]
id=quintain
[/filter]
[set_variable]
name=playerhit
add=1
[/set_variable]
[Edit - two edits already. Forgot filter, and used wrong IDs in FCTH]
UMC Story Images web gallery
On an indefinite Wesbreak for health reasons - please only try to get my attention for UMC story images website issues.
On an indefinite Wesbreak for health reasons - please only try to get my attention for UMC story images website issues.
-
- Posts: 427
- Joined: May 10th, 2011, 7:20 pm
Re: Tutorial Rework
So, this is supposed to make the Quintain hit the first time, guaranteed? It didn't work.
Timshel