sprite and spriteassembler update

assets/mods/basegame/sprites/taimu.properties

@@ -1,37 +1,45 @@
 # complete file name is: SPRITESHEET + bodypart name + EXTENSION
 SPRITESHEET=mods/basegame/sprites/test_werebeastf/taimu_
 EXTENSION=.tga
-# defines frame size and origin point. Origin point is given as: (originx, size.y - 1)
-# ORIGINY is deduced from the sprite size as shown in above; you only need to set ORIGINX
+# defines frame size and origin point. Origin point is given as: (originx, 0)
 CONFIG=SIZE 64,98;ORIGINX 40
 
-# note to self: don't implement skeleton hierarchy: there's too many exceptions
-# besides, you have "ALL" key.
-
-! a skeleton also defines what body parts (images) be used.
-! you can also write multiline text using reverse solidus; this is a feature of .properties
+! A skeleton also defines what body parts (images) be used.
+! You can also write multiline text using reverse solidus; this is a feature of .properties
 ! skeleton joints are ordered: foremost-drawn object comes first, which means lowermost object IN THIS LIST
 !   are painted first, and any object that comes before it will paint over it. In other words, this list is
 !   first reversed then being iterated.
-! Joints' original point is defined in the document sprite_joints.psd. It also has visual representations.
-# TODO right now accessory points are explicitly defined. Should they be injected in run-time?
-SKELETON_STAND=HEADGEAR 0,32;\
-               ARM_REST_LEFT -9,49;HELD_ITEM -6,11;\
-               HEAD 2,83;\
-               BUST_0 4,60;\
-               TORSO_0 0,55;\
-               TORSO_1 0,55;\
-               LEG_REST_RIGHT -6,22;\
-               LEG_REST_LEFT 7,22;\
-               ARM_REST_RIGHT 12,51;\
-               TAIL_0 -11,27
+! Some keywords are considered special within the game, they are:
+!   HEADGEAR, HELD_ITEM, BOOT_L, BOOT_R, GAUNTLET_L, GAUNTLET_R and ARMOUR_* (star means any number starting from zero)
+BODYPARTS=HEADGEAR 13,14;\
+          HEAD 13,14;\
+          ARM_REST_RIGHT 5,3;\
+          ARM_REST_LEFT 6,3;\
+          LEG_REST_RIGHT 12,6;\
+          LEG_REST_LEFT 8,6;\
+          TORSO_0 18,19;\
+          TORSO_1 18,19;\
+          TAIL_0 30,2;\
+          BUST_0 11,2;\
+          HELD_ITEM 0,0
+SKELETON_STAND=HEADGEAR 0,78;\
+               ARM_REST_RIGHT -15,66;\
+               HELD_ITEM -11,33;\
+               HEAD 0,78;\
+               BUST_0 0,63;\
+               TORSO_0 0,54;\
+               TORSO_1 0,54;\
+               LEG_REST_RIGHT -5,41;\
+               LEG_REST_LEFT 3,41;\
+               ARM_REST_LEFT 8,66;\
+               TAIL_0 2,40
 
 # skeleton_stand is used for testing purpose
 ANIM_RUN=DELAY 0.3;ROW 2;SKELETON SKELETON_STAND
-ANIM_RUN_1=LEG_REST_RIGHT 2,2;LEG_REST_LEFT -2,0;TAIL_0 1,0
-ANIM_RUN_2=ALL 0,2;LEG_REST_RIGHT 0,-2;LEG_REST_LEFT 0,2;TAIL_0 -1,0
-ANIM_RUN_3=LEG_REST_RIGHT -2,0;LEG_REST_LEFT 2,2;TAIL_0 -1,0
-ANIM_RUN_4=ALL 0,2;LEG_REST_RIGHT 0,2;LEG_REST_LEFT 0,-2;TAIL_0 1,0
+ANIM_RUN_1=LEG_REST_RIGHT 2,2;LEG_REST_LEFT -2,0;TAIL_0 1,0;TORSO_1 0,-999
+ANIM_RUN_2=ALL 0,2;LEG_REST_RIGHT 0,-2;LEG_REST_LEFT 0,2;TAIL_0 -1,0;TORSO_1 0,-999
+ANIM_RUN_3=LEG_REST_RIGHT -2,0;LEG_REST_LEFT 2,2;TAIL_0 -1,0;TORSO_1 0,-999
+ANIM_RUN_4=ALL 0,2;LEG_REST_RIGHT 0,2;LEG_REST_LEFT 0,-2;TAIL_0 1,0;TORSO_1 0,-999
 
 ANIM_IDLE=DELAY 2;ROW 1;SKELETON SKELETON_STAND
 ANIM_IDLE_1=TORSO_1 0,-999;HEAD 0,-1

assets/mods/basegame/sprites/taimu_glow.properties

@@ -1,37 +1,45 @@
 # complete file name is: SPRITESHEET + bodypart name + EXTENSION
 SPRITESHEET=mods/basegame/sprites/test_werebeastf/taimuglow_
 EXTENSION=.tga
-# defines frame size and origin point. Origin point is given as: (originx, size.y - 1)
-# ORIGINY is deduced from the sprite size as shown in above; you only need to set ORIGINX
+# defines frame size and origin point. Origin point is given as: (originx, 0)
 CONFIG=SIZE 64,98;ORIGINX 40
 
-# note to self: don't implement skeleton hierarchy: there's too many exceptions
-# besides, you have "ALL" key.
-
-! a skeleton also defines what body parts (images) be used.
-! you can also write multiline text using reverse solidus; this is a feature of .properties
+! A skeleton also defines what body parts (images) be used.
+! You can also write multiline text using reverse solidus; this is a feature of .properties
 ! skeleton joints are ordered: foremost-drawn object comes first, which means lowermost object IN THIS LIST
 !   are painted first, and any object that comes before it will paint over it. In other words, this list is
 !   first reversed then being iterated.
-! Joints' original point is defined in the document sprite_joints.psd. It also has visual representations.
-# TODO right now accessory points are explicitly defined. Should they be injected in run-time?
-SKELETON_STAND=HEADGEAR 0,32;\
-               ARM_REST_LEFT -8,49;HELD_ITEM -6,11;\
-               HEAD 2,83;\
-               BUST_0 4,60;\
-               TORSO_0 0,55;\
-               TORSO_1 0,55;\
-               LEG_REST_RIGHT -5,22;\
-               LEG_REST_LEFT 6,22;\
-               ARM_REST_RIGHT 11,51;\
-               TAIL_0 -11,27
+! Some keywords are considered special within the game, they are:
+!   HEADGEAR, HELD_ITEM, BOOT_L, BOOT_R, GAUNTLET_L, GAUNTLET_R and ARMOUR_* (star means any number starting from zero)
+BODYPARTS=HEADGEAR 13,14;\
+          HEAD 13,14;\
+          ARM_REST_RIGHT 5,3;\
+          ARM_REST_LEFT 6,3;\
+          LEG_REST_RIGHT 12,6;\
+          LEG_REST_LEFT 8,6;\
+          TORSO_0 18,19;\
+          TORSO_1 18,19;\
+          TAIL_0 30,2;\
+          BUST_0 11,2;\
+          HELD_ITEM 0,0
+SKELETON_STAND=HEADGEAR 0,78;\
+               ARM_REST_RIGHT -15,66;\
+               HELD_ITEM -11,33;\
+               HEAD 0,78;\
+               BUST_0 0,63;\
+               TORSO_0 0,54;\
+               TORSO_1 0,54;\
+               LEG_REST_RIGHT -5,41;\
+               LEG_REST_LEFT 3,41;\
+               ARM_REST_LEFT 8,66;\
+               TAIL_0 2,40
 
 # skeleton_stand is used for testing purpose
 ANIM_RUN=DELAY 0.3;ROW 2;SKELETON SKELETON_STAND
-ANIM_RUN_1=LEG_REST_RIGHT 2,2;LEG_REST_LEFT -2,0;TAIL_0 1,0
-ANIM_RUN_2=ALL 0,2;LEG_REST_RIGHT 0,-2;LEG_REST_LEFT 0,2;TAIL_0 -1,0
-ANIM_RUN_3=LEG_REST_RIGHT -2,0;LEG_REST_LEFT 2,2;TAIL_0 -1,0
-ANIM_RUN_4=ALL 0,2;LEG_REST_RIGHT 0,2;LEG_REST_LEFT 0,-2;TAIL_0 1,0
+ANIM_RUN_1=LEG_REST_RIGHT 2,2;LEG_REST_LEFT -2,0;TAIL_0 1,0;TORSO_1 0,-999
+ANIM_RUN_2=ALL 0,2;LEG_REST_RIGHT 0,-2;LEG_REST_LEFT 0,2;TAIL_0 -1,0;TORSO_1 0,-999
+ANIM_RUN_3=LEG_REST_RIGHT -2,0;LEG_REST_LEFT 2,2;TAIL_0 -1,0;TORSO_1 0,-999
+ANIM_RUN_4=ALL 0,2;LEG_REST_RIGHT 0,2;LEG_REST_LEFT 0,-2;TAIL_0 1,0;TORSO_1 0,-999
 
 ANIM_IDLE=DELAY 2;ROW 1;SKELETON SKELETON_STAND
 ANIM_IDLE_1=TORSO_1 0,-999;HEAD 0,-1

assets/mods/basegame/sprites/test_sprite.properties

@@ -1,20 +1,29 @@
 # complete file name is: SPRITESHEET + bodypart name + EXTENSION
 SPRITESHEET=mods/basegame/sprites/sprite_assembler_test_assets/test_
 EXTENSION=.tga
-# defines frame size and origin point. Origin point is given as: (originx, size.y - 1)
-# ORIGINY is deduced from the sprite size as shown in above; you only need to set ORIGINX
+# defines frame size and origin point. Origin point is given as: (originx, 0)
 CONFIG=SIZE 48,56;ORIGINX 29
 
-# note to self: don't implement skeleton hierarchy: there's too many exceptions
-# besides, you have "ALL" key.
-
-! a skeleton also defines what body parts (images) be used.
-! you can also write multiline text using reverse solidus; this is a feature of .properties
+! A skeleton also defines what body parts (images) be used.
+! You can also write multiline text using reverse solidus; this is a feature of .properties
 ! skeleton joints are ordered: foremost-drawn object comes first, which means lowermost object IN THIS LIST
 !   are painted first, and any object that comes before it will paint over it. In other words, this list is
 !   first reversed then being iterated.
-! Joints' original point is defined in the document sprite_joints.psd. It also has visual representations.
-# TODO right now accessory points are explicitly defined. Should they be injected in run-time? In that case, certain names (e.g. headgear, held_item) will act as an anchor.
+! Some keywords are considered special within the game, they are:
+!   HEADGEAR, HELD_ITEM, BOOT_L, BOOT_R, GAUNTLET_L, GAUNTLET_R and ARMOUR_* (star means any number starting from zero)
+BODYPARTS=ARM_REST_RIGHT 3,8;\
+          ARM_REST_LEFT 3,8;\
+          FOOT_LEFT 4,2;\
+          FOOT_RIGHT 4,2;\
+          UPPER_TORSO 9,4;\
+          LOWER_TORSO 7,4;\
+          LEG_REST_RIGHT 3,7;\
+          LEG_REST_LEFT 3,7;\
+          HEAD 8,7;\
+          HAND_REST_RIGHT 3,3;\
+          HAND_REST_LEFT 3,3;\
+          HAIR 20,12;\
+          HAIR_FORE 20,12
 SKELETON_STAND=HEADGEAR 0,32;HAIR_FORE 0,32;\
                ARM_REST_RIGHT -7,23;HAND_REST_RIGHT -6,11;HELD_ITEM -6,11;\
                HAIR 0,32;HEAD 0,32;\

assets/mods/basegame/sprites/test_sprite_glow.properties

@@ -1,20 +1,29 @@
 # complete file name is: SPRITESHEET + bodypart name + EXTENSION
 SPRITESHEET=mods/basegame/sprites/sprite_assembler_test_assets/testglow_
 EXTENSION=.tga
-# defines frame size and origin point. Origin point is given as: (originx, size.y - 1)
-# ORIGINY is deduced from the sprite size as shown in above; you only need to set ORIGINX
+# defines frame size and origin point. Origin point is given as: (originx, 0)
 CONFIG=SIZE 48,56;ORIGINX 29
 
-# note to self: don't implement skeleton hierarchy: there's too many exceptions
-# besides, you have "ALL" key.
-
-! a skeleton also defines what body parts (images) be used.
-! you can also write multiline text using reverse solidus; this is a feature of .properties
+! A skeleton also defines what body parts (images) be used.
+! You can also write multiline text using reverse solidus; this is a feature of .properties
 ! skeleton joints are ordered: foremost-drawn object comes first, which means lowermost object IN THIS LIST
 !   are painted first, and any object that comes before it will paint over it. In other words, this list is
 !   first reversed then being iterated.
-! Joints' original point is defined in the document sprite_joints.psd. It also has visual representations.
-# TODO right now accessory points are explicitly defined. Should they be injected in run-time? In that case, certain names (e.g. headgear, held_item) will act as an anchor.
+! Some keywords are considered special within the game, they are:
+!   HEADGEAR, HELD_ITEM, BOOT_L, BOOT_R, GAUNTLET_L, GAUNTLET_R and ARMOUR_* (star means any number starting from zero)
+BODYPARTS=ARM_REST_RIGHT 3,8;\
+          ARM_REST_LEFT 3,8;\
+          FOOT_LEFT 4,2;\
+          FOOT_RIGHT 4,2;\
+          UPPER_TORSO 9,4;\
+          LOWER_TORSO 7,4;\
+          LEG_REST_RIGHT 3,7;\
+          LEG_REST_LEFT 3,7;\
+          HEAD 8,7;\
+          HAND_REST_RIGHT 3,3;\
+          HAND_REST_LEFT 3,3;\
+          HAIR 20,12;\
+          HAIR_FORE 20,12
 SKELETON_STAND=HEADGEAR 0,32;HAIR_FORE 0,32;\
                ARM_REST_RIGHT -7,23;HAND_REST_RIGHT -6,11;HELD_ITEM -6,11;\
                HAIR 0,32;HEAD 0,32;\