You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal is to be able to add new console commands via javascript - however, only operators should have access to the js command so for an op to create a new javascript function and have that function executable by all, it needs to be exposed via another command.
That command will be jsp - (short for js plugin , or js proxy or js protected - take your pick). jsp won't in fact evaluate any javascript code - that would leave the server wide open for all players - instead it looks up a lookup table of javascript functions which have been exposed for use by players.
For example...
/jsp home set
will make the plugin lookup a table to see if there is a 'home' javascript function defined and if there is it calls that function passing in each argument. The distinction between js and jsp is this - js evaluates javascript. jsp looks up a table for a specific javascript function (the 1st parameter supplied to jsp) and invokes that function passing in all subsequent parameters.
The plan is to use the common (among bukkit plugins/servers) home plugin commands as a test-bed.
basic commands:
/jsp home - takes the player home.
/jsp home set - sets the player's current location as home.
/jsp home delete - delete the home reference
/jsp home help - prints help about the command
social commands:
/jsp home - go to 's home.
/jsp home list - display whose homes you can visit
/jsp home ilist - display who can visit your home
/jsp home invite - invite player to your home
/jsp home uninvite - uninvite
/jsp home public - make your home public (anyone can visit)
/jsp home private - make your home private
admin commands:
/jsp home listall - list all of the homes on the server.
/jsp home clear - clears player's home from server.
The goal is to be able to add new console commands via javascript - however, only operators should have access to the js command so for an op to create a new javascript function and have that function executable by all, it needs to be exposed via another command.
That command will be jsp - (short for js plugin , or js proxy or js protected - take your pick). jsp won't in fact evaluate any javascript code - that would leave the server wide open for all players - instead it looks up a lookup table of javascript functions which have been exposed for use by players.
For example...
/jsp home set
will make the plugin lookup a table to see if there is a 'home' javascript function defined and if there is it calls that function passing in each argument. The distinction between js and jsp is this - js evaluates javascript. jsp looks up a table for a specific javascript function (the 1st parameter supplied to jsp) and invokes that function passing in all subsequent parameters.
The plan is to use the common (among bukkit plugins/servers) home plugin commands as a test-bed.
basic commands:
/jsp home - takes the player home.
/jsp home set - sets the player's current location as home.
/jsp home delete - delete the home reference
/jsp home help - prints help about the command
social commands:
/jsp home - go to 's home.
/jsp home list - display whose homes you can visit
/jsp home ilist - display who can visit your home
/jsp home invite - invite player to your home
/jsp home uninvite - uninvite
/jsp home public - make your home public (anyone can visit)
/jsp home private - make your home private
admin commands:
/jsp home listall - list all of the homes on the server.
/jsp home clear - clears player's home from server.
See http://dev.bukkit.org/server-mods/myhome/ for reference.
The text was updated successfully, but these errors were encountered: