From no-reply_wiki at metalforge.org Mon Jul 2 17:01:01 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 02 Jul 2007 17:01:01 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:server_cleanup Message-ID: <1183413661.326529.24917.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/02 17:01 User : ryo Edit Summary: a few items @@ -10,10 +10,12 @@ * Or perhaps we should create our own simple solution that is similar in nature. * ~~all draw_info need to be changed to draw_ext_info~~ done * safe string functions should be used except in rare cases * memory allocation returned values should be checked for NULL. Create a cfmalloc function? - * static buffers should be removed + * static buffers should be removed - almost done + * put all map->player changes in ''remove_ob'' / ''insert_ob_in_map'' so it handles all cases, remove other changes sprinkled in the code + * add client sending of add/remove in inventory in ''remove_ob'' / ''insert_ob_in_ob'' so checks everywhere can be removed See Also: * [[dev_todo:refactor|dev_todo:refactor]] IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:server_cleanup?rev=1167475102 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:server_cleanup -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 2 17:03:01 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 02 Jul 2007 17:03:01 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo_new Message-ID: <1183413781.562196.24920.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/02 17:02 User : ryo Edit Summary: + one @@ -49,8 +49,9 @@ | [[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 | | | [[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. * Target release is when it is hoped the feature will completed. * Priority is important of the feature - 1 being highest priority. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo_new?rev=1180982633 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 Mon Jul 2 17:14:09 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 02 Jul 2007 17:14:09 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page added: dev_todo:functions_implemented_but_not_yet_used Message-ID: <1183414449.949254.24944.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/02 17:14 User : ryo Edit Summary: created This page lists functions that are implemented in the code, but not actually used. Some could really be used, others may probably be removed. ===== discrete attack damage ===== Through the ''damage_xxx'' fields in archetypes, it is possible to define the damage for a specific attacktype. If at least one field is set, ''dam'' is ignored for attack, and the discrete values are used instead. Some archetypes could be updated to actually use this. Also, things like dragon claws could use this. ===== harvesting-like skills ===== See [[dev:skills#sk_harvesting]] for details. Those skills would enable to add fun things like getting fruits from trees, milk from cow, you name it. ===== unit tests ===== Located in ''test''. Only a few are actually used, we could write some for complex things. ===== pants/legs ===== A new body spot, ''body_leg'', was introduced to enable pants. No archetype still uses this. Also, some armours could be considered as having legs, thus should be fixed for that. IP-Address : 82.236.87.204 Old Revision: none New Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 2 20:41:31 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 02 Jul 2007 20:41:31 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:better_client_ui Message-ID: <1183426891.395443.25275.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/02 20:41 User : Edit Summary: @@ -11,4 +11,5 @@ * Compact/expand player stats in gui * themes * Coloring displayed protections (stat area/ possibly message text) based on status * More keyboard control for everything + * Mood music. Some people used to choose the old dxclient win32 client specifically because it had music. IP-Address : 70.255.81.125 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:better_client_ui?rev=1160509287 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:better_client_ui -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Wed Jul 4 15:53:22 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Wed, 04 Jul 2007 15:53:22 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:functions_implemented_but_not_yet_used Message-ID: <1183582402.659377.29724.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/04 15:53 User : ryo Edit Summary: polymorph @@ -20,4 +20,7 @@ Located in ''test''. Only a few are actually used, we could write some for complex things. ===== pants/legs ===== A new body spot, ''body_leg'', was introduced to enable pants. No archetype still uses this. Also, some armours could be considered as having legs, thus should be fixed for that. + + ===== polymorph ===== + This spell has been disabled for ages, but reactivated lately. It doesn't appear in any treasurelist, and no map seems to have any object with this spell. Thus need some quest for it. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used?rev=1183414447 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Fri Jul 6 02:37:31 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Fri, 06 Jul 2007 02:37:31 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:functions_implemented_but_not_yet_used Message-ID: <1183707451.093110.701.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/06 02:37 User : Edit Summary: Add transports section @@ -23,4 +23,7 @@ A new body spot, ''body_leg'', was introduced to enable pants. No archetype still uses this. Also, some armours could be considered as having legs, thus should be fixed for that. ===== polymorph ===== This spell has been disabled for ages, but reactivated lately. It doesn't appear in any treasurelist, and no map seems to have any object with this spell. Thus need some quest for it. + + ===== transports ===== + Transports have been implemented and are active on metalforge for a long time now. But they are hardly used: two ships in Scorn's harbor (just for testing, not useful since you cannot reach any useful location), one in Stoneville. IP-Address : 141.76.45.35 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used?rev=1183582399 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Fri Jul 6 12:47:22 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Fri, 06 Jul 2007 12:47:22 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:char_creation Message-ID: <1183744042.144251.1874.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/06 12:47 User : Edit Summary: added link to more information about the reasons for this changes @@ -10,4 +10,5 @@ * Client sends this info to server, and server validates it is then correct (client should never send wrong data, but someone using a hacked client shouldn't be able to generated bad characters) * As part of this, the different classes would need to become archetypes, so server can know what they are. * Down the road, an advanced creation method could be used where player doesn't choose a class, but rather what skills they want (and maybe get a small pile of gold). That should wait for any skill changes to be made. + Purpose: http://mailman.metalforge.org/pipermail/crossfire/2007-July/011622.html IP-Address : 89.62.20.207 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:char_creation?rev=1158479066 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:char_creation -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sun Jul 15 16:19:12 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sun, 15 Jul 2007 16:19:12 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:functions_implemented_but_not_yet_used Message-ID: <1184534352.524155.25125.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/15 16:19 User : ryo Edit Summary: background music @@ -26,4 +26,7 @@ This spell has been disabled for ages, but reactivated lately. It doesn't appear in any treasurelist, and no map seems to have any object with this spell. Thus need some quest for it. ===== transports ===== Transports have been implemented and are active on metalforge for a long time now. But they are hardly used: two ships in Scorn's harbor (just for testing, not useful since you cannot reach any useful location), one in Stoneville. + + ===== background music ===== + Maps can now have a 'background_music' tag, which will get sent to client when the player enters the map. No map has this set, no client has any handling, and it isn't determined what the tag means (specific music, music genre, ...) IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used?rev=1183707448 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 16 01:29:50 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 16 Jul 2007 01:29:50 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:metaserver_improvements Message-ID: <1184567390.289380.25977.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/16 01:29 User : Edit Summary: Add some notes about http library @@ -1,9 +1,9 @@ ==== Metaserver Redo ==== The current metaserver has room for some improvements. The biggest right now is that there is a single metaserver (thus single point of failure). It also doesn't record all the information that would be useful. - Currently, the metaserver records this informatin: + Currently, the metaserver records this information: * IP address * Hostname (provided by server - not resolved by metaserver!) * number of current players * version of the server @@ -18,24 +18,25 @@ * metaserver should confirm hostname matches IP address from request. This currently isn't feasible because doing nameservice lookups could time out, causing server to hang up * SC_VERSION and CS_VERSION of the server - in this way, client could filter out servers it know it couldn't support. * A text flags section - different flags have different, but standardized, meaning. $ could be pay to play, P means player killing, etc * Multiple metaservers, so there is not a single point of failure. + * Maybe add a second comment field - one for html (to display on the web), and one plain text so it can be properly displayed in the client? === Thoughts on Implementation === - Making it a web based service (cgi-bin script or php script) is a good way to go. The web server deals with running multiple copies at the same time - just, we don't care as much about timeouts in resolving the host name. Web based script access is also quite common, which means that it would be much easier to get multiple instances up compared to requiring a custom program to be run. + Making it a web based service (cgi-bin script or php script) is a good way to go. The web server deals with running multiple copies at the same time - thus, we don't care as much about timeouts in resolving the host name (one of the scripts running on the server may take a while to complete, but that doesn't cause problems as other scripts can run). Web based script access is also quite common, which means that it would be much easier to get multiple instances up compared to requiring a custom program to be run. - While overkill, tieing it into a mysql database on the back end takes care of file locking/contention issues. A secondary table could be used to blacklist certain servers, typically those that are misconfigured. + While overkill, tying it into a mysql database on the back end takes care of file locking/contention issues. A secondary table could be used to blacklist certain servers, typically those that are misconfigured. There would be 3 scripts to handle this: - Script that the server uses to update information - Script that the client uses to get server information. - Script that generates HTML table that people could point their web browser at. - Script 1 could be done relatively simply by passing values in the URL - http://metaserver?sc_version=aaaa&players=3&etc. Or may be other libraries that are commonly available for http transactions that could be used. + Script 1 could be done relatively simply by passing values in the URL - http://metaserver?sc_version=aaaa&players=3&etc. But probably better to use an http request library, and use post submits - means we don't need to do lots of escaping by passing something as a URL. - Scripts 2 & 3 are relatively simple - they basically just dump the data from the mysql database. For the client script, it could be handly for it to include some demarcation line, like '--- Metaserver Info Start ---' so that the client doesn't have to be able to fully parse http - it just needs enough to make a request and look for that, knowing anything that follows it is the information it wants. + Scripts 2 & 3 are relatively simple - they basically just dump the data from the mysql database. For the client script, it could be handly for it to include some demarcation line, like '--- Metaserver Info Start ---' so that the client doesn't have to be able to fully parse http - it just needs enough to make a request and look for that, knowing anything that follows it is the information it wants. But if it also uses a http request library, that should provide necessary parsing logic. - The server component is the hardest part. Since HTTP is tcp connections, these can time out, may take some time to make the connection, etc. Simplest way short term would be to have a seperate process that is started (perhaps through popen) that the server talks to, and that other process updates the metaservers. In a sense, it acts as a proxy, but so long as the popen is done with non blocking IO, never any danger of things getting frozen on the server. That proxy would try to update all the metaservers it knows about, with some extra logic on what to do when a metaserver isn't responding + The server component is the hardest part. Since HTTP is tcp connections, these can time out, may take some time to make the connection, etc. Simplest way short term would be to have a seperate process that is started (perhaps through popen) that the server talks to, and that other process updates the metaservers. In a sense, it acts as a proxy, but so long as the popen is done with non blocking IO, never any danger of things getting frozen on the server. That proxy would try to update all the metaservers it knows about, with some extra logic on what to do when a metaserver isn't responding. Alternatively, using threads may be a cleaner way to do this. The data that the metaserver thread would need is pretty limited, so would not need much in the way of locks (and in fact, a data structure just for the dynamic metaserver data could be created, with the server just locking that as it needs to update it, with perhaps the metaserver thread having its own copy that it periodically copies from the original, so that neither lock would need to be held for very long) There shouldn't be any need for the metaservers to talk to each other. Since each server will try to talk to all the metaservers, there should be no need. The client will choose one of the metaservers from the list to use (at random), thus doing load balancing of a form. The preferred metaserver could also be set in the client. If the client can not connect to the first metaserver, it would try the next, etc. IP-Address : 209.204.178.229 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:metaserver_improvements?rev=1177049965 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:metaserver_improvements -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 16 15:42:21 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 16 Jul 2007 15:42:21 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: guides Message-ID: <1184618541.196047.27535.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/16 15:42 User : Edit Summary: @@ -110,13 +110,15 @@ * [[DM Commands]] ===== Dev Guides ===== This information is not exactly meant for most players, just people making their own maps, or modifications to crossfire. This section is more likely to get outdated. + ==== Maps and Archetypes ==== Documentation on various aspects of modifing and creating maps or archetypes. * [[Custom Item Creation]] - Information and guidelines about creating custom items. + * [[Custom Creature Creation]] - Information and guidelines about creating custom creatures. * [[Item Type Guide]] - Information about how different types and attributes affect objects. * [[Map Scale]] - A note about the scale of maps * [[Map-Making Guide]] - Notes, details and suggestions on making maps * [[Spell Numbers]] - The "spellnumber" works like an ID, it is needed to specify spells in various object-types. E.g. spellbooks, rods/wands/scrolls, firewalls... etc. IP-Address : 72.4.41.2 Old Revision: http://wiki.metalforge.net/doku.php/guides?rev=1171743389 New Revision: http://wiki.metalforge.net/doku.php/guides -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 16 15:52:23 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 16 Jul 2007 15:52:23 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page added: custom_creature_creation Message-ID: <1184619143.945798.27550.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/16 15:52 User : Edit Summary: created ====== Custom Creature Creation ====== This section details how to create custom creatures for your maps in Crossfire. Custom creatures are created using an existing archetype and modifying it to the map maker's purpose. ===== Do and Do Not ===== FIXME ===== How To ===== Information on how it is done ... ==== Make Creature Immune to Diseases ==== * Add a SIGN (Arch: sign) * Set its name to the disease's name * Set the level to 120 (over any possible level) IP-Address : 72.4.41.2 Old Revision: none New Revision: http://wiki.metalforge.net/doku.php/custom_creature_creation -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 16 15:56:37 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 16 Jul 2007 15:56:37 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: custom_creature_creation Message-ID: <1184619397.546380.27559.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/16 15:56 User : Edit Summary: @@ -1,11 +1,14 @@ + Back to the Guides page [[http://wiki.metalforge.net/doku.php/guides]] ====== Custom Creature Creation ====== This section details how to create custom creatures for your maps in Crossfire. Custom creatures are created using an existing archetype and modifying it to the map maker's purpose. ===== Do and Do Not ===== FIXME + ===== General Information ===== + Some things to keep in mind when creating custom creatures. ===== How To ===== Information on how it is done ... - ==== Make Creature Immune to Diseases ==== + ==== Make Your Creature Immune to Diseases ==== * Add a SIGN (Arch: sign) * Set its name to the disease's name * Set the level to 120 (over any possible level) IP-Address : 72.4.41.2 Old Revision: http://wiki.metalforge.net/doku.php/custom_creature_creation?rev=1184619143 New Revision: http://wiki.metalforge.net/doku.php/custom_creature_creation -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 16 15:57:47 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 16 Jul 2007 15:57:47 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: custom_item_creation Message-ID: <1184619467.988890.27562.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/16 15:57 User : eracc Edit Summary: @@ -1,4 +1,5 @@ + Back to the Guides page [[http://wiki.metalforge.net/doku.php/guides]] ====== Creating Custom Items ====== This page contains a set of guidelines for creating custom items for specific maps. Custom items are created using an existing archetype and modifying it to the map maker's purpose. ===== Do and Do Not ===== IP-Address : 72.4.41.2 Old Revision: http://wiki.metalforge.net/doku.php/custom_item_creation?rev=1162662441 New Revision: http://wiki.metalforge.net/doku.php/custom_item_creation -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Tue Jul 17 11:05:04 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Tue, 17 Jul 2007 11:05:04 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: races:quetzalcoatls Message-ID: <1184688304.462234.29552.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/17 11:05 User : Edit Summary: added a missing "+" to the stat modifications table @@ -6,13 +6,12 @@ They can grasp weapons, but their bizarre body shape prevents them from using armour, helmets, and other items of apparel intended for bipedal creatures with two arms, two legs, and a head. Their inability to use armour comes back to haunt them when they compare themselves with other [[.|races]]: highly enchanted armour is usually more beneficial than dragonhide! The wings come in handy: they can use them to levitate, and their hide gets thicker as they gain power, compensating them somewhat for not being able to use armour. ===== Player Race ===== The quetzalcoatl is selectable by players as their race. It has the following modifications: - ====Stat Modifications ==== ^ Str ^ Dex ^ Con ^ Int ^ Wis ^ Pow ^ Cha ^ Net +/- ^ - | +6 | +3 | +6 | -8 | -8 | 6 | 0 | +5 | + | +6 | +3 | +6 | -8 | -8 | +6 | 0 | +5 | ====Stat Maximums ==== ^ Str ^ Dex ^ Con ^ Int ^ Wis ^ Pow ^ Cha ^ | 26 | 23 | 26 | 12 | 12 | 26 | 20 | IP-Address : 75.176.191.140 Old Revision: http://wiki.metalforge.net/doku.php/races:quetzalcoatls?rev=1167696205 New Revision: http://wiki.metalforge.net/doku.php/races:quetzalcoatls -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Thu Jul 19 11:01:59 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Thu, 19 Jul 2007 11:01:59 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: downloading Message-ID: <1184860919.828927.1984.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/19 11:01 User : Edit Summary: Noted version 1.10.0 @@ -1,7 +1,7 @@ ====== Downloading Crossfire ====== - The current version of the Crossfire server is 1.9.1 as of 2006-Jun-30, however there have been numerous updates available via SVN since then. + The current version of the Crossfire server is 1.10.0 as of 2007-Mar-27, however there have been updates available via SVN since then. ===== SourceForge Releases ===== * http://sourceforge.net/project/showfiles.php?group_id=13833 IP-Address : 216.195.168.209 Old Revision: http://wiki.metalforge.net/doku.php/downloading?rev=1165027354 New Revision: http://wiki.metalforge.net/doku.php/downloading -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Thu Jul 19 11:04:58 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Thu, 19 Jul 2007 11:04:58 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: races Message-ID: <1184861098.619071.1987.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/19 11:04 User : Edit Summary: Spelling correction @@ -3,6 +3,7 @@ - ===== Player useable races ===== + + ===== Player usable races ===== * {{:images:dwarf_p.base.151.png}} [[.races:Dwarves]] * {{:images:elf.base.151.png}} [[.races:Elves]] * {{:images:fenx.base.150.png}} [[.races:Fendrakis]] (Fenx) * {{:images:fireborn.base.111.png}} [[.races:Fireborns]] IP-Address : 216.195.168.209 Old Revision: http://wiki.metalforge.net/doku.php/races?rev=1173172648 New Revision: http://wiki.metalforge.net/doku.php/races -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Thu Jul 19 11:56:29 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Thu, 19 Jul 2007 11:56:29 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: downloading Message-ID: <1184864189.134415.2080.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/19 11:56 User : Edit Summary: Sourceforge Subversion server name change @@ -8,13 +8,13 @@ ==== SVN via SourceForge ==== The general commands to check out a module (archtypes, client, maps, server map editor, et al) is the following: - * svn co https://svn.sourceforge.net/svnroot/crossfire/arch - * svn co https://svn.sourceforge.net/svnroot/crossfire/client - * svn co https://svn.sourceforge.net/svnroot/crossfire/maps - * svn co https://svn.sourceforge.net/svnroot/gridarta - * svn co https://svn.sourceforge.net/svnroot/crossfire/server + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/client + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps + * svn co https://crossfire.svn.sourceforge.net/svnroot/gridarta + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/server ==== Trunk & Branch: ==== You will also notice that there are directories labaled as trunk and branch. @@ -36,26 +36,26 @@ Note: The commands, below, presume you are in the directory where the archetypes, client, maps or server currently reside. * Branch: - * svn co https://svn.sourceforge.net/svnroot/crossfire/arch/branches/1.x - * svn co https://svn.sourceforge.net/svnroot/crossfire/client/branches/1.x - * svn co https://svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x - * svn co https://svn.sourceforge.net/svnroot/crossfire/server/branches/1.x + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/branches/1.x + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/branches/1.x + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/server/branches/1.x * Trunk: - * svn co https://svn.sourceforge.net/svnroot/crossfire/arch/trunk - * svn co https://svn.sourceforge.net/svnroot/crossfire/client/trunk - * svn co https://svn.sourceforge.net/svnroot/crossfire/maps/trunk - * svn co https://svn.sourceforge.net/svnroot/crossfire/server/trunk + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/trunk + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/trunk + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps/trunk + * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/server/trunk It is also possible to checkout files from SVN and have them install to a remote directory. This is accomplished by adding the file path to the end of the SVN command. For instance: - svn co https://svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x /path/to/map/directory/ + svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x /path/to/map/directory/ Or, more specifically: - svn co https://svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x /share/crossfire/maps/ + svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x /share/crossfire/maps/ This would check out the latest changes to maps 1.x branch and place them in the /share/crossfire/maps/ directory. ==== Browse the SVN Repository ==== Latest SVN changes and history is availble at: http://crossfire.svn.sourceforge.net/viewvc/crossfire/ IP-Address : 216.195.168.209 Old Revision: http://wiki.metalforge.net/doku.php/downloading?rev=1184860916 New Revision: http://wiki.metalforge.net/doku.php/downloading -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Thu Jul 19 11:58:11 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Thu, 19 Jul 2007 11:58:11 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: downloading Message-ID: <1184864291.635440.2083.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/19 11:58 User : Edit Summary: Spelling corrections @@ -16,9 +16,9 @@ * svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/server ==== Trunk & Branch: ==== - You will also notice that there are directories labaled as trunk and branch. + You will also notice that there are directories labeled as trunk and branch. The trunk is the latest development changes going only into 2.0 when it is released. The 1.x branch is for continued 1.x development, including only small bugfixes and minor features. @@ -26,9 +26,9 @@ Unless doing development it is recommended to use the 1.x branch until 2.0 is released. * Development , recent updates and latest features == trunk * Tested & stable features, bug fixes, etc. == branch - Notice: It is highly recommend that you use a trunk mapset with a trunk server and a branch mapset with a branch server as incompatable changes may occur. Meaning a map in trunk may only work with the trunk server and vice versa. + Notice: It is highly recommend that you use a trunk mapset with a trunk server and a branch mapset with a branch server as incompatible changes may occur. Meaning a map in trunk may only work with the trunk server and vice versa. === Trunk & Branch Commands: === @@ -57,5 +57,5 @@ This would check out the latest changes to maps 1.x branch and place them in the /share/crossfire/maps/ directory. ==== Browse the SVN Repository ==== - Latest SVN changes and history is availble at: http://crossfire.svn.sourceforge.net/viewvc/crossfire/ + Latest SVN changes and history is available at: http://crossfire.svn.sourceforge.net/viewvc/crossfire/ IP-Address : 216.195.168.209 Old Revision: http://wiki.metalforge.net/doku.php/downloading?rev=1184864187 New Revision: http://wiki.metalforge.net/doku.php/downloading -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Thu Jul 19 12:04:21 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Thu, 19 Jul 2007 12:04:21 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: races Message-ID: <1184864661.148464.2092.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/19 12:04 User : Edit Summary: Noted location of race stats table @@ -1,6 +1,7 @@ ====== The Races ====== FIXME Insert lore (be sure to link to [[:gods]] which links to creation myths, when mentioning creation of them) + ===== Player usable races ===== * {{:images:dwarf_p.base.151.png}} [[.races:Dwarves]] @@ -17,8 +18,9 @@ * {{:images:serpentman.base.151.png}} [[.races:Serpent Men]] * {{:images:troll_p.base.151.png}} [[.races:Trolls]] * {{:images:wraithp.base.151.png}} [[.races:Wraiths]] + There is a concise table of these stats at http://crossfire.real-time.com/guides/character/race.html ===== Other races of the world ===== * {{:races:air_elemental.png}} [[.races:Air Elementals]] IP-Address : 216.195.168.209 Old Revision: http://wiki.metalforge.net/doku.php/races?rev=1184861096 New Revision: http://wiki.metalforge.net/doku.php/races -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Thu Jul 19 22:16:13 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Thu, 19 Jul 2007 22:16:13 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev:spells Message-ID: <1184901373.178944.3450.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/19 22:16 User : Edit Summary: Spelling correction @@ -2,8 +2,9 @@ ===== Background ===== This document describe all things spell and spell related that developers need to know. This document outlines the new spell objects and how this all works. + ===== Spell objects ===== In the old model, each spell had a specific number associated with it. @@ -21,9 +22,9 @@ a spellbook is the spell in its inventory. This model makes it very easy to make variations of some spells. Want to make an extra large fireball? All this is needed is to take the - large fireball arch, increase a few parameters, and your all set. + large fireball arch, increase a few parameters, and you're all set. The following is the fields in the object structure, and how they correspond to a spell. Fields that are not mentioned are not used. IP-Address : 216.195.168.209 Old Revision: http://wiki.metalforge.net/doku.php/dev:spells?rev=1168902724 New Revision: http://wiki.metalforge.net/doku.php/dev:spells -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Fri Jul 20 01:48:39 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Fri, 20 Jul 2007 01:48:39 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:metaserver_improvements Message-ID: <1184914119.286763.3780.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/20 01:48 User : Edit Summary: @@ -14,8 +14,9 @@ Proposal for improvements: * All the fields currently present above * Codebase for server, maps, & archetypes. In this way, more readily apparantly what a server is running. This would be text provided by the server. + * Metaserver should include port number of the server, so it would be possible to have multiple servers running on the same host. * metaserver should confirm hostname matches IP address from request. This currently isn't feasible because doing nameservice lookups could time out, causing server to hang up * SC_VERSION and CS_VERSION of the server - in this way, client could filter out servers it know it couldn't support. * A text flags section - different flags have different, but standardized, meaning. $ could be pay to play, P means player killing, etc * Multiple metaservers, so there is not a single point of failure. IP-Address : 209.204.178.229 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:metaserver_improvements?rev=1184567388 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:metaserver_improvements -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 23 16:59:23 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 23 Jul 2007 16:59:23 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:functions_implemented_but_not_yet_used Message-ID: <1185227963.639249.12970.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/23 16:59 User : ryo Edit Summary: Python guilds @@ -29,4 +29,7 @@ Transports have been implemented and are active on metalforge for a long time now. But they are hardly used: two ships in Scorn's harbor (just for testing, not useful since you cannot reach any useful location), one in Stoneville. ===== background music ===== Maps can now have a 'background_music' tag, which will get sent to client when the player enters the map. No map has this set, no client has any handling, and it isn't determined what the tag means (specific music, music genre, ...) + + ===== Python-based guilds ===== + See [[python_guilds]]. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used?rev=1184534348 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Mon Jul 23 17:00:53 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Mon, 23 Jul 2007 17:00:53 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:functions_implemented_but_not_yet_used Message-ID: <1185228053.640078.12979.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/23 17:00 User : ryo Edit Summary: more @@ -32,4 +32,11 @@ Maps can now have a 'background_music' tag, which will get sent to client when the player enters the map. No map has this set, no client has any handling, and it isn't determined what the tag means (specific music, music genre, ...) ===== Python-based guilds ===== See [[python_guilds]]. + + ===== cflogger ===== + + sqlite-based event logger. Generates a database of all events (kills, map enter/leave, ...). + + ===== cfnewspaper ===== + Supposedly used to generate a newspaper. Uses cflogger to find information. Pre-alpha version, doesn't do much. IP-Address : 82.236.87.204 Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used?rev=1185227960 New Revision: http://wiki.metalforge.net/doku.php/dev_todo:functions_implemented_but_not_yet_used -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Tue Jul 24 11:00:58 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Tue, 24 Jul 2007 11:00:58 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: people Message-ID: <1185292858.376361.14862.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/24 11:00 User : Edit Summary: @@ -22,8 +22,9 @@ | Christian Hujer | | Cher | [[http://sourceforge.net/users/christianhujer|christianhujer]] | | [[http://www.riedquat.de]] | | Maarten Vanraes | [[user:alien]] | AL13N | [[http://sourceforge.net/users/alien999999999|alien999999999]] | | | | Mats Rauhala | | MasseR | | | | | Aaron Baugher | [[user:mhoram]] | Mhoram | [[http://sourceforge.net/users/aaron_baugher|aaron_baugher]] | | [[http://aaron.baugher.biz/|aaron.baugher.biz]] | + | Kevin Bulgrien | [[user:kbulgrien]] | kbulgrien | [[http://sourceforge.net/users/kbulgrien|kbulgrien]] | | [[http://kbulgrien.home.att.net/|kbulgrien.home.att.net]] | ===== Package Maintainers ===== ^ Full Name ^ irc ^ Distribution ^ IP-Address : 70.255.81.125 Old Revision: http://wiki.metalforge.net/doku.php/people?rev=1174877762 New Revision: http://wiki.metalforge.net/doku.php/people -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Tue Jul 24 13:35:26 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Tue, 24 Jul 2007 13:35:26 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: guides Message-ID: <1185302126.420586.15105.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/24 13:35 User : Edit Summary: typo fix @@ -2,13 +2,14 @@ Within are several guides detailing various aspects of the game. ===== Map Guides ===== These are various guides to help people find their way around the world. + ==== General Guides ==== Documents that don't fit in the other categories. * [[Beginer's Atlas]] - A [uncompleted] guide to the default mapset. - * [[Landforms]] - A document aimed at mapers. It shows the names of various areas inside the default maps. + * [[Landforms]] - A document aimed at mappers. It shows the names of various areas inside the default maps. ==== Areas ==== Documents relating to specific places IP-Address : 70.255.81.125 Old Revision: http://wiki.metalforge.net/doku.php/guides?rev=1184618539 New Revision: http://wiki.metalforge.net/doku.php/guides -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Tue Jul 24 14:17:47 2007 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Tue, 24 Jul 2007 14:17:47 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page added: skills:lockpicking Message-ID: <1185304667.380899.15177.nullmailer@wiki.metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2007/07/24 14:17 User : Edit Summary: created ====== Description ====== The user may attempt to pick locks, obviating the need for a key. If lockpicking fails to unlock an item, repeated attempts may be successful. ====== Use Skill ====== When facing a locked item, an attempt is made to pick the lock. ====== Ready Skill ====== Makes lockpicking the active skill. Subsequently, firing in the direction of the locked item makes an attempt to pick the lock. IP-Address : 70.255.81.125 Old Revision: none New Revision: http://wiki.metalforge.net/doku.php/skills:lockpicking -- This mail was generated by DokuWiki at http://wiki.metalforge.net/