[ViewVC] Annotation of: cvs/deliantra/server/lib/image_info

# "$Id$";
#
# This file describes the various image files installed.
# For more information on how all this works and about adding new
# image sets, see the doc/Developer/images file.
#
# The format of each line:
# num:extension:long name:fallback:geometry:extension:description
# num is the set number.
# extension is the extension that image set uses (eg, base, clsc)
# long name is just that - a longer (more english) name, eg, classic instead
#   of clsc.  This is really just used by the client for it to map the
#   image names.  Its not really intuitive for users to say -image clsc
# fallback is what set to fallback to if the image does not exist in
#   that set.  In the end, all sets must fall back to set 0.
# geometry is in width x height form.  This is used by the client so it
#   knows the spacing to use.  Images in the set could be of different
#   sizes (eg, a 4 spaces image would be larger), but this is the normal
#   spacing that the client should use.
# extension is for future use - it is passed to the client.  This is mostly
#   here so that the client can know specific information about certain
#   image sets.
# description is just a longer description that the client can display to the
#   user.
#
# NOTE: lines can not be continued with \ - everything must be on one line
#  for things to work.
# Lines that start with # are obviously ignored.
0:base:standard:0:32x32:none:The standard image set.
Revision:	1.2
Committed:	Mon May 8 08:23:12 2006 UTC (18 years ago) by pippijn
Branch:	MAIN
CVS Tags:	rel-2_0, rel-2_1, LAST_C_VERSION, STABLE, difficulty_fix_merge_060810_2300
Branch point for:	difficulty_fix
Changes since 1.1:	+1 -2 lines
Log Message:	Nuked the classic tileset out of image_info. This will now prevent crossfire.1 from being generated.
#	User	Rev	Content
1	pippijn	1.2	# "$Id$";
2	root	1.1	#
3			# This file describes the various image files installed.
4			# For more information on how all this works and about adding new
5			# image sets, see the doc/Developer/images file.
6			#
7			# The format of each line:
8			# num:extension:long name:fallback:geometry:extension:description
9			# num is the set number.
10			# extension is the extension that image set uses (eg, base, clsc)
11			# long name is just that - a longer (more english) name, eg, classic instead
12			# of clsc. This is really just used by the client for it to map the
13			# image names. Its not really intuitive for users to say -image clsc
14			# fallback is what set to fallback to if the image does not exist in
15			# that set. In the end, all sets must fall back to set 0.
16			# geometry is in width x height form. This is used by the client so it
17			# knows the spacing to use. Images in the set could be of different
18			# sizes (eg, a 4 spaces image would be larger), but this is the normal
19			# spacing that the client should use.
20			# extension is for future use - it is passed to the client. This is mostly
21			# here so that the client can know specific information about certain
22			# image sets.
23			# description is just a longer description that the client can display to the
24			# user.
25			#
26			# NOTE: lines can not be continued with \ - everything must be on one line
27			# for things to work.
28			# Lines that start with # are obviously ignored.
29			0:base:standard:0:32x32:none:The standard image set.