Update scenarios from original legacy format #338
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(And remove the old-format corrected version.)
This is little formatting things which would probably end up as spurious changes later anyway
…n unusual melee weapon Idea for this goes to ADoS.
… the new abilities
- Basalt secret door no longer turns into a normal door when discovered - Brazier now has a light radius
Thanks to ADoS for these fixes
CelticMinstrel
force-pushed
the
master
branch
2 times, most recently
from
7442136 to
e7d5b4f
Compare
Items affected are all wands, plus most weapons or armour with usable abilities
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reconverts the blades base and the four packaged scenarios from their original files, then reapplies all the changes that had been made to the scenarios since their initial conversion.
I'm going to leave this open for awhile and occasionally update it if a new correction to legacy import is made, or if a change is made to the scenarios. Once we can be confident that legacy conversion is correct, then I will merge it.