User:EAi/Server Console Commands - Revision history

Vandalite at 21:02, 2 January 2007

2007-01-02T21:02:22Z

← Older revision		Revision as of 21:02, 2 January 2007
Line 2:		Line 2:

	Comments Added by [[User:Vandalite\|Vandalite]]		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		* say -- This is a CORE console command. needed if lua breaks down, for debugging.
	* teamsay		* teamsay
	** Exportable using msg -- ~~may not be a bad idea to keep this one though, and have a wrapper instead for team assignment.~~		* asay -- What's this?
	* asay
	** What's this~~? is it needed~~?
	* msg		* msg
	* amsg		* amsg -- What's this?
	** What's this~~? is it needed~~?		* me -- What's this? -- i know what it is in IRC, does it work here?
	* me		* slap -- What's this? -- i know what it is in IRC, does it work here?
	** What's this? is it ~~needed~~?
	* slap
	** What's this? is it ~~needed~~?
	* nick		* nick
	* vote		* vote
	** Exportable using mapvote resource
	* maps		* maps
	** Exportable using mapvote resource
	* login		* login
	** Should have a lua wrapper with security resource
	* logout		* logout
	** Should have a lua wrapper with security resource
	* setlevel		* setlevel
	** Should have a lua wrapper with security resource
	* chgmypass		* chgmypass
	** Should have a lua wrapper with security resource
	* addaccount		* addaccount
	** Should have a lua wrapper with security resource
	* delaccount		* delaccount
	** Should have a lua wrapper with security resource
	* chgpass		* chgpass
	** Should have a lua wrapper with security resource
	* chglevel		* chglevel
	** Should have a lua wrapper with security resource		* startmap -- Deprecated. loadresource will make this redundant.
	* startmap		* restartmap -- Deprecated. loadresouce will make this redundant.
	** Should have a lua wrapper with mapvote resource
	* restartmap
	** Exportable using mapvote resource
	* mute		* mute
	** Exportable using communications resource (and onPlayerChat interruptions)
	* unmute		* unmute
	** Exportable using communications resource (and onPlayerChat interruptions)
	* kick		* kick
	** Should have a lua wrapper with security resource
	* ban		* ban
	** Should have a lua wrapper with security resource
	* banip		* banip
	** Should have a lua wrapper with security resource
	* unbanip		* unbanip
	** Should have a lua wrapper with security resource
	* shutdown		* shutdown
	* aexec		* aexec -- What's this?
	** What's this~~? is it needed~~?		* whois -- What's this? -- i know what it is in IRC, does it work here?
	* whois		* whowas -- What's this? -- i know what it is in IRC, does it work here?
	** What's this? is it ~~needed~~?
	* whowas
	** What's this? is it ~~needed~~?
	* loadscript		* loadscript
	** legacy. consider changing to loadresource		** 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		** legacy. consider changing to unloadresource -- This is a CORE console command. needed if lua breaks down, for debugging.
	* scripts		* scripts
	** What's this? is it needed?		* debugscript -- This is a CORE console command. needed if lua breaks down, for debugging.
	* debugscript

	For all ~~commands~~ i reccomended putting in the security resource, this is only useful if you have a way of setting ~~commands~~ (from mta server conf) to a security level ~~higher than ANY user, and an architecture is in place to allow resources themselves to have security levels~~. ~~this~~ allows ONLY the security resource to run these commands, 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.		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).		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.		A lot of this you already know, but i put it down cause you're not the only one who might read this.

Vandalite at 20:13, 2 January 2007

2007-01-02T20:13:28Z

← Older revision		Revision as of 20:13, 2 January 2007
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.

			Comments Added by [[User:Vandalite\|Vandalite]]

	* say		* say
	* teamsay		* teamsay
			** Exportable using msg -- may not be a bad idea to keep this one though, and have a wrapper instead for team assignment.
	* asay		* asay
			** What's this? is it needed?
	* msg		* msg
	* amsg		* amsg
			** What's this? is it needed?
	* me		* me
			** What's this? is it needed?
	* slap		* slap
			** What's this? is it needed?
	* nick		* nick
	* vote		* vote
			** Exportable using mapvote resource
	* maps		* maps
			** Exportable using mapvote resource
	* login		* login
			** Should have a lua wrapper with security resource
	* logout		* logout
			** Should have a lua wrapper with security resource
	* setlevel		* setlevel
			** Should have a lua wrapper with security resource
	* chgmypass		* chgmypass
			** Should have a lua wrapper with security resource
	* addaccount		* addaccount
			** Should have a lua wrapper with security resource
	* delaccount		* delaccount
			** Should have a lua wrapper with security resource
	* chgpass		* chgpass
			** Should have a lua wrapper with security resource
	* chglevel		* chglevel
			** Should have a lua wrapper with security resource
	* startmap		* startmap
			** Should have a lua wrapper with mapvote resource
	* restartmap		* restartmap
			** Exportable using mapvote resource
	* mute		* mute
			** Exportable using communications resource (and onPlayerChat interruptions)
	* unmute		* unmute
			** Exportable using communications resource (and onPlayerChat interruptions)
	* kick		* kick
			** Should have a lua wrapper with security resource
	* ban		* ban
			** Should have a lua wrapper with security resource
	* banip		* banip
			** Should have a lua wrapper with security resource
	* unbanip		* unbanip
			** Should have a lua wrapper with security resource
	* shutdown		* shutdown
	* aexec		* aexec
			** What's this? is it needed?
	* whois		* whois
			** What's this? is it needed?
	* whowas		* whowas
			** What's this? is it needed?
	* loadscript		* loadscript
			** legacy. consider changing to loadresource
	* unloadscript		* unloadscript
			** legacy. consider changing to unloadresource
	* scripts		* scripts
			** What's this? is it needed?
	* debugscript		* debugscript

			For all commands i reccomended putting in the security resource, this is only useful if you have a way of setting commands (from mta server conf) to a security level higher than ANY user, and an architecture is in place to allow resources themselves to have security levels. this allows ONLY the security resource to run these commands, 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.

EAi at 04:03, 2 January 2007

2007-01-02T04:03:18Z

New page

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

* say
* teamsay
* asay
* msg
* amsg
* me
* slap
* nick
* vote
* maps
* login
* logout
* setlevel
* chgmypass
* addaccount
* delaccount
* chgpass
* chglevel
* startmap
* restartmap
* mute
* unmute
* kick
* ban
* banip
* unbanip
* shutdown
* aexec
* whois
* whowas
* loadscript
* unloadscript
* scripts
* debugscript