36 lines
1.9 KiB
Plaintext
36 lines
1.9 KiB
Plaintext
This is a README for the Developers directory for crossfire.
|
|
|
|
This directory contains files of interest to those that actually develop
|
|
crossfire (map makers, coders, etc). Files in this directory are not likely
|
|
to be of interest to just players. This README also contains a brief
|
|
summary of each file in this directory.
|
|
|
|
If you add a file to this directory, please update this file. Also,
|
|
user lowercase names for the files, and the addition of readme or doc or
|
|
txt to the file name is not needed - that is implied in the doc directory.
|
|
|
|
svn: Guidelines for developers working with SVN access - guidelines
|
|
for discussing new projects, commit messages, etc.
|
|
images: Guide for adding image sets to crossfire.
|
|
map-technical: Technical aspect of maps - fields in the map header (and
|
|
structure), format for the map files.
|
|
mapguide: Do's and Don'ts when making new maps.
|
|
objects: Explains the different fields/values for the objects, as well as
|
|
breakdowns for a some specific objects (was crossfire.doc)
|
|
plugins: information on plugins, not as up to date as plugins.ps.
|
|
plugins.ps: Describes technical information, and the various events that plugins
|
|
can be connected to.
|
|
programming_guide: Hints, style guide, and directions for coders as well
|
|
as information on sending in patches.
|
|
protocol: Describes the client/server protocol.
|
|
python: python documentation, not up to date (see python.ps).
|
|
python.ps: Contains the crossfire python extensions usable by the plugins.
|
|
random-maps: How to use and options for randomly generated maps.
|
|
random-styles: Description of the various style maps used with the random maps.
|
|
runes: Explains how to use runes on maps, different fields in the runes.
|
|
skills: Directions for adding in skills, as well as how the skill system
|
|
works.
|
|
teleporters: Mapmaker guide for putting teleporters on to maps.
|
|
testplans: Contains various testplans that can be run to help verify
|
|
proper operation of changes made.
|