From no-reply_wiki at metalforge.org Thu Sep 2 11:34:26 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Thu, 02 Sep 2010 11:34:26 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: cfpython Message-ID: <1283445266.120785.25438.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/02 11:34 User : ryo Edit Summary: update definition @@ -748,9 +748,9 @@ Arguments: * ''Number'', ''x'' and ''y'', coordinates of position to teleport the object to ==== Say ==== - Current object says something in current map. + Current object says something in current map. If in a dialog context (reacting to a SAY event), the message will be queued to be displayed after the player actually says something, to enable changing her reply. If not in a dialog context, will just display the message. Argument: * ''string'' to say. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/cfpython?rev=1281771785 New Revision: http://wiki.metalforge.net/doku.php/cfpython -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Fri Sep 3 17:43:00 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Fri, 03 Sep 2010 17:43:00 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client:scratchpad Message-ID: <1283553780.160799.5598.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/03 17:42 User : kbulgrien Edit Summary: Add Leaf's idea for timestamping messages. @@ -53,9 +53,10 @@ * In-client configuration of message routing to the available message panels? * Ability for the user to determine the number of message panels in the client. * This could be used to make smaller layouts as the number of panels could be reduced to 1. * Add a "status bar" style message panel that displays only the last message of a particular type. - * Optional logging of chats and tells. + * Optional logging of chats and tells. + * Time stamping of messages. ====Configuration==== * Document GTK-V2 in-client what Echo Bound Commands means/does. Is it even useful? How? IP-Address : 64.217.180.145 Old Revision: http://wiki.metalforge.net/doku.php/client:scratchpad?rev=1283111665 New Revision: http://wiki.metalforge.net/doku.php/client:scratchpad -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Fri Sep 3 20:09:49 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Fri, 03 Sep 2010 20:09:49 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client:scratchpad Message-ID: <1283562589.427897.6338.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/03 20:09 User : kbulgrien Edit Summary: Add non-hard-coded, line wrap of message panels. @@ -53,8 +53,9 @@ * In-client configuration of message routing to the available message panels? * Ability for the user to determine the number of message panels in the client. * This could be used to make smaller layouts as the number of panels could be reduced to 1. * Add a "status bar" style message panel that displays only the last message of a particular type. + * Automatic line-wrap based on message pane size, font, etc. The client wraps at 40 characters whether that is sensible or not. * Optional logging of chats and tells. * Time stamping of messages. ====Configuration==== IP-Address : 64.217.180.145 Old Revision: http://wiki.metalforge.net/doku.php/client:scratchpad?rev=1283553776 New Revision: http://wiki.metalforge.net/doku.php/client:scratchpad -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Fri Sep 3 20:16:10 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Fri, 03 Sep 2010 20:16:10 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client:scratchpad Message-ID: <1283562970.757198.6353.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/03 20:16 User : kbulgrien Edit Summary: Message routing implementation flexibility regarding number of panels. @@ -49,8 +49,12 @@ ====Communication panels==== * Add a chat-specific panel? + * Message routing system should allow a client to not have a specific number of message panels. + * So layouts can vary the number of available panels to adapt to large/small footprints, etc. + * Auto-disable routing to panels not defined in a layout. + * Disallow configuring routing to unavailable panels. * In-client configuration of message routing to the available message panels? * Ability for the user to determine the number of message panels in the client. * This could be used to make smaller layouts as the number of panels could be reduced to 1. * Add a "status bar" style message panel that displays only the last message of a particular type. IP-Address : 64.217.180.145 Old Revision: http://wiki.metalforge.net/doku.php/client:scratchpad?rev=1283562587 New Revision: http://wiki.metalforge.net/doku.php/client:scratchpad -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 01:24:48 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 01:24:48 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: known_client_issues Message-ID: <1283581488.246919.4087.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 01:24 User : kbulgrien Edit Summary: As client lockup if over-excited with keyboard when quitting the client. @@ -5,8 +5,9 @@ * If you're using ISDN or DSL verify that your MTU is 1492, not 1500. * Do not use a nameserver of Deutsche Telekom or T-Online. ===== Unspecified/Multiple/SVN ===== + * September, 2010. If you apply a bed of reality, hit q to quit, and something else, especially a keybind, in very quick succession, the client freezes up (at least on Linux). killall -hup crossfire-client-gtk2 will kill it, but most window manager functions do not appear to be successfull at closing the hung client. It appears that the client keeps trying to do socket operations to send the commands to the now disconnected server. GDB shows it stuck much if the time in __kernel_vsyscall, but sometimes you can catch in in libpthread.so. In past experience, __kernel_vsyscall can hang for about 4 minutes on Linux before it returns, still, after many, many minutes, the client does not die. mwedel suggested a possible setting for the socket that might help. It looks like the client is very hard to kill if you do not have xkill or know how to go to a console to kill it, so this is a very unfriendly behavior. This has probably been an issue for a very long time, but just has not been noticed or reported. * August, 2010. The GTK-V2 client design specifies that various dialogs (spell, skills, config, etc) should not be drawn with the X close icon on the window frame. This works for various window managers, but appears not to work under the default LXDE configuration on Mandriva 2010 Spring. Another report said that it did not work under KDE 3.5.10 when kde-window-decorator was in use, though KDE is generally considered to not have this issue. In any event, if X close icons appear on client dialogs, DO NOT dismiss them with the X icon. This deletes the dialog and requires a client restart to show it again. Use the Close button, on the lower button bar, to dismiss all client dialogs. * This is fixed in SVN as of 2010/08/19. * ~August, 2010 and earlier. Various reports indicate that crossfire-client-gtk2 themes (colored text/spell window) no longer worked on some distributions when the client is launched from a user account. Workarounds were found. All of them essentially launch the client like this: '''GTK_MODULES=""; crossfire-client-gtk2'''. In at least one instance of non-working themes, GTK_MODULES was set to '''canberra-gtk-module''', but the settings for all reports is unknown. It appears some theme engines are not compatible with crossfire-client-gtk2 theme code. It is not yet known whether there is a way to alter the client so that its themes work properly without regard to the system GTK theme engine setting. * ~July, 2010. The GTK-V2 client with account-based login support has a bug in a character create button that makes it impossible to set up a character. It is thought this bug is in 1.50. Current SVN is fixed. The fix is an update to dialogs.glade, and does not require re-compile. IP-Address : 64.217.180.145 Old Revision: http://wiki.metalforge.net/doku.php/known_client_issues?rev=1282262482 New Revision: http://wiki.metalforge.net/doku.php/known_client_issues -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 01:28:52 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 01:28:52 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client:scratchpad Message-ID: <1283581732.091310.4096.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 01:28 User : kbulgrien Edit Summary: Add mwedel's SO_LINGER idea. @@ -19,8 +19,14 @@ * User-interface controls to configure what audio file to play for a particular mood. * Deploy a basic set of standard audio files with the client. * JXClient uses .wav, but Ragnor says .ogg is preferred, except that he tried and gave up once. It would probably be good to try for .ogg. .wav is uncompressed. * Deploying audio files via network should likely happen outside of the client protocol, and use a standard file transfer protocol, but due to the size of the files this should be carefully thought out. + + ======Infrastructure===== + + =====Network/Socket===== + + * Try SO_LINGER at mwedel's suggestion to try to address very bad lockup if the keyboard is used while quitting the client. ======User Interface===== =====Style/Themes===== IP-Address : 64.217.180.145 Old Revision: http://wiki.metalforge.net/doku.php/client:scratchpad?rev=1283562968 New Revision: http://wiki.metalforge.net/doku.php/client:scratchpad -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 02:44:27 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 02:44:27 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:quest_management_system Message-ID: <1283586267.555052.5215.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 02:44 User : ryo Edit Summary: update @@ -1,4 +1,8 @@ + Update: quests are currently implemented in server, and seem to work along the general ideas below. Thus this is kept for reference. --- //Nicolas 2010/09/04 02:43// + + + (copy of a mail sent to CF --- //[[nicolas.weeger at laposte.net|Ryo Saeba]] 2006/06/10 07:58//) Quests should be finite state automates. Meaning different states, with transitions between states, with conditions for those transitions, etc. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:quest_management_system?rev=1164430133 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:quest_management_system -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 02:46:53 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 02:46:53 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:change_player_speed Message-ID: <1283586413.434483.5224.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 02:46 User : ryo Edit Summary: update @@ -1,4 +1,7 @@ + Update 2010/09: trunk has different speed, so this is probably not relevant anymore. //Nicolas + + Currently, high level players move insanely fast (1.5+). And low level players tend to move quite slowly. Both of these cause problems - high level players outrun lightning bolts, and low level players spend large amounts of time just moving slowly from point a to point b. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:change_player_speed?rev=1175025745 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:change_player_speed -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 02:50:52 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 02:50:52 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo_new Message-ID: <1283586652.054871.5237.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 02:50 User : ryo Edit Summary: strike out things that done, or potentially done @@ -5,9 +5,9 @@ ^ Project/Feature ^ Target Release ^ Priority ^ Status ^ Component ^ Developer ^ | [[dev_todo:Performance Improvements]] - Server has performance issues, especially related to losts of spells | 1.x | 1 | Completed | Server | [[user:mwedel]] | | [[dev_todo:Metaserver improvements]] - Current metaserver has many limitations| 1.x | 2 | None | Server & Client | | | [[dev_todo:Archetype Cleanup]] - Clean up the Archetypes. | 1.x? | 1 | None | Archetypes | | - | [[dev_todo:Fix Weather]] - Fix and improve the weather system. | 1.x | 2 | Completed/Planning | Server | | + | [[dev_todo:Fix Weather]] - Fix and improve the weather system. | 1.x | 2 | Completed/Planning | Server | | | [[dev_todo:Pupland]] - Move pupland onto the world maps | 1.x? | 2 | Coding | Maps | [[user:lalomartins]]? | | [[dev_todo:Protocol Compression]] - Compress client/server communication | 1.x? | 2 | Planning | Client/Server | | | [[dev_todo:Experience Rewarder]] - Add experience rewarder object | 1.x and 2.x | 2 | Done | Server/Maps | [[:user:ryo|Ryo]] | | [[dev_todo:Map Cleanup]] - Clean up maps, remove old hacks, etc | 1.x? | 3? | None? | Maps | | @@ -28,11 +28,11 @@ | [[dev_todo:fix_sound|Fix/Revamp sound]] - Fix and improve the sound system. | 2.0 | 2 | None | Client/Server/Maps | | | [[dev_todo:Better NPCs]] - Better NPC communication | 2.0 | 2 | None | Server | | | [[dev_todo:Smarter Monsters]] - Monsters should attack/defend more intelligently | 2.0 | 2 | None | Server | | | [[dev_todo:lighting|Revamp lighting]] - Improve Lighting/LOS code | 2.0 | 2 | None | Client/Server | | - | [[dev_todo:Time of day based events]] - Stuff happening based on the time of day. | 2.0 | 2 | Planning/Coding | Server/Maps |[[user:tchize|Tchize]] | + | [[dev_todo:Time of day based events]] - Stuff happening based on the time of day. | 2.0 | 2 | Planning/Coding | Server/Maps |[[user:tchize|Tchize]] | | [[dev_todo:Make Slaying Consistent]] - Add does_slay() instead of having different code sprinkled through server | 2.0 | 2 | None | Server | | - | [[dev_todo:Change Player Speed]] - Low level players move too slow, high level players move too fast | 2.0 | 2 | None | Server | | + | [[dev_todo:Change Player Speed]] - Low level players move too slow, high level players move too fast | 2.0 | 2 | None | Server | | | [[dev_todo:Material type improvement]] - Material code should be improved | 2.0 | 2 | None | Server | | | [[dev_todo:Centralized Map Passwords]] - Passwords on maps should be stored centrally, making them easier to change | 2.0 | 2 | None | Server & Maps| | | [[dev_todo:NPC Syntax Highlighting]] - use extended tags to make npc messages easier to understand | 2.0 | 3 | None | Maps | | | [[dev_todo:Discrete attack damage]] - add dam_fire/dam_cold, etc | 2.0 | 3 | Experimental | Maps/Arch/Server | | @@ -47,9 +47,9 @@ | [[dev_todo:Player Economy]] - Have player buying/selling influence economy | 3.0? | 2 | None | Server/Maps | | | [[dev_todo:Improved Player Communication]] - Allow chatting between servers, and connections just for chatting. | 3.0 | 2 | None | Server | | | [[dev_todo:Player Clothing]] - Change player image based on clothing/equipment | 3.0 | 3? | None | Server/Client/Arch | | | [[dev_todo:Python Guilds]] - Update guilds using existing Python Guild scripts | 2.0 | 2? | Coding | Maps | [[user:leaf]] | - | [[dev_todo:In-game monster information]] | ? | ? | Talks | Server | | + | [[dev_todo:In-game monster information]] | ? | ? | Talks | Server | | | [[user:kshinji:estates|Python Estates]] | 1.x? | ? | Planning/Coding | Server | kshinji ? | | [[dev_todo:Functions implemented but not yet used]] | 2.x | ? | to be used | server | | * Project is a brief summary of the project. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo_new?rev=1276363242 New Revision: http://wiki.metalforge.net/doku.php/dev_todo_new -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 02:52:59 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 02:52:59 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo Message-ID: <1283586779.404720.5245.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 02:52 User : ryo Edit Summary: link to dev_todo_new @@ -1,6 +1,9 @@ ====== TODO List ====== This is a general TODO list for the crossfire project. As brainstormed by [[user:Rednaxela]], and [[user:techolous]] on irc. + + + See also: [[dev_todo_new]] ====== Development TODO List ====== This page contains a list of things that are being worked on, or may be implemented in the future. And a place to discuss in depth how a particular feature or change will be implemented. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo?rev=1274277335 New Revision: http://wiki.metalforge.net/doku.php/dev_todo -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 02:52:15 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 02:52:15 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:python_guilds Message-ID: <1283586735.083189.5242.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 02:52 User : ryo Edit Summary: update @@ -3,5 +3,7 @@ Quite a bit of framework is already in place to add new features to the Crossfire guild system. However, this functions hasn't seen any development or updates for quite some time. This TODO was setup to re-implement and update what has been started. + + Update 2010-09: this page is totally out of date //Nicolas// Update 2007-10-20: guilds should be ok, minor bugs may be left. Hint for guild installation: IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:python_guilds?rev=1207533157 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:python_guilds -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 04:10:58 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 04:10:58 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:thread_the_server Message-ID: <1283591458.793581.5700.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 04:10 User : ryo Edit Summary: a few ideas @@ -23,4 +23,27 @@ ===== More information ===== FIXME put information from the logs of IRC discussion here + ===== Nicolas's ideas ===== + + Things to solve: + * thread-safety for shared strings ; not too bad + * thread-safety for freed objects, and active objects + * solution 1: put'em between mutexes + * solution 2: each map has its own list ; issue with linked maps, merge the lists? + + + Things that should definitely be threaded: + * map loading + * caveat: players entering a map will be in a "vacuum" during load ; doesn't seem bad + * map saving + * caveat: issue with DM command "reset", will need to ensure map is correctly saved + + + Things that would be nice to thread: + * one thread per map + * issue: how will the "Object.Teleport" Python function work, since it couldn't cross thread boundaries? simply remove it, and force script makers to use other means? + * same issue with ready_map() through scripts - what happens if the map is already loaded and has its thread running? + * thread for socket processing, one per player maybe + * ideally, one could thread potentially long operations like massive item selling, or massive item drop + * thread socket sending to players, to make the previous operations faster? IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:thread_the_server?rev=1160410641 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:thread_the_server -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sat Sep 4 04:27:21 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 04 Sep 2010 04:27:21 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:thread_the_server Message-ID: <1283592441.986337.5728.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/04 04:27 User : ryo Edit Summary: more @@ -46,4 +46,6 @@ * same issue with ready_map() through scripts - what happens if the map is already loaded and has its thread running? * thread for socket processing, one per player maybe * ideally, one could thread potentially long operations like massive item selling, or massive item drop * thread socket sending to players, to make the previous operations faster? + * split eg item selling and player notification, with that latter moved to a separate thread + IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:thread_the_server?rev=1283591456 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:thread_the_server -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Tue Sep 7 23:15:52 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Tue, 07 Sep 2010 23:15:52 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dm_commands Message-ID: <1283919352.943072.31750.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/07 23:15 User : kbulgrien Edit Summary: Add how to reset a unique map. @@ -163,9 +163,21 @@ ==== reset ==== syntax: reset or reset . - notes: all other characters must be off of the map at the time of reset (a message will appear showing any players on the map during the failed reset.) This will NOT reset any unique items, such as players apartments, in the case of unique items being on a map, it will cause them to be saved before the map is reset. You can also use the command in this syntax to reset the map you are currently standing on: 'reset . + Notes: All other characters must be off of the map at the time of reset (a message will appear showing any players on the map during the failed reset.) This will NOT reset any unique items, such as players apartments, in the case of unique items being on a map, it will cause them to be saved before the map is reset. You can also use the command in this syntax to reset the map you are currently standing on: 'reset . + + To reset a unique map, access to the server file system is needed. Make sure all items of value are retrieved from the map before implementing the reset, or they will be lost. When the map owner says all is clear, consider the example of trying to reset a python guild map (/pup_land/guilds/purple_butterfly/hallofjoining). + + * Use the reset command to reset the map path the same way you would a normal map. + * dm + * reset /pup_land/guilds/purple_butterfly/hallofjoining + * Find the unique map. In this example, the server is installed in /usr/games/crossfire. The unique map is a file named similarly to the in-game map path: In this example, the server is installed in /usr/games/crossfire.v00 + * Presumably there are cases where there might be multiple files with different numbered .vXX extension. If there are more than one, make sure to identify the one to reset. + * For safety, make a backup of the unique map. + * Delete the unique map. + * rm -f /usr/games/crossfire/var/crossfire/unique-items/pup_land\@guilds\@purple_butterfly\@hallofjoining.v00 + * One server admin suggests an additional reset of the map from within game, but, at least on one trunk server, this reports "No such map" after the server unique map file was deleted, and therefore, may not be needed. ==== speed ==== syntax: speed IP-Address : 64.217.180.145 Old Revision: http://wiki.metalforge.net/doku.php/dm_commands?rev=1253240325 New Revision: http://wiki.metalforge.net/doku.php/dm_commands -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Wed Sep 29 13:57:47 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Wed, 29 Sep 2010 13:57:47 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dm_commands Message-ID: <1285786667.209377.29652.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/29 13:57 User : ryo Edit Summary: update reset @@ -161,12 +161,19 @@ notes: remove will, surprisingly enough, remove the object specified by the tag supplied. See Also: free ==== reset ==== - syntax: reset or reset . + syntax: ''reset '' or ''reset .'' or ''reset full-reset '' or ''reset full-reset .'' + Notes: All other characters must be off of the map at the time of reset (a message will appear showing any players on the map during the failed reset.) This will NOT reset any unique items, such as players apartments, in the case of unique items being on a map, it will cause them to be saved before the map is reset. You can also use the command in this syntax to reset the map you are currently standing on: 'reset . + === How to reset a unique map (trunk) === + Since revision 13938, ''reset full-reset '' enables to remove unique items from a map. + + For a player unique map, you need to be outside the map to reset it, and give the full path (using ''reset full-reset .'' while in that map will give you that full path). + + === How to reset a unique map (branch) === To reset a unique map, access to the server file system is needed. Make sure all items of value are retrieved from the map before implementing the reset, or they will be lost. When the map owner says all is clear, consider the example of trying to reset a python guild map (/pup_land/guilds/purple_butterfly/hallofjoining). * Use the reset command to reset the map path the same way you would a normal map. * dm IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dm_commands?rev=1283919349 New Revision: http://wiki.metalforge.net/doku.php/dm_commands -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Wed Sep 29 14:10:32 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Wed, 29 Sep 2010 14:10:32 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dm_commands Message-ID: <1285787432.652423.29876.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/29 14:10 User : ryo Edit Summary: update comment @@ -2,9 +2,9 @@ * See also: [[player_commands]] General notes for DM's: - Case sensitivity is important in player and map names. + Case sensitivity is important in player and map names. Most commands using a player name will work if given a partial name that is non ambiguous. ==== abil ==== syntax: abil IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dm_commands?rev=1285786664 New Revision: http://wiki.metalforge.net/doku.php/dm_commands -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Wed Sep 29 14:23:13 2010 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Wed, 29 Sep 2010 14:23:13 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dm_commands Message-ID: <1285788193.408579.29895.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2010/09/29 14:23 User : ryo Edit Summary: update reset @@ -166,14 +166,14 @@ Notes: All other characters must be off of the map at the time of reset (a message will appear showing any players on the map during the failed reset.) This will NOT reset any unique items, such as players apartments, in the case of unique items being on a map, it will cause them to be saved before the map is reset. You can also use the command in this syntax to reset the map you are currently standing on: 'reset . - === How to reset a unique map (trunk) === - Since revision 13938, ''reset full-reset '' enables to remove unique items from a map. + === How to reset a unique map === + Since revision 13938 (trunk) and 13939 (branch), ''reset full-reset '' enables to remove unique items from a map. For a player unique map, you need to be outside the map to reset it, and give the full path (using ''reset full-reset .'' while in that map will give you that full path). - === How to reset a unique map (branch) === + === How to reset a unique map (before those revisions) === To reset a unique map, access to the server file system is needed. Make sure all items of value are retrieved from the map before implementing the reset, or they will be lost. When the map owner says all is clear, consider the example of trying to reset a python guild map (/pup_land/guilds/purple_butterfly/hallofjoining). * Use the reset command to reset the map path the same way you would a normal map. * dm IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dm_commands?rev=1285787430 New Revision: http://wiki.metalforge.net/doku.php/dm_commands -- This mail was generated by DokuWiki at http://wiki.metalforge.net/