Latest Additions - Revision history

Phil at 17:42, 1 April 2026

2026-04-01T17:42:35Z

← Older revision		Revision as of 17:42, 1 April 2026
Line 1:		Line 1:
			= (Tile) Auto LOD =
			There is new documentation on the auto LOD feature in the tile version
			[[Tile Turn Based Version]]

	= ELSEIFDEF and ELSEIFNDEF =		= ELSEIFDEF and ELSEIFNDEF =
	Added the ability to stack #IFDEF queries. E.g.		Added the ability to stack #IFDEF queries. E.g.

2026-04-01T17:37:26Z

← Older revision		Revision as of 17:37, 1 April 2026
Line 1:		Line 1:
			= ELSEIFDEF and ELSEIFNDEF =
			Added the ability to stack #IFDEF queries. E.g.
			#IFDEF SOMETHING
			...
			#ELSEIFDEF SOMETHING_ELSE
			...
			#ELSEIFNDEF SOMETHING_NOT
			...
			#ELSE
			...
			#ENDIF
			There is no limit to how many checks you can stack.

	= Added DRAGGABLEBY tag =		= Added DRAGGABLEBY tag =
	You can now drag objects using both the left and right mouse button, or both.		You can now drag objects using both the left and right mouse button, or both.

2026-02-23T22:35:26Z

← Older revision		Revision as of 22:35, 23 February 2026
Line 1:		Line 1:
			= Added DRAGGABLEBY tag =
			You can now drag objects using both the left and right mouse button, or both.
			DRAGGABLEBY <unsigned>
			Where the value can be 1 (LMB only), 2 (RMB only), or 3 (both).

	= New functionality for 3DObject =		= New functionality for 3DObject =
	See UI docs here: [[UI#3DOBJECT\|3DObject]]		See UI docs here: [[UI#3DOBJECT\|3DObject]]

2026-02-23T22:33:52Z

new tabstop tag for string rendering

← Older revision		Revision as of 22:33, 23 February 2026
Line 2:		Line 2:
	See UI docs here: [[UI#3DOBJECT\|3DObject]]		See UI docs here: [[UI#3DOBJECT\|3DObject]]

	= ~~new~~ tabstop tag for string rendering =		= New tabstop tag for string rendering =
	See here [[UI#Strings\|Strings]]		See here [[UI#Strings\|Strings]]

2025-11-27T21:03:55Z

← Older revision		Revision as of 21:03, 27 November 2025
Line 1:		Line 1:
			= New functionality for 3DObject =
			See UI docs here: [[UI#3DOBJECT\|3DObject]]

	= new tabstop tag for string rendering =		= new tabstop tag for string rendering =
	See here [[UI#Strings\|Strings]]		See here [[UI#Strings\|Strings]]

2025-05-29T20:03:46Z

← Older revision		Revision as of 20:03, 29 May 2025
Line 1:		Line 1:
			= new tabstop tag for string rendering =
			See here [[UI#Strings\|Strings]]

	= Custom Keyboard Bindings =		= Custom Keyboard Bindings =
	You enter them in the file CORE/CustomKeys.txt. Each entry has the form		You enter them in the file CORE/CustomKeys.txt. Each entry has the form

2025-05-26T20:53:28Z

← Older revision		Revision as of 20:53, 26 May 2025
Line 1:		Line 1:
			= Custom Keyboard Bindings =
			You enter them in the file CORE/CustomKeys.txt. Each entry has the form
			<tag> <key>
			e.g.
			KK_NEXT_UNSHOT B
			KK_SOMETHING_ELSE CTRL+Y

			Note that the ordering of the modifier keys is different to when used directly on hotkeys (as per the UI docs), apologies for that.

			You then use these tags in the UI files for hotkeys, e.g.:
			…
			HOTKEY KK_NEXT_UNSHOT

			They will appear in the key list and can be rebound etc.

			They use the standard string IDs, e.g.
			IDS_KEYDESC_KK_NEXT_UNSHOT,"Next Unshot",
			You can use the same tag as a hotkey for multiple UI objects (e.g. if you want a redefinable key for closing dialogs etc).

			If there is an object OptionsKeyShowConflict then it will have the string IDS_KEYS_CONFLICTED applied to it if there are key definition conflicts.

			If a button called OptionsKeyDefaultButton exists, it will reset the keys to their default

	= SFUNCTION script addition =		= SFUNCTION script addition =
	You can now define a function using an SFUNCTION tag to allow you to return a string from it. An example:		You can now define a function using an SFUNCTION tag to allow you to return a string from it. An example:

2025-03-14T20:49:38Z

← Older revision		Revision as of 20:49, 14 March 2025
Line 1:		Line 1:
			= SFUNCTION script addition =
			You can now define a function using an SFUNCTION tag to allow you to return a string from it. An example:
			char gCharArray[64] ;
			SFUNCTION StringFn()
			{
			return gCharArray ;
			}
			SFUNCTIONs can also be used as normal functions (i.e. ignoring their return values) so you could, for example, have a function that both sets a global string and also returns it, allowing dual use.

	= Tile: Building Damage =		= Tile: Building Damage =
	There are now two ways to show building damage.		There are now two ways to show building damage.

2025-03-10T16:10:19Z

← Older revision		Revision as of 16:10, 10 March 2025
Line 1:		Line 1:
			= Tile: Building Damage =
			There are now two ways to show building damage.

			1 - you can do a texture swap by including a _D version of the building texture (that is, have both a MyTexture.dds and a MyTexture_D.dds).

			2 - you can use a different model entirely. This model needs to be named _DAM (so you would have MyModel.s4f and MyModel_DAM.s4f)

			You should not use both, as the _D texture is always loaded if it exists, which will waste memory.

	= MaxDebug tweak changes =		= MaxDebug tweak changes =
	This is now a bitfield		This is now a bitfield

2025-02-07T17:35:43Z

← Older revision		Revision as of 17:35, 7 February 2025
Line 1:		Line 1:
			= MaxDebug tweak changes =
			This is now a bitfield
			1=extra output spew, 2=throw string error popup @ end of loading calls, 4=throw every string error
			Note that the above is the value, not the bit index. 1 keeps the initial behavior. More bits may be added in future.

	= Progress Bar Textures =		= Progress Bar Textures =
	You can now flag progress bar textures as being 'full sized' - such that they are shown across the full length of the progress bar 'as is' rather than being drawn as a window texture.		You can now flag progress bar textures as being 'full sized' - such that they are shown across the full length of the progress bar 'as is' rather than being drawn as a window texture.