Jump to content

E32 Profiles: Difference between revisions

From EDukeWiki
No edit summary
Line 20: Line 20:
*"<u>version</u>" <float>: for each mod, mutator, etc (possibly version checker/downloader?)
*"<u>version</u>" <float>: for each mod, mutator, etc (possibly version checker/downloader?)
*"<u>autoload</u>" flag: default on (HRP, music pack) vs. default off (mod)
*"<u>autoload</u>" flag: default on (HRP, music pack) vs. default off (mod)
*"<u>game</u>" <string>: (global, duke3d-family, duke3d, nam, ww2gi) (theoretically [duke3d-based, sw, rr, tekwar, whaven-family, whaven, whaven2, corr8]); profiles not matching the current selection of the game tab are simply not shown
*"<u>game</u>" <string>:  
**Some method of describing a set of supported EDuke32 games for which a mutator can run. An incomplete tree follows. In this example any bullet point can be used and all include any descendants. Naming is inexact and for illustration only.
**global
***'''duke3d-based'''
****''duke3d-family''
*****duke3d
******duke3d shareware
*******duke3d shareware v0.99 beta
*******duke3d shareware v1.0
*******duke3d shareware v1.1
*******duke3d shareware v1.3D
******duke3d registered
*******duke3d registered v1.3D
********duke3d registered v1.3D United States
********duke3d registered v1.3D South Korea
*******duke3d registered v1.4/v1.5
*****nam-based
******nam-family
*******nam
*******napalm
******ww2gi
****''redneck-family''
*****rr
*****rrra
*****redneckdeerhuntin
****''paintbrawl''
***'''sw'''
***'''blood'''
***'''tekwar'''
***'''exhumed-worldwide'''
****''PowerSlave''
****''Exhumed''
****''Seireki 1999: Pharaoh no Fukkatsu''
***'''witchaven-family'''
****''witchaven''
****''witchaven2''
***'''corridor8'''
***'''lo7p'''
***'''fate'''
***'''Ken-BUILD (Test Game)'''
**profiles not matching the current selection of the game tab are simply not shown
*"<u>commands</u>" { }: contains list of files/data to load
*"<u>commands</u>" { }: contains list of files/data to load
**"<u>con</u>" (-x)
**"<u>con</u>" (-x)
Line 48: Line 88:
*sub-profile automatically "<u>depend</u>" on the parent
*sub-profile automatically "<u>depend</u>" on the parent
*by default, sub-profiles inherit properties like game and version from parent unless the value is overridden
*by default, sub-profiles inherit properties like game and version from parent unless the value is overridden
*"<u>tie</u>" <profile>: sub-profile is ALWAYS enabled if both its parent and the specified profile are enabled, otherwise never; has the capability to allow more than one "<u>base</u>" flagged profile to run (the profile with the tie command is loaded after the specified profile)
*"<u>tie</u>" <profile>:
**sub-profile is ALWAYS enabled if both its parent and the specified profile are enabled, otherwise never
**has the capability to allow more than one "<u>base</u>" flagged profile to run (the profile with the tie command is loaded after the specified profile)
**the idea is to reconcile compatibility between mutators that may need it


==implementation strategy==
==implementation strategy==
Line 229: Line 272:


==GUI mockup==
==GUI mockup==
This image is outdated in the following ways:
*Ideally, the Duke Plus Extension and "HRP XXX" would be hidden and transparent to the user because they would be <u>tie</u>d to the mutator for which they are a compatibility layer anyway.


[[File:E32_profiles_mockup.png]]
[[File:E32_profiles_mockup.png]]


[[Category:Developer's corner]]
[[Category:Developer's corner]]

Revision as of 02:54, 28 November 2013