Talk:Proposal: Scripted Controls: Difference between revisions

From Multi Theft Auto: Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
The problem with this is that the user could end up with thousands of custom controls over time. - [[User:JonChappell|JonChappell]]
The problem with this is that the user could end up with thousands of custom controls over time. - [[User:JonChappell|JonChappell]]
** Remember that Scripted Controls only appear in the menu when requested by the script.  So you wont have tonnes of useless binds appearing in the "Scripted Controls" section.  You will have lots of .conf files left over i guess - but they arent going to be big file size wise (5kb tops) and can easilly be removed.  Presumably you arent going to have 1000s of different gamemodes either (all of which use scripted controls), so there shouldnt be that many config files anyway.
* Remember that Scripted Controls only appear in the menu when requested by the script.  So you wont have tonnes of useless binds appearing in the "Scripted Controls" section.  You will have lots of .conf files left over i guess - but they arent going to be big file size wise (5kb tops) and can easilly be removed.  Presumably you arent going to have 1000s of different gamemodes either (all of which use scripted controls), so there shouldnt be that many config files anyway. --[[User:Talidan2|Talidan2]] 16:31, 21 December 2006 (CST)
 
 
 
Can i reiterate that this has become essential.  When i first made this suggestion it was not. Back then the scoreboard was hardcoded, and drivebys were supposed to be.  Now that cant be said for either, and the same goes for the previously hardcoded spectator mode.  If so many essentials to be done by resources, scripted controls are very necessary.  This will be needed by many scripts, and will be useful for the map editor.

Latest revision as of 17:31, 23 April 2007

The problem with this is that the user could end up with thousands of custom controls over time. - JonChappell

  • Remember that Scripted Controls only appear in the menu when requested by the script. So you wont have tonnes of useless binds appearing in the "Scripted Controls" section. You will have lots of .conf files left over i guess - but they arent going to be big file size wise (5kb tops) and can easilly be removed. Presumably you arent going to have 1000s of different gamemodes either (all of which use scripted controls), so there shouldnt be that many config files anyway. --Talidan2 16:31, 21 December 2006 (CST)


Can i reiterate that this has become essential. When i first made this suggestion it was not. Back then the scoreboard was hardcoded, and drivebys were supposed to be. Now that cant be said for either, and the same goes for the previously hardcoded spectator mode. If so many essentials to be done by resources, scripted controls are very necessary. This will be needed by many scripts, and will be useful for the map editor.