Silent Creating Custom Menu - Revision history

Gaoesa: /* Example */

2015-09-14T18:18:23Z

Example

2015-09-14T18:07:48Z

Example

2015-09-14T18:02:16Z

Example

2015-09-14T14:04:04Z

Customized Voice Chat Menus

← Older revision		Revision as of 14:04, 14 September 2015
Line 3:		Line 3:
	Starting from silEnT 0.9.0, the following files have changed their name:		Starting from silEnT 0.9.0, the following files have changed their name:

	~~wm_quickmessageT~~.menu => wm_quickmessage_silEnT.menu<br>		wm_quickmessage.menu => wm_quickmessage_silEnT.menu<br>
	wm_quickmessageAlt.menu => wm_quickmessageAlt_silEnT.menu<br>		wm_quickmessageAlt.menu => wm_quickmessageAlt_silEnT.menu<br>
	wm_ftquickmessageAlt.menu => wm_ftquickmessageAlt_silEnT.menu<br>		wm_ftquickmessageAlt.menu => wm_ftquickmessageAlt_silEnT.menu<br>

2015-09-13T18:30:08Z

@@ Line 1: / Line 1: @@
 == Customized Server Menus ==
@@ Line 111: / Line 122: @@
 * Menu files in the etmain directory or the official menus can not be modified and the server refuses to start if it detects such modifications.
 * Old way of customizing the menus still work if the user already has the menus or he manually adds the menus. The restriction is that the server can not reference pk3 files that modify the menus.

2015-09-13T12:26:43Z

Properties

← Older revision		Revision as of 12:26, 13 September 2015
Line 110:		Line 110:
	* The onOpen event is ignored in the custom menus.		* The onOpen event is ignored in the custom menus.
	* Menu files in the etmain directory or the official menus can not be modified and the server refuses to start if it detects such modifications.		* Menu files in the etmain directory or the official menus can not be modified and the server refuses to start if it detects such modifications.
			* Old way of customizing the menus still work if the user already has the menus or he manually adds the menus. The restriction is that the server can not reference pk3 files that modify the menus.

2015-09-13T11:59:08Z

Example

@@ Line 61: / Line 61: @@
 	BUTTON( 6, 32, WINDOW_WIDTH-12, 18, "^7Rules", .3, 14, close custom_main ; open rules )
+}
 </pre>
 The resulting files need to be packed into a zip file that is renamed to pk3 so that all the menu files and the "menus_server_custom.txt" are in and under ui directory.

2015-09-13T11:55:22Z

Example

@@ Line 21: / Line 21: @@
 	loadMenu { "ui/rules.menu" }
+}
 </pre>

2015-09-13T11:53:03Z

Properties

← Older revision		Revision as of 11:53, 13 September 2015
Line 27:		Line 27:
	== Properties ==		== Properties ==

	* When user opens ~~themenus~~, both the official menu and the server customized menu are opened. The menus are opened in a way that the official menu is always on top in case the two menus overlap.		* When user opens the menus, both the official menu and the server customized menu are opened. The menus are opened in a way that the official menu is always on top in case the two menus overlap.
	* If user clicks a button in either menu, the other menu is automatically closed by the mod. This also includes the case when user presses ESC to close the menus.		* If user clicks a button in either menu, the other menu is automatically closed by the mod. This also includes the case when user presses ESC to close the menus.
	* The onOpen event is ignored in the custom menus.		* The onOpen event is ignored in the custom menus.
	* Menu files in the etmain directory or the official menus can not be modified and the server refuses to start if it detects such modifications.		* Menu files in the etmain directory or the official menus can not be modified and the server refuses to start if it detects such modifications.

2015-09-13T11:52:00Z

Example

← Older revision		Revision as of 11:52, 13 September 2015
Line 13:		Line 13:
	== Example ==		== Example ==

	Customized server menu has one requirement, there must be a file called menus_server_custom.txt. This file is used exactly like the old menus.txt. It defines the .menu files that are ~~laded~~ for the custom menu. An example:		Customized server menu has one requirement, there must be a file called menus_server_custom.txt. This file is used exactly like the old menus.txt. It defines the .menu files that are loaded for the custom menu. An example:
	<pre>		<pre>
	// menu defs		// menu defs