summaryrefslogtreecommitdiffstats
path: root/example/serverdata/permissions.xml
Commit message (Collapse)AuthorAgeFilesLines
* Merged the example client and server dataThorbjørn Lindeijer2012-02-251-54/+0
| | | | | | | | | It's easier to just talk about world data and to modify it as a whole. If there is really a need to separate it, a project can still choose to do that (and in whatever suitable way). There is no need to enforce this separation or to do it in our example. Reviewed-by: Erik Schilling
* Moved @announce permission to GM groupThorbjørn Lindeijer2012-02-051-1/+1
| | | | Reviewed-by: Erik Schilling
* Added @skills command which lists all skillsErik Schilling2011-12-041-0/+1
| | | | Reviewed-by: o11c.
* Added @permissions commandErik Schilling2011-11-021-0/+1
| | | | | | | Added @permissions <character> which lists the permissions of a player. Made @givepermission giving feedback on success. Reviewed-by: Thorbjørn Lindeijer.
* Added chatcommand to get position of a character.Erik Schilling2011-09-011-0/+1
| | | | | Add chatcommand @getpos <character> which return the mapid and location of the character. Part of: Mana-Mantis: #385.
* Added a simple crafting systemPhilipp Sehmisch2011-04-271-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | A client can craft something using the @craft command. The command needs a list of item names and amounts. The gameserver checks if the character has these items in the inventory and then passes the list together with the character handle to the lua script function on_craft in the script file scripts/crafting.lua. This function can then be used to evaluate if the list is a valid crafting combination and when this is the case take or give items. Implemented two example crafting scripts there, one which enforces exact item order and amount and one which doesn't. Both are disabled per default and one needs to be enabled by uncommenting a line. Also gave the player group permission to use the @craft command in permissions.xml and added two new items (wood and iron) required for the example crafting combination. Resolves: #333 Reviewed-by: bcs86, Bertram
* Implementing @killmonstersStefan Dombrowski2011-02-221-0/+1
| | | | Reviewed-by: Crush
* Implemented @log and @logsay commands.Philipp Sehmisch2010-12-271-0/+2
| | | | | | | | | | The @log command is the equivalent to tmwAthena's @l. It allows to log a text as a transaction for documentation purpose. The @logsay command works like @t on tmwAthena. It says something in public chat while also logging it as a separate trasaction. Reviewed-by: Thorbjorn
* Transaction logging of various command, new transaction codes and style fix.Philipp Sehmisch2010-12-271-0/+2
| | | | | | | | | | | | | | The @mute, @goto, @attribute and @announce commands now logs transactions to the database. Added new transaction codes to database. I've preliminarily added a lot of codes for not yet supported commands so that we needn't do a database update with every single commit which implements one. Also using the equivalent "say" helper function in place of the "GameState::sayTo" method in the command handler. Reviewed-by: Kage
* Implemented @die chat commandPhilipp Sehmisch2010-12-171-0/+1
| | | | | | | | | | | | The @die chat command kills the evoking character by setting its hit points to 0. The example permissions.xml assigns it to the "tester" rights group and not "players" because server admins who are not aware of this command might run into trouble when they assume that players don't have a method to teleport to their spawn point voluntarily. Resolves: mantis ticket #192 Reviewed-by: Jaxad0127
* Improve warp commandsJared Adams2010-12-061-0/+1
| | | | | | | | @warp no longer takes a character. @charwarp was added to handle that ('#' still means the player). Both can take a map name, map id (preceded by '#') or '#' for the player's current map. Logging of warp commands now logs destination map and player warped (for @charwarp).
* Added @mute chat command.Philipp Sehmisch2010-08-301-0/+1
| | | | | | | | The @mute command stops another character from talking in the public chat for a specified amount of seconds. It doesn't survive a reconnect of the client, but I don't think that this is necessary because a mute by a GM is usually intended as a slap on the wrist with more severe consequences to follow (like @ban).
* Copied basic Lua libs back from tmwserv-data and added dummy dataThorbjørn Lindeijer2010-05-301-0/+42
The dummy data is currently mostly empty data though, so still nothing to see as far as the example content is concerned. Reviewed-by: Bertram