This article contains information for Programmers working or interested in working for The Mana World
This article contains information for Artists working or interested in working for The Mana World
This article is for reference purpose
The features described in this article are already implemented in the game. The article should describe how a certain aspect of the game currently works. You may of course edit this article to improve the description of the circumstances. Your opinions or improvement suggestions about the described aspects themself are of course appreciated, too. But please put these on the discussion page of this article to keep facts and fiction separated.
Example of a sprite definition
The animations of all sprites are defined by xml documents. Here follows an example:
<?xml version="1.0"?> <sprite name="player" action="stand"> <imageset name="base" src="graphics/sprites/player_male_base.png" width="64" height="64" /> <action name="stand" imageset="base"> <animation direction="down"> <frame index="0" /> </animation> <animation direction="left"> <frame index="18" /> </animation> <animation direction="up"> <frame index="36" /> </animation> <animation direction="right"> <frame index="54" /> </animation> </action> <action name="walk" imageset="base"> <animation direction="down"> <frame index="1" delay="75" /> <frame index="2" delay="75" /> <frame index="3" delay="75" /> <frame index="4" delay="75" /> <frame index="5" delay="75" /> <frame index="6" delay="75" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="75" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="75" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="75" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="75" /> <end /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="75" /> <end /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="75" /> <end /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="75" /> <end /> </animation> </action> </sprite>
So if you want to load the playerset you just load player.xml and it takes care of loading all related images. Of course delays are defined in milliseconds.
Specifications
<sprite>
A sprite is an object which can carry several animations, hence we call the root element the sprite. The sprite tag has two optional properties variants and variant_offset. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. The variants property defines the number of variants in the spriteset and the variant_offset property how many sprites are between the first sprites of the variants. When defining multiple variants you only define the animation sequences of the first variant. the engine then shifts the index parameters when it needs another.
<action>
collection of the animation in different directions that belong to an action the character can perform. the properties are the imageset the animation phases are taken from and the name of the action.
possible names:
use-item*
|
attack-bow cast-magic*
| |
attack-stab attack-throw*
\ /
run* attack-swing* sleeping* dead
| | | |
walk attack sit hurt*
\ \ / /
stand
|
default
this table also specifies the substitution precedence. when a specific name is requested but it is not defined the next lower name is used instead. The actions marked with * can be definde without causing an error but there is no situation in the current client program that triggers them.
<animation>
Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction").
the possible directions are:
up down left right default
when a specific direction isn't provided, the default direction is used instead. When no default direction is defined, the first defined direction is used.
Every <animation> has one or more frame or sequence child elements and an optional <end> element.
<frame>
Defines one frame of the animation. The only required property is index. Optional properties include offsetX, offsetY and delay.
index defines the index of the graphic on the spriteset.
The delay property specifies the number of milliseconds the frame is displayed before it is replaced by the next frame in the sequence. The sequence restarts when the last frame is finished. When no delay is specified (or specified as "0") the animation doesn't continue when this frame is reached.
The frame element has the optional properties offsetX and offsetY to specify an offset from the default drawing position for that frame. This allows the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets.
<sequence>
The sequence tag defines one or more phases of animation. It has the required properties delay, start, and end. The delay property specifies the delay in milliseconds between each phase. The start and end properties define the first and the last indexes of the animation sequence on the spritesheet.
<end>
When the animation sequence reaches an end tag, the animation stops and the sprite animation is returned to the "stand" state. This can be used for one time action sequences like attacking. This tag has no properties.
Suggested additions
This article is currently only a proposal
The features or design guidelines described in this article are only a proposal made by one or some persons. It has not been evaluated or accepted by the core development team yet. Feel free to add your personal opinion about them or make counter proposals.
<random> childtag for <animation>
Also, it includes an experimental suggestion on specifying that a random frame should be chosen. This should also have an exclude_current_frame thingy, to make sure a frame isn't shown twice or more in a row. Sometimes this may be wanted though.
sequences based on default sequences
After reflecting on this idea (and the above suggestion) I think a first issue to solve is to reduce the amount of duplicated definitions. For example, at the moment every monster uses the exact same frame size and animation frames. Hence, it would be interesting if the defined sprite could take the actual imageset it uses as a parameter instead of specifying this on its own. This way we can define a monster like:
<sprite name="monster-walking-default"> <imageset name="base" /> ... </sprite> <being name="Scorpion"> <sprite ref="monster-walking-default"> <with-imageset name="base" src="scorpion-base.png" width="60" height="60" /> </sprite> </being> <being name="Red Scorpion"> <sprite ref="monster-walking-default"> <with-imageset name="base" src="scorpion-red-base.png" width="60" height="60" /> </sprite> </being>
Defining an empty imageset (without src attribute) will make the engine require this imageset to be passed as a parameter whenever the spriteset is referenced.
I'm not convinced yet that the name attribute of the sprite element is really necessary. I think I would prefer each sprite to be defined in its own file. However it could be attractive to define multiple things in the same file, but in that case I think we will have to read everything when the client is launched, and only graphics and imagesets can be created lazily (only when necessary). Because the other data consists of just numbers and strings, this should not be really a problem.
Since we're currently not naming sprites and defining each in its own file, the following variations on this approach could be implemented:
Since inheritance
Ability to extend one spriteset from another, while overriding imagesets and possibly also adding new ones and redefining specific animations:
<sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite>
Including other spritesets
Mentioned by Matt, we could have a generic import/include element. This would even allow you to combine several spritesets together. Below the assumption is that you can only define an imageset once while animations can be redefined (actually the same as with the inheritance approach above). This prevents us from loading imagesets unnecessarily and allows us to verify the validity of animation definitions as we encounter them.
<sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite>
Implementation proposal of hairstyles by Modanung
I think the current system with an xml file for every hairstyle with an index and offset defined for every frame is a bit too much. It also takes a lot of work to correct small errors and to add new hairstyles that may have a different frame size and with it a different offset. I suggest we split hairstyles up in three catagories:
- Static hairstyles
- Standard animated hairstyles
- Special case hairstyles
On top of the current system we need a variable that defines which gender can use which hairstyles, in every hairstyle's xml-file.
Static hairstyles
These are hairstyles which only have one frame for each direction and death, so five. All current hairstyles would be static hairstyles. Every individual static hairstyle needs nothing more to be defined then their bitmap, their size and their offset for each direction. The offset for each seperate frame would be defined in a shared file (say hairoffsets.xml), this summed with the individual hairstyle's offset is the offset for that single frame with that hairstyle.
hairstyle1.xml <offsetfile="hairoffsets.xml", framefile="static_hairstyles_frames.xml"> <sprite variants="10" variant_offset="5"> <gender="male"> <imageset name="base" src="graphics/sprites/hairstyle1.png" width="40" height="40" /> <offsetX="0" offsetY ="0" /> End of file
hairoffsets.xml <action name="stand" imageset="base"> <animation direction="down"> <offsetX="0" offsetY ="-29" /> </animation> <animation direction="left"> <offsetX="-1" offsetY ="-29"/> </animation> <animation direction="up"> <offsetX="-1" offsetY ="-25"/> </animation> <animation direction="right"> <offsetX="1" offsetY ="-29"/> </animation> </action> <action name="walk" imageset="base"> <animation direction="down"> <offsetX="0" offsetY ="-28" delay="75"/> <offsetX="0" offsetY ="-29" delay="75" /> <offsetX="0" offsetY ="-29" delay="75" /> <offsetX="0" offsetY ="-28" delay="75" /> <offsetX="0" offsetY ="-29" delay="75" /> <offsetX="0" offsetY ="-29" delay="75" /> </animation> ...etc...
static_hairstyles_frames.xml <animation direction="down"> <frame index="0" /> </animation> <animation direction="left"> <frame index="1" /> </animation> <animation direction="up"> <frame index="2" /> </animation> <animation direction="right"> <frame index="3" /> </animation> <action name="dead" imageset="base"> <animation direction="default"> <frame index="4"/> </animation> End of file
Standard animated hairstyles
These are hairstyles that can be compared with hair in SoM or Chrono Trigger, they move as you walk and attack. They have three frames for each direction and death, so thirteen frames all together. These three frames can be devided in a relaxed frame and two extremes. Those two extremes either being up and down or left and right, depending on the hair style. A heavily greased Evil look would wobble up and down as you walk and a pony talk would wave from left to right. Standard animated hairstyles hairstyles use the same offset as static ones only they have a different file for defining the frames.
hairstyle2.xml <offsetfile="hairoffsets.xml", framefile="animated_hairstyles_frames.xml"> <sprite variants="10" variant_offset="13"> <gender="both"> <imageset name="base" src="graphics/sprites/hairstyle2.png" width="40" height="40" /> <offsetX="0" offsetY ="0" /> End of file
animated_hairstyles_frames.xml <action name="stand" imageset="base"> <animation direction="down"> <frame index="0" /> </animation> <animation direction="left"> <frame index="3" /> </animation> <animation direction="up"> <frame index="6" /> </animation> <animation direction="right"> <frame index="9" /> </animation> </action> <action name="walk" imageset="base"> <animation direction="down"> <frame index="0" delay="75"/> <frame index="1" delay="75" /> <frame index="1" delay="75" /> <frame index="0" delay="75" /> <frame index="2" delay="75" /> <frame index="2" delay="75" /> </animation> ...etc...
Special case hairstyles
And then there are the odd ones, the hairstyles that need a little more freedom. Hairstyles that people want to make wave in the wind, even when the player stands still. Or a birdnest hairstyle with nestlings that constantly open and close their mouth in a random frequency nomatter what you do. I'll take as example a Medusa hairstyle.
hairstyle3.xml <offsetfile="hairoffsets.xml", framefile=0> <sprite variants="10" variant_offset="13"> <gender="female"> <imageset name="base" src="graphics/sprites/hairstyle3.png" width="50" height="60" /> <offsetX="-5" offsetY ="-10" /> <animation direction="down"> <frame index="0" delay="100"/> <frame index="1" delay="100"/> <frame index="2" delay="100"/> </animation> <animation direction="left"> <frame index="3" delay="100"/> <frame index="4" delay="100"/> <frame index="5" delay="100"/> </animation> <animation direction="up"> <frame index="6" delay="100"/> <frame index="7" delay="100"/> <frame index="8" delay="100"/> </animation> <animation direction="right"> <frame index="9" delay="100"/> <frame index="10" delay="100"/> <frame index="11" delay="100"/> </animation> <action name="dead" imageset="base"> <animation direction="default"> <frame index="12"/> </animation> End of file
This hairstyle showes a bunch of snakes on your head that always wave 'n wobble unless you're dead. The animation rolls asychronusly with the attack and walking animations and it also moves when you stand still. But the offsets are in sync. Special hairstyles might also use their own offsets ofcourse I think this pretty much finished my proposal.
