| 1 |
This is a README for the Developers directory for crossfire. |
| 2 |
|
| 3 |
This directory contains files of interest to those that actually develop |
| 4 |
crossfire (map makers, coders, etc). Files in this directory are not likely |
| 5 |
to be of interest to just players. This README also contains a brief |
| 6 |
summary of each file in this directory. |
| 7 |
|
| 8 |
If you add a file to this directory, please update this file. Also, |
| 9 |
user lowercase names for the files, and the addition of readme or doc or |
| 10 |
txt to the file name is not needed - that is implied in the doc directory. |
| 11 |
|
| 12 |
cvs: Guidelines for developers working with CVS access - guidelines |
| 13 |
for discussing new projects, commit messages, etc. |
| 14 |
images: Guide for adding image sets to crossfire. |
| 15 |
map-technical: Technical aspect of maps - fields in the map header (and |
| 16 |
structure), format for the map files. |
| 17 |
mapguide: Do's and Don'ts when making new maps. |
| 18 |
objects: Explains the different fields/values for the objects, as well as |
| 19 |
breakdowns for a some specific objects (was crossfire.doc) |
| 20 |
plugins: Describes technical information, and the various events that plugins |
| 21 |
can be connected to. |
| 22 |
programming_guide: Hints, style guide, and directions for coders as well |
| 23 |
as information on sending in patches. |
| 24 |
protocol: Describes the client/server protocol. |
| 25 |
python: Contains the crossfire python extensions usable by the plugins. |
| 26 |
quests: How to manage player quests. Technical implementation details. |
| 27 |
random-maps: How to use and options for randomly generated maps. |
| 28 |
random-styles: Description of the various style maps used with the random maps. |
| 29 |
runes: Explains how to use runes on maps, different fields in the runes. |
| 30 |
skills: Directions for adding in skills, as well as how the skill system |
| 31 |
works. |
| 32 |
teleporters: Mapmaker guide for putting teleporters on to maps. |
| 33 |
testplans: Contains various testplans that can be run to help verify |
| 34 |
proper operation of changes made. |
