From no-reply_wiki at metalforge.org Tue May 6 15:28:40 2008
From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org)
Date: Tue, 06 May 2008 15:28:40 -0500
Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: map_making
Message-ID: <1210105720.432851.6688.nullmailer@wiki.metalforge.net>
A page in your DokuWiki was added or changed. Here are the details:
Date : 2008/05/06 15:28
User : ryo
Edit Summary: map tags
@@ -76,8 +76,19 @@
- Don't put monsters of high experience points near to entrance where they are trapped as this might allow low level players to boost their experience high by using some weapons or spells from distance, but without danger. For example find a trapped troll and get wand of fireball.
- Monsters on top of other monsters. A troll should not be sitting on top of an oriental dragon. The only exception to this would be if a monster could be on top of another monster (making sense) and hiding it at the same time. A troll on top of an oriental dragon does not make sense (could not fit), nor can the troll hide the oriental dragon. Using tricks like these which are only applicable due to display limitations is something that should not be done, nor should the player need to click on every monster he encounters to see if something is below it. (As a side note, doing this will tend to lock the monsters into position, making them unable to move.)
- Large groups of monsters that can be killed quickly with spells. A fairly popular tactic to make high level maps is just to put 30 dragons (or other tough monsters) in a big room. Do not do this. All the player needs to do is cast a dozen ice storms, and quickly gets millions of experience. Likewise, it is unlikely that any more than 2 or 3 large (multi square) monsters will be able to attack a player or party at once - the remaining 25 will be blocked from doing anything. This then makes it so that having 30 dragons is not any tougher than having 3.
+ ==== Map tags ====
+ (the tags are applicable to trunk maps only)
+
+ The [[crossfire-mapper|Crossfire mapper]] tool can take advantage of special tags in the ''lore'' field to logically link maps together and display their information in a summed way.
+
+ The following tags can be used:
+ * ''@def quest name'': defines a quest with the specified name. Note that this does not link the map to the quest thus defined
+ * ''@quest quest name'': links the map to the quest with the specified name
+ * ''@end'': end of one of the previous tags. You can omit it if the text extends until the end of the lore field
+
+ The text from the tag to the end marker is free-form, though it should be HTML (as this is what mapper generates). Basically, ''@def'' is meant to describe the quest in detail, including rewards and such, while ''@quest'' is intended to specify where to find items or NPCs or such.
==== General Suggestions ====
* If you want to make a high level map, instead of tossing a lot of monsters on it, take existing monsters and make them tougher. Increase their hit points, level (which then means spells they use do more damage), add immunities or protections, remove vulnerabilities, change attack types, etc. Try not to totally change the characteristics of a known monster - a normal dragon should still be dragon like. Also, remember to adjust experience that the monster gives.
@@ -188,5 +199,4 @@
* If you would like to sign up for the Crossfire Maps mailing list, visit https://lists.sourceforge.net/lists/listinfo/crossfire-maps
==== Trunk or Branch ? ====
Brand new content that has never been seen before and is not an update or patch of existing maps should go into trunk. Updates and patches to existing maps should go into trunk and branch.
-
IP-Address : 82.236.87.204
Old Revision: http://wiki.metalforge.net/doku.php/map_making?rev=1199652777
New Revision: http://wiki.metalforge.net/doku.php/map_making
--
This mail was generated by DokuWiki at
http://wiki.metalforge.net/
From no-reply_wiki at metalforge.org Tue May 6 15:38:18 2008
From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org)
Date: Tue, 06 May 2008 15:38:18 -0500
Subject: [Crossfire-wiki] [Crossfire DokuWiki] page added: crossfire-mapper
Message-ID: <1210106298.389601.6704.nullmailer@wiki.metalforge.net>
A page in your DokuWiki was added or changed. Here are the details:
Date : 2008/05/06 15:38
User : ryo
Edit Summary: created
**Crossfire mapper** is a tool, in ''trunk'' SVN (server/utils), that generates a catalog of maps.
The following information is generated:
* a page per map
* a page per region
* a global map index
* the world map, including regions information
* the world map, with exits and blocking zones
* the world map, with elevation information.
This program browses maps from the first map (HallOfSelection), only maps linked from there will be processed.
Maps are generated as the server sees them, that is with weather effects, treasures instead of markers, and things like that, unless the ''-rawmaps'' parameter is used.
For maps, 2 pictures are generated, one real size and one small-size.
Three maps are generated for the world: raw world map, world map with region information, region information only.
Maps are always sorted, by the map name (part after the last /).
Files are generated based on templates, where tags are replaced by their runtime value.
Launching the program without any argument will make it generate the files in ''working-directory/html''.
This program is not part of the build process. To build it, you need the //GD// library. Command line from the ''utils'' directory is:
gcc mapper.c -I../include ../common/libcross.a -o crossfire-mapper -lm -lgd
The following command line parameters are availble:
| -nopics | don't generate pictures. |
| -noindex | don't generate global map index. |
| -root= | destination path. Default 'html'. |
| -limit= | stop processing after this number of maps, -1 to do all maps (default). |
| -showmaps | outputs the name of maps as they are processed. |
| -jpg[=quality] | generate jpg pictures, instead of default png. Quality should be 0-95, -1 for automatic. |
| -forcepics | force to regenerate pics, even if pics's date is after map's. |
| -addmap=