-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Enable optional advancements? #118
Comments
For me, it's not necessary to enable any but I leave it to you. |
It doesn't hurt, but I think the campaign is not long enough to enjoy those advances |
ok I think I'll try enabling them for 1.7.0, just to see how that goes... |
cooljeanius
added a commit
to cooljeanius/A_New_Order
that referenced
this issue
Jan 1, 2024
see nemaara/A_New_Order#118 also continue writing some support conversations
cooljeanius
added a commit
to cooljeanius/A_New_Order-1
that referenced
this issue
Jan 16, 2024
- create CODEOWNERS file - enable optional advancements as per issue nemaara#118 - confirmation of @alxrem's translation credits entry - start on ChangeLog - updated Medic frankenportrait from @DuncanusDillius - even more validator fixes that I thought were too difficult to do previously - start writing support conversations - improve S01 cutscene/dialogue - attempt at debugging odd bug where Lorin randomly disappears when visiting the gallows in S02 - minor updates to the Akladian name generator
PR #171 will close this. |
cooljeanius
added a commit
that referenced
this issue
Apr 2, 2024
another sync of changes from my other repo: - create CODEOWNERS file, to ensure that the primary people who have edited files get notified when changes to them are proposed (I'm the only one in it so far, as anyone else who it'd make sense to add would have to be added as a collaborator to this repo first) - enable optional advancements; closes #118 - confirmation of @alxrem's translation credits entry - start on ChangeLog entries for next release (which will be 1.7.0) - updated Medic frankenportrait from @DuncanusDillius - even more validator fixes that I had thought were too difficult to do previously - start writing support conversations (in macros/conversations_support.cfg), for issue #73 (will probably be rewritten) - improve S01 cutscene/dialogue - attempt at debugging odd bug where Lorin randomly disappears when visiting the gallows in S02 - minor updates to the Akladian name generator
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mainline's optional_unit_advancements.cfg contains a bunch of optional advancements that we could enable: https://www.wesnoth.org/macro-reference.html#file:optional_unit_advancements.cfg
Friendly ones:
{ENABLE_PARAGON}
(so Majid Yahyazad can finally turn into @knyghtmare){ENABLE_WOSE_SHAMAN}
(only relevant if/when Lots of changes! New scenario! New portrait! Bugs fixed! #117 gets merged, and even then I doubt any allied woses would live that long...)Hostile ones:
{ENABLE_ARMAGEDDON_DRAKE}
(only relevant if/when Lots of changes! New scenario! New portrait! Bugs fixed! #117 gets merged, and even then I doubt any enemy drakes would live that long...){ENABLE_NIGHTBLADE}
{ENABLE_TROLL_SHAMAN}
{ENABLE_ANCIENT_LICH}
{ENABLE_DEATH_KNIGHT}
So, what do people think? Does it make sense to enable any of these? Perhaps only on certain difficulty levels?
The text was updated successfully, but these errors were encountered: