Talk:LegacyKing and MertonMonk discuss specs for replacement app

mertonmonk — 5:21 PM My thoughts in partially random order: The 'rules' and 'basic formulas' associated with a game-type can be contained in a default character that is associated with that game-type. This way you can associate the default ability scores and other base elements, including formulas for determining ac, hp, etc, to a default character. The PC's character has a reference to this default character, so the PC character really only contains character selections. For example, a dwarf cleric of level 1 would have a character object that contains links to the default pc, the dwarf object, cleric object, cleric-level-1 object, total-class-level 1 object, and links to whatever objects the character selected for being a dwarf and a level 1 cleric. I like your idea about uids.

The data files for a particular source could be split into multiple files (say, all the feats in one file, classes in another, etc.) or they could all be in one file. Since the object structure for all objects will be the same, having them all in one easily-shared file is a possibility. Having it in multiple files makes it easier for people to split up the work for crafting the data.

mertonmonk — 5:36 PM Internally the code should contain all the data about a character in a map and stacking rules can be defined/applied to the map nodes. All values should be in the format main.sub1...subx..bonustype. For example, combat.ac.armor, would be a valid bonus key. Each value would also contain a link to the source of where it came from so debugging a value is easier. We will need to discuss the syntax of formulas. There are free libraries that can be used to evaluate a math equation once all tokens have been replaced with numerics.

LegacyKing — 6:37 PM Having multiple files allows for easier debugging - and easier organization. Some files are already thousands of lines long I don't imagine it'd be fun to try and find x.

I'm up for the discussion, let me know. The beauty of what Tom Parker built is it supports non-numerical formats. Replacing a string with another string, changing alignment (reversing alignment or gender due to a cursed item is possible).

--[[User:Nylanfs|Paul Grosse]] (talk) 11:33, 30 October 2025 (UTC) Note: We are also no longer really tied to the data files being plain text. The reasoning that ONLY human readable files could qualify as OGC has largely been abandoned along with the original "Gentleman's Agreement" from the original OGL list server discussion.