Go to file
ryo_saeba e62fe5416c Remove obsolete field.
git-svn-id: svn+ssh://svn.code.sf.net/p/crossfire/code/arch/trunk@6566 282e977c-c81d-0410-88c4-b93c2d0d6712
2007-06-13 19:49:48 +00:00
armour Remove obsolete editable field. 2007-06-13 18:16:33 +00:00
connect Remove obsolete field. 2007-06-13 18:30:51 +00:00
construct Remove obsolete editable field. 2007-06-13 18:28:58 +00:00
dev Remove obsolete fields. 2007-05-20 20:04:32 +00:00
disease Remove obsolete field. 2007-06-13 18:32:52 +00:00
door Remove obsolete field. 2007-06-13 18:33:26 +00:00
exit Remove obsolete field. 2007-06-13 18:34:28 +00:00
flesh Remove obsolete field. 2007-06-13 18:35:47 +00:00
floor Fix spelling errors. 2007-05-10 20:26:17 +00:00
food Remove obsolete field. 2007-06-13 18:36:34 +00:00
gods Remove obsolete field. 2007-06-13 18:38:26 +00:00
ground Remove obsolete field. 2007-06-13 18:41:05 +00:00
indoor Remove obsolete field. 2007-06-13 18:42:52 +00:00
inorganic Remove obsolete field. 2007-06-13 18:44:02 +00:00
jewel Remove obsolete field. 2007-06-13 18:45:11 +00:00
light Remove obsolete field. 2007-06-13 18:46:39 +00:00
mapbuilding Remove obsolete field. 2007-06-13 18:46:54 +00:00
misc Remove obsolete field. 2007-06-13 18:49:39 +00:00
monster Remove obsolete field. 2007-06-13 19:01:22 +00:00
optical Remove obsolete field. 2007-06-13 19:19:40 +00:00
planes/fire Remove obsolete field. 2007-06-13 19:21:09 +00:00
player Remove obsolete field. 2007-06-13 19:22:28 +00:00
potion Remove obsolete field. 2007-06-13 19:23:00 +00:00
random Remove obsolete field. 2007-06-13 19:23:22 +00:00
readable Remove obsolete field. 2007-06-13 19:24:03 +00:00
river Remove obsolete field. 2007-06-13 19:24:49 +00:00
shop Remove obsolete field. 2007-06-13 19:25:41 +00:00
skills Remove obsolete field. 2007-06-13 19:49:48 +00:00
spell Remove obsolete fields. 2007-05-20 19:58:30 +00:00
system Remove quest archetypes, as quest support will be removed/rewritten. 2007-06-09 09:00:11 +00:00
talisman Name is useful, else weird things. 2007-06-09 10:40:53 +00:00
transport Converting multi-tile image arches to single images 2007-02-16 20:49:10 +00:00
traps Moved parts of the static treasures file into separate trs files. 2006-12-30 19:40:30 +00:00
wall Name is useful, else weird things. 2007-06-09 10:40:53 +00:00
weapon Name is useful, else weird things. 2007-06-09 10:40:53 +00:00
CHANGES Replace "object xxx" with "Object xxx". 2007-06-12 20:20:23 +00:00
Naming.doc See CHANGES file. 2000-04-17 14:37:09 +00:00
README Fix typo. 2004-10-09 15:55:24 +00:00
TODO Fix typo. 2004-10-09 15:55:24 +00:00

README

This is a generic README file for the arch directory.
You should also read the CHANGES for and Naming.doc file.

 The color bitmap files use the XPM library (called xpm-3.4f on
most ftp sites.  A later version may be out now.)

 This library is needed in order to compile crossfire with the color
pixmap support.

 The pixmap files have the same name as the bitmap file with ".xpm"
concatenated to the end.  If your system has short filename length
limits, this may cause a problem.

 I use 'pixmap' to edit the xpm files.  This should be available the
same place the xpm library can be found.  It does require the xpm
library.

All of the XPM files have been colored.  However, only a small number
have actually been done so properly - that is, by hand, and with the
proper outlines.  Many people are working on fixing more of these up.

 If you do start to work on colorizing the other directories, please
let me know.  Otherwise, you may start working on something that someone
else has already done.

The file xpm.template in the dev directory is a XPM file that has all of
the colors that are allowable for XPM files.  This is to limit the total
number of colors used, in order not of overrun color spaces on systems.
If you really need a color not in that file, please send mail to Mark
Wedel (mwedel@pyramid.com), and it might be added to the list of
acceptable colors.

For a list of colors to use, look at the dev/xpm.template file.


 Mark Wedel
mwedel@pyramid.com
----
Some coloring/perspective hints/clarifications from David Sundqvist:

Perspective in Crossfire is based on the XY coordinate system of possible
player movements, with a slight tilting of the graphics to allow for
greater detail and more interesting graphics, since walls have to be in
that perspective to allow joining. X and Y in graphics should correspond
to X and Y in the object. Z in the object is represented with 2 Y/X.
Keeping perspective consistency is mainly important in fixed objects
like buildings, walls and other background.

Light should generally come from the right side, so the left side of
buildings should be darker or shaded, as needed. 

Wind is generally coming from the left side, so smoke or other things
affected by wind should be travelling towards the right side.