minimod: Elerium and Alloys Listed on Top

[ivandogovich]

From what I can see, your sub sections may be causing the problem.   You Probably should comment out those lines.

Yaml uses 2 spaces to indicate levels in its hierarchy, so those one space levels maybe throwing it off.

Code: [Select]

items:
# ufo components:
  - type: STR_ALIEN_ALLOYS
    listOrder: 1
etc

[SIMON BAILIE]

Tried moving the sections to 2 spaces and all individual items to 4 spaces but it comes up with an error message "invalid node"? Like I can work with the earlier big long list one but I thought it wud be handy to have sections to find items.

[ivandogovich]

Unfortunately, that is not how the "items" sections of rulesets are formatted. 

You can break this into separate rulesets for each group if that is easier, or you can use the hash tag to comment it out.

[SIMON BAILIE]

Like this?

[SIMON BAILIE]

Seems to work now with the # put in front of the sections, I'm no programmer or have qualifications in that respect but I'll have a read thru these 2 websites on yaml to see if I can get a grasp on basic stuff for future reference.
 https://llvm.org/docs/YamlIO.html
https://www.yaml.org/spec/1.2/spec.html#Introduction
Once again thanks for all ur help.

[Arthanor]

You can't do "sections" by just writing stuff in the file. Then the game comes to the line that says "ufo components" and it doesn't know what that means so it stops reading and gives an error.

Anytime you write something in the file that is not in OpenXCom-yaml ruleset syntax, you will get errors. In this case, since it is just for your ease of reading the ruleset and does nothing rules-wise, this is what we call a comment. You need to precede comments with the appropriate marker, in this case a #, and then the game will know that it's not supposed to read that. Something like:

Code: [Select]

items:
# ufo components:
  - type: STR_ALIEN_ALLOYS
    listOrder: 1
  - type: STR_ELERIUM_115
    listOrder: 2
# craft weapons:


[Markus Ramikin]

Added the metadata.yml necessary for OpenXCom Extended. Updated the attached file in the original post, as well as uploaded to openxcom.mod.io.

After rereading this thread I wish I'd done this from the start, if people were going to have this much trouble integrating this little thing. Oh, well.