E32 Profiles - Revision history

Hendricks266: /* profile features */

2013-11-28T16:08:37Z

profile features

← Older revision		Revision as of 09:08, 28 November 2013
Line 85:		Line 85:
	*"<u>commands</u>" { }: contains list of files/data to load		*"<u>commands</u>" { }: contains list of files/data to load
	**"<u>basedir</u>" (-game_dir)		**"<u>basedir</u>" (-game_dir)
			***Note: This changes the "Custom game content directory" in the startup window. Perhaps it should be a user setting, off-limits to mods.
	**"<u>dir</u>" (-j)		**"<u>dir</u>" (-j)
	**"<u>grp</u>"/"<u>zip</u>"/"<u>pk3</u>"/"<u>pk4</u>" (-g)		**"<u>grp</u>"/"<u>zip</u>"/"<u>pk3</u>"/"<u>pk4</u>" (-g)

Hendricks266: /* syntax */

2013-11-28T15:39:51Z

syntax

← Older revision		Revision as of 08:39, 28 November 2013
Line 57:		Line 57:
	*********duke3d registered v1.3D South Korea		*********duke3d registered v1.3D South Korea
	********duke3d registered v1.4/v1.5		********duke3d registered v1.4/v1.5
			*********duke3d_atomic_dukedc
			*********duke3d_atomic_nwinter
			*********duke3d_atomic_vacation
	******nam-based		******nam-based
	*******nam-family		*******nam-family

Hendricks266 at 11:23, 28 November 2013

2013-11-28T11:23:37Z

← Older revision		Revision as of 04:23, 28 November 2013
Line 7:		Line 7:
	==Overview==		==Overview==

	Each profile contains in essence tokens similar in function to the available command-line parameters. Profiles can be mixed and matched by modifying the cfg file once parsed, by passing command-line arguments, or in a GUI interface.		A profile is a unit describing a modification of some sort. Each profile contains in essence tokens similar in function to the available command-line parameters. Profiles can be mixed and matched by modifying the cfg file once parsed, by passing command-line arguments, or in a GUI interface.

	Words formatted like "<u>this</u>" refer to the actual commands used in profiles.		Words formatted like "<u>this</u>" refer to the actual commands used in profiles.

Hendricks266 at 11:23, 28 November 2013

2013-11-28T11:23:03Z

← Older revision		Revision as of 04:23, 28 November 2013
Line 4:		Line 4:

	To the editors: Feel free to add content or notes, but please do not delete anything. (MediaWiki does contain a revision history, in any case.)		To the editors: Feel free to add content or notes, but please do not delete anything. (MediaWiki does contain a revision history, in any case.)

			==Overview==

	Each profile contains in essence tokens similar in function to the available command-line parameters. Profiles can be mixed and matched by modifying the cfg file once parsed, by passing command-line arguments, or in a GUI interface.		Each profile contains in essence tokens similar in function to the available command-line parameters. Profiles can be mixed and matched by modifying the cfg file once parsed, by passing command-line arguments, or in a GUI interface.

Hendricks266 at 11:22, 28 November 2013

2013-11-28T11:22:15Z

← Older revision		Revision as of 04:22, 28 November 2013
Line 31:		Line 31:

	=== syntax ===		=== syntax ===
	*"<u>name</u>" { }: two names, "<u>reference</u>" <~~name~~> ~~and~~ "<u>proper</u>" <~~display name~~>		*"<u>name</u>" { }: two names
			**"<u>reference</u>" <technical_name>
			**"<u>proper</u>" <Display Name>
	*"<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)
Line 79:		Line 81:
	**"<u>basedir</u>" (-game_dir)		**"<u>basedir</u>" (-game_dir)
	**"<u>dir</u>" (-j)		**"<u>dir</u>" (-j)
	**"<u>fs</u>" ~~(-g) (short for~~ "~~filesystem~~"~~; add grp~~/~~zip~~/~~pk3~~/pk4)		**"<u>grp</u>"/"<u>zip</u>"/"<u>pk3</u>"/"<u>pk4</u>" (-g)
	**"<u>con</u>" (-x)		**"<u>con</u>" (-x)
	**"<u>def</u>" (-h)		**"<u>def</u>" (-h)
Line 122:		Line 124:
	commands		commands
	{		{
	~~conmodule~~ "~~conmodule~~.con"		con_module "con_module.con"
	~~defmodule~~ "~~defmodule~~.def"		def_module "def_module.def"
	}		}

Line 182:		Line 184:
	commands		commands
	{		{
	~~conmodule~~ "mymod_specialeffects.con"		con_module "mymod_specialeffects.con"
	~~defmodule~~ "mymod_new8bitart.def"		def_module "mymod_new8bitart.def"
	}		}
	profile		profile
Line 195:		Line 197:
	commands		commands
	{		{
	~~defmodule~~ "mymod_hrp.def"		def_module "mymod_hrp.def"
	}		}
	tie "duke3d_hrp"		tie "duke3d_hrp"
Line 217:		Line 219:
	dir "vaca_plus"		dir "vaca_plus"
	grp "vacation.grp"		grp "vacation.grp"
	~~conmodule~~ "Vacation.con"		con_module "Vacation.con"
	~~defmodule~~ "Vacation.def"		def_module "Vacation.def"
	}		}

Line 230:		Line 232:
	commands		commands
	{		{
	~~conmodule~~ "VacaDP.con"		con_module "VacaDP.con"
	~~defmodule~~ "VacaDP.def"		def_module "VacaDP.def"
	}		}
	tie "dukeplus"		tie "dukeplus"
Line 245:		Line 247:
	commands		commands
	{		{
	~~conmodule~~ "VacaXXX.con"		con_module "VacaXXX.con"
	~~defmodule~~ "VacaXXX.def"		def_module "VacaXXX.def"
	}		}
	depend "xxx_pack"		depend "xxx_pack"
Line 260:		Line 262:
	commands		commands
	{		{
	~~defmodule~~ "vacation_hrp.def"		def_module "vacation_hrp.def"
	}		}

Line 275:		Line 277:
	commands		commands
	{		{
	~~defmodule~~ "vacation_hrp_xxx.def"		def_module "vacation_hrp_xxx.def"
	}		}
	depend "vaca_plus_xxx"		depend "vaca_plus_xxx"

Hendricks266 at 11:18, 28 November 2013

2013-11-28T11:18:45Z

Show changes

Hendricks266 at 10:54, 28 November 2013

2013-11-28T10:54:36Z

@@ Line 20: / Line 20: @@
 *"<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>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>:
 *"<u>commands</u>" { }: contains list of files/data to load
 **"<u>con</u>" (-x)
@@ Line 48: / Line 88: @@
 *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
-*"<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>:
 ==implementation strategy==
@@ Line 229: / Line 272: @@
 ==GUI mockup==
 [[File:E32_profiles_mockup.png]]
 [[Category:Developer's corner]]

Hendricks266: /* sub-profile-specific features */

2012-07-08T22:50:56Z

sub-profile-specific features

← Older revision		Revision as of 15:50, 8 July 2012
Line 46:		Line 46:
	==sub-profile-specific features==		==sub-profile-specific features==
	*displayed indented from the left immediately beneath parent		*displayed indented from the left immediately beneath parent
	*sub-profile "<u>depend</u>" on the parent		*sub-profile automatically "<u>depend</u>" on the parent
	*by default 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)

Hendricks266 at 22:09, 8 July 2012

2012-07-08T22:09:36Z

← Older revision		Revision as of 15:09, 8 July 2012
Line 22:		Line 22:
	*"<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>: (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>commands</u>" { }: contains list of files/data to load		*"<u>commands</u>" { }: contains list of files/data to load
	**con (-x)		**"<u>con</u>" (-x)
	**def (-h)		**"<u>def</u>" (-h)
	**conmodule (-mx)		**"<u>conmodule</u>" (-mx)
	**defmodule (-mh)		**"<u>defmodule</u>" (-mh)
	**grp/zip/pk3 (-g)		**"<u>grp</u>"/"<u>zip</u>"/"<u>pk3</u>" (-g)
	**basedir (-game_dir)		**"<u>basedir</u>" (-game_dir)
	**dir (-j)		**"<u>dir</u>" (-j)
	**rts (-rts)		**"<u>rts</u>" (-rts)
	**map (-map)		**"<u>map</u>" (-map)
	**clipmap (-clipmap)		**"<u>clipmap</u>" (-clipmap)
	**demo (-d)		**"<u>demo</u>" (-d)
	*if a profile is ever force-disabled due to a conflict, its previous on/off status is never lost		*if a profile is ever force-disabled due to a conflict, its previous on/off status is never lost
	*reference name, .e32 file name as passed to the game (absolute and relative accepted), and on/off parsed to .cfg in load order		*reference name, .e32 file name as passed to the game (absolute and relative accepted), and on/off parsed to .cfg in load order

Hendricks266 at 22:08, 8 July 2012

2012-07-08T22:08:41Z

← Older revision		Revision as of 15:08, 8 July 2012
Line 6:		Line 6:

	Each profile contains in essence tokens similar in function to the available command-line parameters. Profiles can be mixed and matched by modifying the cfg file once parsed, by passing command-line arguments, or in a GUI interface.		Each profile contains in essence tokens similar in function to the available command-line parameters. Profiles can be mixed and matched by modifying the cfg file once parsed, by passing command-line arguments, or in a GUI interface.

			Words formatted like "<u>this</u>" refer to the actual commands used in profiles.

	==profile features==		==profile features==