Path Files

For convention each area model has a name pattern:

• levelinitials_typeID_beginID_endID_variationID - example: tv_t0_b0_e0_v0
• tv - Stands for toad-village based levels.
• t[n] - TypeID of model
• b[n]e[n] - Stands for begin and end of area model
• v[n] - Variation

Official table

TypeID	Stands-for
0	normal
1	with elements such water
2	contains killzone
3	x-axis different from level pattern

About b[n]e[n]

Think each area model as a puzzle piece, so to fit then correctly you need the right pieces, e.g ` a - tv_t0_b0_e1_v0 b - tv_t1_b1_e0_v0 c - tv_t2_b3_e0_v0 d - tv_t3_b0_e2_v0

'a' can have 'b' after it, but not 'c' and 'd', for simplicity each endID must be equal beginID. why this is necessary? Imagine a path sequenque that go downwards and this path model has a mesh finishing with it faces at 45 degrees the next path needs to start with a mesh at 45degress to fit nicely with the previous path. `