[gameobj] Migrate XML updates from ;xmlpatch
Maintainers usually reply within 1 day
@mrhoribu is already working on this.
Since Jun 1, 2022.
Assessment
This issue has not been assessed yet.
Description
Migrate XML updates from ;xmlpatch
;xmlpatch was created a workaround for getting changes merged into the upstream gameobj-data.xml. Now that we own the gameobj-data.xml file published in the repo, we can create migrations for the published data and make the script obsolete. I am getting started on the work and wanted to have a discussion about some of the changes required so that we're all on the same page. There are two main types of XML updates in ;xmlpatch:
Phase 1: Updates to existing types
These are pretty straightforward and I've started creating migrations for these. I should have some PRs to send soon.
- Handful of additions and exclusions to existing types
- armor
- clothing
- jewelry
- Creatures and gems from new areas (SoS, Reim)
- Use names (e.g. "rotting fel trunk") instead of nouns for box type and allow optional
shiftingprefix for phased boxes.
Phase 2: New Type Categories
These are all new types that don't currently exist in gameobj-data.xml. I think that they are all worthwhile additions that make sense for us to merge upstream, but if anyone feels like adding these may cause issues, please let me know.
-
reim- creature and gem category. Plan to add asrealm:reim -
moonshard- Duskruin quest items. Propose folding these into theevent:duskruinandquesttypes instead of creating a separate category just for moonshards. -
duskruin- area category for gems. Adding asevent:duskruin -
pennant chase- Pennant Chase quest items to add asevent:pennant chase -
noncorporeal- creature category -
companion- new NPC category for ranger companions -
familiar- new NPC category for wizard familiars -
phased- new type for phased (704) boxes -
breakable- new type for breakable items
I would like to create the new types through migrations, but that requires us to add a command to the migration DSL for creating new tables.
- Dominant language
- Ruby
- Stars
- 27
- Forks
- 67
- Avg merge
- 12h 8m
- Merged PRs (30d)
- 45
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from elanthia-online/scripts
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elanthia-online/scripts#2296 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
elanthia-online/scripts#2171 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
elanthia-online/scripts#2077 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
elanthia-online/scripts#2015 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
elanthia-online/scripts#2005 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
All issues in elanthia-online/scripts
Similar issues
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
solana-foundation/pay-kit#341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
julienXX/terminal-notifier#333 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
serhii-londar/open-source-mac-os-apps#1419 ·
Maintainers usually reply within 5 days