Difference between revisions of "LegacyKing and MertonMonk discuss specs for replacement app"

From PCGen Wiki
Jump to: navigation, search
(Re-use the code that shows promise:)
Line 18: Line 18:
  
 
Formula (Replacement for JEP)
 
Formula (Replacement for JEP)
 +
 +
Full Write up here - [http://pcgen.org/w/index.php/Setting_up_the_new_Formula_System Setting up the Formula System]
  
 
* MODIFY/MODIFYOTHER - Handles all variables
 
* MODIFY/MODIFYOTHER - Handles all variables
* - DYNAMIC  
+
* - [http://pcgen.org/w/index.php/Dynamic_Scopes DYNAMIC Scopes]
* - TABLES
+
* - [http://pcgen.org/w/index.php/Lookup_Table LOOKUP TABLES]
* SELECTION (replace the CHOICE/CHOOSER)
+
* - [http://pcgen.org/w/index.php/INFO/INFOVARS INFO/INFOVARS]
 
 
  
 +
Not Coded:
 +
* [http://pcgen.org/w/index.php/SELECTION_-_A_CHOOSE_Replacement SELECTION] (replace the CHOICE/CHOOSER)
  
 
== What are we solving for - aka Requirements ==
 
== What are we solving for - aka Requirements ==

Revision as of 06:28, 29 October 2025

This page is to lay the groundwork for taking the best of existing PCGen and being unhindered with backwards compatible constraints to build a PCGen "Remastered".


Design Philosophy: Data driven, code engine system agnostic

UI/UX - Every "blade" should be fully customizable and language friendly (Support for any language) - We should be able to define these by 'system'

PCGen built sets based on books, which is a nice structure to understand what is included. But the method of selecting compatible books was painful. A checkbox and tree view would be ideal. Also the idea of optional rules being selected here would make sense. (DISCUSSION TOPIC)

Legal - Systems Licenses should be displayed or available to view, and each content source should clearly delineate it's license.

Code will utilize a simplistic design to replicate to all objects.



Re-use the code that shows promise:

Formula (Replacement for JEP)

Full Write up here - Setting up the Formula System

Not Coded:

What are we solving for - aka Requirements

In most d20 systems a character must prequalify before taking something (feats, powers); conversely, during some situations, the qualifications may be lost causing the loss of an ability (required)

Examples:

  • If a feat required Dex 13, and the character's dexterity is below 13 they lose access to the benefits of the feat.
  • A spellcaster requires a minimum spellcasting score to cast any given level.

PRE/REQ

PRE: What it takes to take the object REQ: What it takes to use the object


Spells/Power - This system while functional, is outdated and requires a major facelift.

Requirements - Ability to group spells together in a hierarchy (Classification, List, Level, or class/level as required by the system)

Examples:

  • 1e spells were grouped by category, schools, class and level
  • 3e spells were grouped by category, class specific level (Also some had special subcategories of casting/ability such as Specialization for wizards, and Domains for clerics)
  • 4e spells were called 'powers' and categorized by tiers and class
  • 5e spells were grouped by category, level

Spells need to be selectable based upon criteria, assignable to specific class or category. And update in real-time (We've had issues where spell assignments never populated until application or character reload)


NICE TO HAVE:

  • - Customizer

SUBPAGES:

PCGen 2e - Token List

Pathfinder 2e - Remastered design