cf.schmorp.de/arch/Naming.doc

image-file

   name.xfa.size.png

   x = "x" (signifying a bigface without splitting)
   f = facing
   a = animation frame
   size = base tile size, 32x32 or 64x64

Rest of this file describes the old numbering scheme.

archetype-file  NAME.arc

image-file      NAME.PDA

        where
                P - part number
                D - coding, or any other instance
                    coding in 
                A - animation phase
numbering, PDA
        - 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F,G,...,Z
        - alphanumerics
        - can be thought as hexadecimals

name NAME:
        - maximum 10 characters long, so max file name is 14 characters,
          that fit into portability requirements:

Part numbers
        3x3
                1 2 3
                4 5 6
                7 8 9
        2x2
                1 2
                3 4
        3x2
                1 2 3
                4 5 6
        2x3
                1 2
                3 4
                5 6
codings:
        direction:

                8  1  2
                 \ | /
                7- 0 -3
                 / | \
                6  5  4
        
        - same as in crossfire

        turnable (reflecting objects):
                0 to left, vertical
                1 to right, horizontal
        - also in gates,signs, ...

walls:
                   1
                   |
                8 -+- 2
                   |
                   4

        - bit-combination; eg. 8 + 4 + 2 + 1 = F is cross,
          4 + 1 = 5 is vertical wall.

river:

    The non branched rivers are stored as river_XY.arc and river_XY.PDA
    The XY use the direction scheme above (that is, river_15 runs
    north/south).  As of now, D and A are always 1.  P will be up to
    3, as rivers that run diagonally have wedges for the corners of the
    adjacent spaces.  These wedges are stored as river_48.211, river_48.311,
    river_26.211 and river_26.311.  The archetypes for these are stored
    in river_48.arc and river_26.arc.

    Junctions are of the form branch_XYZ.[arc/111].  XYZ reperesent the
    three directions the river exits.  367 would be east,southwest, and
    west.  Junctions may also have multiple parts - this happens when
    the junction has a diagonal direction.

    By convention, all directions for the river parts are in ascending
    order.  That is to say if the exit locations are 2,6,3, that would
    be stored as branch_236.

cave:
        -complex

modified:
        93/08 hevi@lut.fi - created
        94/05 master@rahul.net - updated river definitions.

### end of README ###
Revision:	1.2
Committed:	Sat May 26 15:20:40 2007 UTC (19 years, 5 months ago) by root
Content type:	application/msword
Branch:	MAIN
CVS Tags:	rel-2_82, rel-2_81, rel-2_80, rel-3_0, rel-2_6, rel-2_7, rel-2_4, rel-2_5, rel-2_2, rel-2_1, rel-2_72, rel-2_73, rel-2_71, rel-2_76, rel-2_77, rel-2_74, rel-2_75, rel-2_54, rel-2_55, rel-2_56, rel-2_79, rel-2_53, rel-2_32, rel-2_90, rel-2_92, rel-2_93, rel-2_78, rel-2_61, rel-2_43, rel-2_42, rel-2_41, HEAD
Changes since 1.1:	+11 -0 lines
Log Message:	* empty log message *
#	User	Rev	Content
1	root	1.2	image-file
2
3			name.xfa.size.png
4
5			x = "x" (signifying a bigface without splitting)
6			f = facing
7			a = animation frame
8			size = base tile size, 32x32 or 64x64
9
10			Rest of this file describes the old numbering scheme.
11
12	root	1.1	archetype-file NAME.arc
13
14			image-file NAME.PDA
15
16			where
17			P - part number
18			D - coding, or any other instance
19			coding in
20			A - animation phase
21			numbering, PDA
22			- 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F,G,...,Z
23			- alphanumerics
24			- can be thought as hexadecimals
25
26			name NAME:
27			- maximum 10 characters long, so max file name is 14 characters,
28			that fit into portability requirements:
29
30			Part numbers
31			3x3
32			1 2 3
33			4 5 6
34			7 8 9
35			2x2
36			1 2
37			3 4
38			3x2
39			1 2 3
40			4 5 6
41			2x3
42			1 2
43			3 4
44			5 6
45			codings:
46			direction:
47
48			8 1 2
49			\ \| /
50			7- 0 -3
51			/ \| \
52			6 5 4
53
54			- same as in crossfire
55
56			turnable (reflecting objects):
57			0 to left, vertical
58			1 to right, horizontal
59			- also in gates,signs, ...
60
61			walls:
62			1
63			\|
64			8 -+- 2
65			\|
66			4
67
68			- bit-combination; eg. 8 + 4 + 2 + 1 = F is cross,
69			4 + 1 = 5 is vertical wall.
70
71			river:
72
73			The non branched rivers are stored as river_XY.arc and river_XY.PDA
74			The XY use the direction scheme above (that is, river_15 runs
75			north/south). As of now, D and A are always 1. P will be up to
76			3, as rivers that run diagonally have wedges for the corners of the
77			adjacent spaces. These wedges are stored as river_48.211, river_48.311,
78			river_26.211 and river_26.311. The archetypes for these are stored
79			in river_48.arc and river_26.arc.
80
81			Junctions are of the form branch_XYZ.[arc/111]. XYZ reperesent the
82			three directions the river exits. 367 would be east,southwest, and
83			west. Junctions may also have multiple parts - this happens when
84			the junction has a diagonal direction.
85
86			By convention, all directions for the river parts are in ascending
87			order. That is to say if the exit locations are 2,6,3, that would
88			be stored as branch_236.
89
90			cave:
91			-complex
92
93			modified:
94			93/08 hevi@lut.fi - created
95			94/05 master@rahul.net - updated river definitions.
96
97			### end of README ###