The code will detect the string's contents, not the identifier. Either modify the strings referenced by the map info decls such that the maps have the same name consistently across localizations, or add individual translations to the ActionScript code. If you neglect this step, the code will not be effective for players that run the game in a language other than the one your multiplayer mod was tested with.
**g\_demonSelect** was chosen because it does not have an impact on anything in the game engine, it appears to have only been added to be checked by the logic entity in the demon tutorial, which a player is not likely to enter while a multiplayer mod is installed.
## Optional - code to split the map list into two columns. ``` internal function frame2() : * { this.itemIndex = strReplace(this.name,"item","") * 1; this.wrapIndex = 8; if(this.itemIndex > this.wrapIndex) { if(this.x == 0) { this.x = 900; this.y -= 110 * (this.wrapIndex + 1); } } } ``` ``` internal function frame78() : * { this.itemIndex = strReplace(this.name,"item","") * 1; this.wrapIndex = 8; if(this.itemIndex > this.wrapIndex) { if(this.x == 0) { this.x = 900; this.y -= 110 * (this.wrapIndex + 1); } } } ``` ### Editing the Logic Entity. In the shell entities file, add an idTarget\_Command entity for each map to load using the **loaddevmenuoption** command. You should also add an [idTarget\_Command executing any variables that optimize your mod](https://wiki.eternalmods.com/books/9-multiplayer-modding/page/startup-commands) if you have not done so already. Append **g\_demonSelect 0** to it such that a map loading command does not get executed prematurely when the players exit a map back to the lobby menu. In the logic entity editor, add the following nodes to execute these command entities: - A getConsoleVariable node to retrieve the integer value of **g\_demonSelect** set through the SWF code outlined earlier. - A begin node that connects to an activate entities node to trigger your aforementioned console command entity containing your mod's optimizations. - The logic entity has not been tested without the delay node, but the delay is probably necessary to prevent the game from locking up because the logic entity is intentionally looped indefinetely. It's recommend to set this to around 500 milliseconds or so for optimization while keeping the map selection responsive. The node activating your optimization command entity should trigger this node. - An integer switch function: this is what actually acts upon the demon select cvar. It should be triggered by the delay node. Make sure that the 0 option loops back to the delay node, so that the check can keep running until the player selects an option. - activate entity nodes to connect to each individual case, each listing an idTarget\_Command entity for loading a map. ## Optional - add a "random map" entry. If your mod contains several levels, you can add options for selecting a random map, just for fun. In the logic entity editor's properties dialog, add a variable of the type **Entity/List**, and add all the target command entities. If desired, you can add multiple variables, for example, a separate option that picks only the Battlemode maps. Add your node for each custom variable you added. Connect your custom variable node to a get random entity node, then connect it's entity pin to another activate entity node, which is triggered by the corresponding integer that was added for the random option. ## See also - [SWF modding](https://wiki.eternalmods.com/books/7-miscellaneous/page/swf-modding)