New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max torch final victory dialog handling of SoF s9 rework #6628
Max torch final victory dialog handling of SoF s9 rework #6628
Conversation
data/campaigns/Sceptre_of_Fire/scenarios/9_Caverns_of_Flame.cfg
Outdated
Show resolved
Hide resolved
data/campaigns/Sceptre_of_Fire/scenarios/9_Caverns_of_Flame.cfg
Outdated
Show resolved
Hide resolved
data/campaigns/Sceptre_of_Fire/scenarios/9_Caverns_of_Flame.cfg
Outdated
Show resolved
Hide resolved
I tested this and it seems to cover the issues we discussed previously: a non-Krawg unit finding the final rune and also addresses the plot-hole regarding the Gryphon Riders. A bit unfortunate that the entire volcano eruption event has to be duplicated to cover both the Krawg version and the regular Gryphon Rider version - might it be possible to re-use that code? At any rate, as it currently stands it seems to resolve #6332 satisfactorily. This is a change worth including in the change log. There are a few new strings, but not sure if there any fuzzies generated to notify translators about. Maybe @nemaara wants to review the string changes first, but I don't think there were any major ideas added, besides the explanation for Krawg being the only survivor. |
Thank you for testing and confirming on your end. I'll see about doing one more refinement of the dialog. As to minimizing duplication of code, I'll see what I can do. Perhaps I'll define the redundant code as a function/macro and then just call it for both conditions. |
data/campaigns/Sceptre_of_Fire/scenarios/9_Caverns_of_Flame.cfg
Outdated
Show resolved
Hide resolved
data/campaigns/Sceptre_of_Fire/scenarios/9_Caverns_of_Flame.cfg
Outdated
Show resolved
Hide resolved
also, be sure to run |
I would like to provide some replays to show how I have tested the latest commit. Also, I removed a double-space in a piece of dialog, is it okay to bundle it into this PR? |
It's already removed in b775ba8 / 527cd41 - not sure why it's showing as a difference here. Maybe try re-basing your branch to current origin/master? Also, I forgot to mention: would it be reasonable to use 'out-fly' instead of 'outrun'? |
After a quick internet search, outrun seems to be used in a lot of contexts that don't involve literal running. Seems like it can be used in the context of anything that travels faster. Merriam-Webster lists outfly as a word but the Cambridge Dictionary doesn't. I found a graph showing outfly had little usage over time. So, for the sake of being less obscure, I guess I'm in favor of outrun. |
a7d2c9e
to
166796b
Compare
…ic tablet, and add translator hint Things in the scenario didn't quite make logical sense considering the presence of Gryphon Riders. This resolves the issue by allowing them to trigger an event, and by acknowledging them in the endlevel dialog. Additionally, one translator hint is added for the "Smash" text when the rune is smashed.
166796b
to
e0108f1
Compare
The PR is now squashed neatly into a single commit and rebased on top of the HEAD of the present Master branch. Some grammatical/dialog issues have been addressed. Replays of possible test cases have been submitted. After this passes the CI (hopefully optimistic) I submit this for merging. |
Looks good to me. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I check code but I feel like Krawg has way too much plot armour here, but I guess it's fine.
The plot armour was always there - at least since the scenario was rewritten in 1.15.x - my request and this PR are trying to address the game-play issue of Krawg being the only one permitted to break the last rune and the story issue of the Gryphon Riders not being able to escape. |
One thing I like about this reworked SoF is that it removed that non-sensical concept of "Thursagan dying and then all other runecrafters dying with him".. But I dont like SoF's high difficulty curve (since I cannot get pass the 5th level despite 20ish tries) |
Thanks everyone for your contributions. |
[/message] | ||
[message] | ||
speaker=Thursagan | ||
message= _ "Just do it! You riders have a chance to escape, our enemies cannot. We knew that death was likely when we fled here, just go!" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is one of the ones that might have another variant if there's only one gryphon rider, maybe: "Just do it! You and Krawg have a change to escape, our enemies cannot. We knew that death was likely when we fled here, just go!".
Edit: have realised that the scenario no longer recalls all of the player's units. Maybe we should just assume that there are some riders on the recall / recruit lists, who'll try to escape even if they weren't recruited.
This is my contribution to completing what was started in #6334 .
The issue this tries to close is #6332.
Things in the scenario didn't quite make logical sense considering the presence of Gryphon Riders. This resolves the issue by allowing them to trigger an event, and by acknowledging them in the dialog.
The last narrator dialog is slightly different depending on whether or not the player has a gryphon rider in addition having Krawg. Also, events are triggered when Gryphon Riders move to the stone tablet at the bottom of the map.