User:EAi/Server Console Commands: 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:
This is a list of current server console commands, in order to find which could be scripted.
This is a list of current server console commands, in order to find which could be scripted.


* say
Comments Added by [[User:Vandalite|Vandalite]]
Nearly Every command can be exported to a lua command, and accessed through a main command resource, with security considerations coded. only core resources will be noted as needed console commands.
 
* say -- This is a CORE console command. needed if lua breaks down, for debugging.
* teamsay
* teamsay
* asay
* asay -- What's this?
* msg
* msg
* amsg
* amsg -- What's this?
* me
* me -- What's this? -- i know what it is in IRC, does it work here?
* slap
* slap -- What's this? -- i know what it is in IRC, does it work here?
* nick
* nick
* vote
* vote
Line 19: Line 22:
* chgpass
* chgpass
* chglevel
* chglevel
* startmap
* startmap -- Deprecated. loadresource will make this redundant.
* restartmap
* restartmap -- Deprecated. loadresouce will make this redundant.
* mute
* mute
* unmute
* unmute
Line 28: Line 31:
* unbanip
* unbanip
* shutdown
* shutdown
* aexec
* aexec -- What's this?
* whois
* whois -- What's this? -- i know what it is in IRC, does it work here?
* whowas
* whowas -- What's this? -- i know what it is in IRC, does it work here?
* loadscript
* loadscript
** legacy. consider changing to loadresource -- This is a CORE console command. needed if lua breaks down, for debugging.
* unloadscript
* unloadscript
** legacy. consider changing to unloadresource -- This is a CORE console command. needed if lua breaks down, for debugging.
* scripts
* scripts
* debugscript
* debugscript -- This is a CORE console command. needed if lua breaks down, for debugging.
 
For all dunctions i reccomended putting in the security resource. this is only useful if you have a way of setting functions (from mta server conf) to a security level. This allows ONLY the security resource to run these commands (since it's lua), and will only do so if the user has logged in, and communicates with the resource (with console command handlers). This allows easy modifications to the security systems, without needing to reboot the server. Besides, as you said, the more control you have from lua, the better.
 
It should also be noted that various automated things that MTA does now, using map configurations, like respawn, and weapon drops should be exported to resource modules. bring the MTA automated systems completely down, and let lua do it, with simple commands like spawnplayer and spawnweapon. This gives ultimate control over what goes in the map files (or i should say, resource config files). It'll come in handy for gamemodes that need special respawn controls. (i'm thinking gang wars).
 
A lot of this you already know, but i put it down cause you're not the only one who might read this.

Latest revision as of 21:02, 2 January 2007

This is a list of current server console commands, in order to find which could be scripted.

Comments Added by Vandalite Nearly Every command can be exported to a lua command, and accessed through a main command resource, with security considerations coded. only core resources will be noted as needed console commands.

  • say -- This is a CORE console command. needed if lua breaks down, for debugging.
  • teamsay
  • asay -- What's this?
  • msg
  • amsg -- What's this?
  • me -- What's this? -- i know what it is in IRC, does it work here?
  • slap -- What's this? -- i know what it is in IRC, does it work here?
  • nick
  • vote
  • maps
  • login
  • logout
  • setlevel
  • chgmypass
  • addaccount
  • delaccount
  • chgpass
  • chglevel
  • startmap -- Deprecated. loadresource will make this redundant.
  • restartmap -- Deprecated. loadresouce will make this redundant.
  • mute
  • unmute
  • kick
  • ban
  • banip
  • unbanip
  • shutdown
  • aexec -- What's this?
  • whois -- What's this? -- i know what it is in IRC, does it work here?
  • whowas -- What's this? -- i know what it is in IRC, does it work here?
  • loadscript
    • legacy. consider changing to loadresource -- This is a CORE console command. needed if lua breaks down, for debugging.
  • unloadscript
    • legacy. consider changing to unloadresource -- This is a CORE console command. needed if lua breaks down, for debugging.
  • scripts
  • debugscript -- This is a CORE console command. needed if lua breaks down, for debugging.

For all dunctions i reccomended putting in the security resource. this is only useful if you have a way of setting functions (from mta server conf) to a security level. This allows ONLY the security resource to run these commands (since it's lua), and will only do so if the user has logged in, and communicates with the resource (with console command handlers). This allows easy modifications to the security systems, without needing to reboot the server. Besides, as you said, the more control you have from lua, the better.

It should also be noted that various automated things that MTA does now, using map configurations, like respawn, and weapon drops should be exported to resource modules. bring the MTA automated systems completely down, and let lua do it, with simple commands like spawnplayer and spawnweapon. This gives ultimate control over what goes in the map files (or i should say, resource config files). It'll come in handy for gamemodes that need special respawn controls. (i'm thinking gang wars).

A lot of this you already know, but i put it down cause you're not the only one who might read this.