Ruleset Validator for VSCode v0.9.11

[Nord]

Looks like "refNode" still not supported.

[Buscher]

No clue if this is the right spot. I would like to report a few false positives shown by the OpenXcom Ruleset Tools. Some of these are related to how mod: - index: are handled as well as a list being allowed for customArmorPreviewIndex.

Code: [Select]

items:
  - type: STR_SOME_ITEM
    vaporColorSurface: {mod: 40k, index: 2} # Warning: Expected Integer # Works fine in Extended 7.5.8

armors:
  - type: STR_SOME_ARMOR
    moveSound: {mod: 40k, index: 700} # Warning: Expected Integer # Works fine in Extended 7.5.8
    customArmorPreviewIndex: [{mod: 40k, index: 560}, {mod: 40k, index: 561}, {mod: 40k, index: 562}] # Warning: Expected Integer # Works fine in Extended 7.5.8
    layersDefaultPrefix: 20 # Warning: Expected string # The value 20 is not nice but works in Extended 7.5.8

Also if one changes the accuracyMultiplier as a script and it's not part of scripts: and doesn't use the normal syntax, f. ex.

Code: [Select]

items:
# No Warning here
  - type: STR_SOME_ITEM
    accuracyMultiplier:
      firing: 1

accuracyMultiplier: | probably needs extra handling.

Code: [Select]

items:
# Warning: Use syntax from the code field above
  - type: STR_SOMETHING
    accuracyMultiplier: | # Works fine in Extended 7.5.8
      return bonus;


[Meridian]

Yes, this is the right spot.

Thanks for the report.
I'll fix it before the next release.

[The Offensive Lemon]

It appears moveCost for armors isn't supported.

[Meridian]

It appears moveCost for armors isn't supported.

Of course.
moveCost is not an officially released feature yet.

[The Offensive Lemon]

Of course.
moveCost is not an officially released feature yet.

Oh.  I was not aware of that.