Are There Any Option Group Limitations?

[UrsaTeddy]

Greetings,

As the title suggests, I am looking for either a link or a statement as to Limitations to Option Groups in the Settings.

I have a weird behaviour that has been occurring and cannot track it down therefore I am just checking that I am not "breaking" any limitation before I ask for help.

[Moon Wizard]

I'm not sure what you are asking. There's no implicit limitation to option group names; it just controls how the options are displayed in the Options window.

Regards,
JPG

[UrsaTeddy]

I know this probably sounds stupid or facetious, however I am trying to remove any possibilities that can cause problems ...


Regarding the actual text, for example, can I use Emojis? Hidden characters? Punctuation? All alphanumerics? SQL commands? XML as data?

Regarding the controls in the actual options, can I create anything I want - as long as it follows standard <windowclass> formats?

In addition, is there anyway to have a group within a group?

[Moon Wizard]

You are typically specifying the group header text as a string asset resource. Any option with the same header text will be grouped together.

As for actual text, it has only been tested with punctuation and alphanumerics. Anything else may or may not work; and any character used must be available in the font used for the header. (default is Noto Sans Bold)

For options, everything uses the option_entry_cycler windowclass in the CoreRPG ruleset and most other rulesets. While you can specify alternative option window classes, it hasn't been tested in a very long time. Also, I would really consider whether it needs to be anything other than a cycler, before using something else. If it's more than a simple string or number, I would even say it should be elsewhere (like languages, currencies, etc.)

There is no nesting of groups.

Regards,
JPG

[UrsaTeddy]

Great!

That answers the question and the "bug" I was experiencing.

I have developed an extension that uses textboxes in the Options group whereby a GM can turn a setting on/off and the text that was entered is used as a character statistical value.

As far as I have tested, this works, so definitely textbox is a valid object in the Options windows.