Fixed typos for Resurrection Balm and Leather Baldric #579

Merged
josefwk merged 2 commits from master into master 2025-02-08 00:43:29 +00:00
josefwk commented 2025-02-07 15:54:30 +00:00 (Migrated from github.com)

See title. Changes the unidentified name for Leather Baldric (which was "Leather Baldri") and fixes a typo in the name of Resurrection Balm (was "Ressurection Balm").

See title. Changes the unidentified name for Leather Baldric (which was "Leather Baldri") and fixes a typo in the name of Resurrection Balm (was "Ressurection Balm").
josefwk commented 2025-02-07 15:58:28 +00:00 (Migrated from github.com)

So there are other instances of these typos in the following files, not sure if they should be modified or preserved:

  • rsrc/scenarios/busywork/items.xml
  • rsrc/scenarios/stealth/items.xml
  • rsrc/scenarios/valleydy/items.xml
  • rsrc/scenarios/zakhazi/items.xml
  • test/files/town/townRectUniversal/items.xml
  • test/replays/scenarios/use-special-terrain/items.xml

Pushed corrections to these files as well in the interest of expediting the PR, can always cherry pick or request changes.

So there are other instances of these typos in the following files, not sure if they should be modified or preserved: - `rsrc/scenarios/busywork/items.xml` - `rsrc/scenarios/stealth/items.xml` - `rsrc/scenarios/valleydy/items.xml` - `rsrc/scenarios/zakhazi/items.xml` - `test/files/town/townRectUniversal/items.xml` - `test/replays/scenarios/use-special-terrain/items.xml` Pushed corrections to these files as well in the interest of expediting the PR, can always cherry pick or request changes.
CelticMinstrel commented 2025-02-07 18:25:46 +00:00 (Migrated from github.com)

I'll merge this as soon as possible, but it'll need to be cherry-picked to the scen_update branch (#338) too (which would omit the test scenarios). It might take me a bit of time to get to that, though you're also welcome to do that yourself in a second PR.

I'll merge this as soon as possible, but it'll need to be cherry-picked to the `scen_update` branch (#338) too (which would omit the test scenarios). It might take me a bit of time to get to that, though you're also welcome to do that yourself in a second PR.
Sign in to join this conversation.
No description provided.