The Mana World wiki https://wiki.themanaworld.org/index.php/Main_Page MediaWiki 1.37.2 first-letter Media Special Talk User User talk The Mana World The Mana World talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Test Test talk Archive Archive talk Dev Dev talk Net Net talk Classic Classic talk Moubootaur Legends Moubootaur Legends talk Revolt Revolt talk Event Event talk SoM SoM talk Ar Ar talk Cz Cz talk De De talk En En talk Es Es talk Fa Fa talk Fr Fr talk Id Id talk It It talk Pl Pl talk Pt Pt talk Ru Ru talk Sq Sq talk Tr Tr talk Zh Zh talk 0 2026 3639 2006-03-12T15:07:36Z ElvenProgrammer 11 A first attempt at a new animation system 3639 wikitext text/x-wiki This is a first attempt at defining a new animation system which should improve the current behaviour of beings, especially the player. The general idea is to have an xml document defining everything about an animation. Here follows an example of what I'm talking about. <pre> <?xml version="1.0"?> <animation name="player"> <images> <image id="0" name="misc" file="player-male-misc.png" width="64" height="64"/> <image id="1" name="stab" file="player-male-stab.png" width="64" height="64"/> <image id="2" name="bow" file="player-male-bow.png" width="64" height="64"/> </images> <actions> <action name="stand" image="0" frames="1"/> <action name="walk" image="0" frames="6"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> </action> <action name="sit" image="0" frames="1"/> <action name="die" image="0" frames="1"/> <action name="stab" image="1" frames="4"> <frame delay="20"> <frame delay="30"> <frame delay="20"> <frame delay="20"> </action> <action name="bow" image="2" frames="5"> <frame delay="10"> <frame delay="10"> <frame delay="40"> <frame delay="20"> <frame delay="20" </action> </actions> </animation> </pre> So if you want to load the playerset you just load player.xml and it takes care of loading all related images. Reuse of frames should also be considered, so we could specify the exact frames sequence. Just take the bat as an example. The standing animation as well as the walking one require 4 frames. A bat can hardly stay in flight without flapping his wings as it does now. And in the spritesheet the first 2 rows are identical suggesting one of them could be removed. <pre> <?xml version="1.0"?> <animation name="bat"> <images> <image id="0" name="misc" file="monster15.png" width="60" height="60"/> </images> <actions> <action name="stand" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> <action name="walk" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> </action> <action name="die" image="0" frames="1"/> </actions> </animation> </pre> e8w8jpfwdxcrxt1eg1zaxelk5c2si0b 3640 3639 2006-03-12T15:37:47Z Crush 103 3640 wikitext text/x-wiki This is a first attempt at defining a new animation system which should improve the current behaviour of beings, especially the player. The general idea is to have an xml document defining everything about an animation. Here follows an example of what I'm talking about. <pre> <?xml version="1.0"?> <animation name="player"> <images> <image id="0" name="misc" file="player-male-misc.png" width="64" height="64"/> <image id="1" name="stab" file="player-male-stab.png" width="64" height="64"/> <image id="2" name="bow" file="player-male-bow.png" width="64" height="64"/> </images> <actions> <action name="stand" image="0" frames="1"/> <action name="walk" image="0" frames="6"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> </action> <action name="sit" image="0" frames="1"/> <action name="die" image="0" frames="1"/> <action name="stab" image="1" frames="4"> <frame delay="20"> <frame delay="30"> <frame delay="20"> <frame delay="20"> </action> <action name="bow" image="2" frames="5"> <frame delay="10"> <frame delay="10"> <frame delay="40"> <frame delay="20"> <frame delay="20" </action> </actions> </animation> </pre> So if you want to load the playerset you just load player.xml and it takes care of loading all related images. Reuse of frames should also be considered, so we could specify the exact frames sequence. Just take the bat as an example. The standing animation as well as the walking one require 4 frames. A bat can hardly stay in flight without flapping his wings as it does now. And in the spritesheet the first 2 rows are identical suggesting one of them could be removed. <pre> <?xml version="1.0"?> <animation name="bat"> <images> <image id="0" name="misc" file="monster15.png" width="60" height="60"/> </images> <actions> <action name="stand" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> <action name="walk" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> </action> <action name="die" image="0" frames="1"/> </actions> </animation> </pre> == Comments == Maybe the <frame> tags should define the spriteset id and the subimage id of the frame. That way a single animation could consist of frames from different spritesets and different positions inside the spriteset. --[[User:Crush|Crush]] 16:37, 12 March 2006 (CET) jnsr8nxnkx5j81nly404lky2jnb9o2g 3641 3640 2006-03-12T15:48:57Z Crush 103 /* Comments */ made my point a little bit clearer 3641 wikitext text/x-wiki This is a first attempt at defining a new animation system which should improve the current behaviour of beings, especially the player. The general idea is to have an xml document defining everything about an animation. Here follows an example of what I'm talking about. <pre> <?xml version="1.0"?> <animation name="player"> <images> <image id="0" name="misc" file="player-male-misc.png" width="64" height="64"/> <image id="1" name="stab" file="player-male-stab.png" width="64" height="64"/> <image id="2" name="bow" file="player-male-bow.png" width="64" height="64"/> </images> <actions> <action name="stand" image="0" frames="1"/> <action name="walk" image="0" frames="6"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> </action> <action name="sit" image="0" frames="1"/> <action name="die" image="0" frames="1"/> <action name="stab" image="1" frames="4"> <frame delay="20"> <frame delay="30"> <frame delay="20"> <frame delay="20"> </action> <action name="bow" image="2" frames="5"> <frame delay="10"> <frame delay="10"> <frame delay="40"> <frame delay="20"> <frame delay="20" </action> </actions> </animation> </pre> So if you want to load the playerset you just load player.xml and it takes care of loading all related images. Reuse of frames should also be considered, so we could specify the exact frames sequence. Just take the bat as an example. The standing animation as well as the walking one require 4 frames. A bat can hardly stay in flight without flapping his wings as it does now. And in the spritesheet the first 2 rows are identical suggesting one of them could be removed. <pre> <?xml version="1.0"?> <animation name="bat"> <images> <image id="0" name="misc" file="monster15.png" width="60" height="60"/> </images> <actions> <action name="stand" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> <action name="walk" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> </action> <action name="die" image="0" frames="1"/> </actions> </animation> </pre> == Comments == Maybe the <frame> tags should define the spriteset id and the number of the sprite inside the spriteset. That way a single animation could consist of frames from different spritesets and any combination inside the spriteset. a walk animation where the middle animation phase is used twice would look that way: <pre> <action name="walk" image="0" frames="4"> <frame number="0" delay="20" spriteset="0" image="4" /> <frame number="1" delay="20" spriteset="0" image="5" /> <frame number="2" delay="20" spriteset="0" image="6" /> <frame number="3" delay="20" spriteset="0" image="5" /> </action> </pre> --[[User:Crush|Crush]] 16:37, 12 March 2006 (CET) 1fq1zavzdqcm7l6r93osnox7dzoyjmp 3642 3641 2006-03-12T15:51:30Z Crush 103 /* Comments */ 3642 wikitext text/x-wiki This is a first attempt at defining a new animation system which should improve the current behaviour of beings, especially the player. The general idea is to have an xml document defining everything about an animation. Here follows an example of what I'm talking about. <pre> <?xml version="1.0"?> <animation name="player"> <images> <image id="0" name="misc" file="player-male-misc.png" width="64" height="64"/> <image id="1" name="stab" file="player-male-stab.png" width="64" height="64"/> <image id="2" name="bow" file="player-male-bow.png" width="64" height="64"/> </images> <actions> <action name="stand" image="0" frames="1"/> <action name="walk" image="0" frames="6"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> </action> <action name="sit" image="0" frames="1"/> <action name="die" image="0" frames="1"/> <action name="stab" image="1" frames="4"> <frame delay="20"> <frame delay="30"> <frame delay="20"> <frame delay="20"> </action> <action name="bow" image="2" frames="5"> <frame delay="10"> <frame delay="10"> <frame delay="40"> <frame delay="20"> <frame delay="20" </action> </actions> </animation> </pre> So if you want to load the playerset you just load player.xml and it takes care of loading all related images. Reuse of frames should also be considered, so we could specify the exact frames sequence. Just take the bat as an example. The standing animation as well as the walking one require 4 frames. A bat can hardly stay in flight without flapping his wings as it does now. And in the spritesheet the first 2 rows are identical suggesting one of them could be removed. <pre> <?xml version="1.0"?> <animation name="bat"> <images> <image id="0" name="misc" file="monster15.png" width="60" height="60"/> </images> <actions> <action name="stand" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> <action name="walk" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> </action> <action name="die" image="0" frames="1"/> </actions> </animation> </pre> == Comments == Maybe the <frame> tags should define the spriteset id and the number of the sprite inside the spriteset. That way a single animation could consist of frames from different spritesets and any combination inside the spriteset. then i don't see the reason why the number of frames has to be in the <action> tag. isn't it possible to just count the child <frame>'s? a walk animation where the middle animation phase is used twice would look that way: <pre> <action name="walk"> <frame number="0" delay="20" spriteset="0" image="4" /> <frame number="1" delay="20" spriteset="0" image="5" /> <frame number="2" delay="20" spriteset="0" image="6" /> <frame number="3" delay="20" spriteset="0" image="5" /> </action> </pre> --[[User:Crush|Crush]] 16:37, 12 March 2006 (CET) 1xwf58kxicrcewk3vujyu8cikw5he27 3643 3642 2006-03-12T15:56:15Z Crush 103 /* Comments */ unit of delay property 3643 wikitext text/x-wiki This is a first attempt at defining a new animation system which should improve the current behaviour of beings, especially the player. The general idea is to have an xml document defining everything about an animation. Here follows an example of what I'm talking about. <pre> <?xml version="1.0"?> <animation name="player"> <images> <image id="0" name="misc" file="player-male-misc.png" width="64" height="64"/> <image id="1" name="stab" file="player-male-stab.png" width="64" height="64"/> <image id="2" name="bow" file="player-male-bow.png" width="64" height="64"/> </images> <actions> <action name="stand" image="0" frames="1"/> <action name="walk" image="0" frames="6"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> </action> <action name="sit" image="0" frames="1"/> <action name="die" image="0" frames="1"/> <action name="stab" image="1" frames="4"> <frame delay="20"> <frame delay="30"> <frame delay="20"> <frame delay="20"> </action> <action name="bow" image="2" frames="5"> <frame delay="10"> <frame delay="10"> <frame delay="40"> <frame delay="20"> <frame delay="20" </action> </actions> </animation> </pre> So if you want to load the playerset you just load player.xml and it takes care of loading all related images. Reuse of frames should also be considered, so we could specify the exact frames sequence. Just take the bat as an example. The standing animation as well as the walking one require 4 frames. A bat can hardly stay in flight without flapping his wings as it does now. And in the spritesheet the first 2 rows are identical suggesting one of them could be removed. <pre> <?xml version="1.0"?> <animation name="bat"> <images> <image id="0" name="misc" file="monster15.png" width="60" height="60"/> </images> <actions> <action name="stand" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> <action name="walk" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> </action> <action name="die" image="0" frames="1"/> </actions> </animation> </pre> == Comments == Maybe the <frame> tags should define the spriteset id and the number of the sprite inside the spriteset. That way a single animation could consist of frames from different spritesets and any combination inside the spriteset. then i don't see the reason why the number of frames has to be in the <action> tag. isn't it possible to just count the child <frame>'s? a walk animation where the middle animation phase is used twice would look that way: <pre> <action name="walk"> <frame number="0" delay="20" spriteset="0" image="4" /> <frame number="1" delay="20" spriteset="0" image="5" /> <frame number="2" delay="20" spriteset="0" image="6" /> <frame number="3" delay="20" spriteset="0" image="5" /> </action> </pre> --[[User:Crush|Crush]] 16:37, 12 March 2006 (CET) Oh, and something else: it isn't mentioned what exactly the unit of the delay property is. i think the delays should be defined as milliseconds, not frames. that way the animation speed would be independent from the framerate. --[[User:Crush|Crush]] 16:56, 12 March 2006 (CET) cvs9bwft1489kl5x7usbv13v7lme7zn 3648 3643 2006-03-12T18:24:33Z Crush 103 status: red 3648 wikitext text/x-wiki {{Status_red}} This is a first attempt at defining a new animation system which should improve the current behaviour of beings, especially the player. The general idea is to have an xml document defining everything about an animation. Here follows an example of what I'm talking about. <pre> <?xml version="1.0"?> <animation name="player"> <images> <image id="0" name="misc" file="player-male-misc.png" width="64" height="64"/> <image id="1" name="stab" file="player-male-stab.png" width="64" height="64"/> <image id="2" name="bow" file="player-male-bow.png" width="64" height="64"/> </images> <actions> <action name="stand" image="0" frames="1"/> <action name="walk" image="0" frames="6"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> <frame delay="20"> </action> <action name="sit" image="0" frames="1"/> <action name="die" image="0" frames="1"/> <action name="stab" image="1" frames="4"> <frame delay="20"> <frame delay="30"> <frame delay="20"> <frame delay="20"> </action> <action name="bow" image="2" frames="5"> <frame delay="10"> <frame delay="10"> <frame delay="40"> <frame delay="20"> <frame delay="20" </action> </actions> </animation> </pre> So if you want to load the playerset you just load player.xml and it takes care of loading all related images. Reuse of frames should also be considered, so we could specify the exact frames sequence. Just take the bat as an example. The standing animation as well as the walking one require 4 frames. A bat can hardly stay in flight without flapping his wings as it does now. And in the spritesheet the first 2 rows are identical suggesting one of them could be removed. <pre> <?xml version="1.0"?> <animation name="bat"> <images> <image id="0" name="misc" file="monster15.png" width="60" height="60"/> </images> <actions> <action name="stand" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> <action name="walk" image="0" frames="4"/> <frame delay="20" frame="0"> <frame delay="20" frame="1"> <frame delay="20" frame="2"> <frame delay="20" frame="3"> </action> <action name="die" image="0" frames="1"/> </actions> </animation> </pre> == Comments == Maybe the <frame> tags should define the spriteset id and the number of the sprite inside the spriteset. That way a single animation could consist of frames from different spritesets and any combination inside the spriteset. then i don't see the reason why the number of frames has to be in the <action> tag. isn't it possible to just count the child <frame>'s? a walk animation where the middle animation phase is used twice would look that way: <pre> <action name="walk"> <frame number="0" delay="20" spriteset="0" image="4" /> <frame number="1" delay="20" spriteset="0" image="5" /> <frame number="2" delay="20" spriteset="0" image="6" /> <frame number="3" delay="20" spriteset="0" image="5" /> </action> </pre> --[[User:Crush|Crush]] 16:37, 12 March 2006 (CET) Oh, and something else: it isn't mentioned what exactly the unit of the delay property is. i think the delays should be defined as milliseconds, not frames. that way the animation speed would be independent from the framerate. --[[User:Crush|Crush]] 16:56, 12 March 2006 (CET) sppt3bn9df677nam6rmbz5xtga4a4s6 3795 3648 2006-03-14T10:18:55Z ElvenProgrammer 11 Version 0.2 3795 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. 9zfnx4nw7pa22b3zn4sj2owgtrcomgv 3800 3795 2006-03-14T17:47:05Z Bjørn 3 Added my suggestion 3800 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> ea1luo8z1oraa1rwuu9bk9iv0zstgka 3801 3800 2006-03-14T17:56:41Z Bjørn 3 Some addendum 3801 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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 uses as a parameter instead of specifying this on its own. This way we can define a monster like: <pre> <being name="Scorpion"> <sprite ref="monster-walker-default.xml"> <imageset name="base" src="scorpion-base.png" width="..." height="..." /> </sprite> </being> </pre> gp2w6528s4t5b7rhqzemr6nyasnmq5w 3802 3801 2006-03-14T20:44:38Z Bjørn 3 Some small modifications 3802 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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 uses as a parameter instead of specifying this on its own. This way we can define a monster like: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. h3enk0egdm3rsl3cjnu8eg6j0bwxlza 3803 3802 2006-03-15T13:32:54Z Bjørn 3 Red scorpion for further illustration 3803 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. 6zep5oijvgqd53orfkcfqpz5r3gzmhl 3813 3803 2006-03-18T15:05:31Z Peoro 322 3813 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int start; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t ) { start = t; } Img *getFrame ( int t ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-start) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( clock() ); while ( 1 ) { draw ( a.getFrame(clock()) ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. ognuu0k2io0pq7v47h7z4h2oxaqiaab 3814 3813 2006-03-18T15:10:40Z Peoro 322 3814 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int start; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t ) { start = t; } Img *getFrame ( int t ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-start) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( clock() ); while ( 1 ) { draw ( a.getFrame(clock()) ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. br5473quhsn1l09gdqmstdbjv6m15ld 3815 3814 2006-03-18T15:43:53Z Peoro 322 3815 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. k8s4nudb589m980qvi0d20tjbl10ya2 3816 3815 2006-03-18T16:12:17Z Peoro 322 3816 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. rhw2yhz6e4nlbo1jrg3zf4z8em3p5su 3817 3816 2006-03-18T16:50:53Z Doener 43 Added implementation proposal 3817 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> 3tmcjw3l6xnn9vsr7rpmp1nrngq1ake 3818 3817 2006-03-18T16:52:27Z Doener 43 /* Implementation proposal by Doener */ 3818 wikitext text/x-wiki {{Status_red}} After a mini-meeting between me and Doener we refined the model. Each animation will be defined by an xml document, here follows an example: <pre> <?xml version="1.0"?> <animation name="player"> <spritemap name="misc" src="player-male-misc.png" width="64" height="64" /> <spritemap name="stab" src="player-male-stab.png" width="64" height="64" /> <spritemap name="bow" src="player-male-bow.png" width="64" height="64" /> <action name="stand"> <frame spritemap="misc" index="0" delay="0" /> </action> <action name="walk"> <frame spritemap="misc" index="0" delay="20" /> <frame spritemap="misc" index="1" delay="20" /> </action> <action name="bow-attack"> <sequence spritemap="bow" start="0" end="5" delay="20" /> </action> </animation> </pre> 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. == Some attempt by Bjørn == A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. In the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. For the dead frame I have specified no direction attribute, which makes this animation independent of direction. Also, it includes an experimental suggestion on specifying that a random frame should be chosen. <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> 0bm6kznu8a0mak2707xnxwwkl81mbgv 4175 3818 2006-04-30T13:18:55Z Crush 103 cleanup and clarification 4175 wikitext text/x-wiki {{Status_red}} Each animation will be defined by an xml document, here follows an example: <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object is in a specific state (attribute "name") and in a specific direction (attribute "direction"). possible names: <pre> attack-bow | attack-stab sleeping | | run attack-swing sit | | | walk attack dead \ | / stand | (nameless) </pre> this table also specifies the substitution preference when a specific name is requested but it is not defined. the next lower name is used instead. possible directions are: <pre> up down left right </pre> when no direction attribute is provided, this <code>animation</code> is used for all missing directions with the same name. === &lt;frame&gt; === Every <code><animation></code> has one or more <code>frame</code> child elements. each of them defines one frame of the animation. the required attributes are <code>imageset</code> and ether <code>index</code> or <code>start</code> and <code>end</code>. <code>imageset</code> defines the spriteset file from which the frame should be taken and <code>index</code> defines the number of the sprite in this spriteset. when a <code>start</code> and a </code>end</code> tag is provided instead of an <code>index</code> tag the <code>frame</code> tag does not only define one animation phase but multiple phases which all use the same imageset and delay and where the sprite indices in the spriteset are from "start" to "end". an optional attribute is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified the animation doesn't continue when the <code>frame</code> is reached. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === Also, it includes an experimental suggestion on specifying that a random frame should be chosen. === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> 3zm9vgrz9ap4ef2nc8nii1rm9r2nnyc 4176 4175 2006-04-30T13:23:36Z Crush 103 /* &lt;animation&gt; */ 4176 wikitext text/x-wiki {{Status_red}} Each animation will be defined by an xml document, here follows an example: <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object is in a specific state (attribute "name") and in a specific direction (attribute "direction"). possible names: <pre> attack-bow | attack-stab | run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> this table also specifies the substitution preference when a specific name is requested but it is not defined. the next lower name is used instead. possible directions are: <pre> up down left right </pre> when no direction attribute is provided, this <code>animation</code> is used for all missing directions with the same name. === &lt;frame&gt; === Every <code><animation></code> has one or more <code>frame</code> child elements. each of them defines one frame of the animation. the required attributes are <code>imageset</code> and ether <code>index</code> or <code>start</code> and <code>end</code>. <code>imageset</code> defines the spriteset file from which the frame should be taken and <code>index</code> defines the number of the sprite in this spriteset. when a <code>start</code> and a </code>end</code> tag is provided instead of an <code>index</code> tag the <code>frame</code> tag does not only define one animation phase but multiple phases which all use the same imageset and delay and where the sprite indices in the spriteset are from "start" to "end". an optional attribute is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified the animation doesn't continue when the <code>frame</code> is reached. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === Also, it includes an experimental suggestion on specifying that a random frame should be chosen. === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> gvc0gg8rqhucux997kifu1hezfrk1cv 4177 4176 2006-04-30T13:27:37Z Crush 103 /* &lt;animation&gt; */ some more possible animations 4177 wikitext text/x-wiki {{Status_red}} Each animation will be defined by an xml document, here follows an example: <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object is in a specific state (attribute "name") and in a specific direction (attribute "direction"). possible names: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> this table also specifies the substitution preference when a specific name is requested but it is not defined. the next lower name is used instead. possible directions are: <pre> up down left right </pre> when no direction attribute is provided, this <code>animation</code> is used for all missing directions with the same name. === &lt;frame&gt; === Every <code><animation></code> has one or more <code>frame</code> child elements. each of them defines one frame of the animation. the required attributes are <code>imageset</code> and ether <code>index</code> or <code>start</code> and <code>end</code>. <code>imageset</code> defines the spriteset file from which the frame should be taken and <code>index</code> defines the number of the sprite in this spriteset. when a <code>start</code> and a </code>end</code> tag is provided instead of an <code>index</code> tag the <code>frame</code> tag does not only define one animation phase but multiple phases which all use the same imageset and delay and where the sprite indices in the spriteset are from "start" to "end". an optional attribute is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified the animation doesn't continue when the <code>frame</code> is reached. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === Also, it includes an experimental suggestion on specifying that a random frame should be chosen. === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> 98yjiw9aw8ci7xvihvblpt8ivykx7ur 4178 4177 2006-04-30T13:33:08Z Crush 103 /* &lt;animation&gt; */ 4178 wikitext text/x-wiki {{Status_red}} Each animation will be defined by an xml document, here follows an example: <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object is in a specific state (attribute "name") and in a specific direction (attribute "direction"). possible names: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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 possible directions are: <pre> up down left right </pre> when no direction attribute is provided, this <code>animation</code> is used for all missing directions with the same name. === &lt;frame&gt; === Every <code><animation></code> has one or more <code>frame</code> child elements. each of them defines one frame of the animation. the required attributes are <code>imageset</code> and ether <code>index</code> or <code>start</code> and <code>end</code>. <code>imageset</code> defines the spriteset file from which the frame should be taken and <code>index</code> defines the number of the sprite in this spriteset. when a <code>start</code> and a </code>end</code> tag is provided instead of an <code>index</code> tag the <code>frame</code> tag does not only define one animation phase but multiple phases which all use the same imageset and delay and where the sprite indices in the spriteset are from "start" to "end". an optional attribute is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified the animation doesn't continue when the <code>frame</code> is reached. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === Also, it includes an experimental suggestion on specifying that a random frame should be chosen. === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> qdafpjpu74efwg9jzt3jlmzbjgnp1dr 4311 4178 2006-06-27T14:53:01Z Crush 103 4311 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <sprite name="player"> <imageset name="base" src="player-male-base.png" width="64" height="64" /> <animation name="stand" direction="down"> <frame imageset="base" index="0" /> </animation> <animation name="stand" direction="left"> <frame imageset="base" index="18" /> </animation> <animation name="stand" direction="up"> <frame imageset="base" index="36" /> </animation> <animation name="stand" direction="right"> <frame imageset="base" index="54" /> </animation> <animation name="walk" direction="down"> <frames imageset="base" start="1" end="6" delay="10" /> </animation> ... <animation name="sit" direction="down"> <frame imageset="base" index="7" /> </animation> ... <animation name="bow-attack" direction="down"> <frames imageset="base" start="13" end="17" delays="5,5,5,10,50" /> </animation> ... <animation name="dead"> <random> <frame imageset="base" index="8" /> <frame imageset="base" index="26" /> <frame imageset="base" index="44" /> <frame imageset="base" index="62" /> </random> </animation> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object is in a specific state (attribute "name") and in a specific direction (attribute "direction"). possible names: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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 possible directions are: <pre> up down left right </pre> when no direction attribute is provided, this <code>animation</code> is used for all missing directions with the same name. === &lt;frame&gt; === Every <code><animation></code> has one or more <code>frame</code> child elements. each of them defines one frame of the animation. the required attributes are <code>imageset</code> and ether <code>index</code> or <code>start</code> and <code>end</code>. <code>imageset</code> defines the spriteset file from which the frame should be taken and <code>index</code> defines the number of the sprite in this spriteset. when a <code>start</code> and a </code>end</code> tag is provided instead of an <code>index</code> tag the <code>frame</code> tag does not only define one animation phase but multiple phases which all use the same imageset and delay and where the sprite indices in the spriteset are from "start" to "end". an optional attribute is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified the animation doesn't continue when the <code>frame</code> is reached. Each <code>frame</code> and <code>frames</code> element can optionally have attributes <code>x</code> and <code>y</code> to specify an offset from the default drawing position for that frame. This will allow the animation of for example the hairset (or any equipment) to reuse the same frames with different offsets, and be defined exactly like below. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === Also, it includes an experimental suggestion on specifying that a random frame should be chosen. === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> azbjprjqvwq4ffhrx8sjiscd4kst88c 4312 4311 2006-06-28T13:18:58Z Crush 103 using a real-live sample, some corrections regarding identifiers and improved the documentation 4312 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. when a <code>start</code> and a </code>end</code> tag is provided instead of an <code>index</code> tag the an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === Also, it includes an experimental suggestion on specifying that a random frame should be chosen. === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> okx32hoc5hcse1c8nx3me398o9lzrgt 4313 4312 2006-06-28T13:20:29Z Crush 103 /* &lt;frame&gt; */ 4313 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence I call the root element the <code>sprite</code>. Also, I think we should seperately define animations in several directions. For now this example is based on the current playerset image, but by using multiple imagesets this could of course be split up. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === Also, it includes an experimental suggestion on specifying that a random frame should be chosen. === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> tn6q7tx0xyfik7mnh2z6j6mq2gf3h8y 4315 4313 2006-07-02T00:23:49Z Crush 103 /* &lt;sprite&gt; */ explained the variant feature 4315 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === Also, it includes an experimental suggestion on specifying that a random frame should be chosen. === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> 7lh3b2lmkjui3cihdf1vkix7fjq3wnn 4336 4315 2006-07-21T15:33:43Z Modanung 8 Exclude_current_frame thingy 4336 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> ll2i5bxs88ocp6u9zy6zxnni0j3scey 4337 4336 2006-07-21T15:45:17Z Modanung 8 4337 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> == 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 mutch. 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 ===Static hairstyles=== These are hairstyles which only have one frame for each direction, for every animation. 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 indicidual hairstyle's offset is the offset for that single frame with that hairstyle. ...To be finished... ck4z4dsd9vnvhqdoonb5g1rvahflqjt 4365 4337 2006-07-22T12:57:54Z Modanung 8 Finished hairstyle animation proposal 4365 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> == 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 mutch. 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 ===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. <pre> hairstyle1.xml <offsetfile="hairoffsets.xml", framefile="static_hairstyles_frames.xml"> <sprite variants="10" variant_offset="5"> <imageset name="base" src="graphics/sprites/hairstyle1.png" width="40" height="40" /> <offsetX="0" offsetY ="0" /> End of file </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> hairstyle2.xml <offsetfile="hairoffsets.xml", framefile="animated_hairstyles_frames.xml"> <sprite variants="10" variant_offset="13"> <imageset name="base" src="graphics/sprites/hairstyle2.png" width="40" height="40" /> <offsetX="0" offsetY ="0" /> End of file </pre> <pre> 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... </pre> ===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. <pre> hairstyle3.xml <offsetfile="hairoffsets.xml", framefile=0> <sprite variants="10" variant_offset="13"> <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 </pre> This hairstyle showes a bunch of snakes on your head that always wave 'n wobble unless you're dead. It moves asychronusly with the attack and walking animations and it also moves when you stand still. Special hairstyles might also use their own offsets ofcourse I think this pretty much finished my proposal. p2gheuz30hcray7fw3crr03lffmr1gu 4368 4365 2006-07-22T13:00:02Z Modanung 8 /* Special case hairstyles */ 4368 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == An implementation idea by Peoro == An idea to manage the animations should be a class based on a timer which choose automatically the current frame. Who needs animations (players, monsters and npcs) has only to start the animanion and to request the frame to draw it. Each instance of Animation class keep its own start-time (or a personal timer), its total time, number of frames, and the time of every frame. The Animation class has to provide at least a function to start the animation and another one to get the current frame; other usefull functions should pause and restart the animation and allow to jump to a random frame. Here a simple example of a prototype of an Animation class: (I mutilated my original Animation class to simplify and summarize it cutting a lot of other functions and vars and using the most possible of standard items) <pre> class Animation { int nframes; Img **frames; int *times; int totalTime; int startTime; public: Animation ( int n, Img **i, int *t ) { int c; nframes = n; frames = new Img* [n]; times = new int [n]; totalTime = 0; for ( c = 0; c < n; c ++ ) { frames[c] = i[c]; times[c] = t[c]; totalTime += t[c]; } } inline void start ( int t = clock() ) { startTime = t; } Img *getFrame ( int t = clock() ) { int i; int it if ( ! totalTime ) { t = 0; } else { t = (t-startTime) % totalTime; } // searches the current frame for ( i = 0, it = 0; (it + times[i]) < t; i ++, it += times[i] ); return frames[i]; } }; </pre> And here how to use this class: <pre> Img * imgs [] = { img1, img2, img3 }; int times [] = { 20, 20, 30 }; Animation a ( 3, imgs, times ); a.start ( ); while ( 1 ) { draw ( a.getFrame() ); } </pre> An advantage of this class is that the animation speed is indipendent to FPS and it's very easy to use. This is a simple way to manage a lot of animations for who needs more than one: <pre> class AnimationsList { // ltstr is only a const char* comparison function map<const char*, Animation*, ltstr> animations; int startTime; // now Animation::startTime is no more usefull Animation *currentAnimation; public: AnimationsList ( ) : currentAnimation(0) { } inline void addAnimation ( const char *n, Animation *a ) { animations[n] = a; } int setAnimation ( const char *n, int t = clock() ) { map<const char*, Animation*, ltstr>::iterator ai; Animation *a; ai = animations.find ( n ); if ( ai == animations.end() ) { // error... animation not found return 0; } a = ai->second; if ( currentAnimation != a ) { a->start ( ); currentAnimation = a; startTime = t; } return 1; } Img * getFrame ( ) { if ( currentAnimation ) { return currentAnimation->getFrame ( ); } return 0; } }; </pre> Using a multimap instead the map it's possible to keep more than an animation bind to the same string. This would be a good way to make AnimationsList choose a random animation. And here how to use AnimationsList class: <pre> AnimationsList al; al.addAnimation ( "walking" "south", anim1 ); al.addAnimation ( "walking" "north", anim2 ); al.addAnimation ( "anim3", anim3 ); al.setAnimation ( "walking" "south" ); while ( 1 ) { draw ( al.getFrame() ); } </pre> I hope not to had make a mistake writing... Anyway these are only theorical bases. == Implementation proposal by Doener == This proposal is incomplete regarding how new sequences are added to the Animation (which is not the right name for this type of class *g*)... Anyway, you should get the idea... The Frame class encapsulates images and are used to create a single linked list that creates an animation. The idea behind the linked list is that you can easily create loops, by having the last element of the animation pointing to the first one. Also, you can easily prepend a "starting animation" before the loop, like in an animation of a running player. He starts out with one animation and then loops the real running... The Animation class is responsible for mapping animation names to their starting frame and for disposing the encapsulating Frame objects, thus a std::map and a std::list is used to keep track of those objects. The next frame is simply calculated from the time that has passed since the last run of the logic method. The case that a whole animation loop can be skipped is not taken into consideration, because a) we cannot do this with frames linked together arbitrarily and b) animations will probably take around 100ms or longer, ie. we'd have less than 10fps for that case to happen and then there's nothing left to gain by that simple optimization anymore anyway ;) For the linked list features, of course the xml format needs to be adjusted to support that. <pre> /* * Frame class, stored information about frames in an animation */ struct Frame { Image *mImg; // Image for this frame int mDelay; // Time in ms for how long this frame is shown Frame *mNext; // Next frame in sequence }; class Animation { public: Animation():mCurrentFrame(0); ~Animation(); void setSequence(const std::string &); void logic(int timePassed); Image* getCurrentImage() { return mCurrentFrame ? mCurrentFrame->mImg : 0; } private: Frame *mCurrentFrame; typedef std::map<std::string,Frame*> FrameMap; typedef FrameMap::iterator FrameMapIterator; FrameMap mStartFrames; std::list<Frame*> mFrames; int mRemain; } Animation::~Animation() { for_each(mFrames.begin(), mFrames.end(), make_dtor(mFrames)); } void Animation::setSequence(const std::string &name) { FrameMapIterator i = mStartFrames.find(name); mCurrentFrame = (i == mStartFrames.end()) ? 0 : i->second; mRemain = 0; } void Animation::logic(int timePassed) { mRemain += timePassed; while (mRemain >= mCurrentFrame->mDelay) { mRemain -= mCurrentFrame->mDelay; mCurrentFrame = mCurrentFrame->mNext; } }; </pre> == 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 mutch. 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 ===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. <pre> hairstyle1.xml <offsetfile="hairoffsets.xml", framefile="static_hairstyles_frames.xml"> <sprite variants="10" variant_offset="5"> <imageset name="base" src="graphics/sprites/hairstyle1.png" width="40" height="40" /> <offsetX="0" offsetY ="0" /> End of file </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> hairstyle2.xml <offsetfile="hairoffsets.xml", framefile="animated_hairstyles_frames.xml"> <sprite variants="10" variant_offset="13"> <imageset name="base" src="graphics/sprites/hairstyle2.png" width="40" height="40" /> <offsetX="0" offsetY ="0" /> End of file </pre> <pre> 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... </pre> ===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. <pre> hairstyle3.xml <offsetfile="hairoffsets.xml", framefile=0> <sprite variants="10" variant_offset="13"> <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 </pre> 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. 2kt5jarxwt2wwp50epqojoq66tn4563 4550 4368 2006-08-03T00:08:20Z Crush 103 removed obsolete implementation proposals 4550 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == 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 ===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. <pre> hairstyle1.xml <offsetfile="hairoffsets.xml", framefile="static_hairstyles_frames.xml"> <sprite variants="10" variant_offset="5"> <imageset name="base" src="graphics/sprites/hairstyle1.png" width="40" height="40" /> <offsetX="0" offsetY ="0" /> End of file </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> hairstyle2.xml <offsetfile="hairoffsets.xml", framefile="animated_hairstyles_frames.xml"> <sprite variants="10" variant_offset="13"> <imageset name="base" src="graphics/sprites/hairstyle2.png" width="40" height="40" /> <offsetX="0" offsetY ="0" /> End of file </pre> <pre> 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... </pre> ===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. <pre> hairstyle3.xml <offsetfile="hairoffsets.xml", framefile=0> <sprite variants="10" variant_offset="13"> <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 </pre> 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. 8msfn7rdraigykr8md6cbkgs46nkauj 4552 4550 2006-08-04T00:27:52Z Modanung 8 Added gender variable 4552 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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. == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. 3rr704dub1kps1cjp90ezfdmgxvoybh 4772 4552 2006-08-30T16:02:07Z Bjørn 3 Two proposals based on current practices /* sequences based on default sequences */ 4772 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. jaxkoxhe7sdllb1ogm5w2vbhcugqsph 4773 4772 2006-08-30T16:16:45Z Bjørn 3 Missed a / 4773 wikitext text/x-wiki {{Status_yellow}} Each animation will be defined by an xml document, here follows an example: <pre> <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="50" /> <frame index="2" delay="50" /> <frame index="3" delay="50" /> <frame index="4" delay="50" /> <frame index="5" delay="50" /> <frame index="6" delay="50" /> </animation> <animation direction="left"> <sequence start="19" end="24" delay="50" /> </animation> <animation direction="up"> <sequence start="37" end="42" delay="50" /> </animation> <animation direction="right"> <sequence start="55" end="60" delay="50" /> </animation> </action> <action name="sit" imageset="base"> <animation direction="down"> <frame index="7" /> </animation> <animation direction="left"> <frame index="25" /> </animation> <animation direction="up"> <frame index="43" /> </animation> <animation direction="right"> <frame index="61" /> </animation> </action> <action name="dead" imageset="base"> <animation direction="down"> <frame index="8" /> </animation> <animation direction="left"> <frame index="26" /> </animation> <animation direction="up"> <frame index="44" /> </animation> <animation direction="right"> <frame index="62" /> </animation> </action> <action name="attack" imageset="base"> <animation direction="down"> <sequence start="9" end="12" delay="100" /> </animation> <animation direction="left"> <sequence start="27" end="30" delay="100" /> </animation> <animation direction="up"> <sequence start="45" end="48" delay="100" /> </animation> <animation direction="right"> <sequence start="63" end="66" delay="100" /> </animation> </action> </sprite> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | (no name attribute) </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right </pre> when a specific direction isn't provided, the first defined direction is used instead. this can be overridden by defining an animation with the direction "default" for this action. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. == Suggested additions == === multiple delays in a &lt;frame&gt; with start and end attribute === in the bow animation I've chosen a shortcut to specify different delays for different frames. I am undecided yet whether this is a nice feature or whether it'll be better to require multiple <code>frame</code> elements in such cases. === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. fcl0vd9agiutggi3vrb3su313g2vfpm 5093 4773 2006-09-20T23:44:20Z Crush 103 updated to a documentation of the current implementation 5093 wikitext text/x-wiki {{Status_green}} The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item | attack-bow cast-magic | | attack-stab attack-throw \ / run attack-swing sleeping dead | | | | walk attack sit hurt \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> when a specific direction isn't provided, the default direction is used instead. When no default action is defined, the first defined direction is used. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code><end></code> tag, the animation stops and the sprite animation is set back into the "stand" state. This behavior is useful for one time actions like attacking, for example. The end tag has no properties. == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. g8j7xyfk02kuhlmuvspbwvek4d4ge1b 5094 5093 2006-09-21T00:03:10Z Crush 103 /* &lt;action&gt; */ note about unimplemented actions 5094 wikitext text/x-wiki {{Status_green}} The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> when a specific direction isn't provided, the default direction is used instead. When no default action is defined, the first defined direction is used. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code><end></code> tag, the animation stops and the sprite animation is set back into the "stand" state. This behavior is useful for one time actions like attacking, for example. The end tag has no properties. == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. p2pfmmci7sd0t3jmhgjvg1ckj3m2lii 5842 5094 2007-01-07T21:56:16Z Bjørn 3 Made sure the contents shows up at the top 5842 wikitext text/x-wiki {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> when a specific direction isn't provided, the default direction is used instead. When no default action is defined, the first defined direction is used. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code><end></code> tag, the animation stops and the sprite animation is set back into the "stand" state. This behavior is useful for one time actions like attacking, for example. The end tag has no properties. == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. 67ygtmrefgzku00qd79b3bss6y0t5bw 6404 5842 2007-03-24T21:17:37Z Crush 103 ->art and ->programming 6404 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite got two optional properties <code>variants</code> and <code>variant_offset</code>. These are required when there are multiple very similar versions of a sprite in one spriteset. One example for this are the hairset spritesets. <code>variants</code> defines the number of variants in the spriteset and <code>variant_offset</code> 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 wants anotherone. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> when a specific direction isn't provided, the default direction is used instead. When no default action is defined, the first defined direction is used. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code><end></code> tag, the animation stops and the sprite animation is set back into the "stand" state. This behavior is useful for one time actions like attacking, for example. The end tag has no properties. == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. mp8e9usli11sgb8bzvf44yg3ozmwark 8178 6404 2007-11-28T05:15:57Z Jaxad0127 999 /* &lt;sprite&gt; */ Grammer 8178 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> when a specific direction isn't provided, the default direction is used instead. When no default action is defined, the first defined direction is used. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === each of them defines one frame of the animation. the required properties are <code>index</code> and optional <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. an optional property is <code>delay</code>. every frame is displayed for <code>delay</code> millisecounds and then replaced by the next frame in sequence. when the last frame is reached the sequence starts with the first frame again. when no delay is specified (or specified as "0") the animation doesn't continue when this <code>frame</code> is reached. Each <code>frame</code> element can optionally have the properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code><end></code> tag, the animation stops and the sprite animation is set back into the "stand" state. This behavior is useful for one time actions like attacking, for example. The end tag has no properties. == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. er3sl8m77jotbyvn2tbge4omnj58r41 8179 8178 2007-11-28T05:27:25Z Jaxad0127 999 /* &lt;frame&gt; */ Grammer 8179 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> when a specific direction isn't provided, the default direction is used instead. When no default action is defined, the first defined direction is used. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> property specifies the number of milliseconds the frame is displayed before it s replced 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === <code>sequence</code> tag does not only define one animation phase but multiple phases. Its properties are <code>delay</code>, <code>start</code> and <code>end</code> which are all required. The delay is the delay in ms between each phase. the properties <code>start</code> and <code>end</code> define the first and the last index of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code><end></code> tag, the animation stops and the sprite animation is set back into the "stand" state. This behavior is useful for one time actions like attacking, for example. The end tag has no properties. == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. 1amp3y9s8emp6snfr2f28nhu2gi2z9i 8180 8179 2007-11-28T05:34:08Z Jaxad0127 999 /* &lt;sequence&gt; */ Grammer 8180 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> when a specific direction isn't provided, the default direction is used instead. When no default action is defined, the first defined direction is used. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> property specifies the number of milliseconds the frame is displayed before it s replced 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one ov more phases of animation. It has The required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay<code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code><end></code> tag, the animation stops and the sprite animation is set back into the "stand" state. This behavior is useful for one time actions like attacking, for example. The end tag has no properties. == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. lcceoz4iykj3j7b9xeku4xvq0hgrsfr 8181 8180 2007-11-28T05:38:28Z Jaxad0127 999 /* &lt;end&gt; */ Grammer 8181 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> when a specific direction isn't provided, the default direction is used instead. When no default action is defined, the first defined direction is used. Every <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> property specifies the number of milliseconds the frame is displayed before it s replced 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one ov more phases of animation. It has The required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay<code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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 == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. fx5c4fkqjri2vjtpmc0nlkwsmpkyea9 8381 8181 2008-01-04T15:26:36Z Jaxad0127 999 /* &lt;animation&gt; */ action -> direction and removed last paragraph that has nothing to do with this section 8381 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> property specifies the number of milliseconds the frame is displayed before it s replced 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one ov more phases of animation. It has The required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay<code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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 == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. mwzyfnmpz9xl67wltqa0x2feuxuoaud 8382 8381 2008-01-04T15:28:02Z Jaxad0127 999 /* &lt;frame&gt; */ Spelling 8382 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one ov more phases of animation. It has The required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay<code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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 == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. glkddltpr76ffh0bqk3ft5z4h8ahdjs 8383 8382 2008-01-04T15:30:19Z Jaxad0127 999 /* &lt;sequence&gt; */ some small fixes 8383 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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 == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. p0rvrogs9g1ix3co0yhw9eks21gobeu 8384 8383 2008-01-05T04:35:01Z Crush 103 /* &lt;animation&gt; */ that sentence DOES make sense. 8384 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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 == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: <pre> <sprite extends="other-sprite-file.xml"> <imageset name="base" ... /> </sprite> </pre> ==== 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. <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> </sprite> </pre> == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. sz0bxozfonp93g21j52cq9c2epv3f32 10552 8384 2008-11-04T20:12:02Z Bjørn 3 Moved suggested addition to reference, since it was implemented 10552 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </pre> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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: <pre> <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> </pre> Defining an empty imageset (without <code>src</code> 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 <code>name</code> attribute of the <code>sprite</code> 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: == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. erg8m08ljaal9e0he61ug0sz5wez0yh 10553 10552 2008-11-04T20:15:50Z Bjørn 3 Removed more obsolete text 10553 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </pre> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. 9jhxwexnm5rchniu02e6y5egrk3q2p5 10989 10553 2008-12-16T21:47:05Z BasdoMouri 1364 viacdron 10989 wikitext text/x-wiki rocaerc {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </pre> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. pv4q84twmw0pg6rjqjnr073bcracn6h 10990 10989 2008-12-16T22:00:09Z Jaxad0127 999 Revert vandalism 10990 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </pre> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. 9jhxwexnm5rchniu02e6y5egrk3q2p5 11272 10990 2009-01-08T13:54:02Z BasdoMouri 1364 http://mahohmie.qsh.eu/resource1624.htm 11272 wikitext text/x-wiki [http://mahohmie.qsh.eu/resource1624.htm movie times for jarhead] [http://spfortne.qsh.eu/20090104-audio-and-video.html audio and video file formats] [http://cnavieltz.strefa.pl/comment-501.htm ac dc hell highway music video] [http://caraines.qsh.eu/zelnexr.htm movies.max] [http://qasletop.is-the-boss.com/caouchibo.html avast 4.6 crack] {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </pre> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. 9clyp9c8pphz0nofu7d04o238ulmww9 11308 11272 2009-01-08T15:21:29Z Jaxad0127 999 Undo revision 11272 by [[Special:Contributions/BasdoMouri|BasdoMouri]] ([[User talk:BasdoMouri|Talk]]) 11308 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </pre> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. 9jhxwexnm5rchniu02e6y5egrk3q2p5 11692 11308 2009-02-16T16:57:08Z Crush2 1261 added template 11692 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <pre> <?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> </pre> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <pre> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </pre> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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. <pre> 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 </pre> <pre> 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... </pre> <pre> 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 </pre> ===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. <pre> 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 </pre> <pre> 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... </pre> ===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. <pre> 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 </pre> 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. {{Template:Content XML}} f974qz9mz5aewn9skkof3gba9dx7rn9 26656 11692 2013-06-14T21:31:08Z EJlol 294 updated xml tags 26656 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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 <syntaxhighlight lang="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" /> </syntaxhighlight> hairoffsets.xml <syntaxhighlight lang="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... </syntaxhighlight> static_hairstyles_frames.xml <syntaxhighlight lang="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> </syntaxhighlight> ===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 <syntaxhighlight lang="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" /> </syntaxhighlight> animated_hairstyles_frames.xml <syntaxhighlight lang="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... </syntaxhighlight> ===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 <syntaxhighlight lang="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> </syntaxhighlight> 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. {{Template:Content XML}} ek60sih2l6zlr0lxokj0o0pjns2uzm9 26764 26656 2013-06-18T20:50:29Z Jaxad0127 999 Jaxad0127 moved page [[Animations]] to [[Dev:Animations]] 26764 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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 <syntaxhighlight lang="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" /> </syntaxhighlight> hairoffsets.xml <syntaxhighlight lang="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... </syntaxhighlight> static_hairstyles_frames.xml <syntaxhighlight lang="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> </syntaxhighlight> ===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 <syntaxhighlight lang="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" /> </syntaxhighlight> animated_hairstyles_frames.xml <syntaxhighlight lang="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... </syntaxhighlight> ===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 <syntaxhighlight lang="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> </syntaxhighlight> 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. {{Template:Content XML}} ek60sih2l6zlr0lxokj0o0pjns2uzm9 28751 26764 2013-11-10T00:57:15Z Wushin 2233 /* Starting to correct/update documentation on sprite work and animations. */ 28751 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{status_construction}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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: <pre> use-item* | attack-bow cast-magic* | | attack-stab attack-throw* \ / run* attack-swing* sleeping* dead | | | | walk attack sit hurt* \ \ / / stand | default </pre> 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. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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 <syntaxhighlight lang="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" /> </syntaxhighlight> hairoffsets.xml <syntaxhighlight lang="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... </syntaxhighlight> static_hairstyles_frames.xml <syntaxhighlight lang="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> </syntaxhighlight> ===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 <syntaxhighlight lang="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" /> </syntaxhighlight> animated_hairstyles_frames.xml <syntaxhighlight lang="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... </syntaxhighlight> ===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 <syntaxhighlight lang="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> </syntaxhighlight> 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. {{Template:Content XML}} nm8qcmfx2gnpkgce0wvvhxh2hb6zvoe 29397 28751 2014-02-20T04:23:20Z Wushin 2233 /* &lt;action&gt; */ 29397 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{status_construction}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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. Current actions as defined in the base sprite 1.0: Default Walk sit dead attack attack_bow Directions: NSEW New actions/directions will be added as the sprite progresses. Sprite 1.5 work can be seen here [https://trello.com/b/rNnx513z/art-development art trello] The action type matches the item.xml: <pre> <item id="522" image="equipment/weapon/dagger-sharpknife.png" name="Sharp Knife" description="A really sharp knife. Don't hurt yourself!" effect="Damage +10" type="equip-1hand" weapon-type="knife" attack-action="attack" weight="150"> <sprite>weapon-dagger.xml</sprite> <sound event="strike">weapons/knives/sharpknife-miss1.ogg</sound> </item> </pre> Would use attack from the sprite sheets or default if attack is not declared. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> == Suggested additions == {{Status_red}} === &lt;random&gt; childtag for &lt;animation&gt; === 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. == 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 <syntaxhighlight lang="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" /> </syntaxhighlight> hairoffsets.xml <syntaxhighlight lang="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... </syntaxhighlight> static_hairstyles_frames.xml <syntaxhighlight lang="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> </syntaxhighlight> ===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 <syntaxhighlight lang="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" /> </syntaxhighlight> animated_hairstyles_frames.xml <syntaxhighlight lang="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... </syntaxhighlight> ===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 <syntaxhighlight lang="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> </syntaxhighlight> 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. {{Template:Content XML}} dm0s56rog3f3895bnc80jdlc09fj06s 29398 29397 2014-02-20T04:24:56Z Wushin 2233 /* Suggested additions is up to manaplus to provide this now */ 29398 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{status_construction}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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. Current actions as defined in the base sprite 1.0: Default Walk sit dead attack attack_bow Directions: NSEW New actions/directions will be added as the sprite progresses. Sprite 1.5 work can be seen here [https://trello.com/b/rNnx513z/art-development art trello] The action type matches the item.xml: <pre> <item id="522" image="equipment/weapon/dagger-sharpknife.png" name="Sharp Knife" description="A really sharp knife. Don't hurt yourself!" effect="Damage +10" type="equip-1hand" weapon-type="knife" attack-action="attack" weight="150"> <sprite>weapon-dagger.xml</sprite> <sound event="strike">weapons/knives/sharpknife-miss1.ogg</sound> </item> </pre> Would use attack from the sprite sheets or default if attack is not declared. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> == 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 <syntaxhighlight lang="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" /> </syntaxhighlight> hairoffsets.xml <syntaxhighlight lang="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... </syntaxhighlight> static_hairstyles_frames.xml <syntaxhighlight lang="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> </syntaxhighlight> ===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 <syntaxhighlight lang="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" /> </syntaxhighlight> animated_hairstyles_frames.xml <syntaxhighlight lang="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... </syntaxhighlight> ===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 <syntaxhighlight lang="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> </syntaxhighlight> 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. {{Template:Content XML}} 0wgk5lk8ek1nj2tr185320z0o4lzw6n 29400 29398 2014-02-20T04:33:30Z Wushin 2233 /* hairstyles */ 29400 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{status_construction}} {{Status_green}} == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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. Current actions as defined in the base sprite 1.0: Default Walk sit dead attack attack_bow Directions: NSEW New actions/directions will be added as the sprite progresses. Sprite 1.5 work can be seen here [https://trello.com/b/rNnx513z/art-development art trello] The action type matches the item.xml: <pre> <item id="522" image="equipment/weapon/dagger-sharpknife.png" name="Sharp Knife" description="A really sharp knife. Don't hurt yourself!" effect="Damage +10" type="equip-1hand" weapon-type="knife" attack-action="attack" weight="150"> <sprite>weapon-dagger.xml</sprite> <sound event="strike">weapons/knives/sharpknife-miss1.ogg</sound> </item> </pre> Would use attack from the sprite sheets or default if attack is not declared. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> === hairstyles === Most hairstyles which only have one frame for each direction and death, so five frames. The offset for the hairstyles is standard to either haristlye01.xml or hairstyle13.xml Currently the hairsprites follow the [http://manaplus.org/items.xml hairsprite convetion] {{Template:Content XML}} t31sxs865aj5m9djxq0sjiylkcju1z9 29401 29400 2014-02-20T04:37:42Z Wushin 2233 /* adding note to client documentation */ 29401 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} TMW follows the same conventions as laid out by the client [http://manaplus.org/ manaplus] == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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. Current actions as defined in the base sprite 1.0: Default Walk sit dead attack attack_bow Directions: NSEW New actions/directions will be added as the sprite progresses. Sprite 1.5 work can be seen here [https://trello.com/b/rNnx513z/art-development art trello] The action type matches the item.xml: <pre> <item id="522" image="equipment/weapon/dagger-sharpknife.png" name="Sharp Knife" description="A really sharp knife. Don't hurt yourself!" effect="Damage +10" type="equip-1hand" weapon-type="knife" attack-action="attack" weight="150"> <sprite>weapon-dagger.xml</sprite> <sound event="strike">weapons/knives/sharpknife-miss1.ogg</sound> </item> </pre> Would use attack from the sprite sheets or default if attack is not declared. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> === hairstyles === Most hairstyles which only have one frame for each direction and death, so five frames. The offset for the hairstyles is standard to either haristlye01.xml or hairstyle13.xml Currently the hairsprites follow the [http://manaplus.org/items.xml hairsprite convetion] {{Template:Content XML}} 079i7cg4t8zjwqv6n7in4g2ahusnaxp 31854 29401 2014-12-17T16:22:56Z Wushin 2233 /* categorizing */ 31854 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} TMW follows the same conventions as laid out by the client [http://manaplus.org/ manaplus] == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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. Current actions as defined in the base sprite 1.0: Default Walk sit dead attack attack_bow Directions: NSEW New actions/directions will be added as the sprite progresses. Sprite 1.5 work can be seen here [https://trello.com/b/rNnx513z/art-development art trello] The action type matches the item.xml: <pre> <item id="522" image="equipment/weapon/dagger-sharpknife.png" name="Sharp Knife" description="A really sharp knife. Don't hurt yourself!" effect="Damage +10" type="equip-1hand" weapon-type="knife" attack-action="attack" weight="150"> <sprite>weapon-dagger.xml</sprite> <sound event="strike">weapons/knives/sharpknife-miss1.ogg</sound> </item> </pre> Would use attack from the sprite sheets or default if attack is not declared. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> === hairstyles === Most hairstyles which only have one frame for each direction and death, so five frames. The offset for the hairstyles is standard to either haristlye01.xml or hairstyle13.xml Currently the hairsprites follow the [http://manaplus.org/items.xml hairsprite convetion] {{Template:Content XML}} [[Category:Development]] iq8dk6zhxmf7nz4qgz1vdvwobysd173 59464 31854 2024-03-27T03:56:41Z Move page script 2739 Move page script moved page [[Dev:Animations]] to [[Development:Animations]]: Rename Dev: to Development: so the miraheze import works 31854 wikitext text/x-wiki {{Category_programming}} {{Category_art}} {{Status_green}} TMW follows the same conventions as laid out by the client [http://manaplus.org/ manaplus] == Example of a sprite definition == The animations of all sprites are defined by xml documents. Here follows an example: <syntaxhighlight lang="xml"> <?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> </syntaxhighlight> 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 == === &lt;sprite&gt; === A sprite is an object which can carry several animations, hence we call the root element the <code>sprite</code>. The sprite tag has two optional properties <code>variants</code> and <code>variant_offset</code>. 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 <code>variants</code> property defines the number of variants in the spriteset and the <code>variant_offset</code> 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. === &lt;action&gt; === 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. Current actions as defined in the base sprite 1.0: Default Walk sit dead attack attack_bow Directions: NSEW New actions/directions will be added as the sprite progresses. Sprite 1.5 work can be seen here [https://trello.com/b/rNnx513z/art-development art trello] The action type matches the item.xml: <pre> <item id="522" image="equipment/weapon/dagger-sharpknife.png" name="Sharp Knife" description="A really sharp knife. Don't hurt yourself!" effect="Damage +10" type="equip-1hand" weapon-type="knife" attack-action="attack" weight="150"> <sprite>weapon-dagger.xml</sprite> <sound event="strike">weapons/knives/sharpknife-miss1.ogg</sound> </item> </pre> Would use attack from the sprite sheets or default if attack is not declared. === &lt;animation&gt; === Defines an animation sequence that should be displayed when the sprite object faces in a specific direction (attribute "direction"). the possible directions are: <pre> up down left right default </pre> 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 <code><animation></code> has one or more <code>frame</code> or <code>sequence</code> child elements and an optional <code><end></code> element. === &lt;frame&gt; === Defines one frame of the animation. The only required property is <code>index</code>. Optional properties include <code>offsetX</code>, <code>offsetY</code> and <code>delay</code>. <code>index</code> defines the index of the graphic on the spriteset. The <code>delay</code> 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 <code>frame</code> is reached. The <code>frame</code> element has the optional properties <code>offsetX</code> and <code>offsetY</code> 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. === &lt;sequence&gt; === The <code>sequence</code> tag defines one or more phases of animation. It has the required properties <code>delay</code>, <code>start</code>, and <code>end</code>. The <code>delay</code> property specifies the delay in milliseconds between each phase. The <code>start</code> and <code>end</code> properties define the first and the last indexes of the animation sequence on the spritesheet. === &lt;end&gt; === When the animation sequence reaches an <code>end</code> 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. === &lt;include&gt; === Can be used to include another sprite definition file. If you want to override the images, you need to specify them ''before'' the include element. If you want to override any animations, you have to do so ''after'' the include element. Example: <syntaxhighlight lang="xml"> <sprite> <imageset name="base" .../> <include file="other-sprite-file.xml"/> <!-- possibly override or introduce new actions --> </sprite> </syntaxhighlight> === hairstyles === Most hairstyles which only have one frame for each direction and death, so five frames. The offset for the hairstyles is standard to either haristlye01.xml or hairstyle13.xml Currently the hairsprites follow the [http://manaplus.org/items.xml hairsprite convetion] {{Template:Content XML}} [[Category:Development]] iq8dk6zhxmf7nz4qgz1vdvwobysd173 0 10065 40468 2016-04-07T17:29:23Z Wushin 2233 /* Add Better Bitmask tutorial */ 40468 wikitext text/x-wiki ==Bit Masking Easy Reference Chart== |-------------------------------------------------------------------------------------| Byte |0 |1 |2 |3 | |-------------------------------------------------------------------------------------| Nibble |0 |1 |2 |3 |4 |5 |6 |7 | |-------------------------------------------------------------------------------------| 2 Bits |0 |1 |2 |3 |4 |5 |6 |7 |8 |9 |10 |11 |12 |13 |14 |15 | |-------------------------------------------------------------------------------------| Bits |0|1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24|25|26|27|28|29|30|31| |-------------------------------------------------------------------------------------| * All variables haves 4 Bytes, 8 Nibbles, 16 2Bits and/or 32 bits. ** Byte range 0-255 ** Nibble range 0-15 ** 2Bit range 0-3 ** bit range 0 or 1 ==One Nibble Translated== * Binary = Decimal ** 0000 = 0 ** 0001 = 1 ** 0010 = 2 ** 0011 = 3 ** 0100 = 4 ** 0101 = 5 ** 0110 = 6 ** 0111 = 7 ** 1000 = 8 ** 1001 = 9 ** 1010 = 10 ** 1011 = 11 ** 1100 = 12 ** 1101 = 13 ** 1110 = 14 ** 1111 = 15 *** Note: Therefore Setting Bits 4-7 to 1 will make Nibble 1 15. Therefore Setting Bits 0-7 will make Nibble 0 & 1 15, and Byte 0 255 ==Linear Quest Var== * BYTE: ** 0: Step1. ** 1: Step2. ** ... ** 255: Step256. * Nibble: ** 0: Step1. ** 1: Step2. ** ... ** 14: Step16. ==Non-linear Quest Var== * BYTE: Main Quest Line ** NIBBLE: Current-Step *** BIT: Step *** BIT: Step *** BIT: Step *** BIT: Step ** NIBBLE: Sub-Quest *** 0-15: Step 1-16 Dev Note: There are plans to make 64 bit quest variables. 001-1,40,36,0|script|BitMaskDebug|175 { mes "[Bit Mask Debug]"; mes "\"What you wyou like to do?\""; menu "Shift Byte 1.", L_ByteShift, "Shift Nibble 0.", L_NibbleShift, "Shift Bit 4.", L_BitShift, "Done.", L_Close; L_ByteShift: set @debugexample, ((DEBUGEXAMPLE & BYTE_1_MASK) >> BYTE_1_SHIFT); message strcharinfo(0), @debugexample; if (@debugexample == 175) goto L_ByteUnset; mes "Byte 1 set to 175"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(BYTE_1_MASK) | (175 << BYTE_1_SHIFT)); goto L_Close; L_ByteUnset: mes "Byte 1 set to 0"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(BYTE_1_MASK) | (0 << BYTE_1_SHIFT)); goto L_Close; L_NibbleShift: set @debugexample, ((DEBUGEXAMPLE & NIBBLE_0_MASK) >> NIBBLE_0_SHIFT); message strcharinfo(0), @debugexample; if (@debugexample == 10) goto L_NibbleUnset; mes "Nibble 0 set to 10"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(NIBBLE_0_MASK) | (10 << NIBBLE_0_SHIFT)); goto L_Close; L_NibbleUnset: mes "Nibble 0 set to 0"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(NIBBLE_0_MASK) | (0 << NIBBLE_0_SHIFT)); goto L_Close; L_BitShift: set @debugexample, ((DEBUGEXAMPLE & NIBBLE_1_MASK) >> NIBBLE_1_SHIFT); message strcharinfo(0), @debugexample; if (DEBUGEXAMPLE & (1 << 4)) goto L_BitUnset; mes "Bit 4 Set to 1"; set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 4); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 5); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 6); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 7); goto L_Close; L_BitUnset: mes "Bit 4 Set to 0"; set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 4); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 5); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 6); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 7); goto L_Close; L_Close: set @debugexample, 0; close; OnInit: if (debug) end; disablenpc "BitMaskDebug"; end; } ju9ltrgh7r6c4ip6swajiakrph2j0d8 40470 40468 2016-04-07T17:35:33Z Wushin 2233 Wushin moved page [[Bit mask tutorial]] to [[Dev:Bit mask tutorial]] 40470 wikitext text/x-wiki ==Bit Masking Easy Reference Chart== |-------------------------------------------------------------------------------------| Byte |0 |1 |2 |3 | |-------------------------------------------------------------------------------------| Nibble |0 |1 |2 |3 |4 |5 |6 |7 | |-------------------------------------------------------------------------------------| 2 Bits |0 |1 |2 |3 |4 |5 |6 |7 |8 |9 |10 |11 |12 |13 |14 |15 | |-------------------------------------------------------------------------------------| Bits |0|1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24|25|26|27|28|29|30|31| |-------------------------------------------------------------------------------------| * All variables haves 4 Bytes, 8 Nibbles, 16 2Bits and/or 32 bits. ** Byte range 0-255 ** Nibble range 0-15 ** 2Bit range 0-3 ** bit range 0 or 1 ==One Nibble Translated== * Binary = Decimal ** 0000 = 0 ** 0001 = 1 ** 0010 = 2 ** 0011 = 3 ** 0100 = 4 ** 0101 = 5 ** 0110 = 6 ** 0111 = 7 ** 1000 = 8 ** 1001 = 9 ** 1010 = 10 ** 1011 = 11 ** 1100 = 12 ** 1101 = 13 ** 1110 = 14 ** 1111 = 15 *** Note: Therefore Setting Bits 4-7 to 1 will make Nibble 1 15. Therefore Setting Bits 0-7 will make Nibble 0 & 1 15, and Byte 0 255 ==Linear Quest Var== * BYTE: ** 0: Step1. ** 1: Step2. ** ... ** 255: Step256. * Nibble: ** 0: Step1. ** 1: Step2. ** ... ** 14: Step16. ==Non-linear Quest Var== * BYTE: Main Quest Line ** NIBBLE: Current-Step *** BIT: Step *** BIT: Step *** BIT: Step *** BIT: Step ** NIBBLE: Sub-Quest *** 0-15: Step 1-16 Dev Note: There are plans to make 64 bit quest variables. 001-1,40,36,0|script|BitMaskDebug|175 { mes "[Bit Mask Debug]"; mes "\"What you wyou like to do?\""; menu "Shift Byte 1.", L_ByteShift, "Shift Nibble 0.", L_NibbleShift, "Shift Bit 4.", L_BitShift, "Done.", L_Close; L_ByteShift: set @debugexample, ((DEBUGEXAMPLE & BYTE_1_MASK) >> BYTE_1_SHIFT); message strcharinfo(0), @debugexample; if (@debugexample == 175) goto L_ByteUnset; mes "Byte 1 set to 175"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(BYTE_1_MASK) | (175 << BYTE_1_SHIFT)); goto L_Close; L_ByteUnset: mes "Byte 1 set to 0"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(BYTE_1_MASK) | (0 << BYTE_1_SHIFT)); goto L_Close; L_NibbleShift: set @debugexample, ((DEBUGEXAMPLE & NIBBLE_0_MASK) >> NIBBLE_0_SHIFT); message strcharinfo(0), @debugexample; if (@debugexample == 10) goto L_NibbleUnset; mes "Nibble 0 set to 10"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(NIBBLE_0_MASK) | (10 << NIBBLE_0_SHIFT)); goto L_Close; L_NibbleUnset: mes "Nibble 0 set to 0"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(NIBBLE_0_MASK) | (0 << NIBBLE_0_SHIFT)); goto L_Close; L_BitShift: set @debugexample, ((DEBUGEXAMPLE & NIBBLE_1_MASK) >> NIBBLE_1_SHIFT); message strcharinfo(0), @debugexample; if (DEBUGEXAMPLE & (1 << 4)) goto L_BitUnset; mes "Bit 4 Set to 1"; set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 4); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 5); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 6); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 7); goto L_Close; L_BitUnset: mes "Bit 4 Set to 0"; set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 4); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 5); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 6); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 7); goto L_Close; L_Close: set @debugexample, 0; close; OnInit: if (debug) end; disablenpc "BitMaskDebug"; end; } ju9ltrgh7r6c4ip6swajiakrph2j0d8 40473 40470 2016-04-07T18:08:29Z Gumi 2315 40473 wikitext text/x-wiki ==Bit Masking Easy Reference Chart== <table> <tr> <th>long word</th> <td colspan="32">0</td> </tr> <tr> <th>word</th> <td colspan="16">0</td><td colspan="16">1</td> </tr> <tr> <th>byte</th> <td colspan="8">0</td><td colspan="8">1</td><td colspan="8">2</td><td colspan="8">3</td> </tr> <tr> <th>nibble</th> <td colspan="4">0</td><td colspan="4">1</td><td colspan="4">2</td><td colspan="4">3</td> <td colspan="4">4</td><td colspan="4">5</td><td colspan="4">6</td><td colspan="4">7</td> </tr> <tr> <th>2-bit</th> <td colspan="2">0</td><td colspan="2">1</td><td colspan="2">2</td><td colspan="2">3</td> <td colspan="2">4</td><td colspan="2">5</td><td colspan="2">6</td><td colspan="2">7</td> <td colspan="2">8</td><td colspan="2">9</td><td colspan="2">10</td><td colspan="2">11</td> <td colspan="2">12</td><td colspan="2">13</td><td colspan="2">14</td><td colspan="2">15</td> </tr> <tr> <th>bit</th> <td>0</td><td>1</td><td>2</td><td>3</td> <td>4</td><td>5</td><td>6</td><td>7</td> <td>8</td><td>9</td><td>10</td><td>11</td> <td>12</td><td>13</td><td>14</td><td>15</td> <td>16</td><td>17</td><td>18</td><td>19</td> <td>20</td><td>21</td><td>22</td><td>23</td> <td>24</td><td>25</td><td>26</td><td>27</td> <td>28</td><td>29</td><td>30</td><td>31</td> </tr> </table> * All variables haves 1 Long Word, 2 Words, 4 Bytes, 8 Nibbles, 16 2Bits and/or 32 bits. ** Byte range 0-255 ** Nibble range 0-15 ** 2Bit range 0-3 ** bit range 0 or 1 ==One Nibble Translated== * Binary = Decimal ** 0000 = 0 ** 0001 = 1 ** 0010 = 2 ** 0011 = 3 ** 0100 = 4 ** 0101 = 5 ** 0110 = 6 ** 0111 = 7 ** 1000 = 8 ** 1001 = 9 ** 1010 = 10 ** 1011 = 11 ** 1100 = 12 ** 1101 = 13 ** 1110 = 14 ** 1111 = 15 *** Note: Therefore Setting Bits 4-7 to 1 will make Nibble 1 15. Therefore Setting Bits 0-7 will make Nibble 0 & 1 15, and Byte 0 255 ==Linear Quest Var== * BYTE: ** 0: Step1. ** 1: Step2. ** ... ** 255: Step256. * Nibble: ** 0: Step1. ** 1: Step2. ** ... ** 14: Step16. ==Non-linear Quest Var== * BYTE: Main Quest Line ** NIBBLE: Current-Step *** BIT: Step *** BIT: Step *** BIT: Step *** BIT: Step ** NIBBLE: Sub-Quest *** 0-15: Step 1-16 Dev Note: There are plans to make 64 bit quest variables. 001-1,40,36,0|script|BitMaskDebug|175 { mes "[Bit Mask Debug]"; mes "\"What you wyou like to do?\""; menu "Shift Byte 1.", L_ByteShift, "Shift Nibble 0.", L_NibbleShift, "Shift Bit 4.", L_BitShift, "Done.", L_Close; L_ByteShift: set @debugexample, ((DEBUGEXAMPLE & BYTE_1_MASK) >> BYTE_1_SHIFT); message strcharinfo(0), @debugexample; if (@debugexample == 175) goto L_ByteUnset; mes "Byte 1 set to 175"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(BYTE_1_MASK) | (175 << BYTE_1_SHIFT)); goto L_Close; L_ByteUnset: mes "Byte 1 set to 0"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(BYTE_1_MASK) | (0 << BYTE_1_SHIFT)); goto L_Close; L_NibbleShift: set @debugexample, ((DEBUGEXAMPLE & NIBBLE_0_MASK) >> NIBBLE_0_SHIFT); message strcharinfo(0), @debugexample; if (@debugexample == 10) goto L_NibbleUnset; mes "Nibble 0 set to 10"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(NIBBLE_0_MASK) | (10 << NIBBLE_0_SHIFT)); goto L_Close; L_NibbleUnset: mes "Nibble 0 set to 0"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(NIBBLE_0_MASK) | (0 << NIBBLE_0_SHIFT)); goto L_Close; L_BitShift: set @debugexample, ((DEBUGEXAMPLE & NIBBLE_1_MASK) >> NIBBLE_1_SHIFT); message strcharinfo(0), @debugexample; if (DEBUGEXAMPLE & (1 << 4)) goto L_BitUnset; mes "Bit 4 Set to 1"; set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 4); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 5); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 6); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 7); goto L_Close; L_BitUnset: mes "Bit 4 Set to 0"; set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 4); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 5); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 6); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 7); goto L_Close; L_Close: set @debugexample, 0; close; OnInit: if (debug) end; disablenpc "BitMaskDebug"; end; } rgkwszx4p4jjcp9gg4nk5z0ofs875mk 59466 40473 2024-03-27T03:56:42Z Move page script 2739 Move page script moved page [[Dev:Bit mask tutorial]] to [[Development:Bit mask tutorial]]: Rename Dev: to Development: so the miraheze import works 40473 wikitext text/x-wiki ==Bit Masking Easy Reference Chart== <table> <tr> <th>long word</th> <td colspan="32">0</td> </tr> <tr> <th>word</th> <td colspan="16">0</td><td colspan="16">1</td> </tr> <tr> <th>byte</th> <td colspan="8">0</td><td colspan="8">1</td><td colspan="8">2</td><td colspan="8">3</td> </tr> <tr> <th>nibble</th> <td colspan="4">0</td><td colspan="4">1</td><td colspan="4">2</td><td colspan="4">3</td> <td colspan="4">4</td><td colspan="4">5</td><td colspan="4">6</td><td colspan="4">7</td> </tr> <tr> <th>2-bit</th> <td colspan="2">0</td><td colspan="2">1</td><td colspan="2">2</td><td colspan="2">3</td> <td colspan="2">4</td><td colspan="2">5</td><td colspan="2">6</td><td colspan="2">7</td> <td colspan="2">8</td><td colspan="2">9</td><td colspan="2">10</td><td colspan="2">11</td> <td colspan="2">12</td><td colspan="2">13</td><td colspan="2">14</td><td colspan="2">15</td> </tr> <tr> <th>bit</th> <td>0</td><td>1</td><td>2</td><td>3</td> <td>4</td><td>5</td><td>6</td><td>7</td> <td>8</td><td>9</td><td>10</td><td>11</td> <td>12</td><td>13</td><td>14</td><td>15</td> <td>16</td><td>17</td><td>18</td><td>19</td> <td>20</td><td>21</td><td>22</td><td>23</td> <td>24</td><td>25</td><td>26</td><td>27</td> <td>28</td><td>29</td><td>30</td><td>31</td> </tr> </table> * All variables haves 1 Long Word, 2 Words, 4 Bytes, 8 Nibbles, 16 2Bits and/or 32 bits. ** Byte range 0-255 ** Nibble range 0-15 ** 2Bit range 0-3 ** bit range 0 or 1 ==One Nibble Translated== * Binary = Decimal ** 0000 = 0 ** 0001 = 1 ** 0010 = 2 ** 0011 = 3 ** 0100 = 4 ** 0101 = 5 ** 0110 = 6 ** 0111 = 7 ** 1000 = 8 ** 1001 = 9 ** 1010 = 10 ** 1011 = 11 ** 1100 = 12 ** 1101 = 13 ** 1110 = 14 ** 1111 = 15 *** Note: Therefore Setting Bits 4-7 to 1 will make Nibble 1 15. Therefore Setting Bits 0-7 will make Nibble 0 & 1 15, and Byte 0 255 ==Linear Quest Var== * BYTE: ** 0: Step1. ** 1: Step2. ** ... ** 255: Step256. * Nibble: ** 0: Step1. ** 1: Step2. ** ... ** 14: Step16. ==Non-linear Quest Var== * BYTE: Main Quest Line ** NIBBLE: Current-Step *** BIT: Step *** BIT: Step *** BIT: Step *** BIT: Step ** NIBBLE: Sub-Quest *** 0-15: Step 1-16 Dev Note: There are plans to make 64 bit quest variables. 001-1,40,36,0|script|BitMaskDebug|175 { mes "[Bit Mask Debug]"; mes "\"What you wyou like to do?\""; menu "Shift Byte 1.", L_ByteShift, "Shift Nibble 0.", L_NibbleShift, "Shift Bit 4.", L_BitShift, "Done.", L_Close; L_ByteShift: set @debugexample, ((DEBUGEXAMPLE & BYTE_1_MASK) >> BYTE_1_SHIFT); message strcharinfo(0), @debugexample; if (@debugexample == 175) goto L_ByteUnset; mes "Byte 1 set to 175"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(BYTE_1_MASK) | (175 << BYTE_1_SHIFT)); goto L_Close; L_ByteUnset: mes "Byte 1 set to 0"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(BYTE_1_MASK) | (0 << BYTE_1_SHIFT)); goto L_Close; L_NibbleShift: set @debugexample, ((DEBUGEXAMPLE & NIBBLE_0_MASK) >> NIBBLE_0_SHIFT); message strcharinfo(0), @debugexample; if (@debugexample == 10) goto L_NibbleUnset; mes "Nibble 0 set to 10"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(NIBBLE_0_MASK) | (10 << NIBBLE_0_SHIFT)); goto L_Close; L_NibbleUnset: mes "Nibble 0 set to 0"; set DEBUGEXAMPLE, (DEBUGEXAMPLE & ~(NIBBLE_0_MASK) | (0 << NIBBLE_0_SHIFT)); goto L_Close; L_BitShift: set @debugexample, ((DEBUGEXAMPLE & NIBBLE_1_MASK) >> NIBBLE_1_SHIFT); message strcharinfo(0), @debugexample; if (DEBUGEXAMPLE & (1 << 4)) goto L_BitUnset; mes "Bit 4 Set to 1"; set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 4); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 5); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 6); set DEBUGEXAMPLE, DEBUGEXAMPLE | (1 << 7); goto L_Close; L_BitUnset: mes "Bit 4 Set to 0"; set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 4); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 5); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 6); set DEBUGEXAMPLE, DEBUGEXAMPLE &~ (1 << 7); goto L_Close; L_Close: set @debugexample, 0; close; OnInit: if (debug) end; disablenpc "BitMaskDebug"; end; } rgkwszx4p4jjcp9gg4nk5z0ofs875mk 0 3466 9866 2008-08-14T01:45:59Z Jaxad0127 999 Initial draft 9866 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>name</code>s and <code>value</code>s. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> gpgfp74obfyajfpg8bpb0ujuly2k6cx 9867 9866 2008-08-14T01:52:06Z Jaxad0127 999 /* Usage */ Expand on item database 9867 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>name</code>s and <code>value</code>s. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color index to use. The first entry is number one. Undyed items use index 0. ===Others=== I cannot think of other uses for these files at the moment. 200bab52cfu7p45zt1y896rvpsop24q 9868 9867 2008-08-14T01:56:54Z Jaxad0127 999 /* Item Database */ Add item name changing 9868 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>name</code>s and <code>value</code>s. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color index to use. The first entry is number one. Undyed items use index 0. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). ===Others=== I cannot think of other uses for these files at the moment. 2n70mownh67gm6wh9lqe7n9dl3iy7bd 9882 9868 2008-08-14T13:59:10Z Jaxad0127 999 /* &lt;color&gt; */ Add id attribute 9882 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color index to use. The first entry is number one. Undyed items use index 0. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). ===Others=== I cannot think of other uses for these files at the moment. 8k23atf2nyl3zh3fyl3mqhincacol2x 9883 9882 2008-08-14T14:03:03Z Jaxad0127 999 /* Item Database */ Fix ID info 9883 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). ===Others=== I cannot think of other uses for these files at the moment. e3mm4bl8g3v1pti0h5bkb6q9hoic5qo 9888 9883 2008-08-14T14:31:16Z Jaxad0127 999 Add links to example files 9888 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). ===Others=== I cannot think of other uses for these files at the moment. ==Examples== I've made some examples based on the colors in the client code and item databases: *[[User:Jaxad0127/Color files/Hair colors|Hair colors]] *[[User:Jaxad0127/Color files/Pants colors|Pants colors]] *[[User:Jaxad0127/Color files/Shirt colors|Shirt colors]] *[[User:Jaxad0127/Color files/Skirt colors|Skirt colors]] m5ysvn41tkxatj7s7pb70so850dmq99 10065 9888 2008-09-04T19:22:12Z Bjørn 3 Added question about making it global and internationalisation 10065 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). ===Others=== I cannot think of other uses for these files at the moment. ==Examples== I've made some examples based on the colors in the client code and item databases: *[[User:Jaxad0127/Color files/Hair colors|Hair colors]] *[[User:Jaxad0127/Color files/Pants colors|Pants colors]] *[[User:Jaxad0127/Color files/Shirt colors|Shirt colors]] *[[User:Jaxad0127/Color files/Skirt colors|Skirt colors]] == Discussion == ''Wouldn't it make sense rather to have one color file, making all color IDs global? I don't see why you would restrict one set of colors to only one item, and having it global would save a lot of typing and maintenance. Also, what about internationalisation?'' --[[User:Bjørn|Bjørn]] 21:22, 4 September 2008 (CEST) njgwiau6bfhp1q11dwzp0w97mq1whz9 10067 10065 2008-09-04T23:25:46Z Jaxad0127 999 /* Discussion */ respond 10067 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). ===Others=== I cannot think of other uses for these files at the moment. ==Examples== I've made some examples based on the colors in the client code and item databases: *[[User:Jaxad0127/Color files/Hair colors|Hair colors]] *[[User:Jaxad0127/Color files/Pants colors|Pants colors]] *[[User:Jaxad0127/Color files/Shirt colors|Shirt colors]] *[[User:Jaxad0127/Color files/Skirt colors|Skirt colors]] == Discussion == ''Wouldn't it make sense rather to have one color file, making all color IDs global? I don't see why you would restrict one set of colors to only one item, and having it global would save a lot of typing and maintenance. Also, what about internationalisation?'' --[[User:Bjørn|Bjørn]] 21:22, 4 September 2008 (CEST) :One file is possible, yes. But with all the duplicate names in clothing, I thought it would be easier this way. For internationalization, I'll use the same system the DBs use, once it's figured out :). &mdash; [[User:Jaxad0127|<span style="color: #160196">Jaxad</span>]][[User Talk:Jaxad0127|<span style="color: #5B038F">0127</span>]] 01:25, 5 September 2008 (CEST) 6fu2cfjo3xdp5ik5xh6a0r9i3ftaf0z 11679 10067 2009-02-16T14:51:53Z Jaxad0127 999 discussion moved to talk page 11679 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). ===Others=== I cannot think of other uses for these files at the moment. ==Examples== I've made some examples based on the colors in the client code and item databases: *[[User:Jaxad0127/Color files/Hair colors|Hair colors]] *[[User:Jaxad0127/Color files/Pants colors|Pants colors]] *[[User:Jaxad0127/Color files/Shirt colors|Shirt colors]] *[[User:Jaxad0127/Color files/Skirt colors|Skirt colors]] m5ysvn41tkxatj7s7pb70so850dmq99 11681 11679 2009-02-16T14:52:42Z Jaxad0127 999 move examples elsewhere for now 11681 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). fsuk2elop8labagsqndzac8a0ewrceo 11682 11681 2009-02-16T14:53:05Z Jaxad0127 999 [[User:Jaxad0127/Color files]] moved to [[Color XML]]: move outside of my namespace 11682 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). fsuk2elop8labagsqndzac8a0ewrceo 26910 11682 2013-06-24T18:07:13Z Jaxad0127 999 Jaxad0127 moved page [[Color XML]] to [[Dev:Color XML]] 26910 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). fsuk2elop8labagsqndzac8a0ewrceo 59468 26910 2024-03-27T03:56:42Z Move page script 2739 Move page script moved page [[Dev:Color XML]] to [[Development:Color XML]]: Rename Dev: to Development: so the miraheze import works 26910 wikitext text/x-wiki [[Color files]] are files that specify colors that can be used for various purposes. The colors specified in these files are suited for use in [[Image dyeing]] and other purposes. ==Structure== Color files are in XML format. ===&lt;colors&gt;=== This is the root element of the file. ===&lt;color&gt;=== And individual color. <code>Color</code>s have <code>id</code>s, <code>name</code>s, and <code>value</code>s. The <code>id</code> is the value used to identify the color. The <code>name</code> is a description for the user. The <code>value</code> is the information used by the code. Example (these are the current hair colors): <code> &lt;colors&gt; &lt;color id="0" name="Light Red" value="#8c4b41,da9041,ffffff"/&gt; &lt;color id="1" name="Green" value="#06372b,489e25,fdedcc"/&gt; &lt;color id="2" name="Red" value="#5f0b33,91191c,f9ad81"/&gt; ... &lt;/colors&gt; </code> ==Usage== ===Item Database=== In the item database, item elements reference the color files. Example: <code> &lt;item id="-1" type="hairsprite" colors="colors_hairstyles.xml"&gt; &lt;sprite gender="male"&gt;hairstyle1-male.xml&lt;/sprite&gt; &lt;sprite gender="female"&gt;hairstyle1-female.xml&lt;/sprite&gt; &lt;/item&gt; </code> When the server sends a dyed item, it also sends the color id to use. The client adds the color name to the item name (turning "Cotton Shirt" to "Red Cotton Shirt" for a color named "Red"). fsuk2elop8labagsqndzac8a0ewrceo 0 987 69 2005-05-23T18:24:32Z Pajarico 5 69 wikitext text/x-wiki Feel free to add yours. = General art = http://themanaworld.org/archive/nevilytis/mana05.jpg http://themanaworld.org/archive/nevilytis/mana011.jpg http://themanaworld.org/archive/nevilytis/mana049.jpg * by nevilytis I saw the post about the login screen and some of the chars inspired me... http://themanaworld.org/archive/itsnervedamage/Manaworld.png * by itsnervedamage = Temple art = Those two were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. [http://themanaworld.org/archive/pajarico/scenery-temple2-3052006.jpg]<br> [http://themanaworld.org/archive/pajarico/temple-desert-30042006.jpg]<br> * by [[Pajarico]] mo9aocoli9kt1bafl3dhlqv5iybn2qo 70 69 2005-05-23T19:29:03Z Bjørn 3 Used thumbnails /* Temple art */ 70 wikitext text/x-wiki Feel free to add yours. = General art = http://themanaworld.org/archive/nevilytis/mana05.jpg http://themanaworld.org/archive/nevilytis/mana011.jpg http://themanaworld.org/archive/nevilytis/mana049.jpg * by nevilytis I saw the post about the login screen and some of the chars inspired me... http://themanaworld.org/archive/itsnervedamage/Manaworld.png * by itsnervedamage = Temple art = Those two were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. [http://themanaworld.org/archive/pajarico/scenery-temple2-3052006.jpg http://themanaworld.org/archive/pajarico/thumbs/scenery-temple2-3052006.jpg.thumb.jpg] [http://themanaworld.org/archive/pajarico/temple-desert-30042006.jpg http://themanaworld.org/archive/pajarico/thumbs/temple-desert-30042006.jpg.thumb.jpg] * by [[Pajarico]] m6ss7keennqisyczjpti9qtho8krpk4 396 70 2005-05-23T19:34:34Z Bjørn 3 More thumbnails 396 wikitext text/x-wiki Feel free to add yours. = General art = [http://themanaworld.org/archive/nevilytis/mana05.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana05.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana011.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana011.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana049.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana049.jpg.thumb.jpg] * by nevilytis I saw the post about the login screen and some of the chars inspired me... [http://themanaworld.org/archive/itsnervedamage/Manaworld.png http://themanaworld.org/archive/itsnervedamage/thumbs/Manaworld.png.thumb.jpg] * by itsnervedamage = Temple art = Those two were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. [http://themanaworld.org/archive/pajarico/scenery-temple2-3052006.jpg http://themanaworld.org/archive/pajarico/thumbs/scenery-temple2-3052006.jpg.thumb.jpg] [http://themanaworld.org/archive/pajarico/temple-desert-30042006.jpg http://themanaworld.org/archive/pajarico/thumbs/temple-desert-30042006.jpg.thumb.jpg] * by [[Pajarico]] pitrsobrqdrh97txvhjwg07ucdiqg4u 774 396 2005-07-07T23:13:24Z Bjørn 3 Small gallery /* Temple art */ 774 wikitext text/x-wiki Feel free to add yours. = General art = [http://themanaworld.org/archive/nevilytis/mana05.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana05.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana011.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana011.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana049.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana049.jpg.thumb.jpg] * by nevilytis I saw the post about the login screen and some of the chars inspired me... [http://themanaworld.org/archive/itsnervedamage/Manaworld.png http://themanaworld.org/archive/itsnervedamage/thumbs/Manaworld.png.thumb.jpg] * by itsnervedamage = Temple art = These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> 9gbg5uhq7ivvky1xp1zqdd84nqjvcqr 775 774 2005-09-15T10:29:42Z Pajarico 5 /* Temple art */ 775 wikitext text/x-wiki Feel free to add yours. = General art = [http://themanaworld.org/archive/nevilytis/mana05.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana05.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana011.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana011.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana049.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana049.jpg.thumb.jpg] * by nevilytis I saw the post about the login screen and some of the chars inspired me... [http://themanaworld.org/archive/itsnervedamage/Manaworld.png http://themanaworld.org/archive/itsnervedamage/thumbs/Manaworld.png.thumb.jpg] * by itsnervedamage = Temple art = These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> = Creature art = <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> hlf1kep841iorq0weqxmd89ybxxi0oe 776 775 2005-09-15T10:34:36Z Pajarico 5 /* Creature art */ 776 wikitext text/x-wiki Feel free to add yours. = General art = [http://themanaworld.org/archive/nevilytis/mana05.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana05.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana011.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana011.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana049.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana049.jpg.thumb.jpg] * by nevilytis I saw the post about the login screen and some of the chars inspired me... [http://themanaworld.org/archive/itsnervedamage/Manaworld.png http://themanaworld.org/archive/itsnervedamage/thumbs/Manaworld.png.thumb.jpg] * by itsnervedamage = Temple art = These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> = Creature art = <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> = Architectural concepts = <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} </gallery> iowypwxechb9b16vft17vtbe7owl2nu 795 776 2005-09-15T10:40:56Z Pajarico 5 /* Architectural concepts */ 795 wikitext text/x-wiki Feel free to add yours. = General art = [http://themanaworld.org/archive/nevilytis/mana05.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana05.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana011.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana011.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana049.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana049.jpg.thumb.jpg] * by nevilytis I saw the post about the login screen and some of the chars inspired me... [http://themanaworld.org/archive/itsnervedamage/Manaworld.png http://themanaworld.org/archive/itsnervedamage/thumbs/Manaworld.png.thumb.jpg] * by itsnervedamage = Temple art = These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> = Creature art = <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> = Architectural concepts = Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} </gallery> 3ono9t9ypkng1ejrfsm5wsomrog510h 824 795 2005-09-16T00:11:36Z Bjørn 3 No need for duplicates ;-) /* Architectural concepts */ 824 wikitext text/x-wiki Feel free to add yours. = General art = [http://themanaworld.org/archive/nevilytis/mana05.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana05.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana011.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana011.jpg.thumb.jpg] [http://themanaworld.org/archive/nevilytis/mana049.jpg http://themanaworld.org/archive/nevilytis/thumbs/mana049.jpg.thumb.jpg] * by nevilytis I saw the post about the login screen and some of the chars inspired me... [http://themanaworld.org/archive/itsnervedamage/Manaworld.png http://themanaworld.org/archive/itsnervedamage/thumbs/Manaworld.png.thumb.jpg] * by itsnervedamage = Temple art = These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> = Creature art = <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> = Architectural concepts = Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} </gallery> j47z4lgrh1j7ax0xy5zv89k9zv9tq30 825 824 2005-09-17T06:06:57Z Pajarico 5 /* General art */ Using uploaded images 825 wikitext text/x-wiki Feel free to add yours. = General art = <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} </gallery> <gallery> Image:Characters.png|{{Image:Characters.png}} </gallery> = Temple art = These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> = Creature art = <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> = Architectural concepts = Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} </gallery> 2e9cceczoegwx3tuf3d0k0xjrlq1cm1 826 825 2005-09-17T06:25:32Z Pajarico 5 Re-sort 826 wikitext text/x-wiki Feel free to add yours. = Architectural art = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} </gallery> <gallery> Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> qky9vsube15hbxesr9xwm65s3lfbm9c 827 826 2005-09-17T06:33:50Z Pajarico 5 /* Architectural art */ 827 wikitext text/x-wiki Feel free to add yours. = Architecture = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} </gallery> <gallery> Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> r5heu5t3nq3ddcu5lmqcseidg9720hi 837 827 2005-09-17T11:34:49Z Bjørn 3 Make one gallery /* Character art */ 837 wikitext text/x-wiki Feel free to add yours. = Architecture = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> rj5paivuktwt0ewg4vl26cqobbukkzh 908 837 2005-09-18T09:52:50Z Pajarico 5 /* Architectural concepts */ Added wall preview 908 wikitext text/x-wiki Feel free to add yours. = Architecture = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> 9y9ic5rkt1f777i04semjkwric5o93q 976 908 2005-09-23T15:13:54Z Pajarico 5 /* Creature art */ Added tree. 976 wikitext text/x-wiki Feel free to add yours. = Architecture = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> ixn5thwkahc0n1ye1vnc2d2xumardq5 977 976 2005-09-30T17:13:07Z Pajarico 5 /* Creature art */ Added leap monster 977 wikitext text/x-wiki Feel free to add yours. = Architecture = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> n4y6qzadvh8qevedr96ebkgf0vko9x6 2048 977 2005-09-30T17:13:53Z Pajarico 5 /* Architectural concepts */ Added street view 2048 wikitext text/x-wiki Feel free to add yours. = Architecture = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> 3oy2edf2lme09rqtksfemk8d54wvws3 3903 2048 2006-04-12T20:00:36Z Pajarico 5 /* Creature art */ 3903 wikitext text/x-wiki Feel free to add yours. = Architecture = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. 4boetfv5s505m5ejt92m53dbudgx7bc 4357 3903 2006-07-22T12:38:14Z Pajarico 5 /* Architectural concepts */ 4357 wikitext text/x-wiki Feel free to add yours. = Architecture = == Temple art == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. hjo09rg4wemcg8sjgsthg9f9k8vsdii 4370 4357 2006-07-22T13:01:03Z Pajarico 5 /* Architecture */ Cleaned, resort, added... 4370 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. l0uely8v68e5uvhzm9aovsvoimmmk3i 4375 4370 2006-07-22T13:10:06Z Pajarico 5 /* Beings */ 4375 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg Image:Weapon-crossbow sword hybrid-30042005.jpg Image:Weapon-chain-30042006.jpg </gallery> sesvctk3uk1hk9f2muyxndm55d97adl 4378 4375 2006-07-22T13:20:39Z Pajarico 5 /* Weapons */ 4378 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> 0jdcez91ad27alhl7x4oef3o2c4xmxo 4383 4378 2006-07-22T13:25:20Z Pajarico 5 /* Weapons */ 4383 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> ocu02mvo9yhcmzs92tada54p4nqjhuj 4386 4383 2006-07-22T13:35:04Z Pajarico 5 /* Outdoor */ Added 3 4386 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> 5j42tzriv5rpjqvwumer0rc0601kt1y 4396 4386 2006-07-22T13:41:43Z Pajarico 5 /* Weapons */ Added more categories, empty ATM 4396 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objets = == Items == == Clothes == == Furniture == 74c7r34fo8rl6t466192rgi4709qibs 4399 4396 2006-07-22T13:45:47Z Pajarico 5 /* Objets */ Oops take 2 (spelling) 4399 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == == Furniture == sw5cqshv9hfqurscrnm77jh81rfuqka 4400 4399 2006-07-22T15:03:11Z Pajarico 5 /* Temples */ 4400 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == == Furniture == 3brf1tdu9c45a1eo65pml68aszra43o 4851 4400 2006-09-07T09:58:54Z Pajarico 5 /* Buildings */ 4851 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == == Furniture == sx19mds280zouygl7s36evnvnu7o36z 5514 4851 2006-11-29T06:41:47Z Deesine 578 /* Character art */ 5514 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == == Furniture == hol46qnqj4o4y72s4bsswjq8o7wxvua 5515 5514 2006-11-29T06:43:01Z Deesine 578 /* Clothes */ 5515 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} </gallery> == Furniture == sf032ko61pso40rx1a6r5fdrem9393f 5517 5515 2006-11-29T12:17:00Z Deesine 578 /* Clothes */ 5517 wikitext text/x-wiki Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == 3fzg70poexso5dscyrgg7nfzyd5141z 6389 5517 2007-03-24T21:10:15Z Crush 103 ->art 6389 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == 8otws40r6vo2std47jizacn7udwptmj 6890 6389 2007-06-16T15:45:13Z Pajarico 5 /* Outdoor */ Added door 6890 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == h2p573q6k7gjjxqdz2puhhv4o242mta 6892 6890 2007-06-16T15:46:59Z Pajarico 5 /* Outdoor */ oops 6892 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png|{{Image:Door.png}} Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower2.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == 1ksdk9wxjjha6uetmzeymafzmjk7ws2 8309 6892 2007-12-23T14:28:34Z Pajarico 5 /* Outdoor */ Corrected link 8309 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png|{{Image:Door.png}} Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower02.png|{{Image:Arch-tower2.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == r33a3mx7tqh4t94219ucbbdy2mjrbkl 8311 8309 2007-12-23T14:35:44Z Pajarico 5 /* Outdoor */ Corrected description 8311 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png|{{Image:Door.png}} Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower02.png|{{Image:Arch-tower02.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == k7nlmcym37ghsjawtgfykmf19tx75ft 11237 8311 2009-01-03T09:53:10Z DelnoDarmo 1478 reldomlim 11237 wikitext text/x-wiki vicvit {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png|{{Image:Door.png}} Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower02.png|{{Image:Arch-tower02.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == ojgesqcwyof76t0qaqfxdmj3hxp3xhw 11240 11237 2009-01-03T14:31:05Z Bjørn 3 Reverted edits by [[Special:Contributions/DelnoDarmo|DelnoDarmo]] ([[User_talk:DelnoDarmo|Talk]]); changed back to last version by [[User:Pajarico|Pajarico]] 11240 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png|{{Image:Door.png}} Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower02.png|{{Image:Arch-tower02.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana05.jpg|{{Image:Mana05.jpg}} Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Mana049.jpg|{{Image:Mana049.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == k7nlmcym37ghsjawtgfykmf19tx75ft 12531 11240 2009-07-05T10:38:20Z Bjørn 3 Removed references to deleted images /* Character art */ 12531 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png|{{Image:Door.png}} Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower02.png|{{Image:Arch-tower02.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == de2ffhfs3088bbmxbqhq4lquurx62xs 26918 12531 2013-06-24T18:42:54Z Jaxad0127 999 Jaxad0127 moved page [[Concept art]] to [[Dev:Concept art]] 26918 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png|{{Image:Door.png}} Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower02.png|{{Image:Arch-tower02.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == de2ffhfs3088bbmxbqhq4lquurx62xs 59470 26918 2024-03-27T03:56:42Z Move page script 2739 Move page script moved page [[Dev:Concept art]] to [[Development:Concept art]]: Rename Dev: to Development: so the miraheze import works 26918 wikitext text/x-wiki {{Category_art}} Feel free to add yours. = Architecture = == Buildings == Complete buildings. <gallery> Image:Arch-house.jpg Image:Arch-magic hut.jpg|{{Image:Arch-magic hut.jpg}} Image:Arch-forest hut.png|{{Image:Arch-forest hut.png}} Image:Arch-nomad hut.png|{{Image:Arch-nomad hut.png}} Image:Arch-mud house.png|{{Image:Arch-mud house.png}} Image:Palace-25072005.jpg|{{Image:Palace-25072005.jpg}} Image:Cityobservatorium2nn.jpg|{{Image:Cityobservatorium2nn.jpg}} Image:School.jpg|{{Image:School.jpg}} </gallery> == Temples == These two temples were suggestions for the temple on the desertic city, but were rejected for some limitations and due to the fact that there is no temple anymore on that city. Maybe it would fit on another place. <gallery> Image:Arch-firetemple01.jpg|{{Image:Arch-firetemple01.jpg}} Image:Scenery-temple2-3052006.jpg|{{Image:Scenery-temple2-3052006.jpg}} Image:Temple-desert-30042006.jpg|{{Image:Temple-desert-30042006.jpg}} Image:City-26072005.jpg|{{Image:City-26072005.jpg}} </gallery> == Architectural concepts == Some architecture works. The approach here is to show different version of a same thing, just portraying the object itself and nothing else. We will discuss later where we use each one. === Outdoor === <gallery> Image:Door.png|{{Image:Door.png}} Image:Arch-preview04.png|{{Image:Arch-preview04.png}} Image:Arch-preview06.png|{{Image:Arch-preview06.png}} Image:Tulimshar-wall.jpg|{{Image:Tulimshar-wall.jpg}} Image:Tulimshar street.jpg|{{Image:Tulimshar street.jpg}} Image:Arch-tower02.png|{{Image:Arch-tower02.png}} Image:Arch-tower03.png|{{Image:Arch-tower03.png}} Image:Arch-tower01.jpg|{{Image:Arch-tower01.jpg}} Image:Arch-window01.jpg|{{Image:Arch-window01.jpg}} Image:Arch-window02.jpg|{{Image:Arch-window02.jpg}} Image:Arch-window03.jpg|{{Image:Arch-window03.jpg}} Image:Arch-window04.jpg|{{Image:Arch-window04.jpg}} Image:Arch-window05.jpg|{{Image:Arch-window05.jpg}} Image:Serpent.inn-detail.jpg|{{Image:Serpent.inn-detail.jpg}} Image:Unknown-logo.jpg|{{Image:Unknown-logo.jpg}} </gallery> === Indoor === <gallery> Image:Arch-library.png|{{Image:Arch-library.png}} </gallery> = Beings = == Character art == <gallery> Image:Mana011.jpg|{{Image:Mana011.jpg}} Image:Characters.png|{{Image:Characters.png}} Image:Hairstyles1.jpg|{{Image:Hairstyles1.jpg}} </gallery> == Creature art == See [[Creature proposal]]. = Weapons = <gallery> Image:Weapon-fire wire-30042005.jpg|{{Image:Weapon-fire wire-30042005.jpg}} Image:Weapon-crossbow sword hybrid-30042005.jpg|{{Image:Weapon-crossbow sword hybrid-30042005.jpg}} Image:Weapon-chain-30042006.jpg|{{Image:Weapon-chain-30042006.jpg}} Image:Axe.png|{{Image:Axe.png}} </gallery> = Objects = == Items == == Clothes == <gallery> Image:Costumes1.jpg|{{Image:Costumes1.jpg}} Image:Dee_WinterCostumes2.jpg|{{Image:Dee_WinterCostumes2.jpg}} </gallery> == Furniture == de2ffhfs3088bbmxbqhq4lquurx62xs 0 3706 11717 2009-02-21T01:59:23Z Kess 1128 Copied everyone from [[Developers]], missing people need to be added 11717 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions !! Location |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art || USA, born in El Salvador |- | Alexander Baldeck (kth5/Shura) || Programming || |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming || Germany |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming || Germany |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation || Brazil |- | [[User:Bear|Bear]] || Scripting || USA |- | [[User:Bertram|Bertram]] || Programming || France |- | [[User:Bjørn|Bjørn Lindeijer]] || Project leading, programming || The Netherlands |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) || USA |- | Chetic || Mapping || |- | [[User:Kage|Chuck Miller (Kage)]] || Programming || USA |- | [[User:Clef|Clef]] || Pixel art || |- | [[User:Dabe|David Del Re (Dabe)]] || Writing || USA |- | [[User:Demon|Demon]] || Pixel art || |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming || Denmark |- | [[User:deviexx|deviexx]] || Content management || |- | [[User:Doener|Doener]] || Programming || Germany |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project leading, programming || Italy |- | [[User:Fate|Fate]] || Content management, eAthena developing || |- | [[User:Golgo|Golgo]] || Pixel art || |- | Gnulia || Concept art || |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming || France |- | Igor Morgado (imorgado) || Testing || |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, minor programming || USA |- | [[User:Javila|Javila]] || Programming || Brazil |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of art, story and music || Finland |- | [[User:JoshLangley|JoshLangley]] || Programming (client) || Australia |- | [[User:kindjal|kindjal]] || Programming || France, currently Italy |- | [[User:Kinetic|Kinetic]] || Pixel art || USA |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art || Poland |- | [[User:Kyokai|Kyokai]] || Game design || |- | [[User:Len|L Pabin (len)]] || Pixel art, concept art, mapping; Head of Pixellation || USA |- | [[User:maci|maci]] || User support || Germany |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art || USA |- | [[User:Magick|Magick]] || Music || |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming || Poland |- | [[User:hackgrid|Matt]] || Blabbering idiocy || Germany |- | [[User:Mkael|Mkael]] || Concept art || Finland |- | [[User:Modanung|Modanung]] || Pixel art, concept art || The Netherlands |- | [[User:Mra|Mra]] || Programming || Germany |- | [[User:Neko-mon|Neko-mon]] || Pixel art || Brazil |- | Neorice || Pixel art || |- | [[User:Nym|nym]] || Programming || Australia |- | [[User:Pajarico|Pajarico]] || Art, writing || Spain |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) || Germany |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design || USA |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming || Germany |- | [[User:Platyna|Platyna]] || Packaging (Slackware) || Poland |- | Quiche_On_A_leash (QOAL) || Content management || |- | Rodney Dawes (dobey) || Packaging || |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming || The Netherlands |- | Romulo Fernandes (razor85) || Art || |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) || |- | [[User:Sora|Sora]] || Pixel art || Poland |- | [[User:Sull|Sull]] || Pixel art, hosting || Canada |- | [[User:Talaroc|Talaroc]] || Pixel art || |- | Ti Sing Hao || Music || |- | [[User:Trapdoor|trapdoor]] || Programming || England |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) || Germany |- | Ultramichy || Hosting || |- | [[User:VictorSan|VictorSan]] || Programming || Spain |- | Vlady || Art || |- | [[User:Yosuhara|Yosuhara]] || Pixel art || Slovakia |- | zenogais (bitshift2002) || Programming || |- | [[User:Zipon|Zipon]] || Mapping || Denmark |} bhg4bofx2t3o1f95h4pciw8nui1jhu0 11720 11717 2009-02-21T02:13:18Z Kess 1128 Remove location 11720 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bertram|Bertram]] || Programming |- | [[User:Bjørn|Bjørn Lindeijer]] || Project leading, programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | [[User:Doener|Doener]] || Programming |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project leading, programming |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, minor programming |- | [[User:Javila|Javila]] || Programming |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of art, story and music |- | [[User:JoshLangley|JoshLangley]] || Programming (client) |- | [[User:kindjal|kindjal]] || Programming |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | [[User:Kyokai|Kyokai]] || Game design |- | [[User:Len|L Pabin (len)]] || Pixel art, concept art, mapping; Head of Pixellation |- | [[User:maci|maci]] || User support |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Modanung|Modanung]] || Pixel art, concept art |- | [[User:Mra|Mra]] || Programming |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:Pajarico|Pajarico]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:Platyna|Platyna]] || Packaging (Slackware) |- | Quiche_On_A_leash (QOAL) || Content management |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Talaroc|Talaroc]] || Pixel art |- | Ti Sing Hao || Music |- | [[User:Trapdoor|trapdoor]] || Programming |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | Vlady || Art |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} t6ryqnfoklzs1sy77njbfff4fooa1jx 11725 11720 2009-02-21T22:36:48Z EJlol 294 added my self to contributors. 11725 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bertram|Bertram]] || Programming |- | [[User:Bjørn|Bjørn Lindeijer]] || Project leading, programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | [[User:Doener|Doener]] || Programming |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project leading, programming |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, minor programming |- | [[User:Javila|Javila]] || Programming |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of art, story and music |- | [[User:JoshLangley|JoshLangley]] || Programming (client) |- | [[User:kindjal|kindjal]] || Programming |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | [[User:Kyokai|Kyokai]] || Game design |- | [[User:Len|L Pabin (len)]] || Pixel art, concept art, mapping; Head of Pixellation |- | [[User:maci|maci]] || User support |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Modanung|Modanung]] || Pixel art, concept art |- | [[User:Mra|Mra]] || Programming |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:Platyna|Platyna]] || Packaging (Slackware) |- | Quiche_On_A_leash (QOAL) || Content management |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Talaroc|Talaroc]] || Pixel art |- | Ti Sing Hao || Music |- | [[User:Trapdoor|trapdoor]] || Programming |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | Vlady || Art |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} sumy8uu0ll8idmo7dm34h5qysitr35c 11854 11725 2009-03-19T13:22:40Z Bjørn 3 Link to QOAL's user here too 11854 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bertram|Bertram]] || Programming |- | [[User:Bjørn|Bjørn Lindeijer]] || Project leading, programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | [[User:Doener|Doener]] || Programming |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project leading, programming |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, minor programming |- | [[User:Javila|Javila]] || Programming |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of art, story and music |- | [[User:JoshLangley|JoshLangley]] || Programming (client) |- | [[User:kindjal|kindjal]] || Programming |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | [[User:Kyokai|Kyokai]] || Game design |- | [[User:Len|L Pabin (len)]] || Pixel art, concept art, mapping; Head of Pixellation |- | [[User:maci|maci]] || User support |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Modanung|Modanung]] || Pixel art, concept art |- | [[User:Mra|Mra]] || Programming |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:Platyna|Platyna]] || Packaging (Slackware) |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Talaroc|Talaroc]] || Pixel art |- | Ti Sing Hao || Music |- | [[User:Trapdoor|trapdoor]] || Programming |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | Vlady || Art |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} 1xssb7oukno6388ou2yn54ckp0lueyk 11938 11854 2009-04-23T08:45:05Z Kess 1128 Updating from the AUTHORS files, please check! 11938 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git]] repositories’ <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, minor programming |- | Jean-Francois Lampron || |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} szmcb5daody4v14284byffncqq27s7d 11940 11938 2009-04-23T12:18:48Z Jaxad0127 999 11940 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git]] repositories’ <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} nt9h0pcmy08urny13mfgitrmugyv39a 12001 11940 2009-05-04T02:55:37Z Fother 1315 Add myself... narcism rocks. 12001 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git]] repositories’ <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} 5q1dxb144thvdbzw1or9cml55porfy9 12374 12001 2009-06-11T08:47:49Z Freeyorp 1501 Added myself. 12374 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git]] repositories’ <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} p7oskae2kn8xa0lw5m0edrvz30uxj8u 12391 12374 2009-06-12T19:51:45Z Superkoop 1088 Added myself 12391 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git]] repositories’ <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} tlvvc9gzdwntl8i5eryiuq8e0toqcjh 14040 12391 2009-12-10T12:48:39Z Luca1189 1666 14040 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository]] repositories’ <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} 43reb1ubse5hddx0fdvp1pn38r599fy 14041 14040 2009-12-10T12:49:20Z Luca1189 1666 14041 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} dit4k5ivzn163mgx7ezkx11ewr7gcs5 14479 14041 2009-12-31T01:49:58Z Swimmy 1495 14479 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Swimmy|Daiki Matsubara (Swimmy)]] || Translation (Japanese) |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} 7hutj5l6d8d88s1h5kdm5u8ljcr7x7o 14733 14479 2010-01-22T13:22:44Z Swimmy 1495 added Tiana as a Game Master 14733 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Swimmy|Daiki Matsubara (Swimmy)]] || Translation (Japanese) |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} im0iqbwhffsbxj3k970p89z0fp1zh5q 14816 14733 2010-02-06T08:04:44Z Swimmy 1495 added Narus as Game Master 14816 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} 05xaf9s5jx7p0yqd529k3nzybz6yjdd 15099 14816 2010-06-02T13:04:52Z IvanMorve 1788 heh 15099 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} m6zy9rozfbfsxexlu36d0gvddwjygr1 16142 15099 2010-11-22T04:10:27Z Hoogli 1124 16142 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjørn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] dov4wxmsrtz5a5fst8nrihmlyt3gqjl 23310 16142 2012-01-31T22:12:57Z Bjørn 3 Fixed some messed up characters 23310 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjorn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] sj3fc28gk5noepixbyxw1c5nowkwaq2 23419 23310 2012-02-07T18:16:58Z Argul 1858 adding me 23419 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjorn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] 389ctjobecg2705naohnt22axtb05pj 23421 23419 2012-02-07T18:24:38Z Alige 1888 added self 23421 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki System Operator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Bjorn|Bjørn Lindeijer]] || Project Leader; programming, translation (Dutch) |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] b58e2vwel609861sdda23eun80pcter 23424 23421 2012-02-07T19:50:45Z Bjørn 3 Changed to full name 23424 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories’]] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://gitorious.org/projects/tmw/repos/mainline/blobs/master/AUTHORS client] and [http://gitorious.org/projects/tmwserv/repos/mainline/blobs/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki System Operator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] cyv7rmvuagtmmc6tu4q6e7ww0vwvlgj 23426 23424 2012-02-07T20:11:06Z Bjørn 3 Some link updates 23426 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki System Operator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] 42rheyo6mzld2y6tvtcyw4idqixsjkq 23560 23426 2012-02-25T23:16:17Z Alige 1888 Added skipy. 23560 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] 65xkj94wddu74nsq8ufql42yv4sktet 24403 23560 2012-09-05T19:58:15Z Rodrigo 2213 24403 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:Rodrigo|Pluto]] || Translation (Shqip) | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] rg30fuzgjrpj3lrdp0s6125goonbxym 24404 24403 2012-09-05T19:58:50Z Rodrigo 2213 24404 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:Rodrigo|Pluto]] || Translation (Shqip) |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] g4dpb6qld89utp1ppil9hxli6p6l8g4 24432 24404 2012-09-08T12:00:28Z Rodrigo 2213 24432 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Pluto]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] ham6vylj5u9wk5v6z9jmebwngtnby2l 24472 24432 2012-09-13T11:32:15Z Nard 1877 24472 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Pluto]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux-th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] kznau4uco4jcxl9qinwg26imtmoqqdz 24473 24472 2012-09-13T11:32:46Z Nard 1877 24473 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Pluto]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] 86lg4qf15vb9138fu7gulbrojmgxb4u 24474 24473 2012-09-13T11:35:14Z Nard 1877 24474 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Pluto]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:Peablog|Peablog]] || Testing, error and bug Reporting |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] f394fbh6iiellxpr8b9xzy5lxojt6ue 24476 24474 2012-09-13T11:40:17Z Nard 1877 24476 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:Peablog|Peablog]] || Testing, error and bug Reporting |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Argul| Stefan Beller (PjotrOrial) ]] || Scripting, Mapping, Programmer |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] 13jylnd65pj55o41uieo6itrzsr9yz7 25755 24476 2013-03-11T09:44:12Z Argul 1858 remove me 25755 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:Peablog|Peablog]] || Testing, error and bug Reporting |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] 26roqwlt4iygzffkqdsys338mkukgyd 25760 25755 2013-03-14T15:58:26Z Nard 1877 25760 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | doorsman || Game master |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || Game master |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || Game master |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | [[User:Narus|Narus]] || Game Master |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | [[User:QwertyDragon]] aka [[User:Peablog|Peablog]] || Testing, error and bug Reporting, Dialog writing and correctrion. | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || Game Master |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || Game master |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] ojtw238faosaivxiecyi6jmwwscpusx 25763 25760 2013-03-14T16:16:24Z Nard 1877 25763 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:QwertyDragon]] aka [[User:Peablog|Peablog]] || Testing, error and bug Reporting, Dialog writing and correctrion. | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] icjrq58j3k3hapo4hsuknvf020z6pc3 25769 25763 2013-03-14T17:19:44Z Peablog 2134 25769 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Ali-G|Ali-G]] || Pixel Art, Scripting, Mapping Lead, XML Lead, Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] e96payt5472jvxg2uc4eql97uspg0i3 26283 25769 2013-04-23T14:34:05Z Alige 1888 26283 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alige|Alige]] || Pixel Art, Scripting, Mapping, XML, Wiki Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] meszkvxjv5nitq2deynjxy3itdoi3od 26447 26283 2013-05-28T06:17:08Z Cassy 2265 Adding Silent Dawn as Game Master 26447 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [http://gitorious.org/projects/tmwart/repos/mainline/blobs/master/AUTHORS art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alige|Alige]] || Pixel Art, Scripting, Mapping, XML, Wiki Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] fxi2jruacpz864gnk6tc7t52lx45kji 26643 26447 2013-06-13T09:27:58Z EJlol 294 fixed link 26643 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alige|Alige]] || Pixel Art, Scripting, Mapping, XML, Wiki Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] 424vdz1awc52r46hbe5hxqkbyg13bgy 26665 26643 2013-06-15T16:13:08Z Nard 1877 26665 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | [[User:4144|4144]] || Client programming. |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alige|Alige]] || Pixel Art, Scripting, Mapping, XML, Wiki Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chef Chelios || Pixel art. |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | Ginaria || Pixel art. |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] 7wy3u20pe5zpwyn2nc6atckpa9dzwns 27985 26665 2013-08-04T19:27:22Z Cassy 2265 added Melkior as GM 27985 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | [[User:4144|4144]] || Client programming. |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alige|Alige]] || Pixel Art, Scripting, Mapping, XML, Wiki Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chef Chelios || Pixel art. |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | Ginaria || Pixel art. |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Melkior|Melkior]] || [[Game Masters|Game master]] |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] || [[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] sjqh62fzrgv5yo6j94pr64ylty8kg5b 28011 27985 2013-08-06T06:25:01Z Cassy 2265 Big Crunch -> ex GM... 28011 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | [[User:4144|4144]] || Client programming |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alige|Alige]] || Pixel Art, Scripting, Mapping, XML, Wiki Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chef Chelios || Pixel art |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | Ginaria || Pixel art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Melkior|Melkior]] || [[Game Masters|Game master]] |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] || [[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correction |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] qomp6pqk4hhel3pqyhko4tv35m5g6fa 28013 28011 2013-08-06T10:24:16Z Cassy 2265 CapitanAwesome -> *ex*-GM 28013 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. The definitive source of contributors should be found in the respective [[Git repository|git repositories']] <code>AUTHORS</code> files: [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt art], [http://github.com/mana/mana/tree/master/AUTHORS client] and [http://github.com/mana/manaserv/tree/master/AUTHORS server]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | [[User:4144|4144]] || Client programming |- | Aaron Marks || Programming (server) |- | [[User:Axltrozz|Alex Argumedo (Axltrozz)]] || Pixel art |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alige|Alige]] || Pixel Art, Scripting, Mapping, XML, Wiki Translation (French), Wiki Administrator |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] || Programming |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Av3nger|Av3nger]] || Pixel art, mapping, translation |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | [[User:Doener|Björn Steinbrink (Doener)]] || Programming |- | CapitanAwesome || (ex-)[[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chef Chelios || Pixel art |- | Chetic || Mapping |- | [[User:Kage|Chuck Miller (Kage)]] || Programming |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Trapdoor|David Athay (trapdoor)]] || Programming |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] || Project Leader; programming, translation (Italian) |- | Eric Scrivner || Programming (client) |- | [[User:Fate|Fate]] || Content management, eAthena developing |- | Fredrik Reveny || Programming (client) |- | [[User:Freeyorp|Freeyorp]] || Programming (client), Pixel art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | Ginaria || Pixel art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | [[User:Jaxad0127|Jared Adams (Jaxad0127)]] || Content management, mapping, programming |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Rotonen|Joni Orponen (Rotonen)]] || Head of Art, Story and Music |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | [[User:Irukard|Krzysztof Daszuta (Irukard)]] || Pixel art |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | [[User:hackgrid|Matt]] || Blabbering idiocy |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Melkior|Melkior]] || [[Game Masters|Game master]] |- | [[User:Meway|Meway]] || Pixel art |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] || [[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Prsm || [[Game Masters|Game master]] |- | [[User:the-me|Patrick Matthäi]] || Packaging (Debian) |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:Crush|Philipp Sehmisch (Crush)]] || Pixel art, mapping, programming |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correction |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | [[User:QOAL|Scott Ellis (Quiche_on_a_leash, QOAL)]] || Content management |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | Skipy || Pixel art |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | [[User:Bjorn|Thorbjørn Lindeijer (bjorn)]] || Project Leader; programming, translation (Dutch) |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:Tuxtgz|Tuxtgz]] || Programming (web interface) |- | [[User:Tux|Tux9th]] || Content development, maps |- | Ultramichy || Hosting |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | [[User:Yosuhara|Yosuhara]] || Pixel art |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |- | [[User:Platyna|Zuzanna K. Filutowska (Platyna)]] || Packaging (Slackware) |} [[Category:reference]] oohrolyr2mm6mq15jjxr6ni3p76owdh 28304 28013 2013-09-25T13:13:29Z Tux 2198 28304 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:melkior|melkior]] || [[Game Masters|Game master]] |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] 7m5xmx2dxfcpyrw6038749xvugfylm0 28967 28304 2013-12-03T17:28:42Z Melkior 1643 28967 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:melkior|melkior]] || (ex-)[[Game Masters|Game master]] |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] d25eqpt31aultiwmdt8sal01h220ky2 28991 28967 2013-12-05T16:21:44Z Melkior 1643 28991 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] hwvkjiesy20ifsr9plythh6mb7ah1s4 29288 28991 2014-02-13T20:20:54Z Cassy 2265 adding Lizandra 29288 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] kznldcshmckzru4uf8nf5twj17iylba 29289 29288 2014-02-13T20:28:48Z Cassy 2265 addings meway and salmondine as well 29289 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] kd0xxyyjn7jh0nmm262o5jl2c7jrh6d 29290 29289 2014-02-13T20:35:44Z Cassy 2265 adding ChefChelios and correcting Lizandra's name 29290 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] dtl6ch2sza9pk3pwheefvm52xru6use 29291 29290 2014-02-13T21:04:12Z Cassy 2265 added Qoal as well 29291 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] jtdl9461fnpf2pw3d0enbfqv7vbrs1s 29292 29291 2014-02-14T22:05:38Z Wushin 2233 /* The whole world should know Im awesome I'm just seeing if anyone else reads these */ 29292 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis, Best-Looking. |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] 538039dhtr33vckwyqt1ekwbenkvd91 29294 29292 2014-02-16T13:53:01Z Cassy 2265 -.- 29294 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] ed15lzar49g0hd0cy77lqlu1ed9u7wb 29433 29294 2014-02-21T09:28:47Z Cassy 2265 added veryape, Chay and myself 29433 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, Dialog writing and correctrion. |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] n9im7412fo69akccz9z0rax9gbemm25 29438 29433 2014-02-21T13:53:58Z SudoPlatypus 2255 29438 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] r1pb7tij6xq1721zw50mk5q4q6kw9zm 29485 29438 2014-02-27T06:56:07Z Cassy 2265 adding V0id 29485 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] dr6qvepgcs5a60ez9vtr6nanbj1e7i5 29668 29485 2014-03-02T18:31:30Z Madcamel 1494 29668 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] kke4sdvees8nuqo84txdbz4onpetmzf 29965 29668 2014-03-28T07:47:01Z Cassy 2265 adding tux9th 29965 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] kwu3vufb9dkr4x65a8wc3rb431rr3b1 30957 29965 2014-07-03T20:24:23Z Wushin 2233 30957 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] mf4g9yprg7kg24mxb4g1zsrej7lts0g 31386 30957 2014-10-23T02:28:31Z Gumi 2315 31386 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] 4qe427zfdw5uqc4k00n6g3td8u0ljqz 31822 31386 2014-12-17T06:13:57Z Wushin 2233 Wushin moved page [[Contributors]] to [[Dev:Contributors]]: Organize for SEO 31822 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] 4qe427zfdw5uqc4k00n6g3td8u0ljqz 31840 31822 2014-12-17T16:17:57Z Wushin 2233 /* categorizing */ 31840 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] [[Category:Development]] 178z0uwtxzv1939qqdgi485v5nwxrez 32573 31840 2015-02-07T02:56:27Z Wushin 2233 /* updated for o11c's resignation */ 32573 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:reference]] [[Category:Development]] 6st4ki6r2ko0jdmlu2uwtqgu3im1lel 33696 32573 2015-03-11T08:22:16Z Cassy 2265 removing category 33696 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] qyhh7oatkq41oangu9v5arg6vtgdkzo 34810 33696 2015-04-02T08:27:55Z Yubaba 2094 34810 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria || Sound scape, SoundFX, Writing, testing, |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] h85biir05ld7mgaaz705t5szsh9uef2 34811 34810 2015-04-02T08:28:53Z Yubaba 2094 34811 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria || Music, SoundFX, Writing, testing, Mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] 1m197gzlcfjoca24i2cpxnlrmkdmn1x 34812 34811 2015-04-02T08:29:51Z Yubaba 2094 34812 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, testing, Mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] 8krspjos8s5fspeaofjcxyxr5g1h2ig 40020 34812 2015-12-13T04:59:28Z Pyndragon 2420 Add myself 40020 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[developers|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, testing, Mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] 3s6bj0d2gdg8znlhfks7ukgdvhceobd 46004 40020 2019-04-08T16:29:46Z Jesusalva 2520 Fix broken link 46004 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[TMW_Team|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, testing, Mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] pgn77c0tmoujcu8vhtw5f7p6y1ubvac 50448 46004 2020-01-18T20:13:24Z ComfyCheeks 2713 Added fother as pixel artist 50448 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[TMW_Team|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, testing, Mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | Fother || Pixel Artist |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] af3arma702gju4gyr26al6f00wuc1ke 50449 50448 2020-01-18T20:19:16Z ComfyCheeks 2713 Added fother, skipy, salmondine, 50449 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[TMW_Team|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || (ex-)[[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, testing, Mapping |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || (ex-)[[Game Masters|Game master]] |- | doorsman || (ex-)[[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | Fother || Pixel Art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || (ex-)[[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || (ex-)[[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || (ex-)[[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Salmondine || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Skipy || Pixel art |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || (ex-)[[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] i2pjeymm2exdwjz6puajdti0x8ivtbh 50451 50449 2020-01-18T20:44:33Z ComfyCheeks 2713 Some Game masters had (ex) beside their name but some didn't even though they are not current. Just made it more consistent. 50451 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[TMW_Team|current main developers]]. {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, Wiki edits, Testing, Art |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || [[Game Masters|Game master]] |- | doorsman || [[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | Fother || Pixel Art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || [[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || [[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || [[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Salmondine || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Skipy || Pixel art |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || [[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] sv2i336vtosiotwstbvxfug5coaq46w 50452 50451 2020-01-18T21:24:16Z Jesusalva 2520 Toolchain warning. Actually, even `make contrib` is not being put on wiki, so. 50452 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[TMW_Team|current main developers]]. '''Note: This list may be outdated.''' {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, Wiki edits, Testing, Art |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || [[Game Masters|Game master]] |- | doorsman || [[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | Fother || Pixel Art |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || [[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || [[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || [[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Salmondine || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Skipy || Pixel art |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || [[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] tjv8onc96bgz1hi36irpe63pbgrcyoq 50453 50452 2020-01-18T21:29:53Z ComfyCheeks 2713 Removed the duplicates 50453 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[TMW_Team|current main developers]]. '''Note: This list may be outdated.''' {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, Wiki edits, Testing, Art |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || [[Game Masters|Game master]] |- | doorsman || [[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || [[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || [[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || [[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Skipy || Pixel art |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || [[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] ioybuwgqfbtyvnjg7yc15uzbonfnals 53628 50453 2021-01-10T23:50:44Z Speiros 2726 Added myself to the list as a wiki editor. 53628 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[TMW_Team|current main developers]]. '''Note: This list may be outdated.''' {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, Wiki edits, Testing, Art |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || [[Game Masters|Game master]] |- | doorsman || [[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || [[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || [[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || [[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Skipy || Pixel art |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Speiros|Speiros]] || Wiki editing |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || [[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] mxidgqs4arejf69440knfbkirajy6hn 59472 53628 2024-03-27T03:56:42Z Move page script 2739 Move page script moved page [[Dev:Contributors]] to [[Development:Contributors]]: Rename Dev: to Development: so the miraheze import works 53628 wikitext text/x-wiki People that have contributed to the game, small and large. See also the page listing the [[TMW_Team|current main developers]]. '''Note: This list may be outdated.''' {| class="sortable" style="width:100%; padding:5px; border-bottom:2px solid #efdead;" |- style="background:#efdead; align:left;" ! Name (nick) !! Main contributions |- | Aaron Marks || Programming (server) |- | Alexander Baldeck (kth5/Shura) || Programming |- | [[User:Alons|AlOns]] || [[Game Masters|Game master]] |- | [[User:Gagaofdeath|Andrej Sinicyn]] || Programming |- | Andrew Hall (meway) || Pixel art |- | Bagzie || Pixel Art |- | [[User:Bear|Bear]] || Scripting |- | Big Crunch || [[Game Masters|Game master]] |- | CapitanAwesome || [[Game Masters|Game master]] |- | [[User:Cassy|Cassy]] || Pixel art, scripting, mapping |- | [[User:Catfish_Man|Catfish_Man]] || Porting (Mac) |- | Cedric Borgese (moi1392) || Programming (client) |- | [[User:Chayenne|Chay (Bernhardt)]] || Pixel art, scripting, mapping |- | Chicka-Maria (Comfycheeks/Yubaba) || Music, SoundFX, Writing, Wiki edits, Testing, Art |- | ChefChelios || Pixel art |- | Chetic || Mapping |- | [[User:Clef|Clef]] || Pixel art |- | [[User:Dabe|David Del Re (Dabe)]] || Writing |- | Daniel Foerster (Pyndragon) || tmwA, Script/dialogue fixes |- | [[User:Demon|Demon]] || Pixel art |- | [[User:Peavey|Dennis Friis (peavey)]] || Programming |- | [[User:deviexx|deviexx]] || Content management |- | Delasia || [[Game Masters|Game master]] |- | doorsman || [[Game Masters|Game master]] |- | Douglas Boffey || Programming (client) |- | Duane Bailey || Programming (client) |- | Eric Scrivner || Programming (client) |- | Filipa Serra e Silva (Lizandra) || Pixel art |- | Fredrik Reveny || Programming (client) |- | [[User:Modanung|Frode Lindeijer (Modanung)]] || Pixel art, concept art |- | [[User:Golgo|Golgo]] || Pixel art |- | Gnulia || Concept art |- | [[User:Silene|Guillaume Melquiond (Silene)]] || Programming |- | [[User:kindjal|Huynh Ngoc Chau Tran (kindjal)]] || Programming |- | Igor Morgado (imorgado) || Testing |- | Ira Rice || Programming (client) |- | [[User:Mra|Jan-Fabian Humann (Mra)]] || Programming |- | [[User:Fother|Jarrett Thomas-Huxley (Fother_J)]] || Pixel art |- | Jean-Francois Lampron || |- | [[User:Superkoop|John Koopman (Superkoop)]] || Mapping |- | [[User:Javila|José Ávila (Javila)]] || Programming |- | Johannelaliberte || Testing, error and bug Reporting. |- | [[User:JoshLangley|Joshua Langley (JoshLangley)]] || Programming (client) |- | [[User:Jumpy|Jumpy]] || Translation (French) |- | [[User:Katze|Katze]] || [[Game Masters|Game master]] |- | [[User:Kess|Kess Vargavind]] || Translation (Swedish) |- | [[User:Kinetic|Kinetic]] || Pixel art |- | [[User:Kyokai|Kiyoshi Kyokai (Kyokai)]] || Game design |- | Leif Kildelund (GonzoDark) || Translation (Danish) |- | [[User:Len|Leonard Pabin III (Len)]] || Head of Pixellation; pixel art, concept art, mapping |- | Lloyd Bryant || Programming (client) |- | [[User:AnonDuck|AnonDuck]] || Programming (server), scripting, hacker |- | [[User:Maester Pixel|Maester Pixel]] || Pixel art |- | [[User:Magick|Magick]] || Music |- | [[User:maci|Marcel W. Wysocki (maci)]] || User support |- | Mark Dunbar (salmondine) || Pixel Art |- | [[User:IvanMorve|Martin (IvanMorve)]] || Pixel art |- | MasterKenobi || [[Game Masters|Game master]] |- | [[User:Usiu|Mateusz Kaduk (Usiu)]] || Programming |- | Matthias Hartmann || Programming (client), translation (German) |- | [[User:Meko|Meko]] || Scripting, mapping |- | [[User:Mkael|Mkael]] || Concept art |- | mrgrey || [[Game Masters|Game master]] |- | [[User:Narus|Narus]] ||[[Game Masters|Game master]] |- | [[User:Neko-mon|Neko-mon]] || Pixel art |- | Neorice || Pixel art |- | [[User:Nym|nym]] || Programming |- | [[User:o11c|o11c]] || Programming, Scripting |- | [[User:EJlol|Oscar Klein Heerenbrink (EJlol)]] || Pixelart |- | [[User:Rodrigo|Arian Asimi (Pluto)]] || Pixel Art, Translation (Shqip) |- | [[User:Pajarico|Pajarico Guaje (Pajarico)]] || Art, writing |- | Platyna|| former Server Hostess, former Project Administrator. |- | Prsm || [[Game Masters|Game master]] |- | [[User:Pauan|Pauan]] || Concept art, pixel art, interface design |- | Qoal || [[Game Masters|Game master]], pixel art |- | [[User:QwertyDragon|QwertyDragon]] || Testing, error and bug Reporting, dialog writing |- | Rodney Dawes (dobey) || Packaging |- | [[User:Avaniel|Rogier Polak (Avaniel)]] || Programming |- | Romulo Fernandes (razor85) || Art |- | [[User:Talaroc|Ryan Voss (Talaroc)]] || Pixel art |- | Silent Dawn || [[Game Masters|Game master]] |- | Skipy || Pixel art |- | Simon Edwardsson (simonedw/simedw) || Packaging (Mac) |- | [[User:Sora|Sora]] || Pixel art |- | [[User:Speiros|Speiros]] || Wiki editing |- | [[User:Sull|Sull]] || Pixel art, hosting |- | [[User:Swimmy|Swimmy]] || Translation (Japanese) |- | Tatjana || |- | Ti Sing Hao || Music |- | [[User:Tiana|Tiana]] || [[Game Masters|Game master]] |- | [[User:tux|tux9th]] || Mapping, Scripting |- | Ultramichy || former Server Hoster |- | [[User:veryape|veryapeGM]] || [[Game Masters|Game master]] |- | [[User:VictorSan|VictorSan]] || Programming |- | [[User:V0id|V0id (Vincent Petithory)]] || Mapping, Pixel Art, Programming, Scripting |- | [[User:Vink|Vink]] || [[Game Masters|Game master]] |- | Vlady || Art |- | [[User:Bertram|Yohann Ferreira (Bertram)]] || Programming |- | Wushin || Art, Content, Wiki, Mapping, Programming, Manavis |- | zenogais (bitshift2002) || Programming |- | [[User:Zipon|Zipon]] || Mapping |} [[Category:Development]] mxidgqs4arejf69440knfbkirajy6hn 0 2069 3881 2006-04-12T19:03:53Z Pajarico 5 3881 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ia6iumzq7xk4ftaezuzrr3fw4kesm3r 3882 3881 2006-04-12T19:06:23Z Pajarico 5 3882 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ---- = Creatures = == Number 1 == eakvl5cau6gbmu46wfm5i8j08fzlgw9 3885 3882 2006-04-12T19:27:51Z Pajarico 5 /* Template */ 3885 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' If it is a strong monster or weak, etc. * '''Movements''' How fast it moves, both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Proposed as mini-monster, etc. ---- = Creatures = == Number 1 == qk6cvp3faxtjy0r43dop0ghn0b4nki5 3886 3885 2006-04-12T19:28:50Z Pajarico 5 /* Creatures */ 3886 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ---- = Creatures = == Number 1 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' sl0e3j52exyp9eg6l1p4ug6hscyk7gi 3887 3886 2006-04-12T19:29:28Z Pajarico 5 /* Template */ 3887 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ---- = Creatures = == Number 1 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' aj35rh134i35nteptezzmna9lxoo365 3888 3887 2006-04-12T19:29:57Z Pajarico 5 /* Number 1 */ 3888 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ---- = Creatures = == Number 1 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == 9l2m9yzac7u8efqo1a5kf0pbbk0yhfb 3889 3888 2006-04-12T19:34:13Z Pajarico 5 /* Number 2 */ 3889 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ---- = Creatures = == Number 1 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' 4oaiblsiqxznixn3lcdf69mk3f4cubx 3890 3889 2006-04-12T19:39:42Z Pajarico 5 /* Number 1 */ Fixed thumbnails 3890 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' nx1xqdu0221tsaxh5fgodvn0ebezz3e 3892 3890 2006-04-12T19:46:10Z Pajarico 5 /* Template */ 3892 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Proposed as mini-boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' mjc0ooqcymgia8xfqqwhuxi9kakc7wl 3893 3892 2006-04-12T19:47:00Z Pajarico 5 /* Number 2 */ 3893 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ---- = Creatures = == Number 1 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' gnlujexwzwd3hjknicycs9cx0yde4im 3894 3893 2006-04-12T19:48:56Z Pajarico 5 /* Template */ Have saved this change 3 times now, trying once again :P 3894 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Proposed as mini-boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' mjc0ooqcymgia8xfqqwhuxi9kakc7wl 3895 3894 2006-04-12T19:50:11Z Pajarico 5 /* Number 2 */ 3895 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). ---- = Creatures = == Number 1 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' gnlujexwzwd3hjknicycs9cx0yde4im 3896 3895 2006-04-12T19:50:30Z Pajarico 5 /* Template */ Have saved this change 3 times now, trying once again :P 3896 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Proposed as mini-boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' mjc0ooqcymgia8xfqqwhuxi9kakc7wl 3897 3896 2006-04-12T19:50:52Z Pajarico 5 /* Number 2 */ 3897 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Proposed as mini-boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' b2ekhdci1y2d8drsn63lq49d4v59t3e 3898 3897 2006-04-12T19:52:08Z Pajarico 5 /* Template */ 3898 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Proposed as mini-boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' dkr5v7r7n8lv2mgnk67nzei2qyf68bm 3900 3898 2006-04-12T19:56:19Z Pajarico 5 /* Number 3 */ Added third 3900 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Proposed as mini-boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' 7z24kh7z0bm2g3zbt8nwktxutq3gvv5 3901 3900 2006-04-12T19:56:59Z Pajarico 5 /* Template */ 3901 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' 2pmdurc5y7dosgwe6xvpai9ue2u413y 3902 3901 2006-04-12T19:58:10Z Pajarico 5 /* Number 4 */ Another one. Modanung fill this up! 3902 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == [[Image:Creature01-stand.png|100px]] [[Image:Creature01-crouch.png|100px]] [[Image:Creature01-attack.png|100px]] [[Image:Creature01-dead.png|100px]] * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' nmsf8bpt420eqx32dpvuxzs9yaie4hi 3905 3902 2006-04-12T20:13:02Z Pajarico 5 /* Number 5 */ The fifth 3905 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name. * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). k1hlm1d66d3u3c5mzt9y86b2pizuyh4 3906 3905 2006-04-12T20:14:17Z Pajarico 5 /* Template */ 3906 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a human figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). agmzdpt8s7rwi42a7003lzmwpnq0mmm 3907 3906 2006-04-12T20:15:13Z Pajarico 5 /* Template */ 3907 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). r7euemjcqkgbz0bysi4hqr7jr5c1bjy 3908 3907 2006-04-12T20:16:11Z Pajarico 5 /* Number 4 */ 3908 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). k9svtb1qcxyysnkl1dr4wipz2phx8rd 3909 3908 2006-04-12T20:24:06Z Pajarico 5 /* Number 5 */ One more 3909 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Number 6 == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't moves, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... 3q95g5hzrpxeip1mah30i6rvximhzyh 4227 3909 2006-05-15T17:58:33Z Pajarico 5 /* Number 6 */ Added one more 4227 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Number 6 == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. 4fcas0uxwjxmoil252g2j03s6tya3hq 5456 4227 2006-11-24T18:42:50Z Cblade 567 Cblade Idea 1 5456 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Number 6 == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. ==CBlade's Ideas 1== '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Special Abilities:''' *** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) *** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) *** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) *** Fangs of Draining - Everytime the spider attacks not only does it deal HP damage, but MP damage as well, but the spider regains 1/4 of the MP damage as MP. *** Magic Immunities - Time *** Magic Immunities - Cold *** Magic Vulernabilities - Fire *** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, 5yf5c8uor2dj1eio5ki6o3lmxjeqzvz 5457 5456 2006-11-24T18:50:52Z Cblade 567 CBlade's Ideas 1 5457 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Number 6 == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. ==CBlade's Ideas 1== '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Fangs of Draining - Everytime the spider attacks not only does it deal HP damage, but MP damage as well, but the spider regains 1/4 of the MP damage as MP. ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, gm3o916vumxxxobzfiejngwduihjbau 5458 5457 2006-11-24T18:56:35Z Cblade 567 CBlade's Ideas 1 5458 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Number 3 == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 4 == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Number 6 == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. ==CBlade's Ideas 1== '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' fog7dzpftnxvh6z9u7p4ud0dv1bq3wu 5479 5458 2006-11-24T22:51:17Z Crush 103 used monster names as chapter headlines 5479 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' bbp6p1i3ypdnav8q3jhdk5vsu35mn9x 5481 5479 2006-11-25T17:00:19Z Cblade 567 Dok'e Mono 5481 wikitext text/x-wiki {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' m8coufm25mmz8nlj789ca4en2gl7t4g 6385 5481 2007-03-24T21:07:18Z Crush 103 ->art development 6385 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' adhihldwfu7qqg7eht1oncirpajv82m 7402 6385 2007-08-23T19:02:54Z Falcata 566 /* Creatures */ Added "Living Lava" monster. 7402 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == <gallery> Image:Monster-slime-lava.png|{{Image:Monster-slime-lava.png}} </gallery> * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore * '''Behaviour''' Attack when attacked, steals items like most slimes, but stolen items are destroyed unless immune to heat * '''Notes''' Lava that has been inhabited by a fire elemental, granting it a semblance of life. l8ga451offmqce50ial26wlty8g9nxv 7403 7402 2007-08-23T19:04:09Z Falcata 566 /* Living Lava */ 7403 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore * '''Behaviour''' Attack when attacked, steals items like most slimes, but stolen items are destroyed unless immune to heat * '''Notes''' Lava that has been inhabited by a fire elemental, granting it a semblance of life. c77l2y0qgjgfhhprz5ewtje1uex4e8c 7404 7403 2007-08-23T19:05:49Z Falcata 566 /* Living Lava */ 7404 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == * [http://wiki.themanaworld.org/images/4/44/Monster-slime-lava.png Image] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore * '''Behaviour''' Attack when attacked, steals items like most slimes, but stolen items are destroyed unless immune to heat * '''Notes''' Lava that has been inhabited by a fire elemental, granting it a semblance of life. 4qtzc2ctkkolutg31zz57biaizr3g3b 7420 7404 2007-08-26T09:52:46Z Bjørn 3 Reverted edits by [[Special:Contributions/Falcata|Falcata]] ([[User_talk:Falcata|Talk]]); changed back to last version by [[User:Crush|Crush]] 7420 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' adhihldwfu7qqg7eht1oncirpajv82m 7421 7420 2007-08-26T09:53:39Z Bjørn 3 Blah, I wanted to roll back only one revision 7421 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore * '''Behaviour''' Attack when attacked, steals items like most slimes, but stolen items are destroyed unless immune to heat * '''Notes''' Lava that has been inhabited by a fire elemental, granting it a semblance of life. c77l2y0qgjgfhhprz5ewtje1uex4e8c 7526 7421 2007-08-28T04:39:11Z Kreeg 513 /* Enchanted Tree */ 7526 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore * '''Behaviour''' Attack when attacked, steals items like most slimes, but stolen items are destroyed unless immune to heat * '''Notes''' Lava that has been inhabited by a fire elemental, granting it a semblance of life. qi8vbe0jh2g2jwyj9jhpvzt36k9xja6 7531 7526 2007-09-03T00:20:22Z Falcata 566 /* Living Lava */ Expanded on monster information 7531 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. mdiirn2au80hnp3ctnzil3xjlyuswzc 7627 7531 2007-10-03T16:57:08Z Kreeg 513 /* Enchanted Tree */ 7627 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. mivk8r0kgc6bl1u84nmr6wqt1q4yc24 7628 7627 2007-10-03T16:58:38Z Kreeg 513 /* Enchanted Tree */ 7628 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. 52q0l18ce4wzb5mtvel6sfwwkxu601i 7690 7628 2007-10-10T05:36:36Z Kreeg 513 /* Enchanted Tree */ 7690 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.gif|{{MonstertreeIdle.gif}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. 8rd6jxx6fj1h9dediu9ufuenjl9n47w 7691 7690 2007-10-10T05:37:07Z Kreeg 513 /* Enchanted Tree */ 7691 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. ngjk8utqab2xd102s5ds2im7f1nha0g 7692 7691 2007-10-10T05:50:49Z Kreeg 513 /* Enchanted Tree */ 7692 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. gfc8m7jcyhhmur8ne5qa2ewk8n95wz0 8226 7692 2007-12-13T16:05:50Z Pajarico 5 /* Royal maggot */ Added section 8226 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. 4hrrn620kq7kd76qhoarwr2gu3mzsrz 8263 8226 2007-12-21T11:39:22Z Pajarico 5 /* Template */ Added 'Forum post' to template 8263 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. 7k2des4wruky9lbbujaxckpxaej9tdc 8264 8263 2007-12-21T11:40:18Z Pajarico 5 /* Royal maggot */ Added link to forum 8264 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] ra4w2fu50ctxhqg8rlpbkkwxl2t8wu3 8328 8264 2007-12-25T17:09:27Z Pajarico 5 /* Royal maggot */ 8328 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' 1j6o2wrjip16mmcqsyy4j05wttqppa2 8568 8328 2008-01-30T01:29:52Z Pkemrin 1070 /* Creatures */ 8568 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Rabite == <gallery> Image:Ribite_001.png </gallery> * '''Name''' Rabite * '''Type''' Unfriendly - Hostile * '''Area''' Low Level Forest Area's * '''HP''' Low * '''Attack power''' Low * '''Movements''' Slow, until someone gets within range, then medium to attack * '''Contains items''' Candy, Occasionally chocolate * '''Behavior''' Hops around in grassy area's until someone comes within range, then attacks without provocation * '''Notes''' Creature should be commonly found hopping around in grassy forest area's. Should not ever drop rare items, but should occasionally drop healing items like candy. fipco1ig01f8gun8zgosx0z3a7etei6 8570 8568 2008-01-30T02:28:54Z Falcata 566 /* Rabite */ 8570 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Rabite == <gallery> Image:Ribite_001.png </gallery> * '''Name''' Rabite * '''Type''' Unfriendly - Hostile * '''Area''' Low Level Forest Area's * '''HP''' Low * '''Attack power''' Low * '''Movements''' Slow, until someone gets within range, then medium to attack * '''Contains items''' Candy, Occasionally chocolate * '''Behavior''' Hops around in grassy area's until someone comes within range, then attacks without provocation * '''Notes''' Creature should be commonly found hopping around in grassy forest area's. Should not ever drop rare items, but should occasionally drop healing items like candy. '''Comment:''' I seriously doubt that the Rabite will be included in TMW, due to copyrights. [[User:Falcata|Bobby Jim]] 03:28, 30 January 2008 (CET) hinmkr1mjm17oyyg0u3jvsxy9h353bf 8572 8570 2008-01-30T10:39:00Z Crush 103 Rabbite deleted - copyright violation. 8572 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' 1j6o2wrjip16mmcqsyy4j05wttqppa2 8894 8572 2008-03-20T02:25:48Z Axltrozz 602 /*Bitan*/ 8894 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 mxaihwgvcu2tfk490lz8e57p83c2rli 9713 8894 2008-07-10T16:50:04Z Yanom 1139 9713 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack bf60rlg7bl4vy2jkt4grv1ldapykl7s 9725 9713 2008-07-11T01:50:43Z Yanom 1139 /* Ice Dragon */ 9725 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] hu5ofnu8456flytbhjrdhh5817ink2e 9732 9725 2008-07-12T18:47:21Z Yanom 1139 /* Royal maggot */ 9732 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] 6g9ugbpmg9ytg380k98g9trtg5h0xz3 9860 9732 2008-08-13T23:04:36Z Z orochii 1238 Homemade creature ^^. 9860 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Zouveleki Orochii Productions ^^ (¬¬) == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Monster * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''HP''' Medium (1000 or so...?) * '''Attack Power''' Medium (88-98) * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. [[User:Z orochii|Z orochii]] c8ezw2s2potoli8towsc1v3do8g64na 9861 9860 2008-08-13T23:05:51Z Z orochii 1238 /* Zouveleki Orochii Productions ^^ (¬¬) */ 9861 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Zouveleki Orochii Productions ^^ (¬¬) == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''HP''' Medium (1000 or so...?) * '''Attack Power''' Medium (88-98) * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. [[User:Z orochii|Z orochii]] n32gdtgt0xplz1txnc4lraxnfm4y486 9865 9861 2008-08-13T23:13:10Z Crush 103 format 9865 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''HP''' Medium (1000 or so...?) * '''Attack Power''' Medium (88-98) * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. [[User:Z orochii|Z orochii]] 6vlgeqtnt7t4dk82lawkeh96t0g47zs 9869 9865 2008-08-14T02:53:52Z Z orochii 1238 /* Wormoid */ 9869 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''HP''' Medium (700 or so...?) * '''Attack Power''' Medium (48-53) * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. [[User:Z orochii|Z orochii]] njpe9xa0xjjpz27wy9odj2ui20r1e6e 9870 9869 2008-08-14T03:01:11Z Z orochii 1238 /* Wormoid */ 9870 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be" or so, fitting between the Rudolf Slime and Red Slime or so ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 [[User:Z orochii|Z orochii]] pbaozkipoejvf24098elnqroz1c860a 9871 9870 2008-08-14T03:01:38Z Z orochii 1238 /* Wormoid */ 9871 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be" or so, fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 [[User:Z orochii|Z orochii]] btnl6nf8iz1lor22gqjtdn4g3xb04rh 9872 9871 2008-08-14T03:02:06Z Z orochii 1238 /* Wormoid */ 9872 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 [[User:Z orochii|Z orochii]] cmn8kd5xt6pnee6i99m804ph2la4a2r 9873 9872 2008-08-14T03:03:48Z Z orochii 1238 /* Wormoid */ 9873 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation and check how am I doing a get better, and contribute with the game with better doings. dx3nyi6hgxlez2cgstv1qt57yleoy3u 9874 9873 2008-08-14T03:04:44Z Z orochii 1238 /* Wormoid */ 9874 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? qezcki07b0arczrnj2vd11gpzqqhvoi 9875 9874 2008-08-14T03:05:22Z Z orochii 1238 /* Wormoid */ 9875 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more, hehehehh... k35tcy1f9po6ge3xl98kat4go6opbhd 9876 9875 2008-08-14T03:05:38Z Z orochii 1238 /* Wormoid */ 9876 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... 1wautwggvs2xmupuzr0siv11l6jkuf7 10138 9876 2008-09-16T16:17:11Z Blodyavenger 1268 /* Number 1 */ 10138 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... tgjybk2b6xd8yb7ev32lanelwsp5gzc 10139 10138 2008-09-16T16:17:29Z Blodyavenger 1268 /* Number 1 */ 10139 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... 9uwm2z2nfl7dwmfbikjvnhxe66prr75 11003 10139 2008-12-17T03:56:17Z NocarOlere 1374 rotroccc4 11003 wikitext text/x-wiki chiacele {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... 0me8jlgnvkqigimx69jptyta1r5c78n 11009 11003 2008-12-17T05:31:59Z Jaxad0127 999 Revert vandalism 11009 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... 9uwm2z2nfl7dwmfbikjvnhxe66prr75 11282 11009 2009-01-08T14:10:32Z NocarOlere 1374 http://chifire.strefa.pl/news-935.html 11282 wikitext text/x-wiki [http://chifire.strefa.pl/news-935.html lost in space video clip] [http://bukgetert.0lx.net/sitemap.htm link] [http://baslozaro.is-the-boss.com/article99.html mo license bureau] [http://chifire.strefa.pl/news-1917.html jet plane crash videos] [http://lofaako.strefa.pl/article282.html pflugerville movie theater] {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... aa0w6zrgxeof9wqlwx8s8ol5riy1txt 11317 11282 2009-01-08T15:22:25Z Jaxad0127 999 Undo revision 11282 by [[Special:Contributions/NocarOlere|NocarOlere]] ([[User talk:NocarOlere|Talk]]) 11317 wikitext text/x-wiki {{Category_art}} {{Status_red}} This page is intended as a whiteboard for graphic developers to post their creations. I prefered the word ''creature'' over ''monster'' because I pretend to aglutinate every living being which is not a player nor a NPC. I will suggest a standard questionnaire with a number of characteristics you should provide. If you don't know what to put on some of them don't worry! someone will fill the gaps with his/ her suggestions. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. Feel free to suggest more fields. --[[User:Pajarico|Pajarico]] 21:03, 12 April 2006 (CEST) ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketchs: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behaviour''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Assigned to''' Type the developer (pixel artists) name and the a link to the active forum thread (if any). * '''Attached script''' Link to the script which defines the behaviour. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum post''' Link to the forum thread about this creature. ---- = Creatures = == Number 1 == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbyes * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 == Number 2 == <gallery> Image:Creature-unknown01.jpg|{{Image:Creature-unknown01.jpg}} </gallery> * '''Name''' * '''Type''' Friendly * '''Area''' Between wet places and desertic lands, savannah and/or forest would fit quite well * '''HP''' High * '''Movements''' Moves slow * '''Behaviour''' Roam, never attacks * '''Assigned to''' == Enchanted Tree == <gallery> Image:Creaturetree.jpg|{{Image:Creaturetree.jpg}} Image:CreaturetreeSizeProposal.jpg|{{Image:CreaturetreeSizeProposal.jpg}} Image:Eviltree_proposal.png|{{Eviltree_proposal.png}} Image:MonstertreeIdle.png|{{MonstertreeIdle.png}} Image:MonstertreeWalking.gif|{{MonstertreeWalking.gif}} </gallery> * '''Name''' Enchanted tree * '''Type''' Unfriendly * '''Area''' Forest * '''HP''' Medium/high * '''Attack power''' High * '''Movements''' Doesn't move or very slow, attacks slow * '''Contains items''' Wood * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' Kreeg * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?p=25948#25948 == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behaviour''' * '''Assigned to''' == Number 5 == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbyes. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). == Swamp Flower == <gallery> Image:Creature-swampflower01.png|{{Image:Creature-swampflower01.png}} </gallery> * '''Name''' Swamp flower. * '''Type''' Unfriendly. * '''Area''' Forest, near pound or lakes. * '''HP''' Medium/high. * '''Attack power''' High. * '''Movements''' Doesn't move, it just floats following the water current. Attacks fast. * '''Contains items''' Special bush wood. * '''Behaviour''' Attack when attacked or attack always. * '''Assigned to''' * '''Notes''' The ''special bush wood'' is what the spines are made with. Take it to a carpenter and he will craft durable items like plates, shields, helmets... == Number 7 == ''No image'' * '''Name''' ??. * '''Type''' Unfriendly. * '''Area''' Desert. * '''HP''' Unknown. * '''Attack power''' Very high (lethal). * '''Movements''' Doesn't move, just waits. * '''Behaviour''' Attack always if you fall in it. * '''Assigned to''' * '''Notes''' It lives under the sand, like some spiders, ants, or the worms in Star Wars. This creature is probably of an unknown nature and form as no one has seen it outside of the sand. As long as you don't fall in its trap it can't touch you, but if you fall in it you are death. I haven't draw any sketch, it should be done with an animation derivated from the sand tiles. == Beornth Spider == '' No Image '' * '''Name: Beornth Spider''' * '''Type: Always Hostle''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Crittical Hits (+10%) + Moderate Posion Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Posions - Increases Posion damage to Dangerous levels (10 mp / use) ** Improve Crittical - Increases the crittical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulernabilities - Fire ** Magic Vulernabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Componants: Beornth Venom - Crafting Poisons''' * '''Harvistable Componants: Beornth Belly - Crafting Mana Potions''' ==Dok'e Mono== '' No Image '' * '''Name: Dok'e Mono''' * '''Creature Discription''' Like a miniture person, but green and ugly. * '''Type: Neutral''' * '''Area: Muddy Caves''' * '''Hp: 50''' * '''Mp: 250''' * '''Attacks: Mild Damage, with a very good chance of stuning the combatant (+30%)''' * '''Movement: Slow and Sneaky''' * '''Behavior: Sneak and Steal first, if caught then fight.''' * '''Assigned to: None Yet''' * '''Size: 2 to 3 feet''' * '''Special Abilities:''' ** Steal from players ** Knock Unconscious (15 Mp / Use) 45% Fail Chance, No Damage ** Regeneration (2 Mp / Sec) Heals 5 Hp / Sec ** Ressurect Other Monsters (20 Mp / Use) As Ressurection *'''Notes:''' It likes to steal, alot of shiny objects... *'''Harvistable Componants: NONE''' == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behaviour''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. == Royal maggot == <gallery> Image:Creature-royal maggot.png Image:Peacock front02 - melbourne zoo.jpg Image:Clearfin Lionfish.jpg </gallery> * '''Name''' Royal maggot --Maggotae superioris (or whatever, really ;)). * '''Type''' Foe. * '''Area''' Desert. * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Same as current maggot with poisonous spines. * '''Contains items''' * '''Behaviour''' Mostly calm. Attacks when attacked or when it detects a threatening presence (players staying around for too long or such). * '''Assigned to''' * '''Attached script''' * '''Notes''' This a metamorphosed state of the maggot. I have to work on the spines, I had in mind to make them as an hybrid between the spines of that fish and the tail of a peacock. * '''Forum post''' [http://forums.themanaworld.org/viewtopic.php?t=3278 here] == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behaviour''' Attacks when stepped near it. * '''Assigned to''' * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum post''' == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Forum Post''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 == Ice Dragon == * '''Name''' Ice Dragon * '''Type''' Boss * '''Area''' Icy Cave * '''HP''' Insane * '''Attack Power''' Insane * '''Movements''' Walk and Freeze attack [[Image:icedragon.png]] == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''Behaviour''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... 9uwm2z2nfl7dwmfbikjvnhxe66prr75 13300 11317 2009-09-13T17:01:55Z Fother 1315 Updated template section, reorg & added additional projects (still need to add a few personal projects here as well). 13300 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 = Forgotten Proposals/Concepts = == Bitan == <gallery> Image:BitanIcon.png </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? j49hpp328i9145ob5o77dkvhqznlpnu 13322 13300 2009-09-18T01:36:41Z Fother 1315 /*Yeti*/ added to WIP List 13322 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? 1c1er09o2o9krrmf602knrw0bumwmeq 13336 13322 2009-09-20T02:47:36Z Skipy 1669 13336 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== [[Image:The_eye_plant.png‎]] * Name-eye plant * Type- unfriendly * Area-bog * HP- = mid..= to snakes * Attack power-mid as wall= to snakes * Movements-stay put...fix * Contains items Items it should drop (or it shouldn't).-not sure???? * Behavior- attack always. * Note-magic * Proposed by skipy.(sorry if i did not put this on here right..first time) * Proposal date- * Assigned to- * Assignment date- * Last change- dwvijvokho484vqdmnqpweqe324w2ng 14426 13336 2009-12-28T12:30:37Z Viann 1561 14426 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * Name-eye plant * Type- unfriendly * Area-bog * HP- = mid..= to snakes * Attack power-mid as wall= to snakes * Movements-stay put...fix * Contains items Items it should drop (or it shouldn't).-not sure???? * Behavior- attack always. * Note-magic * Proposed by skipy.(sorry if i did not put this on here right..first time) * Proposal date- * Assigned to- * Assignment date- * Last change- 2cta1pspkdswzblb24aeoy7z9o5szgp 14427 14426 2009-12-28T12:40:20Z Viann 1561 /* Voakwood */ 14427 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| |*[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * Name-eye plant * Type- unfriendly * Area-bog * HP- = mid..= to snakes * Attack power-mid as wall= to snakes * Movements-stay put...fix * Contains items Items it should drop (or it shouldn't).-not sure???? * Behavior- attack always. * Note-magic * Proposed by skipy.(sorry if i did not put this on here right..first time) * Proposal date- * Assigned to- * Assignment date- * Last change- d3pd25jh6yw3hvt7xhvo2usxatbjtjt 14428 14427 2009-12-28T12:40:57Z Viann 1561 /* Voakwood */ 14428 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * Name-eye plant * Type- unfriendly * Area-bog * HP- = mid..= to snakes * Attack power-mid as wall= to snakes * Movements-stay put...fix * Contains items Items it should drop (or it shouldn't).-not sure???? * Behavior- attack always. * Note-magic * Proposed by skipy.(sorry if i did not put this on here right..first time) * Proposal date- * Assigned to- * Assignment date- * Last change- ijhhuls9vv05p3hs5hnx3jpo7vtz246 14439 14428 2009-12-28T16:12:36Z Viann 1561 14439 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * Name-eye plant * Type- unfriendly * Area-bog * HP- = mid..= to snakes * Attack power-mid as wall= to snakes * Movements-stay put...fix * Contains items Items it should drop (or it shouldn't).-not sure???? * Behavior- attack always. * Note-magic * Proposed by skipy.(sorry if i did not put this on here right..first time) * Proposal date- * Assigned to- * Assignment date- * Last change- ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * Name: Biometrix * Type: Friendly * Area: desert * HP: 500 * Attack power: 50-60 * Movements: fast * Contains items: ** Iron Ore ** Sulphur Powder ** pearl * Behavior: attack when attacked * Attached script: ??? * Proposal by: Viann * Proposal date: 2009-December-28 * Assigned to: Viann * Assignment date: 2009-December-27 * Last change: 2009-December-28 elz1ni3u326ksee2jod6pufoel08hea 14441 14439 2009-12-28T16:39:54Z Viann 1561 /* eye plant */ 14441 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * Name: eye plant * Type: unfriendly * Area: bog * HP: = mid..= to snakes * Attack power: mid as wall= to snakes * Movements: stay put...fix * Contains items: Items it should drop (or it shouldn't).-not sure???? * Behavior: attack always. * Note: magic * Proposed by: skipy.(sorry if i did not put this on here right..first time) * Proposal date: * Assigned to: * Assignment date: * Last change: ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * Name: Biometrix * Type: Friendly * Area: desert * HP: 500 * Attack power: 50-60 * Movements: fast * Contains items: ** Iron Ore ** Sulphur Powder ** pearl * Behavior: attack when attacked * Attached script: ??? * Proposal by: Viann * Proposal date: 2009-December-28 * Assigned to: Viann * Assignment date: 2009-December-27 * Last change: 2009-December-28 ie0gqgme4x4n6vdc2esc5529q9callw 14442 14441 2009-12-28T16:41:32Z Viann 1561 /* eye plant */ 14442 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' * '''Assigned to''' * '''Assignment date''' * '''Last change''' ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * Name: Biometrix * Type: Friendly * Area: desert * HP: 500 * Attack power: 50-60 * Movements: fast * Contains items: ** Iron Ore ** Sulphur Powder ** pearl * Behavior: attack when attacked * Attached script: ??? * Proposal by: Viann * Proposal date: 2009-December-28 * Assigned to: Viann * Assignment date: 2009-December-27 * Last change: 2009-December-28 hhhnwkgv2m50fkltxl2tna85tv0geni 14443 14442 2009-12-28T16:42:02Z Viann 1561 /* eye plant */ 14443 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * Name: Biometrix * Type: Friendly * Area: desert * HP: 500 * Attack power: 50-60 * Movements: fast * Contains items: ** Iron Ore ** Sulphur Powder ** pearl * Behavior: attack when attacked * Attached script: ??? * Proposal by: Viann * Proposal date: 2009-December-28 * Assigned to: Viann * Assignment date: 2009-December-27 * Last change: 2009-December-28 tpmhxmpizdb7j832ei981hr0olc4rfe 14444 14443 2009-12-28T16:43:37Z Viann 1561 /* Biometrix */ 14444 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * '''Name''' Biometrix * '''Type''' Friendly * '''Area''' desert * '''HP''' 500 * '''Attack power''' 50-60 * '''Movements''' fast * '''Contains items''' ** Iron Ore ** Sulphur Powder ** pearl * '''Behavior''' attack when attacked * '''Attached script''' ??? * '''Proposal by''' Viann * '''Proposal date''' 2009-December-28 * '''Assigned to''' Viann * '''Assignment date''' 2009-December-27 * '''Last change''' 2009-December-28 1dfuy1g8rpfnhruo9x1t1gnbq2219sk 14445 14444 2009-12-28T16:46:12Z Viann 1561 14445 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * '''Name''' Biometrix * '''Type''' Friendly * '''Area''' desert * '''HP''' 500 * '''Attack power''' 50-60 * '''Movements''' fast * '''Contains items''' ** Iron Ore ** Sulphur Powder ** pearl * '''Behavior''' attack when attacked * '''Attached script''' ??? * '''Proposal by''' [[User:Viann|<span style="color:#009900">Viann]] * '''Proposal date''' 2009-December-28 * '''Assigned to''' [[User:Viann|<span style="color:#009900">Viann]] * '''Assignment date''' 2009-December-27 * '''Last change''' 2009-December-28 = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? q0z6fj7kbh8mz7gqyrjbtp07gltnbmn 16901 14445 2010-12-13T12:03:22Z Newtkiller 1563 /* Voakwood */ 16901 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) *[[User:Newtkiller|<span style="color:#009900">Newtkiller]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * '''Name''' Biometrix * '''Type''' Friendly * '''Area''' desert * '''HP''' 500 * '''Attack power''' 50-60 * '''Movements''' fast * '''Contains items''' ** Iron Ore ** Sulphur Powder ** pearl * '''Behavior''' attack when attacked * '''Attached script''' ??? * '''Proposal by''' [[User:Viann|<span style="color:#009900">Viann]] * '''Proposal date''' 2009-December-28 * '''Assigned to''' [[User:Viann|<span style="color:#009900">Viann]] * '''Assignment date''' 2009-December-27 * '''Last change''' 2009-December-28 = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? hb059jk7ne2q4mwdvoipd2x26gkjy3p 27077 16901 2013-07-01T19:39:33Z Jaxad0127 999 Jaxad0127 moved page [[Creature proposal]] to [[Dev:Creature proposal]] 27077 wikitext text/x-wiki {{Category_art}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) *[[User:Newtkiller|<span style="color:#009900">Newtkiller]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * '''Name''' Biometrix * '''Type''' Friendly * '''Area''' desert * '''HP''' 500 * '''Attack power''' 50-60 * '''Movements''' fast * '''Contains items''' ** Iron Ore ** Sulphur Powder ** pearl * '''Behavior''' attack when attacked * '''Attached script''' ??? * '''Proposal by''' [[User:Viann|<span style="color:#009900">Viann]] * '''Proposal date''' 2009-December-28 * '''Assigned to''' [[User:Viann|<span style="color:#009900">Viann]] * '''Assignment date''' 2009-December-27 * '''Last change''' 2009-December-28 = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? hb059jk7ne2q4mwdvoipd2x26gkjy3p 29395 27077 2014-02-20T04:10:26Z Wushin 2233 29395 wikitext text/x-wiki {{Outdated}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) *[[User:Newtkiller|<span style="color:#009900">Newtkiller]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * '''Name''' Biometrix * '''Type''' Friendly * '''Area''' desert * '''HP''' 500 * '''Attack power''' 50-60 * '''Movements''' fast * '''Contains items''' ** Iron Ore ** Sulphur Powder ** pearl * '''Behavior''' attack when attacked * '''Attached script''' ??? * '''Proposal by''' [[User:Viann|<span style="color:#009900">Viann]] * '''Proposal date''' 2009-December-28 * '''Assigned to''' [[User:Viann|<span style="color:#009900">Viann]] * '''Assignment date''' 2009-December-27 * '''Last change''' 2009-December-28 = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? dotv6u2ekx5siv304ls6m7eu0ieyusx 29396 29395 2014-02-20T04:14:22Z Wushin 2233 /* no longer relevant to current dev. do not delete */ 29396 wikitext text/x-wiki {{Status_outdated}} This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Ghost== {{Opinions| | }} <gallery> Image:Fother-generic-ghost.png|{{Image:Fother-generic-ghost.png}} </gallery> * '''Name''' Ghost * '''Type''' Unfriendly * '''Area''' Ancestral Tombs, Haunted Dwellings * '''HP''' ??? * '''Attack power''' ??? * '''Movements''' ** '''Walk''' Slow ** '''Tracking''' High Medium * '''Contains items''' ** Ectoplasm * '''Behavior''' Aggressive * '''Notes''' Ghosts are the disembodied souls of the dead. * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' Include date of proposal * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-July 7 * '''Last change''' 2009-July 7 ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) *[[User:Newtkiller|<span style="color:#009900">Newtkiller]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 == Yeti == {{Opinions| | }} <gallery> Image:Hkurn-yeti.gif|{{Image:Hkurn-yeti.gif}} </gallery> * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' Yeti * '''Type''' Unfriendly * '''Area''' Snowy mountains * '''HP''' ??? * '''Attack power'''??? * '''Movements''' ??? * '''Contains items''' ??? * '''Behavior''' Attacks on sight. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=8069 * '''Proposed by''' [[User:hkurn|hkurn]] * '''Proposal date''' 2009-Aug 30 * '''Assigned to''' [[User:hkurn|hkurn]] and [[User:bcs86|bcs86]] * '''Assignment date''' 2009-Aug 30 * '''Last change''' 2009-Sep = Forgotten Proposals/Concepts = == Bitan == {{Opinions| | }} <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif‎|100px]] * '''Name''' Biometrix * '''Type''' Friendly * '''Area''' desert * '''HP''' 500 * '''Attack power''' 50-60 * '''Movements''' fast * '''Contains items''' ** Iron Ore ** Sulphur Powder ** pearl * '''Behavior''' attack when attacked * '''Attached script''' ??? * '''Proposal by''' [[User:Viann|<span style="color:#009900">Viann]] * '''Proposal date''' 2009-December-28 * '''Assigned to''' [[User:Viann|<span style="color:#009900">Viann]] * '''Assignment date''' 2009-December-27 * '''Last change''' 2009-December-28 = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. == Living Lava == {{Opinions| | }} [[Image:Monster-slime-lava.png]] * '''Type''' Unfriendly * '''Area''' Volcanic caverns, lava fields, similar regions. * '''HP''' High * '''Attack power''' Medium-High * '''Movements''' slow speed, moves faster when hostile. * '''Contains items''' Chunks of ore, any fire-resistant items it has picked up * '''Behavior''' Attack when attacked, picks up items like most slimes, but the items are destroyed unless they are immune or resistant to fire. * '''Notes''' This monster is lava that has been inhabited by a fire elemental, granting it a semblance of life. When this monster moves, it leaves a thin trail of lava behind it, which damages anyone who comes in contact with it unless they have equipped boots that are fire resistant. The lava cools and solidifies after a short while. Upon dying, it slowly cools and solidifies. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png‎]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? 8yubhuq1t59zkwhhwlmagih58o8if1d 29550 29396 2014-02-28T06:39:30Z Cassy 2265 leaving a note about better places (trello & forum) to suggest monsters, fixing image links and deleting mobs that already have their own Trello card 29550 wikitext text/x-wiki <div style="background-color: #DDDDDD; text-align: center; border: 1px solid #555555; margin-bottom: 10px;"> '''This article is outdated''' '''Please use our [https://trello.com/b/rNnx513z/art-development Art Development Board on Trello] or the subforum "[https://forums.themanaworld.org/viewforum.php?f=2 TMW]" if you want to suggest new mobs. Also this wiki page might help you: [[Dev:Monster Design]].''' This page will get archieved soon and the monsters suggested transfered to Trello where they won't get forgotton. </div> This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) *[[User:Newtkiller|<span style="color:#009900">Newtkiller]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif|100px]] * '''Name''' Biometrix * '''Type''' Friendly * '''Area''' desert * '''HP''' 500 * '''Attack power''' 50-60 * '''Movements''' fast * '''Contains items''' ** Iron Ore ** Sulphur Powder ** pearl * '''Behavior''' attack when attacked * '''Attached script''' ??? * '''Proposal by''' [[User:Viann|<span style="color:#009900">Viann]] * '''Proposal date''' 2009-December-28 * '''Assigned to''' [[User:Viann|<span style="color:#009900">Viann]] * '''Assignment date''' 2009-December-27 * '''Last change''' 2009-December-28 = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? 5ks6t87bk1yhbnumy57jbq07uc9rx9x 59474 29550 2024-03-27T03:56:42Z Move page script 2739 Move page script moved page [[Dev:Creature proposal]] to [[Development:Creature proposal]]: Rename Dev: to Development: so the miraheze import works 29550 wikitext text/x-wiki <div style="background-color: #DDDDDD; text-align: center; border: 1px solid #555555; margin-bottom: 10px;"> '''This article is outdated''' '''Please use our [https://trello.com/b/rNnx513z/art-development Art Development Board on Trello] or the subforum "[https://forums.themanaworld.org/viewforum.php?f=2 TMW]" if you want to suggest new mobs. Also this wiki page might help you: [[Dev:Monster Design]].''' This page will get archieved soon and the monsters suggested transfered to Trello where they won't get forgotton. </div> This page is intended as a whiteboard for graphic developers to post their creations. Please, when suggesting other data add a comma and your suggest. Do not erase or alter previous work. ---- = Template = * '''A drawing''' of the creature '''at least in one position''', showing a clear view of it; add a recognizable figure for comparing its height. Other advisable sketches: death frame, attacking frame, other action frame(s) (idle animation, hiding, etc.). Please, use thumbnails. * '''Name''' * '''Type''' Friendly/unfriendly (the latter concerns every creature capable of doing damage even if its not programmed to attack first). * '''Area''' Where do you think it should spawn. * '''HP''' * '''Attack power''' * '''Movements''' Speed of the movements both walking/flying and attacking. * '''Contains items''' Items it should drop (or it shouldn't). * '''Behavior''' Attack when attacked, attack always, make groups, roam, follow another being... * '''Attached script''' Link to the script which defines the behavior. This will make more sense when scripts are usable ;). * '''Notes''' Story, proposed as mini-boss or boss, trainable... * '''Forum thread''' Link to the forum thread about this creature. * '''Proposed by''' List the name of the proposer * '''Proposal date''' Include date of proposal * '''Assigned to''' List the name of the person developing the graphics * '''Assignment date''' Include date of artist assignment (when work began on creating pixel art for creature). * '''Last change''' Include date of last change or work on assignment. ---- = Concepts = {{Status_red}} = Work in Progress = == Beornth Spider == {{Opinions| | }} <gallery> Image:Example-spiderboss.gif|{{Image:Example-spiderboss.gif}} </gallery> * '''Name: Beornth Spider''' * '''Type: Always Hostile''' * '''Area: Muddy areas and Swamps''' * '''Hp: 450''' * '''Mp: 150''' * '''Attack: Moderate + Improved Chance for Critical Hits (+10%) + Moderate Poison Damage + Moderate MP Damage''' * '''Movement: Fast and Deadly, Sneaky''' * '''Behavior: Let no one go by with out a fight''' * '''Assigned to: None Yet ''' * '''Size: Standing 7 to 8 feet tall, about 6 feet by 7.5 feet dimensionally.''' * '''Special Abilities:''' ** Web - Decreases movement, attack and casting speeds of those fighting it by 75%: Over an AOE (15mp / use) ** Amplify Poisons - Increases Poison damage to Dangerous levels (10 mp / use) ** Improve Critical - Increases the critical hit rate an additional 5% (5mp / use) ** Drain MP - restores 1/2 mp damage dealt ** Magic Immunities - Time ** Magic Immunities - Cold ** Magic Vulnerabilities - Fire ** Magic Vulnerabilities - Light * '''Notes''' It likes to kill and kill for fun, * '''Harvistable Components: Beornth Venom - Crafting Poisons''' * '''Harvistable Components: Beornth Belly - Crafting Mana Potions''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' 2006-? ?? * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' ??? * '''Last change''' ??? ==Voakwood== {{Opinions| *[[User:Viann|<span style="color:#009900">Viann]] 12:40, 28 December 2009 (UTC) *[[User:Newtkiller|<span style="color:#009900">Newtkiller]] 12:40, 28 December 2009 (UTC) | }} <gallery> Image:Concept-oldtree.png|{{Image:Concept-oldtree.png}} </gallery> * '''Name''' Voakwood (a play on Volk + Oak + Wood) * '''Type''' Friendly * '''Area''' Woodland, Forest. * '''HP''' A lot * '''Attack power''' same as flowers. * '''Movements''' ** '''Walk''' Stationary ** '''Tracking''' Only when in range * '''Contains items''' ** Raw Log 4X ** Voakwood Sap ** Bird's Nest ** Bee Hive ** Jar of Honey * '''Behavior''' Passive * '''Notes''' She's what the Log Heads used to be part of before Jack liberated them from their mother's branches... still a concept. For TMWServ, Voakwood should have a small chance to spawn multiple Log heads to attack the player. On death, if a Bee Hive is dropped, an ''Angry Swarm'' (creature consisting of a swirling set of bees) should be spawned to attack the player). * '''Forum thread''' none * '''Proposed by''' [[User:Fother|Fother]] * '''Proposal date''' 2009-June 10 * '''Assigned to''' [[User:Fother|Fother]] * '''Assignment date''' 2009-June 16 * '''Last change''' 2009-June 16 <gallery> Image:BitanIcon.png|{{Image:BitanIcon.png}} </gallery> * '''Name''' Bitan. * '''Type''' Boss * '''Area''' Desert/Forest * '''HP''' High * '''Attack Power''' Very High * '''Movements''' Walk and Attack * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=2963 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Carnivore nematode == {{Opinions| | }} <gallery> Image:Creature-nematode.png </gallery> * '''Name''' Carnivore nematode. * '''Type''' Foe. * '''Area''' Desert (soft soil and sand dunes). * '''HP''' Medium. * '''Attack power''' Medium/high. * '''Movements''' Attack (maybe with one animation will suffice, an animation placed underneath the player with earth moving), the rest of the movements happen underground. * '''Contains items''' Meat. * '''Behavior''' Attacks when stepped near it. * '''Attached script''' * '''Notes''' It moves and lives underground and detects movement on the surface. Then it attacks when the player is on an active zone. A script should rule which tiles are in the scope of an attack. The player can run to rocks, mountains or harder soil to avoid the attack. * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leap Monster == {{Opinions| | }} <gallery> Image:Leapmonster.jpg|{{Image:Leapmonster.jpg}} </gallery> * '''Name''' Leap monster * '''Type''' * '''Area''' * '''HP''' * '''Attack power''' * '''Movements''' * '''Contains items''' * '''Behavior''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Leaflo == {{Opinions| | }} <gallery> Image:Creature-forest01.png|{{Image:Creature-forest01.png}} </gallery> * '''Name''' Leaflo * '''Type''' Unfriendly. * '''Area''' Forest, in pound or lakes. * '''HP''' Low/medium. * '''Attack power''' High, lethal for newbies. Very poisonous. * '''Movements''' Moves slow, attacks fast. * '''Contains items''' Poison. * '''Behavior''' Attack when attacked or attack always. * '''Notes''' Attacks with its tail when annoyed or if you step on it. The attack itself is very weak, but the inoculated poison stays for long and takes many HPs from the player until the poison dilutes or you take an antidote. Take the poison (item) to a specialized alchemist, he will produce a fine antidote. This was my first contribution in color for TMW ;). * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? == Lurker == {{Opinions| | }} <gallery> Image:Creature01-stand.png|{{Image:Creature01-stand.png}} Image:Creature01-crouch.png|{{Image:Creature01-crouch.png}} Image:Creature01-attack.png|{{Image:Creature01-attack.png}} Image:Creature01-dead.png|{{Image:Creature01-dead.png}} </gallery> * '''Name''' * '''Type''' Unfriendly * '''Area''' Between wet places and desert lands, savannah and/or forest would fit quite well. * '''HP''' Quite high * '''Attack power''' High, lethal for newbies * '''Movements''' Moves slow, attacks fast * '''Contains items''' * '''Behavior''' Attack when attacked or attack always. * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' http://forums.themanaworld.org/viewtopic.php?f=8&t=4872&p=41136#p41136 * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' [[User:Blodyavenger|Blodyavenger]] * '''Assignment date''' ??? * '''Last change''' 2008-Sep 16 == Wormoid == {{Opinions| | }} [[Image:Wormoid.png]] * '''Name''' Wormoid (think 'bout a better one ok?) * '''Type''' Medium Lvl Normal Creature * '''Area''' Depending, it can be in a lava cave or an icy cave. Don't matter what, A CAVE... please. * '''Movement''' Attack and walking at Medium speed(slower than player, but not much) * '''Skills''' Stunning Powder * '''Type''' Friendly * '''Items''' Maybe rare ones...something like ruby eye (0.05%) * '''HP''' Medium (420 or so...?) * '''Attack Power''' Medium (40-50) * '''Defense''' 15% * '''Experience''' 150 * '''Behavior''' Attack when attacked, make groups. If near to death, it runs or something like that. They're a friendly specie of humanoids. * '''Attached Script''' N/A * '''Notes''' They came from the southern territories, always moving to the north. Have a good resistance to different climate conditions, but prefers the dark places cause of their sensible sight. Have a primitive nature, similar to the nomad humans on prehistory. '''STATS - just doing a "would be", fitting between the Rudolf Slime and Red Slime or something like that ^^.''' * '''Attached script''' ??? * '''Notes''' ??? * '''Forum thread''' ??? * '''Proposed by''' ??? * '''Proposal date''' ??? * '''Assigned to''' ??? * '''Assignment date''' ??? * '''Last change''' ??? Put your comments here, adding info: [[User:Z orochii|Z orochii]]. I just want to have some evaluation. Don't matter, right? Wait for more production, hehehehh... ==Biometrix== {{Opinions| | }} [[Image:Biometrix.gif|100px]] * '''Name''' Biometrix * '''Type''' Friendly * '''Area''' desert * '''HP''' 500 * '''Attack power''' 50-60 * '''Movements''' fast * '''Contains items''' ** Iron Ore ** Sulphur Powder ** pearl * '''Behavior''' attack when attacked * '''Attached script''' ??? * '''Proposal by''' [[User:Viann|<span style="color:#009900">Viann]] * '''Proposal date''' 2009-December-28 * '''Assigned to''' [[User:Viann|<span style="color:#009900">Viann]] * '''Assignment date''' 2009-December-27 * '''Last change''' 2009-December-28 = Completed Unreleased Creatures = Please use this section for completed creatures that have not been implemented in game. For in game creatures, please see [[Monster_reference|Monster Reference]]. Please note that completed status does not guarantee content will be implemented. ==eye plant== {{Opinions| | }} [[Image:The_eye_plant.png]] * '''Name''' eye plant * '''Type''' unfriendly * '''Area''' bog * '''HP''' = mid..= to snakes * '''Attack power''' mid as wall= to snakes * '''Movements''' stay put...fix * '''Contains items''' Items it should drop (or it shouldn't).-not sure???? * '''Behavior''' attack always. * '''Note''' magic * '''Proposed by''' skipy.(sorry if i did not put this on here right..first time) * '''Proposal date''' ??? * '''Assigned to'''??? * '''Assignment date''' ??? * '''Last change'''??? 5ks6t87bk1yhbnumy57jbq07uc9rx9x 0 945 33 2005-05-23T02:20:57Z 82.73.47.9 Added link to my user page. 33 wikitext text/x-wiki * [[Chetic]] * ElvenProgrammer * [[User:Bjørn | Bjørn Lindeijer]] * [[Sull]] * [[Kyokai]] * [[Talaroc]] * [[Rotonen]] * [[MaesterPixel]] * [[Magick]] * [[maci]] * [[Irukard]] * [[Aacheron]] 3ckbclz2if9jy3i2066mwnz9gw7t057 35 33 2005-05-23T09:25:00Z Bjørn 3 Added nym 35 wikitext text/x-wiki * Chetic * ElvenProgrammer * [[User:Bjørn | Bjørn Lindeijer]] * Sull * Kyokai * Talaroc * Rotonen * MaesterPixel * Magick * [[User:Nym | Nym]] * maci * Irukard * Aacheron jkp0l7cfai4uxmtish78zcamlk79gyu 58 35 2005-05-23T09:51:17Z Mra 2 added Mra 58 wikitext text/x-wiki * Aacheron * [[User:Bjørn | Bjørn Lindeijer]] * Chetic * ElvenProgrammer * Irukard * Kyokai * maci * MaesterPixel * Magick * [[User:Mra | Mra]] * [[User:Nym | Nym]] * Rotonen * Sull * Talaroc 8a0zhdh9jrh59nxxkkn1hwo5gpdilpu 155 58 2005-05-23T16:07:47Z Bjørn 3 Added Pajarico 155 wikitext text/x-wiki * Aacheron * [[User:Bjørn | Bjørn Lindeijer]] * Chetic * ElvenProgrammer * Irukard * Kyokai * maci * MaesterPixel * Magick * [[User:Mra | Mra]] * [[User:Nym | Nym]] * [[User:Pajarico | Pajarico]] * Rotonen * Sull * Talaroc 0o8nc26qsso2kg22ig0k324h19quc5p 179 155 2005-05-30T08:26:25Z ElvenProgrammer 11 179 wikitext text/x-wiki * Aacheron * [[User:Bjørn | Bjørn Lindeijer]] * Chetic * [[User:ElvenProgrammer | ElvenProgrammer]] * Irukard * Kyokai * maci * MaesterPixel * Magick * [[User:Mra | Mra]] * [[User:Nym | Nym]] * [[User:Pajarico | Pajarico]] * Rotonen * Sull * Talaroc tlr021vyaa1oc6wk8olrpaz3y48wgtd 181 179 2005-06-03T22:09:28Z 84.61.5.101 181 wikitext text/x-wiki * Aacheron * [[User:Bjørn | Bjørn Lindeijer]] * Chetic * [[User:ElvenProgrammer | ElvenProgrammer]] * Irukard * Kyokai * [[User:maci | maci]] * MaesterPixel * Magick * [[User:Mra | Mra]] * [[User:Nym | Nym]] * [[User:Pajarico | Pajarico]] * Rotonen * Sull * Talaroc 2cpri9i47snbx7wpaurybsni4anq7h1 182 181 2005-06-04T17:32:00Z Bjørn 3 Table layout, occupations added 182 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer |- | style="background:#f6f0e0;" | [[User:ElvenProgrammer|ElvenProgrammer]] | style="background:#f6f0e0;" | Project leader, programmer |- | [[User:Golgo|Golgo]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Irukard|Irukard]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Kyokai|Kyokai]] | Game systems designer |- | style="background:#f6f0e0;" | [[User:maci|maci]] | style="background:#f6f0e0;" | User support |- | [[User:Magick|Magick]] | Musician |- | style="background:#f6f0e0;" | [[User:Modanung|Modanung]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Mra|Mra]] | Programmer |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer |- | [[User:Pajarico|Pajarico]] | Concept artist, writer |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music |- | [[User:Talaroc|Talaroc]] | Pixel artist |- | style="background:#f6f0e0; border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="background:#f6f0e0; border-bottom: 2px solid #efdead;" | Programmer |} s0jzcbjl3xdjzfh89d2qg2mtfrruupd 190 182 2005-06-05T04:44:56Z Demon 13 190 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer |- | style="background:#f6f0e0;" | [[User:ElvenProgrammer|ElvenProgrammer]] | style="background:#f6f0e0;" | Project leader, programmer |- | [[User:Golgo|Golgo]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Irukard|Irukard]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Kyokai|Kyokai]] | Game systems designer |- | style="background:#f6f0e0;" | [[User:maci|maci]] | style="background:#f6f0e0;" | User support |- | [[User:Magick|Magick]] | Musician |- | style="background:#f6f0e0;" | [[User:Modanung|Modanung]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Mra|Mra]] | Programmer |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer |- | [[User:Pajarico|Pajarico]] | Concept artist, writer |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music |- | [[User:Talaroc|Talaroc]] | Pixel artist |- | [[User:Demon|Demon]] | Pixel artist |- | style="background:#f6f0e0; border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="background:#f6f0e0; border-bottom: 2px solid #efdead;" | Programmer |} 7utu1hpw9qj1u209dr28zraugvcmzve 196 190 2005-06-05T17:56:07Z Bjørn 3 Update row background color 196 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer |- | style="background:#f6f0e0;" | [[User:ElvenProgrammer|ElvenProgrammer]] | style="background:#f6f0e0;" | Project leader, programmer |- | [[User:Golgo|Golgo]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Irukard|Irukard]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Kyokai|Kyokai]] | Game systems designer |- | style="background:#f6f0e0;" | [[User:maci|maci]] | style="background:#f6f0e0;" | User support |- | [[User:Magick|Magick]] | Musician |- | style="background:#f6f0e0;" | [[User:Modanung|Modanung]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Mra|Mra]] | Programmer |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer |- | [[User:Pajarico|Pajarico]] | Concept artist, writer |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music |- | [[User:Talaroc|Talaroc]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer |} kfwet7x0fk2onozdwevn806sc48uynz 221 196 2005-06-06T23:59:37Z Bjørn 3 Added Bear, Javila and deviexx 221 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:deviexx|deviexx]] | Content manager |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Irukard|Irukard]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer |- | [[User:Kyokai|Kyokai]] | Game systems designer |- | style="background:#f6f0e0;" | [[User:maci|maci]] | style="background:#f6f0e0;" | User support |- | [[User:Magick|Magick]] | Musician |- | style="background:#f6f0e0;" | [[User:Modanung|Modanung]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Mra|Mra]] | Programmer |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer |- | [[User:Pajarico|Pajarico]] | Concept artist, writer |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music |- | [[User:Talaroc|Talaroc]] | Pixel artist |- | style="background:#f6f0e0; border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="background:#f6f0e0; border-bottom: 2px solid #efdead;" | Programmer |} 74q0qv33c0bfz0vfizt0bwd85qo3uk3 223 221 2005-06-11T06:51:02Z 80.183.109.101 223 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:deviexx|deviexx]] | Content manager |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Irukard|Irukard]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer |- | [[User:kindjal|kindjal]] | Programmer |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer |- | [[User:maci|maci]] | User support |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician |- | [[User:Modanung|Modanung]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer |- | [[User:Nym|nym]] | Programmer |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer |- | [[User:Rotonen|Rotonen]] | Head of art, story and music |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer |} qma9wo17ilur9cscfvpqvtkotwpc05y 224 223 2005-06-11T14:17:17Z ElvenProgrammer 11 224 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:deviexx|deviexx]] | Content manager |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Irukard|Irukard]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer |- | [[User:kindjal|kindjal]] | Programmer |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer |- | [[User:maci|maci]] | User support |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician |- | [[User:Modanung|Modanung]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer |- | [[User:Nym|nym]] | Programmer |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer |- | [[User:Rotonen|Rotonen]] | Head of art, story and music |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer |} 3dxgtsqlpqab2x03f0ba5jt74yb7949 225 224 2005-06-11T14:17:56Z ElvenProgrammer 11 225 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:deviexx|deviexx]] | Content manager |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Clef|Clef]] | Pixel artist |- | [[User:Irukard|Irukard]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer |- | [[User:kindjal|kindjal]] | Programmer |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer |- | [[User:maci|maci]] | User support |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician |- | [[User:Modanung|Modanung]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer |- | [[User:Nym|nym]] | Programmer |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer |- | [[User:Rotonen|Rotonen]] | Head of art, story and music |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer |} 6m7nzxfygb2ytf4bwibuic2nb8v8ymo 226 225 2005-06-11T14:20:05Z ElvenProgrammer 11 226 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:deviexx|deviexx]] | Content manager |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Irukard|Irukard]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer |- | [[User:kindjal|kindjal]] | Programmer |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer |- | [[User:maci|maci]] | User support |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician |- | [[User:Modanung|Modanung]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer |- | [[User:Nym|nym]] | Programmer |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer |- | [[User:Rotonen|Rotonen]] | Head of art, story and music |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | "Pixel artist |- | [[User:Talaroc|Talaroc]] | Pixel artist |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer |} dlstc04gi6ea7ru795y63fgz0iv9bub 230 226 2005-06-11T14:20:47Z ElvenProgrammer 11 230 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:deviexx|deviexx]] | Content manager |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Irukard|Irukard]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer |- | [[User:kindjal|kindjal]] | Programmer |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer |- | [[User:maci|maci]] | User support |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician |- | [[User:Modanung|Modanung]] | Pixel artist |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer |- | [[User:Nym|nym]] | Programmer |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer |- | [[User:Rotonen|Rotonen]] | Head of art, story and music |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist |- | [[User:Talaroc|Talaroc]] | Pixel artist |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer |} c762wtqniqa67akzcf0z6409dct7tz2 231 230 2005-06-11T23:27:31Z Bjørn 3 Added location field 231 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter | |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:kindjal|kindjal]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician | style="background:#f6f0e0;" | |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} 8o27pvard6rzxs0me7inig91yzkberz 232 231 2005-06-11T23:33:36Z 213.25.76.128 232 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter | |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:kindjal|kindjal]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician | style="background:#f6f0e0;" | |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} ay9ujdvaoll6ap1rvar7kda9d5dduxu 233 232 2005-06-11T23:36:01Z Bjørn 3 Pajarico from Spain 233 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter | |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:kindjal|kindjal]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician | style="background:#f6f0e0;" | |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} k10rlckxvtn60hjqajdcixjn4wf3033 244 233 2005-06-11T23:37:54Z Bjørn 3 Correction 244 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter | |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:kindjal|kindjal]] | Programmer | Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician | style="background:#f6f0e0;" | |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} n4glso0r0wqkxpq2b49y7534l68jmdn 255 244 2005-06-12T10:31:42Z Bjørn 3 Rotonen from Finland 255 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter | |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:kindjal|kindjal]] | Programmer | Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician | style="background:#f6f0e0;" | |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} 9x5kac5kfqaz7g6zkj7jdvvxkd9nluv 256 255 2005-06-13T09:21:28Z Nym 6 256 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter | |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:kindjal|kindjal]] | Programmer | Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician | style="background:#f6f0e0;" | |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} s36jg89pnmdx73mk63a3p2hkl627cf9 257 256 2005-06-13T09:24:04Z 213.130.251.49 257 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter | |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:kindjal|kindjal]] | Programmer | Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Magick|Magick]] | style="background:#f6f0e0;" | Musician | style="background:#f6f0e0;" | |- | [[User:Mkael|Mkael]] | Concept artist | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} nnmw8spnq6pfb9rg5t0ddf32xpz1q7w 259 257 2005-06-13T09:30:28Z Bjørn 3 Order corrections 259 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter | |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:ElvenProgrammer|ElvenProgrammer]] | style="background:#f6f0e0;" | Project leader, programmer | style="background:#f6f0e0;" | Italy |- | [[User:Golgo|Golgo]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Irukard|Irukard]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | Poland |- | [[User:Javila|Javila]] | Programmer | |- | style="background:#f6f0e0;" | [[User:kindjal|kindjal]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Italy |- | [[User:Kyokai|Kyokai]] | Game systems designer | |- | style="background:#f6f0e0;" | [[User:maci|maci]] | style="background:#f6f0e0;" | User support | style="background:#f6f0e0;" | Germany |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer | style="border-bottom: 2px solid #efdead;" | Poland |} afuef5gb9fahkgodbaqft1kiw50b6yu 261 259 2005-06-13T09:41:44Z Bjørn 3 Added Sull, Bertram and Maester Pixel 261 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:kindjal|kindjal]] | Programmer | Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} qgkb5837wylsb0ygazv1qbusoobkbd3 264 261 2005-06-13T15:22:17Z Javila 4 Added my country ;-) 264 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} 7msmbx2auue66te0b8cah60o8cowy18 323 264 2005-06-14T05:29:18Z 80.183.109.101 323 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} ieamzwradgpum4djaileitdzqs2r96p 324 323 2005-06-28T08:26:39Z ElvenProgrammer 11 fixing order 324 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} jes7j0qnb92036pjf8s03fh1rkuyrxa 351 324 2005-06-28T08:36:47Z ElvenProgrammer 11 fixing style 351 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Sull|Sull]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | Canada |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} e74zdxg2rly0ro3mk7gsjpkrvhy7jml 352 351 2005-07-01T18:37:45Z Sull 17 352 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} l313jrc9fvtgd3p6pqy6jwo7p224as7 380 352 2005-07-01T20:11:16Z ElvenProgrammer 11 Sull please stay 380 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Nym|nym]] | Programmer | Australia |- | style="background:#f6f0e0;" | [[User:Pajarico|Pajarico]] | style="background:#f6f0e0;" | Concept artist, writer | style="background:#f6f0e0;" | Spain |- | [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland |- | style="background:#f6f0e0;" | [[User:Sull|Sull]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | Canada |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead; background:#f6f0e0;" | Poland |} e74zdxg2rly0ro3mk7gsjpkrvhy7jml 576 380 2005-07-04T14:03:30Z Bjørn 3 Added Neko-mon to the list 576 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer | style="border-bottom: 2px solid #efdead;" | Poland |} 0of476cex9irc4uncsubjbn1bqdqaom 584 576 2005-07-29T05:23:56Z CatfishMan 35 584 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Bear|Bear]] | Scripter |- | style="background:#f6f0e0;" | [[User:Bertram|Bertram]] | style="background:#f6f0e0;" | Programmer, Debian package maintainer | style="background:#f6f0e0;" | France |- | [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands |- | style="background:#f6f0e0;" | [[User:Clef|Clef]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Demon|Demon]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:deviexx|deviexx]] | style="background:#f6f0e0;" | Content manager | style="background:#f6f0e0;" | |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | style="background:#f6f0e0;" | [[User:Catfish_Man|Catfish_Man]] | style="background:#f6f0e0;" | Mac Port | style="background:#f6f0e0;" | United States |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer | style="border-bottom: 2px solid #efdead;" | Poland |} rhvwo9v9r1p5hi0fotkgkvagoujy39b 585 584 2005-07-30T11:58:02Z Bjørn 3 Added Doener and Andrej and fixed background 585 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Andrej|Andrej Sinicyn]] | Programmer | |- | style="background:#f6f0e0;" | [[User:Bear|Bear]] | style="background:#f6f0e0;" | Scripter | style="background:#f6f0e0;" | |- | [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Doener|Doener]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Germany |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Catfish_Man|Catfish_Man]] | Mac port | United States |- | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Poland |} 1i0z5aougw73ivos68cewau7wzgb55m 586 585 2005-07-30T12:05:59Z Gagaofdeath 58 586 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Andrej|Andrej Sinicyn]] | Programmer | Germany |- | style="background:#f6f0e0;" | [[User:Bear|Bear]] | style="background:#f6f0e0;" | Scripter | style="background:#f6f0e0;" | |- | [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Doener|Doener]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Germany |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Catfish_Man|Catfish_Man]] | Mac port | United States |- | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Poland |} dejg3o78huucmxl371kfct8ckzsf3ci 637 586 2005-07-30T12:22:22Z Bjørn 3 Fix user page link 637 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany |- | style="background:#f6f0e0;" | [[User:Bear|Bear]] | style="background:#f6f0e0;" | Scripter | style="background:#f6f0e0;" | |- | [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Doener|Doener]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Germany |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Catfish_Man|Catfish_Man]] | Mac port | United States |- | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Poland |} g28r6rotftyzwf7lzqu2wiy2lxr4s71 638 637 2005-08-19T21:50:06Z Irukard 32 I added friend of mine who wanna become pixel artist in TMW 638 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany |- | style="background:#f6f0e0;" | [[User:Bear|Bear]] | style="background:#f6f0e0;" | Scripter | style="background:#f6f0e0;" | |- | [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Doener|Doener]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Germany |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sora|Sora]] | Pixel artist | Poland |- | [[User:Sull|Sull]] | Pixel artist | Canada |- | style="background:#f6f0e0;" | [[User:Talaroc|Talaroc]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Catfish_Man|Catfish_Man]] | Mac port | United States |- | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Programmer | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Poland |} 6ncjsd548v93z05v9643jtvh8tmrbg7 2008 638 2005-08-19T21:56:56Z Irukard 32 fixed colors in developers chart. 2008 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany |- | style="background:#f6f0e0;" | [[User:Bear|Bear]] | style="background:#f6f0e0;" | Scripter | style="background:#f6f0e0;" | |- | [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Doener|Doener]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Germany |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sora|Sora]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Sull|Sull]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | Canada |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Catfish_Man|Catfish_Man]] | style="background:#f6f0e0;" | Mac port | style="background:#f6f0e0;" | United States |- | style="border-bottom: 2px solid #efdead;" | [[User:Usiu|Usiu]] | style="border-bottom: 2px solid #efdead;" | Programmer | style="border-bottom: 2px solid #efdead;" | Poland |} et512w3n5cqj03azfurqsc3ixiz0jkz 3348 2008 2005-12-28T23:37:51Z Bjørn 3 Added Platyna, our Slackware package maintainer 3348 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany |- | style="background:#f6f0e0;" | [[User:Bear|Bear]] | style="background:#f6f0e0;" | Scripter | style="background:#f6f0e0;" | |- | [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Doener|Doener]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Germany |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sora|Sora]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Sull|Sull]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | Canada |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Catfish_Man|Catfish_Man]] | style="background:#f6f0e0;" | Mac port | style="background:#f6f0e0;" | United States |- | [[User:Usiu|Usiu]] | Programmer | Poland |- | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | [[User:Platyna|Zuzanna K. Filutowska]] | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Slackware package maintainer | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Poland |} m0tgd8bxhcfwu8poib5fvy3ydtgy3c3 3349 3348 2005-12-28T23:40:54Z Bjørn 3 Ok nickname then 3349 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany |- | style="background:#f6f0e0;" | [[User:Bear|Bear]] | style="background:#f6f0e0;" | Scripter | style="background:#f6f0e0;" | |- | [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Doener|Doener]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Germany |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sora|Sora]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Sull|Sull]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | Canada |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Catfish_Man|Catfish_Man]] | style="background:#f6f0e0;" | Mac port | style="background:#f6f0e0;" | United States |- | [[User:Usiu|Usiu]] | Programmer | Poland |- | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | [[User:Platyna]] | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Slackware package maintainer | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Poland |} ge4npbr6uywv6hx6405ge9vcomv2aip 3350 3349 2005-12-28T23:41:13Z Bjørn 3 But that didn't look nice 3350 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location |- | [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany |- | style="background:#f6f0e0;" | [[User:Bear|Bear]] | style="background:#f6f0e0;" | Scripter | style="background:#f6f0e0;" | |- | [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France |- | style="background:#f6f0e0;" | [[User:Bjørn|Bjørn Lindeijer]] | style="background:#f6f0e0;" | Lead Programmer | style="background:#f6f0e0;" | The Netherlands |- | [[User:Clef|Clef]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Demon|Demon]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:deviexx|deviexx]] | Content manager | |- | style="background:#f6f0e0;" | [[User:Doener|Doener]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Germany |- | [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy |- | style="background:#f6f0e0;" | [[User:Golgo|Golgo]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | |- | [[User:Irukard|Irukard]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Javila|Javila]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Brazil |- | [[User:kindjal|kindjal]] | Programmer | France, currently Italy |- | style="background:#f6f0e0;" | [[User:Kyokai|Kyokai]] | style="background:#f6f0e0;" | Game systems designer | style="background:#f6f0e0;" | |- | [[User:maci|maci]] | User support | Germany |- | style="background:#f6f0e0;" | [[User:Maester Pixel|Maester Pixel]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | USA |- | [[User:Magick|Magick]] | Musician | |- | style="background:#f6f0e0;" | [[User:Mkael|Mkael]] | style="background:#f6f0e0;" | Concept artist | style="background:#f6f0e0;" | Finland |- | [[User:Modanung|Modanung]] | Pixel artist | The Netherlands |- | style="background:#f6f0e0;" | [[User:Mra|Mra]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | |- | [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil |- | style="background:#f6f0e0;" | [[User:Nym|nym]] | style="background:#f6f0e0;" | Programmer | style="background:#f6f0e0;" | Australia |- | [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain |- | style="background:#f6f0e0;" | [[User:Rotonen|Rotonen]] | style="background:#f6f0e0;" | Head of art, story and music | style="background:#f6f0e0;" | Finland |- | [[User:Sora|Sora]] | Pixel artist | Poland |- | style="background:#f6f0e0;" | [[User:Sull|Sull]] | style="background:#f6f0e0;" | Pixel artist | style="background:#f6f0e0;" | Canada |- | [[User:Talaroc|Talaroc]] | Pixel artist | |- | style="background:#f6f0e0;" | [[User:Catfish_Man|Catfish_Man]] | style="background:#f6f0e0;" | Mac port | style="background:#f6f0e0;" | United States |- | [[User:Usiu|Usiu]] | Programmer | Poland |- | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | [[User:Platyna|Platyna]] | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Slackware package maintainer | style="border-bottom: 2px solid #efdead;background:#f6f0e0;" | Poland |} 81dyaupimzsvysei2nk67dj82yofhcd 3365 3350 2005-12-29T01:15:14Z Bjørn 3 Using templates for the rows 3365 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | Germany}} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | }} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} |} seum7vk5rodymo4fks64ewgcw1pxsfo 3366 3365 2005-12-29T01:20:01Z Bjørn 3 I don't know this, got filled in by accident 3366 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | }} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} |} 2x68hf7osghpd7u1wvj2wkkrhojiw4d 3370 3366 2005-12-29T13:35:33Z Bjørn 3 Mra is from Germany 3370 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} |} 15nv1mvhgud9q1q1wzjc7ml9yqwwuc0 3469 3370 2006-02-11T21:21:41Z Crush 103 added myself to the developer list 3469 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Crush]] | Pixel artist, programmer | Germany}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Demon|Demon]] | Pixel artist | }} {{dev2| [[User:deviexx|deviexx]] | Content manager | }} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Usiu|Usiu]] | Programmer | Poland}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} |} ojdm3u9nh1siy83dgogktmk9g95ttst 3470 3469 2006-02-12T04:34:29Z Tenche 39 3470 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Crush]] | Pixel artist, programmer | Germany}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Demon|Demon]] | Pixel artist | }} {{dev2| [[User:deviexx|deviexx]] | Content manager | }} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Usiu|Usiu]] | Programmer | Poland}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Tenche|Tenche]] | Graphic Designer, Pixel Artist | USA}} |} jm91wf93818mg7n79i1sdyai7p3ekjk 3472 3470 2006-02-12T11:07:47Z Modanung 8 Corrected to alphabetical order 3472 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tenche|Tenche]] | Graphic Designer, Pixel Artist | USA}} {{dev2| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 76rv0rwehqv7tgruc8h8esrtiv9sof0 3473 3472 2006-02-12T17:26:53Z Hackgrid 217 3473 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Tenche|Tenche]] | Graphic Designer, Pixel Artist | USA}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} mf3x3z6xrdcv0we19c0y0m21nphscmq 3478 3473 2006-02-12T19:04:51Z Modanung 8 Corrected the blabbering idiot's position. :) 3478 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Tenche|Tenche]] | Graphic Designer, Pixel Artist | USA}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 00l7b9moiysj52maxl3w1vymnkkog7a 3482 3478 2006-02-13T08:03:32Z ElvenProgrammer 11 As far as I know Tenche is not a developer 3482 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 6kqlbpweb6qp4liwclxmakt03z05od6 3634 3482 2006-03-10T16:10:25Z Kinetic 142 3634 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} r8vc5epogxyeh9biqfmaveff457tu6z 3792 3634 2006-03-13T21:58:25Z Crush 103 3792 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 92kb8uywjhoqe47ha7em0bmz2i7iqeu 3793 3792 2006-03-13T22:34:49Z Modanung 8 I do more 3793 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} hrsv8b6y8uxy2gq8qlz3m77t67tmlwv 3807 3793 2006-03-15T15:59:20Z Tuxtgz 317 3807 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} |} qd2tb9fir2bogrjo3qyghavtp7dwax8 3808 3807 2006-03-15T16:36:25Z Bjørn 3 List in lexical order 3808 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| [[User:Clef|Clef]] | Pixel artist | }} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Concept artist, writer | Spain}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 23x5ivcvbsbhgrohgkhoyv0kabd241o 4460 3808 2006-07-23T12:00:11Z Pajarico 5 Sepparated in active and retired 4460 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer|Germany}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} hgtkersxr75hkzfegjek5jwr73z8nmn 4711 4460 2006-08-20T13:06:43Z Bjørn 3 Added Pauan to list of developers 4711 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer|Germany}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} bq49x4szleuifr0sugtx47xlrbgmu27 4714 4711 2006-08-20T15:43:51Z Crush 103 ordered the developers list alphabetically 4714 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer|Germany}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} n1r2jh63ic9pcph6371h9bh7rm88trp 4715 4714 2006-08-20T15:45:12Z Crush 103 got confused because of matts wiki user name 4715 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer|Germany}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} bfs85adym58oimyox7bj2tovftqyq0c 4741 4715 2006-08-26T21:16:19Z Bjørn 3 Added silene the great programmer 4741 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:silene|silene]] | Programmer | France}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer|Germany}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} iuzws1fmqw1g5ijo2dt3t1lysaomy7m 4742 4741 2006-08-26T21:25:04Z Silene 423 Going with my real name 4742 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer|Germany}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="75px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="200px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 7h3ns82t5gfso5cxs9xzlfxn2hrzs5w 4744 4742 2006-08-26T21:43:16Z Bjørn 3 Might as well actually align the two tables then :-) 4744 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer|Germany}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 7dthfsxthklth5azj4sbbmjgz8cuawy 5111 4744 2006-09-22T13:28:11Z VictorSan 511 /* Active */ 5111 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 5y1gdrz5aitiobwzj72j3e8u9chruck 5594 5111 2006-12-15T01:50:09Z Paintballnsk 586 I would really like information on joining the programing and music team 5594 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:paintballnsk|paintballnsk]] | Programmer | USA}} {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} arzppaqw85uc5lzas13amth3k8wvajd 5595 5594 2006-12-15T18:20:28Z Crush 103 Revert: When you want to join the team please read the "joining the project" article. 5595 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} 5y1gdrz5aitiobwzj72j3e8u9chruck 5767 5595 2007-01-02T22:00:30Z Sixpointnine 590 /* Active */ 5767 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Sixpointnine|Sixpointnine]] | Pixel Artist | Unknown 0.o}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} c454cgahbxhm55cbj69f40xv666kmqh 5784 5767 2007-01-03T17:31:17Z Bjørn 3 Moved deviexx and Talaroc to retired 5784 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Sixpointnine|Sixpointnine]] | Pixel Artist | Unknown 0.o}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} jw9i82kani166cu6o96v5p3o64otlj3 5795 5784 2007-01-03T18:03:11Z Bjørn 3 Join the team first before you add yourself (talk to Elven or me if you're interested) 5795 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bear|Bear]] | Scripter | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} |} g3kpokzcga7hpkzvcj6j74d59spcibz 6012 5795 2007-02-07T21:03:04Z Bjørn 3 Moved Bear and nym to retired and added some people who were only mentioned on the About page 6012 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} 691tnd58g7bp6m8xob4w46nmh5yi7qr 6018 6012 2007-02-08T04:44:57Z Pauan 473 Let's not forget Dabe too. :P 6018 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Usiu]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} 7fru20gle3qvomjycahdbr7thfqd571 6163 6018 2007-03-01T10:25:22Z Usiu 10 /* Retired */ 6163 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} e7sbf0c4rq5unxk4el1khe7hr9luq2u 6164 6163 2007-03-01T10:25:45Z Usiu 10 /* Retired */ 6164 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} c79hylu7ogvr9hxhheqg5qijdmvw4tx 6165 6164 2007-03-01T13:39:02Z Crush 103 added avaniel and trapdoor to developers list 6165 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Avaniel|Avaniel]] | Programmer | }} {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer |}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} akzx7dg5rmrtdwdwyu3awr7558ijoeu 6166 6165 2007-03-01T14:29:29Z Avaniel 462 Modified the Avaniel entry 6166 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer |}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} jy6bvhcen6gn1i17w9unyk572srsx4s 6196 6166 2007-03-04T07:17:35Z Pauan 473 Added in AxlTrozz and modified my profile slightly. 6196 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer |}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} bn25j0vlvtcwcka7ylu68py2o9ogg2y 6268 6196 2007-03-07T17:19:54Z Bjørn 3 Filled in trapdoor's location 6268 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer, Debian package maintainer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} 51s7v4dprbmsq250q2z1d9shr3dtr8c 6285 6268 2007-03-09T18:25:26Z Bjørn 3 Added Patrick, our new Debian package maintainer 6285 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| kth5 (Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} pa3ohjg2feohquif91r8bckx5h52jnf 6329 6285 2007-03-21T11:45:30Z Bjørn 3 Added real name /* Retired */ 6329 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} m5cjusxnymerl2txw7k69w0uq64yzl1 6606 6329 2007-05-25T00:25:44Z Uppgames 724 /* Active */ 6606 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Av3nger|Av3nger]] | Pixel art,map creation and translations | Brazil}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} betoidn07i3iwv8jzqtxhd1ygxfv750 6627 6606 2007-05-25T12:20:21Z Crush 103 restored alphabetic order 6627 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art,map creation and translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} p1j4z3eivzjbrrjg120q2fqgyei4d7i 6628 6627 2007-05-25T15:49:49Z Uppgames 724 /* Active */ 6628 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel Art,Map Creation,Translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} b03jryan8oeuuoac1blfy6uzk7nz2t8 6630 6628 2007-05-27T00:36:20Z Yosuhara 324 6630 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel Art,Map Creation,Translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} 42v52kpszxkubczz33nkns4ndyd8cb2 6645 6630 2007-06-02T11:51:13Z Bjørn 3 Small adjustments 6645 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} td0x1ylglam37uinm80te501djg9ucu 7373 6645 2007-08-21T09:43:31Z JoshLangley 911 /* Retired */ 7373 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} e3o334nr13u752xfya3ordfbpz0hjmr 7374 7373 2007-08-21T09:45:59Z JoshLangley 911 /* Retired */ 7374 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} td0x1ylglam37uinm80te501djg9ucu 7375 7374 2007-08-21T09:46:41Z JoshLangley 911 /* Active */ 7375 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} amco7tw5t34lr0dh07hbsjov5yq53d7 7378 7375 2007-08-21T11:03:03Z Bjørn 3 Keeping it alphabetical was a good idea 7378 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} |} 8gu4fe0606f6a7na19mxbcr359rbamk 7572 7378 2007-09-11T00:23:23Z Crush 103 Josh Langley wrote on a bugtracker ticket: "I've lost motivation to work on this project for an undetermined amount of time, and I'm working on another project." 7572 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} e3o334nr13u752xfya3ordfbpz0hjmr 7589 7572 2007-09-17T06:51:03Z Len 640 /* Active */ 7589 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Len|Len]] | Pixel artist, concept artist | USA}} {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} bzvy3j286fdqpzs975q9m7pz17tub2e 7590 7589 2007-09-17T18:09:20Z Crush 103 please keep the alphabetic order 7590 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Len|Len]] | Pixel artist, concept artist | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} cw7pn1ogm7nk3ekgmj9rb669skhvgl8 7593 7590 2007-09-20T16:50:44Z Len 640 /* Active */ 7593 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Rotonen]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} 7rzvz5k0ksfj27a6yy1l0sc51locvz2 8512 7593 2008-01-18T00:29:01Z Rotonen 16 Added in my full name. 8512 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Irukard]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} bo8rhwsso8dcejeu7ryxd1or1hcq7u0 8520 8512 2008-01-20T13:30:18Z Irukard 32 Added my full name too :P 8520 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Crush]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} 4ueq26om0z4okhsce3vni756wb5jt6n 8521 8520 2008-01-20T13:32:55Z Crush 103 Following the recent real-name trend 8521 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} hcau228ih3w77hucsfs39hu94dpqas9 8816 8521 2008-02-26T12:35:34Z Len 640 /* Active */ 8816 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|Dabe]] | Story and Geography writer | }} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Webinterface-Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} 71omsx3vmihkgg85ba7sbdrg2060oj2 8825 8816 2008-02-27T09:30:01Z Dabe 333 added my full name and fixed Tuxtgz's title. 8825 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|ElvenProgrammer]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} pgq8lbqngulnrxnee82uys1hkt1aqtj 8829 8825 2008-02-27T11:49:09Z ElvenProgrammer 11 /* Active */ Filled in my full name 8829 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Axltrozz]] | Pixel artist | USA}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} djxdcfwavfzqkviyo7p8katqzjvtydo 8878 8829 2008-03-09T18:48:59Z Axltrozz 602 /* Active */ adding my real name 8878 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} 2y2aipk3kl75bb6bm1ohic9es4ijr6o 8944 8878 2008-04-01T05:56:12Z Len 640 /* Active */ 8944 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} 1ajs0cc03shj61n6x4913xkgi3cer31 8945 8944 2008-04-01T05:56:34Z Len 640 /* Retired */ 8945 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper | USA}} {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} 0a0yckyflj8tju9ud8h4dfe1j5vxhkn 8948 8945 2008-04-02T03:33:25Z Len 640 /* Retired */ 8948 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} hvwt3xivc5bjuntgo586r9w6ccsgzw5 8949 8948 2008-04-02T03:35:11Z Len 640 /* Active */ 8949 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of art(maybe)| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} |} 8d22cimf80ujyf9exd0rg6q57g71f53 8999 8949 2008-04-07T13:05:00Z Irukard 32 retired. 8999 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of art(maybe)| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} 5heatdlaw3jiu256qzhgh9e7sh5l1c5 9001 8999 2008-04-07T14:05:44Z Crush 103 restored colorisation. 9001 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of art(maybe)| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} tewfoo07fzcxpotik2irepwhp58k82o 9020 9001 2008-04-08T13:58:28Z QOAL 530 Adding myself 9020 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of art(maybe)| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:QOAL|Quiche_on_a_leash]] | Content implementation | England}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} bu7wr7656wu6ihutzed8yd3a4nm34mx 9109 9020 2008-04-14T12:21:34Z Peavey 1131 /* Active */ add myself as dev 9109 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of art(maybe)| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:peavey|peavey]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:QOAL|Quiche_on_a_leash]] | Content implementation | England}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} ip454ijtbuagnkipfkl3kogxs0y5jfq 9110 9109 2008-04-14T12:23:05Z Peavey 1131 /* Active */ add my name 9110 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of art(maybe)| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:QOAL|Quiche_on_a_leash]] | Content implementation | England}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} 2lxgpa4ibnyjhvafwf62a61k6cb4576 9175 9110 2008-04-19T23:26:09Z Len 640 /* Active */ 9175 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:QOAL|Quiche_on_a_leash]] | Content implementation | England}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} 9uzupx1mc4samt06e31l2q25mrc7hza 9194 9175 2008-04-22T07:48:35Z Bjørn 3 Fix whitespace 9194 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:QOAL|Quiche_on_a_leash]] | Content implementation | England}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} 8uvj1ja7w4leg21efw7hzyiewl1lka6 9590 9194 2008-06-07T21:37:34Z Zipon 25 /* Active */ 9590 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:QOAL|Quiche_on_a_leash]] | Content implementation | England}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev2| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} r3bcxydo0p5r41bt9mp5mzqz69mrgbv 9592 9590 2008-06-08T15:48:05Z Crush 103 fixed the colors 9592 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:QOAL|Quiche_on_a_leash]] | Content implementation | England}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} bhnowmhl77yf8ae7qr8jtcys2tg58l5 9973 9592 2008-08-25T17:40:04Z QOAL 530 9973 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev2| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} cqse7xtcq5ewybf7r8047ngy93fyvrm 10052 9973 2008-09-03T14:15:15Z Jaxad0127 999 add myself 10052 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} q6zjm8tle0ywrttkf8mywg9n40mg1kh 10080 10052 2008-09-08T18:54:44Z Vink 1127 /* Active */ 10080 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev1| [[User:Bertram|Bertram]] | Programmer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager, mapper, minor programming | USA}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Vink|Lena Andersson (Vink)]] | Content Manager | Sweden}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} 40j1e8sydibjs0fs552jf7c9dtmqq86 10083 10080 2008-09-10T17:59:31Z Vink 1127 /* Active */ 10083 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev1| [[User:Bertram|Bertram]] | Programmer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager, mapper, minor programming | USA}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Vink|Lena Andersson (Vink)]] | Part of Content Management Task Force | Sweden}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} is4oulj10whpvpslbf127f5l0qsr4vj 10084 10083 2008-09-10T18:03:43Z Jaxad0127 999 /* Active */ 10084 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev1| [[User:Bertram|Bertram]] | Programmer | France}} {{dev2| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Vink|Lena Andersson (Vink)]] | Part of Content Management Task Force | Sweden}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} npc1t18rf804fysxxdp6lf144r750h4 10213 10084 2008-09-20T08:33:27Z Kr0n05931 1273 Moved QOAL and Axltrozz to the retired section 10213 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:Vink|Lena Andersson (Vink)]] | Part of Content Management Task Force | Sweden}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev2| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev1| [http://forums.themanaworld.org/memberlist.php?mode=viewprofile&u=1823 Quiche_On_A_leash] | |}} |} 61j5iao3entqnqjony08xt5a04ws8wd 10214 10213 2008-09-20T08:36:57Z Kr0n05931 1273 /* Retired */ --fixed broken table 10214 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:Vink|Lena Andersson (Vink)]] | Part of Content Management Task Force | Sweden}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev2| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev1| Quiche_On_A_leash | Content Management |}} |} fd0hhx4tk5fb58bo4jole2sxtbnb0fx 10310 10214 2008-10-09T04:13:45Z Vink 1127 /* Active */ 10310 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev1| Quiche_On_A_leash | Content Management |}} |} p04spyuzi8rpltglxclfuroihsod2xq 10398 10310 2008-10-20T17:14:07Z Irukard 32 Am I back? 10398 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} 5eq9mbxm3v6r4hnxi94pnf6pte1a3ko 10529 10398 2008-10-31T23:49:43Z Kage 1313 /* Active */ 10529 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} odwiyybwr2ukg5abp5i2s13tf1j8i3p 10554 10529 2008-11-04T20:58:12Z Gekoudi 894 /* Retired */ 10554 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Telospanton | Fan, player of TMW | Greece }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} 5w22iavabr6vpfkikrwpbvuc50n7ca4 10555 10554 2008-11-04T21:06:14Z Fate 1137 Added myself 10555 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Telospanton | Fan, player of TMW | Greece }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} n09dbr00u0mqp3pofcdopm6w6849h2q 10559 10555 2008-11-04T21:14:40Z Gekoudi 894 /* Retired */ 10559 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| [[Telospanton]] | Fan, player of TMW | Greece }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} brjsckr2bfdwx7e2rrhtms8yydwdufg 10560 10559 2008-11-04T21:18:29Z Gekoudi 894 /* Retired */ 10560 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} plsxeuaxk1ruwuyx0nl373ywczp7y9z 10561 10560 2008-11-04T21:20:04Z Gekoudi 894 /* Active */ 10561 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[Telospanton]] | Fan, player of TMW | Greece }} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev2| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} q0l5xfd3h08lk7g2mm9jbnvsljmrgex 10565 10561 2008-11-04T22:11:35Z Crush2 1261 Revert: This is a list of developers who do something for TMW, not for players. 10565 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} plsxeuaxk1ruwuyx0nl373ywczp7y9z 10848 10565 2008-11-30T11:20:18Z Exceptionfault 1227 /* Active */ added myself 10848 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} {{dev2| Quiche_On_A_leash | Content Management |}} |} f98altpoviey9qls4fvkfjfsp4rlajz 10868 10848 2008-12-01T21:23:33Z Bjørn 3 Updated the list some 10868 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} 1ux2sur2kkqt6f7etjvfxyfldb0n3c5 11113 10868 2008-12-20T04:35:13Z CnachIract 1456 dronout 11113 wikitext text/x-wiki relercoo == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} mcgsunf2so6tgkvvvrvvcquustcs6dd 11149 11113 2008-12-20T20:53:36Z Crush2 1261 revert: spambot 11149 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} 1ux2sur2kkqt6f7etjvfxyfldb0n3c5 11179 11149 2008-12-24T23:25:24Z Len 640 /* Active */ 11179 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} osyrosfh1stz5m0gck6kg66iugjzv1k 11180 11179 2008-12-24T23:26:00Z Len 640 /* Retired */ 11180 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} grezu9pqp2a1azm9kaafn03ar62fahk 11181 11180 2008-12-24T23:26:39Z Len 640 /* Retired */ 11181 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} j1d016ehdz29d8fqpwp2xluzzeruf0q 11182 11181 2008-12-24T23:28:36Z Len 640 /* Retired */ 11182 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} iweproleuvu04buwokn8oa8oa1w5tuz 11183 11182 2008-12-24T23:59:21Z Len 640 /* Retired */ 11183 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} 8tx0v3hd83ctm7hnv2a6gkjh5g85i2x 11184 11183 2008-12-25T00:00:33Z Len 640 /* Active */ 11184 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} dt3qwt0yrfuzk0e1kbupbmurogzgr24 11195 11184 2008-12-28T09:48:53Z Len 640 /* Active */ 11195 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} 8tx0v3hd83ctm7hnv2a6gkjh5g85i2x 11196 11195 2008-12-28T09:49:25Z Len 640 /* Retired */ 11196 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} iweproleuvu04buwokn8oa8oa1w5tuz 11383 11196 2009-01-08T16:10:18Z CnachIract 1456 http://tacataca.strefa.pl/comment-1663.htm 11383 wikitext text/x-wiki [http://tacataca.strefa.pl/comment-1663.htm kal ho na ho full movie] [http://fispruil.qsh.eu/news388.html legend of dragoon video game] [http://relquaca.is-the-boss.com/20081228-advanced-office.html advanced office password recovery 3.02 cracks] [http://zelfibu.strefa.pl/zelhen-1284.html pamela anderson tommy lee video clip] [http://cnavieltz.strefa.pl/sitemap.htm url] == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} age0o3213spy4kltbls63on11ssd2kq 11444 11383 2009-01-08T16:39:42Z EJlol 294 Undo revision 11383 by [[Special:Contributions/CnachIract|CnachIract]] ([[User talk:CnachIract|Talk]]) 11444 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} iweproleuvu04buwokn8oa8oa1w5tuz 11456 11444 2009-01-09T10:40:03Z Bjørn 3 Fixed header size 11456 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Fate|Fate]] | Programmer (client, eAthena), Pixel artist | USA }} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} 6wph7cm7o4ynsqluoi1ty7vq75qz00k 11468 11456 2009-01-12T15:09:38Z Fate 1137 Removed myself from the list of active developers 11468 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev1| Gnulia | Concept artist | }} {{dev2| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev1| Igor Morgado (imorgado) | Tester | }} {{dev2| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev1| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev2| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev1| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev2| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev1| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev2| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev1| [[User:Magick|Magick]] | Musician | }} {{dev2| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev1| [[User:Mra|Mra]] | Programmer | Germany}} {{dev2| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev1| Neorice | Pixel artist | }} {{dev2| [[User:Nym|nym]] | Programmer | Australia}} {{dev1| Rodney Dawes (dobey) | Packager (install process) | }} {{dev2| Romulo Fernandes (razor85) | Artist | }} {{dev1| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev2| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev1| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev2| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev1| Ti Sing Hao | Musician | }} {{dev2| Ultramichy | Hosting | }} {{dev1| Vlady | Artist | }} {{dev2| zenogais (bitshift2002) | Programmer | }} {{dev1| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev2| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} 5igr2adu9uh7u3s4kfndwg6crmsv0y5 11469 11468 2009-01-12T15:11:18Z Fate 1137 Added myself to the list of retired developers 11469 wikitext text/x-wiki == Active == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} == Retired == {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Gagaofdeath|Andrej Sinicyn]] | Programmer | Germany}} {{dev2| [[User:Bear|Bear]] | Scripter | USA}} {{dev1| [[User:Catfish_Man|Catfish_Man]] | Mac port | USA}} {{dev2| Chetic | Mapper | }} {{dev1| [[User:Clef|Clef]] | Pixel artist | }} {{dev2| [[User:Demon|Demon]] | Pixel artist | }} {{dev1| [[User:deviexx|deviexx]] | Content manager | }} {{dev2| Fate | Content and eAthena developer | }} {{dev1| [[User:Golgo|Golgo]] | Pixel artist | }} {{dev2| Gnulia | Concept artist | }} {{dev1| [[User:Silene|Guillaume Melquiond (Silene)]] | Programmer | France}} {{dev2| Igor Morgado (imorgado) | Tester | }} {{dev1| [[User:Javila|Javila]] | Programmer | Brazil}} {{dev2| [[User:JoshLangley|JoshLangley]] | Client Programmer | Australia}} {{dev1| [[User:kindjal|kindjal]] | Programmer | France, currently Italy}} {{dev2| [[User:Kinetic|Kinetic]] | Pixel artist | USA}} {{dev1| Alexander Baldeck (kth5/Shura) | Programmer | }} {{dev2| [[User:Kyokai|Kyokai]] | Game systems designer | }} {{dev1| [[User:Maester Pixel|Maester Pixel]] | Pixel artist | USA}} {{dev2| [[User:Magick|Magick]] | Musician | }} {{dev1| [[User:Mkael|Mkael]] | Concept artist | Finland}} {{dev2| [[User:Mra|Mra]] | Programmer | Germany}} {{dev1| [[User:Neko-mon|Neko-mon]] | Pixel artist | Brazil}} {{dev2| Neorice | Pixel artist | }} {{dev1| [[User:Nym|nym]] | Programmer | Australia}} {{dev2| Rodney Dawes (dobey) | Packager (install process) | }} {{dev1| Romulo Fernandes (razor85) | Artist | }} {{dev2| Simon Edwardsson (simonedw/simedw) | Packager (Mac) | }} {{dev1| [[User:Sora|Sora]] | Pixel artist | Poland}} {{dev2| [[User:Sull|Sull]] | Pixel artist and hosting | Canada}} {{dev1| [[User:Talaroc|Talaroc]] | Pixel artist | }} {{dev2| Ti Sing Hao | Musician | }} {{dev1| Ultramichy | Hosting | }} {{dev2| Vlady | Artist | }} {{dev1| zenogais (bitshift2002) | Programmer | }} {{dev2| [[User:Len|L Pabin (len)]] | Pixel artist, concept artist, mapper, and Head of Pixellation| USA}} {{dev1| [[User:Axltrozz|Alex Argumedo (Axltrozz)]] | Pixel artist | USA, born in El Salvador}} |} ebeg14h1ntjl8s1vt2roqyo1o7x80s6 11718 11469 2009-02-21T02:06:04Z Kess 1128 I’m not sure which ones are considered to be main developers, so I’ll leave that for someone else; note that *everyone* is mentioned in [[Contributors]] 11718 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| Quiche_On_A_leash | Content Management |}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} 3qcs6mkov1mlzalhi5kmkc830daz4c8 11839 11718 2009-03-15T21:14:18Z QOAL 530 Tad more info for myself 11839 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] | Content Management | England}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} ldwqw96s9y6akrzbkg3sj1cvxncfz38 12096 11839 2009-05-12T19:41:38Z Blue112 1569 Added myself to the developers list. 12096 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Blue112|Blue Sans Douze (Blue112)]]| Programmer | Luxembourg}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev2| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev1| [[User:Doener|Doener]] | Programmer | Germany}} {{dev2| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] | Content Management | England}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} bsc05t95zsn6m7greipn1tt54uo4r8h 12097 12096 2009-05-12T20:59:47Z Crush2 1261 fixed colors 12097 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Blue112|Blue Sans Douze (Blue112)]]| Programmer | Luxembourg}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev1| [[User:maci|maci]] | User support | Germany}} {{dev2| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev1| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev2| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev1| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev2| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev1| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev2| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev1| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev2| [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] | Content Management | England}} {{dev1| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev2| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev1| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev2| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev1| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev2| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev1| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev2| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} dbv3g90y6b5eqoayg0el9jq53q45x7v 12965 12097 2009-08-12T08:54:39Z Freeyorp 1501 Added self 12965 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Blue112|Blue Sans Douze (Blue112)]]| Programmer | Luxembourg}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Freeyorp|Freeyorp]] | Programmer, minor pixel art | NZ}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content Manager Task Force member, mapper, minor programming | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] | Content Management | England}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} hwyx3a5ius7s8k8fprk4jrkyewi6e82 12967 12965 2009-08-12T15:18:45Z Jaxad0127 999 adjust my entry 12967 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Blue112|Blue Sans Douze (Blue112)]]| Programmer | Luxembourg}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Freeyorp|Freeyorp]] | Programmer, minor pixel art | NZ}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content manager, programming, mapper | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] | Content Management | England}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} kd2ktioippqlq2zc7351ye0bv2les5x 14697 12967 2010-01-16T15:32:59Z Guy111 1778 14697 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev2| [[User:Booth|Booth]] | Ideas for new ways to abuse | USA}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Blue112|Blue Sans Douze (Blue112)]]| Programmer | Luxembourg}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Freeyorp|Freeyorp]] | Programmer, minor pixel art | NZ}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content manager, programming, mapper | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] | Content Management | England}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} 1r5as6zaoeq7z9gi3bqrcu9wptld6gl 14703 14697 2010-01-16T15:56:55Z Crush 103 Undo revision 14697 by [[Special:Contributions/Guy111|Guy111]] ([[User talk:Guy111|Talk]]) revert: vandalism 14703 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Blue112|Blue Sans Douze (Blue112)]]| Programmer | Luxembourg}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Freeyorp|Freeyorp]] | Programmer, minor pixel art | NZ}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content manager, programming, mapper | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] | Content Management | England}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} kd2ktioippqlq2zc7351ye0bv2les5x 16141 14703 2010-11-22T04:10:17Z Hoogli 1124 16141 wikitext text/x-wiki The current main developers. See also the page listing all [[contributors]]. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev2| [[User:Exceptionfault|Andreas Habel (Exceptionfault)]] | Programmer | Germany}} {{dev1| [[User:Av3nger|Av3nger]] | Pixel art, map creation, translations | Brazil}} {{dev2| [[User:Bertram|Bertram]] | Programmer | France}} {{dev1| [[User:Bjørn|Bjørn Lindeijer]] | Lead Programmer | The Netherlands}} {{dev2| [[User:Blue112|Blue Sans Douze (Blue112)]]| Programmer | Luxembourg}} {{dev1| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev2| [[User:Crush|Philipp Sehmisch (Crush)]] | Pixel artist, mapper, programmer | Germany}} {{dev1| [[User:Dabe|David Del Re (Dabe)]] | Story and Geography writer | USA}} {{dev2| [[User:Doener|Doener]] | Programmer | Germany}} {{dev1| [[User:ElvenProgrammer|Eugenio Favalli (ElvenProgrammer)]] | Project leader, programmer | Italy}} {{dev2| [[User:Freeyorp|Freeyorp]] | Programmer, minor pixel art | NZ}} {{dev1| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Content manager, programming, mapper | USA}} {{dev2| [[User:maci|maci]] | User support | Germany}} {{dev1| [[User:hackgrid|Matt]] | Blabbering idiot | Germany}} {{dev2| [[User:Modanung|Modanung]] | Pixel artist, concept artist | The Netherlands}} {{dev1| [[User:Pajarico|Pajarico]] | Art, writer | Spain}} {{dev2| [[User:the-me|Patrick Matthäi]] | Debian package maintainer | Germany}} {{dev1| [[User:Pauan|Pauan]] | Graphics artist (painting, pixel art, interface design, etc.) | USA}} {{dev2| [[User:Peavey|Dennis Friis (peavey)]] | Programmer | Denmark}} {{dev1| [[User:Platyna|Platyna]] | Slackware package maintainer | Poland}} {{dev2| [[User:Avaniel|Rogier Polak (Avaniel)]] | Programmer | The Netherlands}} {{dev1| [[User:QOAL|Scott Ellis (Quiche_on_a_leash)]] | Content Management | England}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | Head of art, story and music | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist | Poland}} {{dev2| [[User:Trapdoor|trapdoor]] | Programmer | England}} {{dev1| [[User:Tuxtgz|Tuxtgz]] | Web-interface Programmer | Germany}} {{dev2| [[User:Usiu|Mateusz Kaduk (Usiu)]] | Programmer | Poland}} {{dev1| [[User:VictorSan|VictorSan]] | Programmer | Spain}} {{dev2| [[User:Yosuhara|Yosuhara]] | Pixel artist | Slovakia}} {{dev1| [[User:Zipon|Zipon]] | Mapper | Denmark}} |} [[Category:reference]] 9273mpefb0yocmythkihd098zj89z1u 17989 16141 2011-02-10T08:40:55Z Wombat 1239 started a developer archive and cleared page to be made new. 17989 wikitext text/x-wiki [[Developer Archive]] 9iboklomzcqszkzdl9scqf2iez9sgyg 17992 17989 2011-02-10T09:16:02Z Wombat 1239 updated list of developers 17992 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Wombat|Wombat]] | TMW-eA content leader | USA}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Freeyorp|Freeyorp]] | Server administrator, programmer, support | NZ}} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Server administrator, programmer, support | USA}} {{dev1| [[User:Platyna|Platyna]] | Server administrator, Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | TMW-eA content advisor, head of TMW CRs | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist, art advisor | Poland}} {{dev2| [[User:Salmondine|Salmondine]] | Pixel artist | USA}} {{dev1| [[User:Lien|Lien]] | Pixel artist, script writer | France}} {{dev2| [[User:Skipy|Skipy]] | Pixel artist | France}} {{dev1| [[User:Meway|Meway]] | Pixel artist | USA}} {{dev2| [[User:Poison_ivy|Enchilado]] | Pixel artist, script writer | NZ}} {{dev1| [[User:Saturn|Saturn]] | Sound | ???}} {{dev2| [[User:Alastrim|Alastrim]] | Script writer | ???}} {{dev1| [[User:Nmaligec|Nmaligec]] | Script writer, XML | USA}} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Script writer, mapping, programmer | Germany}} {{dev1| [[User:Cody_Martin|Cody Martin]] | Programmer, support | ???}} {{dev2| [[User:Jenalya|Jenalya ]] | Script writer, programmer | Germany}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | Sound | ???}} |} [[Category:reference]] ==See Also== [[Developer Archive]] 1bcorgltvvzxt112uo6r7hqm7jpkkz5 17996 17992 2011-02-10T11:09:51Z Alastrim 1776 17996 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Name ! style="background:#efdead;" width="200px" align="left" | Occupation ! style="background:#efdead;" width="150px" align="left" | Location {{dev1| [[User:Wombat|Wombat]] | TMW-eA content leader | USA}} {{dev2| [[User:Kage|Chuck Miller (Kage)]] | Programmer | USA}} {{dev1| [[User:Freeyorp|Freeyorp]] | Server administrator, programmer, support | NZ}} {{dev2| [[User:Jaxad0127|Jared Adams (Jaxad0127)]] | Server administrator, programmer, support | USA}} {{dev1| [[User:Platyna|Platyna]] | Server administrator, Slackware package maintainer | Poland}} {{dev2| [[User:Rotonen|Joni Orponen (Rotonen)]] | TMW-eA content advisor, head of TMW CRs | Finland}} {{dev1| [[User:Irukard|Krzysztof Daszuta (Irukard)]] | Pixel artist, art advisor | Poland}} {{dev2| [[User:Salmondine|Salmondine]] | Pixel artist | USA}} {{dev1| [[User:Lien|Lien]] | Pixel artist, script writer | France}} {{dev2| [[User:Skipy|Skipy]] | Pixel artist | France}} {{dev1| [[User:Meway|Meway]] | Pixel artist | USA}} {{dev2| [[User:Poison_ivy|Enchilado]] | Pixel artist, script writer | NZ}} {{dev1| [[User:Saturn|Saturn]] | Sound | ???}} {{dev2| [[User:Alastrim|Alastrim]] | Script writer | BR}} {{dev1| [[User:Nmaligec|Nmaligec]] | Script writer, XML | USA}} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Script writer, mapping, programmer | Germany}} {{dev1| [[User:Cody_Martin|Cody Martin]] | Programmer, support | ???}} {{dev2| [[User:Jenalya|Jenalya ]] | Script writer, programmer | Germany}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | Sound | ???}} |} [[Category:reference]] ==See Also== [[Developer Archive]] pk998wa2vfuu5jk72955piovic62pil 17998 17996 2011-02-10T12:54:50Z Freeyorp 1501 Split tmwAthena, tmw-manaserv, and other roles. Split usernames and names. Clarify ambiguous roles and include more roles. Add many tmw-manaserv developers. Unknown entries changes from ??? to - 17998 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | - }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | - | Scripting, Mapping, Programmer | - | IRC Channel Operator | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Merlin|merlin]] | - | - | Mapping | - | - }} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] rrc3tf5wiy8qprdv7cgwtmdo1qgjf4t 17999 17998 2011-02-10T13:22:50Z Argul 1858 adding PjotrOrials real name 17999 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | - }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | IRC Channel Operator | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Merlin|merlin]] | - | - | Mapping | - | - }} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] j9jf22w6u5eqq9qdlilc66d43q3rmiq 18000 17999 2011-02-10T13:40:21Z Argul 1858 18000 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | - }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Merlin|merlin]] | - | - | Mapping | - | - }} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] 827fna4vxkyhj19s01umzwf085ka5d2 18072 18000 2011-02-13T08:20:27Z Wombat 1239 Added Crush using archive information with tmw-ea updated role "advisor" and applying archived role to manaserv...may need further updates to get accurate. 18072 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | - }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Pixel artist, mapper, programmer | - | Germany}} {{dev2| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | - | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev1| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] f5of0bpdclvvolop26ccw1nflv779u5 18073 18072 2011-02-13T08:23:02Z Wombat 1239 added merlin's role in tmw-ea 18073 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | - }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Pixel artist, mapper, programmer | - | Germany}} {{dev2| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev1| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] l87wc9qb5u4jnjber54hascxx8oapil 18074 18073 2011-02-13T09:01:46Z Alige 1888 updated my country 18074 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Pixel artist, mapper, programmer | - | Germany}} {{dev2| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev1| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] fagshr6pva4o967xv3nfvo0qtpwhean 18077 18074 2011-02-14T09:05:20Z Crush 103 Sorry, but I don't intent to do any graphical or mapping work anymore, because my limited time for TMW has more value when I spend it on programming. 18077 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | programmer | - | Germany}} {{dev2| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev1| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] ofd1mpqpofevnqatppx12o6p3c41ouj 18078 18077 2011-02-14T09:06:41Z Crush 103 oh, but I do have time for forum moderation because I can do it at work during my breaks. 18078 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev2| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev1| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] ionam6moc31rxx6vgksg7hxqe2ig39e 18117 18078 2011-02-21T15:36:38Z Wombat 1239 Added Dark Mage to developer list 18117 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev2| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] r7erp1bbyp7wcbai99ht6edepq4956v 18119 18117 2011-02-21T15:47:39Z Alige 1888 I did big fixes in the french translations 18119 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop, Translations (French) | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev2| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | - | Pixel artist, Scripting | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] 5vamjna03odshag0kh98000eicm4ydn 18256 18119 2011-03-27T03:25:24Z Poison ivy 1529 Added my real name (actually, my last name and the initials of my second and third names). 18256 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop, Translations (French) | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev2| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | Pixel artist, Scripting | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] q20cnxwwxk9w7z87o3z9axymtrrnxlx 18267 18256 2011-04-02T17:30:10Z Blue112 1569 18267 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | - | Wiki Sysop, Translations (French) | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev2| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | Pixel artist, Scripting | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] mt06s2ca6x6ty97fpr3t4y4dw0b07h6 18455 18267 2011-05-02T16:06:08Z Alige 1888 18455 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | - | Content, Mapping | Wiki Sysop, Translations (French) | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev2| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | Pixel artist, Scripting | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] ati7ahy7be95l2dqysrtedahk7r0juj 18469 18455 2011-05-05T16:35:52Z Alige 1888 updated me and added o11c and reorganised colors 18469 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11C]] | - | Programmer | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | France}} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} |} [[Category:reference]] ==See Also== [[Developer Archive]] rp19ftsm786ye67kojjpf6vel1phu3z 18565 18469 2011-05-22T17:13:47Z Alige 1888 added yubaba to the team 18565 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11C]] | - | Programmer | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | Sound Lead | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]] ew6rpnzk5b908uhm2jivg9aq0a3azch 18624 18565 2011-05-30T17:37:44Z O11c 2047 Fix accidental capitalization 18624 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | BR }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | - | Programmer | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | Sound Lead | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]] 4ay3i3vmgod685piab0pe93fm07fjqk 18820 18624 2011-06-26T23:46:40Z Alastrim 1776 18820 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | Pixel artist, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Head Smasher1|Head Smasher1]] | - | Sound | - | - | - }} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | Art advisor | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | - | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Merlin|merlin]] | - | Tilesets | Mapping | - | - }} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | - | Programmer | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | Sound | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | Sound Lead | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]] qli7vcldoa3b4fe4rbvbqmax3x0vciv 18920 18820 2011-07-10T06:40:41Z Wombat 1239 tmwa content developer and related updates to list 18920 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | Art Director, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | Scripting, Programmer | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | - | Programmer | - | - | USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | Sound Lead | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]] jr8aselfywboj9l7s7uhfvp5at5pvwl 18953 18920 2011-07-17T03:11:21Z Hal9000 2105 18953 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | Art Director, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | Scripting, Programmer | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | - | Programmer | - | - | USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | Content Lead | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | Sound Lead | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]] 0rd5kruetr0l40sbwpuy0ipz2l1a2su 19200 18953 2011-08-05T11:40:02Z Wombat 1239 19200 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | Art Director, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | Scripting, Programmer | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | - | Programmer | - | - | USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | Leader | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | Sound Lead | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]] sb3ca5n7vt7rb24l1h3tncd2oug3mwu 19445 19200 2011-08-09T18:50:39Z O11c 2047 Update my entry a bit 19445 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | Scripting | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | Scripting, Mapping, Programmer | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | Art Director, Scripting | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | Scripting, Programmer | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | Scripting, Programmer | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | Source Lead | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | Pixel artist | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | Leader | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | Sound Lead | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]] i12cn6jncst1p5jyph8v41iuadt0xqc 19880 19445 2011-08-30T04:54:51Z O11c 2047 Make the board noticeable 19880 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]] jcfoeubuyqcv9um28t0rq0yjvtnf6x6 19894 19880 2011-08-31T21:43:34Z Alige 1888 added a link to project and teams 19894 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - |Scripting | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] jx3k41d8atq5htp0lsgyxtwaux6pvhr 20174 19894 2011-09-18T13:51:15Z Alige 1888 Added XML to Dark_Mage 20174 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | - }} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] l9t5wdc25qcth2g3tkb3msql5mzk82d 20604 20174 2011-09-25T17:43:39Z Alige 1888 Added Yubaba's country. 20604 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | - | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] rp62dwyr6i0zz74lhojagfyytub9e0d 21183 20604 2011-10-01T09:45:46Z Salmondine 1679 added real name to user salmondine 21183 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | - | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] jqeqyn4pcx810yj33aprkogml3wm2li 21613 21183 2011-10-16T13:17:42Z Irukard 32 21613 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish) | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] pfspcp35qmeybz8vwvyi8tkg5ubq5vq 22574 21613 2011-11-06T23:15:32Z Salmondine 1679 added lizandra to list and moved some dev1 and dev2 tags for consistancy 22574 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Content, Mapping, Translations (French) | - | Wiki Sysop, Mantis Administrator | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish) | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | - | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] lnxopuhazjmxgg02j3m7kyp8kqkyqwp 22575 22574 2011-11-06T23:22:34Z Alige 1888 Updated my line. 22575 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | {{Board|Map Lead}} | - | Wiki SysOp | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish) | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | - | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] nxbdl7tnmo1edusfv2n34ek4tcsp3jz 22576 22575 2011-11-06T23:24:35Z Salmondine 1679 Lizandra requested real name added. 22576 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | {{Board|Map Lead}} | - | Wiki SysOp | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish) | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] 6uyxl6jrcexmkedeeyxhe7rwc7hsbtz 22883 22576 2011-11-19T07:10:43Z Irukard 32 22883 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | {{Board|Map Lead}} | - | Wiki SysOp | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] h214ugqjf10myzka2lzop2pto90l4al 23058 22883 2011-12-12T22:51:16Z Alige 1888 Updated own activites. 23058 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Map Lead, XML Lead, Pixel Artist, Scripting | - | Wiki SysOp | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] 05rzh0l0pz6rlkav61rjbjyl3pen4b9 23171 23058 2012-01-02T20:52:27Z Alige 1888 removed self 23171 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev2| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] qqy6upctm5jcriuaim2afonqaibdzkm 23218 23171 2012-01-04T16:06:27Z Alige 1888 Reverted edits by [[Special:Contributions/Ali-G|Ali-G]] ([[User talk:Ali-G|talk]]) to last revision by [[User:Irukard|Irukard]] 23218 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | {{Board|Map Lead}} | - | Wiki SysOp | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] h214ugqjf10myzka2lzop2pto90l4al 23307 23218 2012-01-30T22:18:20Z Alige 1888 Undo revision 23218 by [[Special:Contributions/Ali-G|Ali-G]] ([[User talk:Ali-G|talk]]) Removed self. 23307 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev2| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== [[Developer Archive]]<br />[[Projects and Teams]] qqy6upctm5jcriuaim2afonqaibdzkm 23420 23307 2012-02-07T18:21:14Z Alige 1888 added a link to the contributors page 23420 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev2| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | - }} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] noji38d6z74xo3b70nuqsknho9r12a7 23561 23420 2012-02-25T23:18:26Z Alige 1888 small edits 23561 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Ali-G|Ali-G]] | - | Wiki Admin | - | - | France }} {{dev1| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev2| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev1| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev2| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev1| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev2| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev1| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev2| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev1| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev1| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev2| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev1| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev2| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev1| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev2| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev1| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev2| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev1| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev2| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev1| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev2| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev1| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev2| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev1| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev2| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev1| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev2| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev1| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev2| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev1| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev2| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev1| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] svixwf6m79gn3g860ol9st873icb02y 23983 23561 2012-07-09T21:46:29Z Alige 1888 removed self 23983 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev2| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] 4tni06r5p4y62zc12zzle3artd9jkw5 24407 23983 2012-09-05T20:08:03Z Rodrigo 2213 24407 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Rodrigo|Pluto]] | Arian Asimi | - | - | Translations (Shqip) | Kosova}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] 4jeh9u283vu4ja92hu08c6tuhe6eyjl 24431 24407 2012-09-08T11:56:58Z Rodrigo 2213 24431 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Rodrigo|Pluto]] | Arian Asimi | Pixel artist | Pixel artist | Translations (Shqip) | Kosova}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] ofe4idmo1bpdzcflxrc6xdvmucc2s70 24445 24431 2012-09-08T20:36:28Z Jenalya 1876 Update my role 24445 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev2| [[User:Rodrigo|Pluto]] | Arian Asimi | Pixel artist | Pixel artist | Translations (Shqip) | Kosova}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Content Lead, Scripting}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] rgxieg61t3b09wze3vaanf86mf27frg 24475 24445 2012-09-13T11:38:18Z Nard 1877 24475 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | - | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] 932f8mww169de5bsdmaonq4c3xk8h9r 24880 24475 2012-11-14T13:30:23Z Meway 1474 Added my name 24880 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | Andrew Hall | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] l50250tapjhmxw2tro8t1cij94adouh 25674 24880 2013-02-19T11:27:55Z Yubaba 2094 25674 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | Andrew Hall | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | Server and Network Administrator, IRC Network Administrator, Forums Administrator | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead, Mapping}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] m7vpxusvd2tqsq4xwu2uyexy5ajzy69 26446 25674 2013-05-28T03:42:54Z O11c 2047 remove Platyna's roles. There are many other problems with this page, but that was the worst 26446 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | Andrew Hall | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | - | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead, Mapping}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] 23iosds5h1tozbufmfzt29w8znxih5p 26666 26446 2013-06-15T16:16:04Z Nard 1877 26666 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | {{Board|Client development, Programmer}} | - | - | Russia }} {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | Andrew Hall | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | - | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead, Mapping}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] essinbp0ivcl1hqmtwjgyihu87mevq1 27089 26666 2013-07-01T19:43:15Z Jaxad0127 999 Jaxad0127 moved page [[Developers]] to [[Dev:Developers]] 27089 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | {{Board|Client development, Programmer}} | - | - | Russia }} {{dev1| [[User:Alastrim|Alastrim]] | - | {{Board|Scripting}} | - | - | Brasil }} {{dev2| [[User:Argul|Argul (PjotrOrial) ]] | Stefan Beller | {{Board|Scripting, Mapping, Programmer}} | - | - | Germany}} {{dev1| [[User:Axltrozz|Axltrozz]] | - | - | Tileset and Mapping | IRC Channel Operator | - }} {{dev2| [[User:bcs|bcs]] | - | - | Pixel art | - | - }} {{dev1| [[User:Bertram|Bertram]] | Yohann Ferreira | - | - | dev.themanaworld.org services administrator, IRC Channel Operator, Programmer | France}} {{dev2| [[User:Black_Don|Black Don]] | - | - | Pixel Artist | - | - }} {{dev1| [[User:Blue112|BlueSoul]] | - | - | Programmer | - | - }} {{dev2| [[User:Cody_Martin|Cody]] | Cody Martin | - | - | IRC Channel Operator, Programmer | - }} {{dev1| [[User:Crush|Crush]] | Philipp Sehmisch | Advisor | Programmer | Forum Moderator | Germany}} {{dev3| [[User:Dark_Mage|Dark Mage]] | - | Scripting, XML | - | Translations (Russian) | Russia}} {{dev1| [[User:Poison_ivy|Enchilado]] | W E Sayers | {{Board|Art Director, Scripting}} | - | - | Australia}} {{dev2| [[User:Feline Monstrocity|Feline Monstrocity]]| - | - | Soundscape | - | Wales, UK }} {{dev1| [[User:Freeyorp|Freeyorp]] | - | - | Balance, Mechanics and Systems Lead | server.themanaworld.org and testing.themanaworld.org Services Administrator, IRC Services Administrator, Forums Administrator, Programmer | NZ}} {{dev2| [[User:Hal9000|Hal9000]] | Francesco Miglietta | Pixel Artist | - | - | Italy}} {{dev1| [[User:Irukard|Irukard]] | Krzysztof Daszuta | - | Pixel Artist | Translations (Polish), Facebook Community Page Maintainer | Poland}} {{dev2| [[User:Ivan|Ivan]] | Ivan Morve | - | Pixel Artist | - | - }} {{dev1| [[User:Jaxad0127|Jaxad0127]] | Jared Adams | - | - | server.themanaworld.org and testing.themanaworld.org Services Administrator, Website Services Administrator, IRC Channel Administrator, Forums Administrator, Wiki Sysop and Bureaucrat, Mantis Administrator, Programmer | USA}} {{dev2| [[User:John_Pyle|John P]] | John Pyle | - | Story Lead | - | - }} {{dev1| [[User:Jenalya|Jenalya]] | - | {{Board|Scripting, Programmer}} | - | - | Germany}} {{dev2| [[User:Kage|Kage]] | Chuck Miller | {{Board|Scripting, Programmer}} | - | IRC Channel Operator, Forums Global Moderator, Programmer | USA}} {{dev1| [[User:krazyjakee|krazyjakee]] | - | - | Soundscape | - | - }} {{dev2| [[User:Lien|Lien]] | - | Pixel artist, Scripting | - | - | France}} {{dev1| [[User:Lizandra|Lizandra]] | Filipa Serra e Silva | Pixel artist | - | - | Portugal}} {{dev2| [[User:Hackgrid|Matt]] | - | - | - | Blabbering idiot | Germany}} {{dev1| [[User:Meway|Meway]] | Andrew Hall | Pixel artist | Pixel Artist | - | USA}} {{dev2| [[User:Nmaligec|Nmaligec]] | - | Scripting, XML | - | - | USA}} {{dev1| [[User:o11c|o11c]] | Ben Longbons | {{Board|Source Lead}} | - | - | Western USA}} {{dev2| [[User:Platyna|Platyna]] | Zuzanna K. Filutowska | - | - | - | Poland}} {{dev1| [[User:Rotonen|Rotonen]] | Joni Orponen | Advisor | Project Lead | IRC Channel Administrator, Forums Administrator | Finland}} {{dev2| [[User:Salmondine|Salmondine]] | Mark Dunbar | Pixel artist | - | - | USA}} {{dev1| [[User:Saturn|Saturn]] | - | - | Soundscape Lead | - | - }} {{dev2| [[User:Skipy|Skipy]] | - | {{Board|Pixel artist}} | - | - | USA}} {{dev1| [[User:Wombat|Wombat]] | - | {{Board|Leader}} | - | IRC Channel Operator, Forums Global Moderator, Mantis Administrator | USA}} {{dev2| [[User:Yubaba|Yubaba]] | - | {{Board|Sound Lead, Mapping}} | - | - | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] essinbp0ivcl1hqmtwjgyihu87mevq1 28302 27089 2013-09-25T13:11:49Z Tux 2198 28302 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting | - | - | - }} {{dev1| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev2| Straelyn | - | Pixel Arts, Scripting, Coding | - | - | - }} {{dev1| [[User:tux|tux9th]] | - | Mapping Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:V0id|V0id]] | Vincent Petithory | Mapping, Scripting, Programming, Pixel Arts| - | - | France}} {{dev1| Wushin | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev2| [[User:Yubaba|Yubaba]] | - | - | - | {{Board|Sound Lead}} | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] 5ir2z38rs4eoc30dwyj6zd3kboh5szl 28316 28302 2013-09-27T20:25:01Z Yubaba 2094 28316 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting | - | - | - }} {{dev1| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev2| Straelyn | - | Pixel Arts, Scripting, Coding | - | - | - }} {{dev1| [[User:tux|tux9th]] | - | Mapping Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:V0id|V0id]] | Vincent Petithory | Mapping, Scripting, Programming, Pixel Arts| - | - | France}} {{dev1| Wushin | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev2| [[User:Yubaba|Yubaba]] | Mapping, SFX, Soundscape | - | - | {{Board|Sound Lead}} | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] 74qzodct9wq4mjvzkbpi5wfi7qp3msc 28317 28316 2013-09-27T20:25:45Z Yubaba 2094 28317 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting | - | - | - }} {{dev1| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev2| Straelyn | - | Pixel Arts, Scripting, Coding | - | - | - }} {{dev1| [[User:tux|tux9th]] | - | Mapping Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:V0id|V0id]] | Vincent Petithory | Mapping, Scripting, Programming, Pixel Arts| - | - | France}} {{dev1| Wushin | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev2| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] tv8ax3q69q5heuaj1oi91f07s8rm2p6 28825 28317 2013-11-15T11:54:40Z Cassy 2265 adding links to user pages 28825 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting | - | - | - }} {{dev1| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev2| [[User:Straelyn|Straelyn]] | - | Pixel Arts, Scripting, Coding | - | - | - }} {{dev1| [[User:tux|tux9th]] | - | Mapping Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:V0id|V0id]] | Vincent Petithory | Mapping, Scripting, Programming, Pixel Arts| - | - | France}} {{dev1| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev2| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] ppea7edazkxsqeak7bwvy6xkmi4ooh1 29309 28825 2014-02-17T10:21:50Z Cassy 2265 deleting Straelyn as he quit dev'ing and playing, adding Chay 29309 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:V0id|V0id]] | Vincent Petithory | Mapping, Scripting, Programming, Pixel Arts| - | - | France}} {{dev1| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev2| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] rri39sunzrc4jm9w96lzt1w00bmcwo5 29310 29309 2014-02-17T10:22:45Z Cassy 2265 29310 wikitext text/x-wiki {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:V0id|V0id]] | Vincent Petithory | Mapping, Scripting, Programming, Pixel Arts| - | - | France}} {{dev1| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev2| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} [[Category:reference]] ==See Also== * [[Projects and Teams]] * [[Developer Archive]] * [[Contributors]] dw012gtppyb00anbazxry9ccn6vvxqi 29478 29310 2014-02-26T13:57:21Z Cassy 2265 updating with additional information like links to Trello 29478 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:V0id|V0id]] | Vincent Petithory | Mapping, Scripting, Programming, Pixel Arts| - | - | France}} {{dev1| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev2| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] gl79mf6wztmjfp8sefcy7m0dxmubny1 29486 29478 2014-02-27T06:57:28Z Cassy 2265 deleted V0id, already added to [[Contributors]] and [[Developer Archive]] 29486 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev1| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] ir5agiese238bnaig3swn2h6inrgy9z 29566 29486 2014-02-28T08:42:21Z Cassy 2265 /* Recent projects */ small grammar mistake 29566 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev1| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] 1zm13789rjdqp5fzcqvjvsb8znw9upb 29708 29566 2014-03-03T12:41:49Z Cassy 2265 adding [[Dev:Main]] and [[Joining the project]] under "see also" 29708 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | - }} {{dev1| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] 0g61eial46memve6y1kwz9qbpo1zjld 29760 29708 2014-03-06T04:37:58Z Wushin 2233 /* Developers */ 29760 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] dpt7qornhe7wyoq1y82g7qbzczv7wd4 29781 29760 2014-03-06T18:38:52Z Yubaba 2094 29781 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:Wushin|Wushin]] | - | Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] aqcidolef8u21lybl5dl04jqcltiw1s 29796 29781 2014-03-08T21:06:25Z Wushin 2233 /* Developers */ 29796 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Chayenne|Chay (Bernhardt)]] | - | Pixel Arts, Scripting, Mapping | - | - | - }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] 5hbxdtx40nyvfzvr5pbtohh13tsko2m 29797 29796 2014-03-08T21:06:44Z Chayenne 2288 removed chayenne 29797 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev2| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] eiyhetw1p0hi0dltaa746fctwklhxi9 29813 29797 2014-03-11T10:48:45Z Chayenne 2288 fixed colors 29813 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev2| [[User:tux|tux9th]] | - | Mapping, Scripting | - | {{Board|Content Lead}} | -}} {{dev1| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev2| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] kydcadqemamqmz71eclm2g6kolmo2ya 29966 29813 2014-03-28T07:49:07Z Cassy 2265 deleting tux9th as he resigned today - see https://forums.themanaworld.org/viewtopic.php?f=12&t=18177 ... 29966 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev2| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] a2r0q67vayjq7spwg4djyywhx48cgtc 30956 29966 2014-07-03T20:23:37Z Wushin 2233 /* Developers */ 30956 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev2| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | ? }} {{dev1| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev2| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] 4vwwx2usl5tga6erpm8m46dochek67k 31106 30956 2014-07-27T05:08:51Z Gumi 2315 /* Developers */ 31106 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev2| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev1| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev2| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] iv103qbtzuj93t41ivovyvcssrlszts 31107 31106 2014-07-27T05:10:57Z Gumi 2315 /* Developers */ update list color 31107 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev2| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] 2xn95dnznnsoc6ddulqfzfhegv4lc1d 31839 31107 2014-12-17T16:17:38Z Wushin 2233 /* categorizing */ 31839 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev2| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] [[Category:Development]] o87gpzuf6knozulpy52b5ag5rmqyah9 32357 31839 2015-01-19T09:04:15Z Cassy 2265 added license.txt in the "See also" 32357 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev2| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on Trello, an organisation platform with a very clearly arranged interface that makes it comfortable to work with. TMW has an own group on Trello which includes so called "Boards". In those boards you can find several "Cards" - each card stands for a bigger or smaller project, like for example a card for a new big quest in the Content Development Board or a card for just a small icon of a new monster drop. You can click at a card to see the progress of it. At the right side of a each board you can see the most recent changes and therefore the things being recently worked on. Relevant links: * [https://trello.com/themanaworld TMW Organisation] * [https://trello.com/b/ojhvZu1f/content-development Content Development Board] * [https://trello.com/b/rNnx513z/art-development Art Development Board] [[Category:reference]] [[Category:Projects]] [[Category:Development]] 8g7gku5s64w4niwj6mm6da6ief786fl 32358 32357 2015-01-19T09:59:58Z Cassy 2265 Replacing Trello with the forums for development organization 32358 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev2| [[User:o11c|o11c]] | Ben Longbons | tmwA Server programming, Scripting | - | {{Board|Source Lead}} | Western USA}} {{dev1| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev2| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:reference]] [[Category:Projects]] [[Category:Development]] lt03v1dsu57lu5kqj3oeffhr945kwxn 32574 32358 2015-02-07T02:56:36Z Wushin 2233 /* updated for o11c's resignation */ 32574 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev1| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev2| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:reference]] [[Category:Projects]] [[Category:Development]] qnizblsho2vzut5a4hp7pfv7mtq4pj4 32584 32574 2015-02-09T10:34:16Z Cassy 2265 minor style correction 32584 wikitext text/x-wiki ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:reference]] [[Category:Projects]] [[Category:Development]] p5hv93bgkhao4h0bx5w2ghlhgum95su 33679 32584 2015-03-11T07:23:36Z Cassy 2265 adding templates, removing categories 33679 wikitext text/x-wiki {{Template:Metakey}} {{Template:Metadesc}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] s165n2v5oq9r4pw9uipzi37z3hzh568 38411 33679 2015-08-03T22:02:09Z Mpslinux 2406 38411 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | tmwAthena roles ! style="background:#edfead;" width="170px" align="left" | tmw-manaserv roles ! style="background:#efdead;" width="170px" align="left" | Other roles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development, programming | - | - | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | - | Germany }} {{dev1| [[User:Meko|Meko]] | - | Mapping, Scripting | - | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwA Server programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] 6wq96o3jqv2489hydtbav026v5dpz0k 39736 38411 2015-10-24T00:25:00Z Gumi 2315 /* Developers */ 39736 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | Roles ! style="background:#edfead;" width="170px" align="left" | Active projects ! style="background:#efdead;" width="170px" align="left" | Titles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development | - | {{Board|Client Lead}} | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | - | {{Board|Wiki Admin}} | Germany }} {{dev1| [[User:Meko|Meko (Gumi)]] | - | tmwAthena programming, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3] | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwAthena programming, Pixel Arts, Mapping, Scripting | - | {{Board|Content Lead, Server Admin}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] bx1hdxmqba768dty7k596l0r4zqod0b 39737 39736 2015-10-24T00:37:09Z Gumi 2315 /* Developers */ 39737 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | Roles ! style="background:#edfead;" width="170px" align="left" | Active project(s) ! style="background:#efdead;" width="170px" align="left" | Titles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development | [https://manaplus.org/ ManaPlus] | {{Board|Client Lead}} | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | [[User:Cassy|Witch Cult Quest]] | {{Board|Wiki Admin}} | Germany }} {{dev1| [[User:Meko|Meko (Gumi)]] | - | tmwAthena programming, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Elements, Races | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwAthena programming, Pixel Arts, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Professions | {{Board|TMWA Lead, Content Lead, Server Admin}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] 1t3v3u517dc0d4tcmbt4uknugasy091 39949 39737 2015-11-23T21:28:50Z Wushin 2233 /* Add Nami Back as active */ 39949 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | Roles ! style="background:#edfead;" width="170px" align="left" | Active project(s) ! style="background:#efdead;" width="170px" align="left" | Titles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development | [https://manaplus.org/ ManaPlus] | {{Board|Client Lead}} | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | [[User:Cassy|Witch Cult Quest]] | {{Board|Wiki Admin}} | Germany }} {{dev1| [[User:Meko|Meko (Gumi)]] | - | tmwAthena programming, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Elements, Races | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwAthena programming, Pixel Arts, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Professions | {{Board|TMWA Lead, Content Lead, Server Admin}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} {{dev1| [[User:Nami|Nami]] | - | Art Director | - | Art Leand | UK}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] 3wraukqncsic0c5iqkwxpbopisqvkmp 39950 39949 2015-11-23T21:29:35Z Wushin 2233 /* Wushin can't spell */ 39950 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | Roles ! style="background:#edfead;" width="170px" align="left" | Active project(s) ! style="background:#efdead;" width="170px" align="left" | Titles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development | [https://manaplus.org/ ManaPlus] | {{Board|Client Lead}} | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | [[User:Cassy|Witch Cult Quest]] | {{Board|Wiki Admin}} | Germany }} {{dev1| [[User:Meko|Meko (Gumi)]] | - | tmwAthena programming, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Elements, Races | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwAthena programming, Pixel Arts, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Professions | {{Board|TMWA Lead, Content Lead, Server Admin}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} {{dev1| [[User:Nami|Nami]] | - | Art Director | - | Art Lead | UK}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] ll8ret9dsh69utyfuhfdcwg7d1kx579 39951 39950 2015-11-24T01:14:54Z Gumi 2315 styling 39951 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | Roles ! style="background:#edfead;" width="170px" align="left" | Active project(s) ! style="background:#efdead;" width="170px" align="left" | Titles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development | [https://manaplus.org/ ManaPlus] | {{Board|Client Lead}} | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | [[User:Cassy|Witch Cult Quest]] | {{Board|Wiki Admin}} | Germany }} {{dev1| [[User:Meko|Meko (Gumi)]] | - | tmwAthena programming, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Elements, Races | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwAthena programming, Pixel Arts, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Professions | {{Board|TMWA Lead, Content Lead, Server Admin}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} {{dev2| [[User:Nami|Nami]] | - | Art Director | - | {{Board|Art Lead}} | UK}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] jdrnk8zjz3vhczkg4vbw133fsdunmfy 40602 39951 2016-08-05T20:04:34Z Gumi 2315 40602 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | Roles ! style="background:#edfead;" width="170px" align="left" | Active project(s) ! style="background:#efdead;" width="170px" align="left" | Titles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:4144|4144]] | - | Client development | [https://manaplus.org/ ManaPlus] | {{Board|Client Lead}} | - }} {{dev2| [[User:Cassy|Cassy]] | - | Pixel Arts, Scripting, Mapping | [[User:Cassy|Witch Cult Quest]] | {{Board|Wiki Admin}} | Germany }} {{dev1| [[User:Meko|Gumi]] | - | tmwAthena programming, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Elements, Races | - | Canada }} {{dev2| [[User:Wushin|Wushin]] | - | tmwAthena programming, Pixel Arts, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Professions | {{Board|TMWA Lead, Content Lead, Server Admin}} | Midwest US }} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Sound Lead}} | Canada}} {{dev2| [[User:Nami|Nami]] | - | Art Director | - | {{Board|Art Lead}} | UK}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] g0hhzwadqtkxpke7eof5gzqv9i8e7mw 40709 40602 2016-09-25T13:37:32Z WildX 1896 Updated list 40709 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== The list below shows the active developers who are working on TMW's content or server. {| border="0" cellspacing="0" cellpadding="5" width="100%" style="border-bottom: 2px solid #efdead" ! style="background:#efdead;" width="150px" align="left" | Username(s) ! style="background:#edfead;" width="100px" align="left" | Name ! style="background:#efdead;" width="170px" align="left" | Roles ! style="background:#edfead;" width="170px" align="left" | Active project(s) ! style="background:#efdead;" width="170px" align="left" | Titles ! style="background:#edfead;" width="150px" align="left" | Location {{dev1| [[User:Reid|Reid]] | - | Pixel Art, Scripting, Mapping, Concepts | [[User:Reid|Aurora 1.1]] | {{Board|Senior Developer}} | France }} {{dev2| [[User:Wushin|Wushin]] | - | Server administration, programming, Pixel Art, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Professions | {{Board|Senior Developer}} | Midwest US }} {{dev1| [[User:4144|4144]] | - | Client development | [https://manaplus.org/ ManaPlus] | {{Board|Senior Developer}} | Russia }} {{dev2| [[User:Alige|Alige]] | - | Pixel Art, Mapping, Scripting | - | {{Board|Developer}} | France}} {{dev1| [[User:Yubaba|Yubaba (Chicka-Maria)]] | - | Mapping, Soundscape design, SFX | - | {{Board|Developer}} | Canada}} {{dev2| [[User:Ledmitz|Ledmitz]] | - | Soundscape design, SFX | - | {{Board|Developer}} | - }} {{dev1| [[User:Meko|Gumi]] | - | Programming, Mapping, Scripting | [https://github.com/mekolat/tmwa/tree/magic-v3 magic-v3], Elements, Races | {{Board|Developer}} | Canada }} {{dev2| [[User:Omatt|Omatt]] | - | Scripting | - | {{Board|Developer}} | France}} |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] kjvw2sizbjvyd0ohsdrlp89jwcdix87 40712 40709 2016-09-25T15:09:45Z WildX 1896 WIP 40712 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== {| class="wikitable" |+ The Mana World Team members ! Username(s) ! Titles ! Roles ! Location |- ! Reid | Senior Developer || Pixel Art, Scripting, Mapping, Concepts || France |- ! Wushin | Senior Developer || Server Administration, Programming, Pixel Art, Mapping, Scripting || USA (Midwest) |- ! 4144 | Senior Developer || Client Development, Server Administration || Russia |- ! Alige | Developer || Pixel Art, Mapping, Scripting || France |- ! Chicka-Maria (Yubaba) | Developer || Music & SFX, Mapping || Canada |- ! Ledmitz | Developer || SFX || - |- ! Gumi (Mekolat, Meko) | Developer || Programming, Scripting, Mapping || Canada |- ! Omatt | Developer || Scripting || France |- ! WildX | Game Master || GM, Forum Admin, Community Manager, Lore Writing || United Kingdom |- ! MrGrey | Game Master || GM, Eye candy || Canada |- ! Prsm | Game Master || GM || Canada |- ! Veryape | Game Master || GM, Server Admin || Sweden |- !NitayandaGM | Game Master || GM || Israel |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] qbh1k2f0ypoh5yy09jk2azvy9l3wogh 40713 40712 2016-09-25T15:27:30Z WildX 1896 /* Developers */ 40713 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== {| class="wikitable" |+ The Mana World Team members ! Username(s) ! Titles ! Roles ! Location |- ! Reid | Senior Developer || Pixel Art, Scripting, Mapping, Concepts || France |- ! Wushin | Senior Developer || Server Administrator, Programming, Pixel Art, Mapping, Scripting || USA (Midwest) |- ! 4144 | Senior Developer || Client Development, Server Administrator || Russia |- ! Alige | Developer || Pixel Art, Mapping, Scripting || France |- ! Chicka-Maria (Yubaba) | Developer || Music & SFX, Mapping || Canada |- ! Ledmitz | Developer || SFX || - |- ! Gumi (Mekolat, Meko) | Developer || Programming, Scripting, Mapping || Canada |- ! Omatt | Developer || Scripting || France |- ! WildX | Game Master || GM, Forum Admin, Community Manager, Lore Writing || United Kingdom |- ! MrGrey | Game Master || GM, ''Eye candy'' || Canada |- ! Prsm | Game Master || GM || Canada |- ! Veryape | Game Master || GM, Server Administrator || Sweden |- !NitayandaGM | Game Master || GM || Israel |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] 28a6lbqxotwd6orbpm8t207xxtm371i 40721 40713 2016-09-26T11:27:35Z WildX 1896 /* Developers */ 40721 wikitext text/x-wiki {{Meta}} {{Category_playerinfo}} ==Developers== {| class="wikitable" |+ The Mana World Team members ! Username(s) ! Titles ! Roles ! Location |- ! Reid | Senior Developer || Pixel Art, Scripting, Mapping, Concepts || France |- ! Wushin | Senior Developer || Server Administrator, Programming, Pixel Art, Mapping, Scripting || USA (Midwest) |- ! 4144 | Senior Developer || Client Development, Server Administrator || - |- ! Alige | Developer || Pixel Art, Mapping, Scripting || France |- ! Chicka-Maria (Yubaba) | Developer || Music & SFX, Mapping || Canada |- ! Ledmitz | Developer || SFX || Canada |- ! Gumi (Mekolat, Meko) | Developer || Programming, Scripting, Mapping || Canada |- ! Omatt | Developer || Scripting || France |- ! WildX | Game Master || GM, Forum Admin, Community Manager, Lore Writing || United Kingdom |- ! MrGrey | Game Master || GM, ''Eye candy'' || Canada |- ! Prsm | Game Master || GM || Canada |- ! Veryape | Game Master || GM, Server Administrator || Sweden |- !NitayandaGM | Game Master || GM || Israel |} '''See also:''' * [[Developer Archive]] * [[Contributors]] * [https://github.com/themanaworld/tmwa-client-data/blob/master/license.txt Graphic authors and contributors (license.txt)] * [[Dev:Main|Development Home]] * [[Joining the project]] ==Recent projects== Most of TMW's development is shown on the forum, [https://forums.themanaworld.org/viewforum.php?f=2 subforum Development TMW]. In the past most development was done in Trello. There are still many cards there. Relevant links: [https://trello.com/themanaworld TMW Organisation], [https://trello.com/b/ojhvZu1f/content-development Content Development Board], [https://trello.com/b/rNnx513z/art-development Art Development Board]. The development organization was switched back to the forums because players rather check the forums than Trello. [[Category:Development]] fj15po9j7iqo1135jv1989kq8gdtzzw 46103 40721 2019-10-09T13:33:59Z Jesusalva 2520 Redirect to TMW Team page 2/2 46103 wikitext text/x-wiki #REDIRECT [[TMW Team]] diezkzm82vthgm4wo7dlulypuggqix0 59476 46103 2024-03-27T03:56:43Z Move page script 2739 Move page script moved page [[Dev:Developers]] to [[Development:Developers]]: Rename Dev: to Development: so the miraheze import works 46103 wikitext text/x-wiki #REDIRECT [[TMW Team]] diezkzm82vthgm4wo7dlulypuggqix0 0 8163 33311 2015-03-06T14:28:08Z Alexanderlime 2382 Alexanderlime moved page [[Dev:Evol-Hercules atcommands]] to [[User:Alexanderlime/Evol-Hercules atcommands]]: Moved the page after getting meko's advice 33311 wikitext text/x-wiki #REDIRECT [[User:Alexanderlime/Evol-Hercules atcommands]] 2xn083f2mp5t2tlzx30dkogfe4mo8t2 33313 33311 2015-03-06T14:29:56Z Gumi 2315 Blanked the page 33313 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 33314 33313 2015-03-06T14:30:09Z Gumi 2315 Redirected page to [[User:Alexanderlime/Evol-Hercules atcommands]] 33314 wikitext text/x-wiki #REDIRECT [[User:Alexanderlime/Evol-Hercules atcommands]] 2xn083f2mp5t2tlzx30dkogfe4mo8t2 59478 33314 2024-03-27T03:56:43Z Move page script 2739 Move page script moved page [[Dev:Evol-Hercules atcommands]] to [[Development:Evol-Hercules atcommands]]: Rename Dev: to Development: so the miraheze import works 33314 wikitext text/x-wiki #REDIRECT [[User:Alexanderlime/Evol-Hercules atcommands]] 2xn083f2mp5t2tlzx30dkogfe4mo8t2 0 8162 33308 2015-03-06T14:26:32Z Alexanderlime 2382 Alexanderlime moved page [[Dev:Evol-Hercules server]] to [[User:Alexanderlime/Evol-Hercules server]]: Decided to move it under my page after getting meko's advice 33308 wikitext text/x-wiki #REDIRECT [[User:Alexanderlime/Evol-Hercules server]] k5mp1xor7hx4ywh2icun9hnvrpf1cbe 59480 33308 2024-03-27T03:56:43Z Move page script 2739 Move page script moved page [[Dev:Evol-Hercules server]] to [[Development:Evol-Hercules server]]: Rename Dev: to Development: so the miraheze import works 33308 wikitext text/x-wiki #REDIRECT [[User:Alexanderlime/Evol-Hercules server]] k5mp1xor7hx4ywh2icun9hnvrpf1cbe 0 12384 50485 2020-01-24T02:50:36Z Jesusalva 2520 Jesusalva moved page [[Dev:GM Commands]] to [[Legacy:GM Commands]]: The GM commands for both servers differ and I can see someone tried to update with new server and didn't finish. Result, broken page. Move for sanity. 50485 wikitext text/x-wiki #REDIRECT [[Legacy:GM Commands]] hy09x57nk9r3kg7nhh41nm2ks67y3id 56934 50485 2022-12-08T02:59:00Z Jesusalva 2520 Text replacement - "Legacy" to "Classic" 56934 wikitext text/x-wiki #REDIRECT [[Classic:GM Commands]] pm7n9ti8gz17a7amgt1q3xmfhdnkyeq 59482 56934 2024-03-27T03:56:43Z Move page script 2739 Move page script moved page [[Dev:GM Commands]] to [[Development:GM Commands]]: Rename Dev: to Development: so the miraheze import works 56934 wikitext text/x-wiki #REDIRECT [[Classic:GM Commands]] pm7n9ti8gz17a7amgt1q3xmfhdnkyeq 0 10080 40523 2016-05-04T17:13:07Z Gumi 2315 Created page with "<table> <tr><th>Aliases</th><th>Anchor</th></tr> <tr><td>hurnscald, hurns, hurn</td><td>009-1, 55, 37</td></tr> <tr><td>nivalis, niv</td><td>020-1, 74, 83</td></tr> <tr><td>tu..." 40523 wikitext text/x-wiki <table> <tr><th>Aliases</th><th>Anchor</th></tr> <tr><td>hurnscald, hurns, hurn</td><td>009-1, 55, 37</td></tr> <tr><td>nivalis, niv</td><td>020-1, 74, 83</td></tr> <tr><td>tulimshar, tulim, tul</td><td>001-1, 64, 101</td></tr> <tr><td>candor, newbington, noob</td><td>029-1, 52, 93</td></tr> <tr><td>oldwizard, wizard, oldwiz</td><td>013-1, 41, 92</td></tr> jdcycy40t1we8ua0p5bo4g6nrptoju6 40524 40523 2016-05-04T17:19:45Z Gumi 2315 40524 wikitext text/x-wiki <table> <tr><th>Aliases</th><th>Anchor</th></tr> <tr><td>hurnscald, hurns, hurn</td><td>009-1, 55, 37</td></tr> <tr><td>nivalis, niv</td><td>020-1, 74, 83</td></tr> <tr><td>tulimshar, tulim, tul</td><td>001-1, 64, 101</td></tr> <tr><td>candor, newbington, noob</td><td>029-1, 52, 93</td></tr> <tr><td>asphodel, swamp, swampvillage, undeadtown</td><td>026-1, 32, 33</td></tr> <tr><td>oldwizard, wizard, oldwiz</td><td>013-1, 41, 92</td></tr> <tr><td>desert, pachua</td><td>006-1, 34, 99</td></tr> <tr><td>forest, katze</td><td>015-1, 58, 35</td></tr> <tr><td>dimondscove, dimond</td><td>010-2, 31, 39</td></tr> <tr><td>graveyard, gy</td><td>027-1, 71, 87</td></tr> 4qvc2dg1izg8p7iiozbk7jbsz2d424l 40525 40524 2016-05-04T17:27:09Z Gumi 2315 40525 wikitext text/x-wiki <table> <tr><th>Aliases</th><th>Anchor</th></tr> <tr><td>hurnscald, hurns, hurn</td><td>009-1, 55, 37</td></tr> <tr><td>nivalis, niv</td><td>020-1, 74, 83</td></tr> <tr><td>tulimshar, tulim, tul</td><td>001-1, 64, 101</td></tr> <tr><td>candor, newbington, noob</td><td>029-1, 52, 93</td></tr> <tr><td>asphodel, swamp, swampvillage, undeadtown</td><td>026-1, 32, 33</td></tr> <tr><td>oldwizard, wizard, oldwiz</td><td>013-1, 41, 92</td></tr> <tr><td>desert, pachua</td><td>006-1, 34, 99</td></tr> <tr><td>forest, katze</td><td>015-1, 58, 35</td></tr> <tr><td>dimondscove, dimond</td><td>010-2, 31, 39</td></tr> <tr><td>graveyard, gy</td><td>027-1, 71, 87</td></tr> <tr><td>generalkrukan, krukan</td><td>027-6, 39, 47</td></tr> <tr><td>generalrazha, razha</td><td>027-7, 39, 35</td></tr> <tr><td>generalterogan, terogan</td><td>027-8, 39, 52</td></tr> <tr><td>gmisland, eventisland, easterisland, island</td><td>028-1, 99, 40</td></tr> <tr><td>auditorium, scene</td><td>028-1, 119, 69</td></tr> <tr><td>theater</td><td>017-2, 26, 23</td></tr> <tr><td>gmlounge, lounge, backstage, gm</td><td>017-9, 26, 23</td></tr> <tr><td>cindycave, cindy</td><td>031-3, 47, 26</td></tr> <tr><td>terranite, terracave, terra</td><td>012-3, 448, 65</td></tr> <tr><td>terranitesafe, terrasafe, safeterra</td><td>012-4, 473, 184</td></tr> 1drmlklruaxslvciwl840vkzsywjqe1 40526 40525 2016-05-04T17:38:49Z Gumi 2315 40526 wikitext text/x-wiki It is now possible to use map aliases instead of map names. <br><br> == Anchors == <table> <tr><th>Aliases</th><th>Anchor</th></tr> <tr><td>hurnscald, hurns, hurn</td><td>009-1, 55, 37</td></tr> <tr><td>nivalis, niv</td><td>020-1, 74, 83</td></tr> <tr><td>tulimshar, tulim, tul</td><td>001-1, 64, 101</td></tr> <tr><td>candor, newbington, noob</td><td>029-1, 52, 93</td></tr> <tr><td>asphodel, swamp, swampvillage, undeadtown</td><td>026-1, 32, 33</td></tr> <tr><td>oldwizard, wizard, oldwiz</td><td>013-1, 41, 92</td></tr> <tr><td>desert, pachua</td><td>006-1, 34, 99</td></tr> <tr><td>forest, katze</td><td>015-1, 58, 35</td></tr> <tr><td>dimondscove, dimond</td><td>010-2, 31, 39</td></tr> <tr><td>graveyard, gy</td><td>027-1, 71, 87</td></tr> <tr><td>generalkrukan, krukan</td><td>027-6, 39, 47</td></tr> <tr><td>generalrazha, razha</td><td>027-7, 39, 35</td></tr> <tr><td>generalterogan, terogan</td><td>027-8, 39, 52</td></tr> <tr><td>gmisland, eventisland, easterisland, island</td><td>028-1, 99, 40</td></tr> <tr><td>auditorium, scene</td><td>028-1, 119, 69</td></tr> <tr><td>theater</td><td>017-2, 26, 23</td></tr> <tr><td>gmlounge, lounge, backstage, gm</td><td>017-9, 26, 23</td></tr> <tr><td>cindycave, cindy</td><td>031-3, 47, 26</td></tr> <tr><td>terranite, terracave, terra</td><td>012-3, 448, 65</td></tr> <tr><td>terranitesafe, terrasafe, safeterra</td><td>012-4, 473, 184</td></tr> <tr><td>bluesage, blue</td><td>048-2, 40, 46</td></tr> <tr><td>xmasinn, xmas</td><td>030-2, 85, 46</td></tr> <tr><td>barbarians, fluffy</td><td>033-1, 71, 33</td></tr> <tr><td>park, porttown, farms</td><td>057-1, 100, 77</td></tr> <tr><td>hills, orum</td><td>017-1, 112, 49</td></tr> <tr><td>batcave, bat</td><td>011-3, 30, 26</td></tr> </table> <br><br> == Examples == <table> <tr><th>Command</th><th>Behaviour</th></tr> <tr><td>@warp 009-1</td><td>warps you to 009-1, at a random (x,y) location</td></tr> <tr><td>@warp hurnscald</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@warp 009-1 55 37</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@warp hurnscald 55 37</td><td>warps you to 009-1, at (55,37)</td></tr> </table> lh9tq1hkvf6jy2h6qlk115ow3nhjfob 40527 40526 2016-05-04T17:41:58Z Gumi 2315 /* Examples */ 40527 wikitext text/x-wiki It is now possible to use map aliases instead of map names. <br><br> == Anchors == <table> <tr><th>Aliases</th><th>Anchor</th></tr> <tr><td>hurnscald, hurns, hurn</td><td>009-1, 55, 37</td></tr> <tr><td>nivalis, niv</td><td>020-1, 74, 83</td></tr> <tr><td>tulimshar, tulim, tul</td><td>001-1, 64, 101</td></tr> <tr><td>candor, newbington, noob</td><td>029-1, 52, 93</td></tr> <tr><td>asphodel, swamp, swampvillage, undeadtown</td><td>026-1, 32, 33</td></tr> <tr><td>oldwizard, wizard, oldwiz</td><td>013-1, 41, 92</td></tr> <tr><td>desert, pachua</td><td>006-1, 34, 99</td></tr> <tr><td>forest, katze</td><td>015-1, 58, 35</td></tr> <tr><td>dimondscove, dimond</td><td>010-2, 31, 39</td></tr> <tr><td>graveyard, gy</td><td>027-1, 71, 87</td></tr> <tr><td>generalkrukan, krukan</td><td>027-6, 39, 47</td></tr> <tr><td>generalrazha, razha</td><td>027-7, 39, 35</td></tr> <tr><td>generalterogan, terogan</td><td>027-8, 39, 52</td></tr> <tr><td>gmisland, eventisland, easterisland, island</td><td>028-1, 99, 40</td></tr> <tr><td>auditorium, scene</td><td>028-1, 119, 69</td></tr> <tr><td>theater</td><td>017-2, 26, 23</td></tr> <tr><td>gmlounge, lounge, backstage, gm</td><td>017-9, 26, 23</td></tr> <tr><td>cindycave, cindy</td><td>031-3, 47, 26</td></tr> <tr><td>terranite, terracave, terra</td><td>012-3, 448, 65</td></tr> <tr><td>terranitesafe, terrasafe, safeterra</td><td>012-4, 473, 184</td></tr> <tr><td>bluesage, blue</td><td>048-2, 40, 46</td></tr> <tr><td>xmasinn, xmas</td><td>030-2, 85, 46</td></tr> <tr><td>barbarians, fluffy</td><td>033-1, 71, 33</td></tr> <tr><td>park, porttown, farms</td><td>057-1, 100, 77</td></tr> <tr><td>hills, orum</td><td>017-1, 112, 49</td></tr> <tr><td>batcave, bat</td><td>011-3, 30, 26</td></tr> </table> <br><br> == Examples == <table> <tr><th>Command</th><th>Behaviour</th></tr> <tr><td>@warp 009-1</td><td>warps you to 009-1, at a random (x,y) location</td></tr> <tr><td>@warp hurnscald</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@warp 009-1 55 37</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@warp hurnscald 55 37</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@charwarp 009-1 PLAYER</td><td>warps PLAYER to 009-1, at a random (x,y) location</td></tr> <tr><td>@charwarp hurnscald PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> <tr><td>@charwarp 009-1 55 37 PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> <tr><td>@charwarp hurnscald 55 37 PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> </table> When using anchors, you can either use the predefined (x,y) or specify your own. If you use a map name instead (ie 009-1) then you must specify the (x,y), or else a random position is chosen. 24engsoass2dzl21rv7xfimlql6pjwg 40528 40527 2016-05-04T17:42:32Z Gumi 2315 /* Examples */ 40528 wikitext text/x-wiki It is now possible to use map aliases instead of map names. <br><br> == Anchors == <table> <tr><th>Aliases</th><th>Anchor</th></tr> <tr><td>hurnscald, hurns, hurn</td><td>009-1, 55, 37</td></tr> <tr><td>nivalis, niv</td><td>020-1, 74, 83</td></tr> <tr><td>tulimshar, tulim, tul</td><td>001-1, 64, 101</td></tr> <tr><td>candor, newbington, noob</td><td>029-1, 52, 93</td></tr> <tr><td>asphodel, swamp, swampvillage, undeadtown</td><td>026-1, 32, 33</td></tr> <tr><td>oldwizard, wizard, oldwiz</td><td>013-1, 41, 92</td></tr> <tr><td>desert, pachua</td><td>006-1, 34, 99</td></tr> <tr><td>forest, katze</td><td>015-1, 58, 35</td></tr> <tr><td>dimondscove, dimond</td><td>010-2, 31, 39</td></tr> <tr><td>graveyard, gy</td><td>027-1, 71, 87</td></tr> <tr><td>generalkrukan, krukan</td><td>027-6, 39, 47</td></tr> <tr><td>generalrazha, razha</td><td>027-7, 39, 35</td></tr> <tr><td>generalterogan, terogan</td><td>027-8, 39, 52</td></tr> <tr><td>gmisland, eventisland, easterisland, island</td><td>028-1, 99, 40</td></tr> <tr><td>auditorium, scene</td><td>028-1, 119, 69</td></tr> <tr><td>theater</td><td>017-2, 26, 23</td></tr> <tr><td>gmlounge, lounge, backstage, gm</td><td>017-9, 26, 23</td></tr> <tr><td>cindycave, cindy</td><td>031-3, 47, 26</td></tr> <tr><td>terranite, terracave, terra</td><td>012-3, 448, 65</td></tr> <tr><td>terranitesafe, terrasafe, safeterra</td><td>012-4, 473, 184</td></tr> <tr><td>bluesage, blue</td><td>048-2, 40, 46</td></tr> <tr><td>xmasinn, xmas</td><td>030-2, 85, 46</td></tr> <tr><td>barbarians, fluffy</td><td>033-1, 71, 33</td></tr> <tr><td>park, porttown, farms</td><td>057-1, 100, 77</td></tr> <tr><td>hills, orum</td><td>017-1, 112, 49</td></tr> <tr><td>batcave, bat</td><td>011-3, 30, 26</td></tr> </table> <br><br> == Examples == <table> <tr><th>Command</th><th>Behaviour</th></tr> <tr><td>@warp 009-1</td><td>warps you to 009-1, at a random (x,y) location</td></tr> <tr><td>@warp hurnscald</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@warp 009-1 55 37</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@warp hurnscald 55 37</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@charwarp 009-1 PLAYER</td><td>warps PLAYER to 009-1, at a random (x,y) location</td></tr> <tr><td>@charwarp hurnscald PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> <tr><td>@charwarp 009-1 55 37 PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> <tr><td>@charwarp hurnscald 55 37 PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> </table> When using anchors (ie "hurnscald"), you can either use the predefined (x,y) or specify your own. If you use a map name instead (ie "009-1") then you must specify the (x,y), or else a random position is chosen. 4d5jnompqq0d8vbi0rtgb85kofkcz41 59484 40528 2024-03-27T03:56:43Z Move page script 2739 Move page script moved page [[Dev:GM Commands/anchors]] to [[Development:GM Commands/anchors]]: Rename Dev: to Development: so the miraheze import works 40528 wikitext text/x-wiki It is now possible to use map aliases instead of map names. <br><br> == Anchors == <table> <tr><th>Aliases</th><th>Anchor</th></tr> <tr><td>hurnscald, hurns, hurn</td><td>009-1, 55, 37</td></tr> <tr><td>nivalis, niv</td><td>020-1, 74, 83</td></tr> <tr><td>tulimshar, tulim, tul</td><td>001-1, 64, 101</td></tr> <tr><td>candor, newbington, noob</td><td>029-1, 52, 93</td></tr> <tr><td>asphodel, swamp, swampvillage, undeadtown</td><td>026-1, 32, 33</td></tr> <tr><td>oldwizard, wizard, oldwiz</td><td>013-1, 41, 92</td></tr> <tr><td>desert, pachua</td><td>006-1, 34, 99</td></tr> <tr><td>forest, katze</td><td>015-1, 58, 35</td></tr> <tr><td>dimondscove, dimond</td><td>010-2, 31, 39</td></tr> <tr><td>graveyard, gy</td><td>027-1, 71, 87</td></tr> <tr><td>generalkrukan, krukan</td><td>027-6, 39, 47</td></tr> <tr><td>generalrazha, razha</td><td>027-7, 39, 35</td></tr> <tr><td>generalterogan, terogan</td><td>027-8, 39, 52</td></tr> <tr><td>gmisland, eventisland, easterisland, island</td><td>028-1, 99, 40</td></tr> <tr><td>auditorium, scene</td><td>028-1, 119, 69</td></tr> <tr><td>theater</td><td>017-2, 26, 23</td></tr> <tr><td>gmlounge, lounge, backstage, gm</td><td>017-9, 26, 23</td></tr> <tr><td>cindycave, cindy</td><td>031-3, 47, 26</td></tr> <tr><td>terranite, terracave, terra</td><td>012-3, 448, 65</td></tr> <tr><td>terranitesafe, terrasafe, safeterra</td><td>012-4, 473, 184</td></tr> <tr><td>bluesage, blue</td><td>048-2, 40, 46</td></tr> <tr><td>xmasinn, xmas</td><td>030-2, 85, 46</td></tr> <tr><td>barbarians, fluffy</td><td>033-1, 71, 33</td></tr> <tr><td>park, porttown, farms</td><td>057-1, 100, 77</td></tr> <tr><td>hills, orum</td><td>017-1, 112, 49</td></tr> <tr><td>batcave, bat</td><td>011-3, 30, 26</td></tr> </table> <br><br> == Examples == <table> <tr><th>Command</th><th>Behaviour</th></tr> <tr><td>@warp 009-1</td><td>warps you to 009-1, at a random (x,y) location</td></tr> <tr><td>@warp hurnscald</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@warp 009-1 55 37</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@warp hurnscald 55 37</td><td>warps you to 009-1, at (55,37)</td></tr> <tr><td>@charwarp 009-1 PLAYER</td><td>warps PLAYER to 009-1, at a random (x,y) location</td></tr> <tr><td>@charwarp hurnscald PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> <tr><td>@charwarp 009-1 55 37 PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> <tr><td>@charwarp hurnscald 55 37 PLAYER</td><td>warps PLAYER to 009-1, at (55,37)</td></tr> </table> When using anchors (ie "hurnscald"), you can either use the predefined (x,y) or specify your own. If you use a map name instead (ie "009-1") then you must specify the (x,y), or else a random position is chosen. 4d5jnompqq0d8vbi0rtgb85kofkcz41 0 12383 50468 2020-01-22T02:36:17Z Jesusalva 2520 Not complete but meh 50468 wikitext text/x-wiki {{I18n}} <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== ====rEvolt Server==== Pertaining to The Mana World: rEvolt. =====Player pages===== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====Recent Game Updates===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. <br><br> ====Wiki Admin pages==== =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well. *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] s8xr8dck84tinbpd1f83evtpnq8k3au 50469 50468 2020-01-22T02:37:23Z Jesusalva 2520 Translating this a fool's errand 50469 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== ====rEvolt Server==== Pertaining to The Mana World: rEvolt. =====Player pages===== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====Recent Game Updates===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. <br><br> ====Wiki Admin pages==== =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well. *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] m8nh9abxm1n6hj4720qoafyld8c8xa4 50470 50469 2020-01-22T02:40:23Z Jesusalva 2520 Remove some sections which would be too hard to maintain 50470 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well. *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 5u8vcimflpyewx689rbda5epr6o2053 50472 50470 2020-01-22T02:46:38Z Jesusalva 2520 Working with Git Issues 50472 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well. *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] ryh9b8tn2egcbdcrjl4v6r3weqol727 50473 50472 2020-01-22T02:48:52Z Jesusalva 2520 Dev:Testing_Server 50473 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well. *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] mc85lhljrjq7ebyv0zl5s3lbu7bg7i4 50474 50473 2020-01-22T03:02:42Z Jesusalva 2520 kytty's list 50474 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== * [[Legacy:Hamond]] * [[Legacy:Thurstan]] * [[Legacy:Wolfgang]] * [[Legacy:Nicholas]] * [[Legacy:Tondor]] * [[Legacy:Hurnscald_Booksheld]] * [[Legacy:Luca]] * [[Legacy:Miriam]] <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well. *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] g5fqub60m0rvs16wfgpyu4ts3jiz8w2 50475 50474 2020-01-22T03:04:42Z Jesusalva 2520 50475 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== * [[Legacy:Hamond]] * [[Legacy:Thurstan]] * [[Legacy:Wolfgang]] * [[Legacy:Nicholas]] * [[Legacy:Tondor]] * [[Legacy:Hurnscald_Booksheld]] * [[Legacy:Luca]] * [[Legacy:Miriam]] <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well. *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set. -- Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] s2xf8fjx44v9nmsx1x2afv9c9vck7hm 50476 50475 2020-01-22T03:08:33Z Jesusalva 2520 At least two extensions are already available (sort of) 50476 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== * [[Legacy:Hamond]] * [[Legacy:Thurstan]] * [[Legacy:Wolfgang]] * [[Legacy:Nicholas]] * [[Legacy:Tondor]] * [[Legacy:Hurnscald_Booksheld]] * [[Legacy:Luca]] * [[Legacy:Miriam]] <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] i5hpp3cmep4430evnv7wogmut0kp587 51493 50476 2020-06-26T10:16:22Z EJlol 294 /* General tasks */ 51493 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, leave a link on the banner about Legacy page, in case player is looking for TMW:Legacy information. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. ::Many NPCs are listed as a quest. They should be recategorized as NPC instead, and if they really contain a quest, they should be split and/or moved. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== * [[Legacy:Hamond]] * [[Legacy:Thurstan]] * [[Legacy:Wolfgang]] * [[Legacy:Nicholas]] * [[Legacy:Tondor]] * [[Legacy:Hurnscald_Booksheld]] * [[Legacy:Luca]] * [[Legacy:Miriam]] <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] e7hgeyd9e2219dsz8xp69eiqbbjv39t 51918 51493 2020-07-14T18:48:26Z Jesusalva 2520 /* Namespace Issues - Mention new {{Disambiguation}}, subject to EJlol's renaming */ 51918 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. ::Many NPCs are listed as a quest. They should be recategorized as NPC instead, and if they really contain a quest, they should be split and/or moved. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== * [[Legacy:Hamond]] * [[Legacy:Thurstan]] * [[Legacy:Wolfgang]] * [[Legacy:Nicholas]] * [[Legacy:Tondor]] * [[Legacy:Hurnscald_Booksheld]] * [[Legacy:Luca]] * [[Legacy:Miriam]] <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] hjrk7oputcu97mvzyzku9ei0bnde0ay 51991 51918 2020-07-17T13:39:03Z EJlol 294 /* Wiki Content */ Add link to page where you can see all the pages with notes 51991 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written, and Information about [[Legacy:Walkthrough]] (Including Category_Playerinfo tag) have to be added. * [[Getting_started#Raising_your_Stats|Raising Your Stats]] must be entirely rewritten to new stats system * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Getting_started#Quick_walkthrough|Quick Walkthrough]] is duplicate data: Burn with fire and link to official Walkthrough instead. * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Getting_started#Training_technique]] should speak about shortcut window (F8) instead. * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Getting_started#Endgame]] speaks about magic training which no longer exists. But there's scoreboards ('''@scoreboards''' command), inifinite challenge and bosses to defeat and absorb their skills with the Master Skill Book. * [[Getting_started#Final_thoughts]] final paragraph is no longer relevant due to the new server Guild System. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [[NPCs]] need to be reestructurated and entirely rewritten. Even Legacy NPCs there might need some help, like putting them in the right category. ::Many NPCs are listed as a quest. They should be recategorized as NPC instead, and if they really contain a quest, they should be split and/or moved. * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== * [[Legacy:Hamond]] * [[Legacy:Thurstan]] * [[Legacy:Wolfgang]] * [[Legacy:Nicholas]] * [[Legacy:Tondor]] * [[Legacy:Hurnscald_Booksheld]] * [[Legacy:Luca]] * [[Legacy:Miriam]] <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 31r7z87x7cc54hcymbyn9lnazcqds7j 51992 51991 2020-07-17T13:44:02Z EJlol 294 Removed some todo's 51992 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== * [[Legacy:Hamond]] * [[Legacy:Thurstan]] * [[Legacy:Wolfgang]] * [[Legacy:Nicholas]] * [[Legacy:Tondor]] * [[Legacy:Hurnscald_Booksheld]] * [[Legacy:Luca]] * [[Legacy:Miriam]] <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 21qllujd6c7f509hmy9g5cw8mqws247 53635 51992 2021-01-11T02:34:07Z Speiros 2726 /* Legacy Server */ Updated needs for the Legacy NPC's, as it was just a list of ones that needed pages, and was missing a lot of details. 53635 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== '''Here are the steps for what is required on this''' [[Legacy:NPCs_(all)]] '''page.''' # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page. <br><br> ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 4s47v1nawdftl7bfv6y5cag0el2ipn3 53636 53635 2021-01-11T02:48:47Z Speiros 2726 /* Legacy Server */ 53636 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== '''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page. <br> [[Legacy:Navigation]]''' needs these steps done to it''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] kzptbxyruadbjqsubh7emtpo3jjtpx8 53637 53636 2021-01-11T03:20:40Z Speiros 2726 /* Legacy Server */ Updated needs. 53637 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 11 January 2021)</small>''<br> '''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page. <br> [[Legacy:Navigation]]''' needs these steps done to it''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]]'''Things required''' # Ensure all items are added # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. End of list on this date. ____ ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 7biieszc3h0rdy07k24jwpekgxjto0l 53680 53637 2021-01-11T07:10:47Z Speiros 2726 /* Legacy Server */ Added more things to do 53680 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 11 January 2021)</small>''<br> '''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to. # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br><br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 50bk02zwufbczygtok81thm86x7vjk5 53719 53680 2021-01-12T07:42:43Z Speiros 2726 /* Legacy Server */ Minor information update 53719 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 11 January 2021)</small>''<br> '''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section.)''</small> # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to. # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] i9kfz5b63eamuhzi1rwu0y7kjct1tnv 53727 53719 2021-01-12T08:53:30Z Speiros 2726 /* Legacy Server */ Formatting, and other info added 53727 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 11 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Legacy wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to. # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] m67g9k7t4oo9kicqclo98yadxhsmws7 54060 53727 2021-01-26T13:43:36Z Speiros 2726 /* Legacy Server */ Updated todo list for Legacy wiki 54060 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 27 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Legacy wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Legacy]]" and a "Category:LegacyNPC]]" typed in the "See Also" or "Other info" section. # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added - for example, [[Legacy:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to. # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] djnfvxh4acs3zqvyx67wv8sigqujk2e 54061 54060 2021-01-26T13:51:45Z Speiros 2726 More updates. 54061 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 27 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Legacy wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Legacy]]" and a "Category:LegacyNPC]]" typed in the "See Also" or "Other info" section. # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added - for example, [[Legacy:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to. # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> [[Special:Categories]] '''Things that need doing''' # Sifting through the categories and ensuring that none of the pages go to dead links. Ensure that they are filed correctly in the categories first, before moving. I noticed that there are many "Legacy" categories with no proper page. So check to see if there is an existing page, or whether the existing page needs updating. Otherwise, a page will need adding for the Legacy categories. Check first. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 3k3f1b28xpxbwy4r5ckgayiu28cf7vn 54066 54061 2021-01-26T14:20:58Z EJlol 294 /* Legacy Server */ Added note about template adding the categories 54066 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 27 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Legacy wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Legacy]]" and a "Category:LegacyNPC]]" typed in the "See Also" or "Other info" section. ::This is not needed when using the [[Template:LegacyNPC|template]] # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added - for example, [[Legacy:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to. # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> [[Special:Categories]] '''Things that need doing''' # Sifting through the categories and ensuring that none of the pages go to dead links. Ensure that they are filed correctly in the categories first, before moving. I noticed that there are many "Legacy" categories with no proper page. So check to see if there is an existing page, or whether the existing page needs updating. Otherwise, a page will need adding for the Legacy categories. Check first. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. <br><br> ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] qen7v7d8anrq90safk4oiburca82nrt 54071 54066 2021-01-26T16:09:23Z WildX 1896 Add tutorials section with first video link 54071 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 27 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Legacy wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Legacy]]" and a "Category:LegacyNPC]]" typed in the "See Also" or "Other info" section. ::This is not needed when using the [[Template:LegacyNPC|template]] # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added - for example, [[Legacy:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to. # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> [[Special:Categories]] '''Things that need doing''' # Sifting through the categories and ensuring that none of the pages go to dead links. Ensure that they are filed correctly in the categories first, before moving. I noticed that there are many "Legacy" categories with no proper page. So check to see if there is an existing page, or whether the existing page needs updating. Otherwise, a page will need adding for the Legacy categories. Check first. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. ===Editing tips and tutorials=== * Check out [https://www.youtube.com/watch?v=-rGU6iH3h4w&t Speiros' guide to editing NPC pages] to understand NPC page templates and get a feel for wiki editing in general. ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 1bzjlgm59wudz3blye2hjoqtm4cklpu 54180 54071 2021-01-28T08:29:25Z Speiros 2726 small addition to things to do. 54180 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 28 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Legacy wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. # Any missing NPC's need adding to the page. # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Legacy]]" and a "Category:LegacyNPC]]" typed in the "See Also" or "Other info" section. ::This is not needed when using the [[Template:LegacyNPC|template]] # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added - for example, [[Legacy:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to (for example, [[Legacy:Love Triangle Quest|Love Triangle Quest]] seems to have been in error). # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> [[Special:Categories]] '''Things that need doing''' # Sifting through the categories and ensuring that none of the pages go to dead links. Ensure that they are filed correctly in the categories first, before moving. I noticed that there are many "Legacy" categories with no proper page. So check to see if there is an existing page, or whether the existing page needs updating. Otherwise, a page will need adding for the Legacy categories. Check first. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. ===Editing tips and tutorials=== * Check out [https://www.youtube.com/watch?v=-rGU6iH3h4w&t Speiros' guide to editing NPC pages] to understand NPC page templates and get a feel for wiki editing in general. ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 6byaxqxyuyicusxigf051w08zvgqlgl 54688 54180 2021-02-16T04:39:59Z Speiros 2726 /* Legacy Server */ Updates. 54688 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://webchat.freenode.net/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://webchat.freenode.net/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 16 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Legacy wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. ''(Completed on 16 February 2021)'' # Any missing NPC's need adding to the page. ''(Completed on 16 February 2021)'' # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Legacy]]" and a "Category:LegacyNPC]]" typed in the "See Also" or "Other info" section. ::This is not needed when using the [[Template:LegacyNPC|template]] # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added - for example, [[Legacy:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to (for example, [[Legacy:Love Triangle Quest|Love Triangle Quest]] seems to have been in error). # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> [[Special:Categories]] '''Things that need doing''' # Sifting through the categories and ensuring that none of the pages go to dead links. Ensure that they are filed correctly in the categories first, before moving. I noticed that there are many "Legacy" categories with no proper page. So check to see if there is an existing page, or whether the existing page needs updating. Otherwise, a page will need adding for the Legacy categories. Check first. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. ===Editing tips and tutorials=== * Check out [https://www.youtube.com/watch?v=-rGU6iH3h4w&t Speiros' guide to editing NPC pages] to understand NPC page templates and get a feel for wiki editing in general. ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] 0n1xhmegk83azykcgjtiyu8uvqcejb0 54996 54688 2021-05-28T21:27:30Z Jesusalva 2520 Text replacement - "webchat.freenode.net" to "web.libera.chat" 54996 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://web.libera.chat/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Legacy: Namespace where appropriate. * Move pages on Dev: Namespace to Legacy: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Legacy Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Legacy information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Legacy:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Legacy:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Legacy Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Legacy's version (can use both Legacy: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Legacy and rEvolt are different. Dev pages only relevant to Legacy can be safely moved to Legacy: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Legacy Server; Therefore, redirects from Dev: to Legacy: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Legacy Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Legacy Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://web.libera.chat/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Legacy Server===== ''<small>(edited by Speiros, 16 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Legacy wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Legacy:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. ''(Completed on 16 February 2021)'' # Any missing NPC's need adding to the page. ''(Completed on 16 February 2021)'' # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Legacy]]" and a "Category:LegacyNPC]]" typed in the "See Also" or "Other info" section. ::This is not needed when using the [[Template:LegacyNPC|template]] # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Legacy:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Legacy:Items]] '''Things required''' # Ensure all items are added - for example, [[Legacy:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Legacy:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Legacy:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to (for example, [[Legacy:Love Triangle Quest|Love Triangle Quest]] seems to have been in error). # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Legacy:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Legacy:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Legacy:Geography]] and/or [[Legacy:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> [[Special:Categories]] '''Things that need doing''' # Sifting through the categories and ensuring that none of the pages go to dead links. Ensure that they are filed correctly in the categories first, before moving. I noticed that there are many "Legacy" categories with no proper page. So check to see if there is an existing page, or whether the existing page needs updating. Otherwise, a page will need adding for the Legacy categories. Check first. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. ===Editing tips and tutorials=== * Check out [https://www.youtube.com/watch?v=-rGU6iH3h4w&t Speiros' guide to editing NPC pages] to understand NPC page templates and get a feel for wiki editing in general. ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] bhes9cfka8meo3qr8if6xvw4ifm7yue 56321 54996 2022-12-07T20:51:43Z Jesusalva 2520 Text replacement - "Legacy" to "Classic" 56321 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://web.libera.chat/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Classic: Namespace where appropriate. * Move pages on Dev: Namespace to Classic: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Classic Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Classic information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Classic:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Classic:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Classic Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Classic's version (can use both Classic: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Classic and rEvolt are different. Dev pages only relevant to Classic can be safely moved to Classic: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Classic Server; Therefore, redirects from Dev: to Classic: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Classic Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Classic Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://web.libera.chat/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Classic Server===== ''<small>(edited by Speiros, 16 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Classic wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Classic:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. ''(Completed on 16 February 2021)'' # Any missing NPC's need adding to the page. ''(Completed on 16 February 2021)'' # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Classic]]" and a "Category:ClassicNPC]]" typed in the "See Also" or "Other info" section. ::This is not needed when using the [[Template:ClassicNPC|template]] # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Classic:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Classic:Items]] '''Things required''' # Ensure all items are added - for example, [[Classic:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Classic:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Classic:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to (for example, [[Classic:Love Triangle Quest|Love Triangle Quest]] seems to have been in error). # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Classic:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Classic:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Classic:Geography]] and/or [[Classic:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> [[Special:Categories]] '''Things that need doing''' # Sifting through the categories and ensuring that none of the pages go to dead links. Ensure that they are filed correctly in the categories first, before moving. I noticed that there are many "Classic" categories with no proper page. So check to see if there is an existing page, or whether the existing page needs updating. Otherwise, a page will need adding for the Classic categories. Check first. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. ===Editing tips and tutorials=== * Check out [https://www.youtube.com/watch?v=-rGU6iH3h4w&t Speiros' guide to editing NPC pages] to understand NPC page templates and get a feel for wiki editing in general. ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] h3u3oxf5lpvrfgbp0zarzlh1pyzdpt2 59486 56321 2024-03-27T03:56:43Z Move page script 2739 Move page script moved page [[Dev:Game Wiki Work]] to [[Development:Game Wiki Work]]: Rename Dev: to Development: so the miraheze import works 56321 wikitext text/x-wiki <div style="background-color: #FFBFBF; text-align: center; border: 1px solid #BF4000; margin-bottom: 10px;"> '''Please read before working with/on this page:''' This page is used as an overview of things that need to be done (added, updated, etc.) in '''this wiki only'''. Please keep it as clean and updated as possible. You can always ask on [https://web.libera.chat/?channels=#themanaworld IRC] and/or on our [https://forums.themanaworld.org forum] if you don't understand something. For bigger changes on important pages, it's recommended that you ask. Also keep in mind that new players read the wiki and often take it as a first impression. Thank you. </div> '''Note:''' Most points in the [[Things to do#Player pages|Player pages]] section can be edited by everyone, while other pages, like dev pages, usually need more technical know-how. '''So please feel free to help!''' PS. This only covers '''the wiki''' and have absolutely no relation with game development or whatsoever. ==Wiki Content== <br> ===To-Do=== <!-- PLEASE ADD POINTS PLAYERS CAN DO WITHOUT TECHNICAL KNOWLEDGE FIRST --> * [[Screenshots]]: Place images in correct year and add images from forum to fill in missing years <br> Pertaining to The Mana World: rEvolt. =====Namespace Issues===== * Pages made for unreleased items from page references. * Move pages on Main Namespace to Classic: Namespace where appropriate. * Move pages on Dev: Namespace to Classic: Namespace where appropriate. * Move pages on rEvolt namespace to main namespace. There's no need to leave redirects behind. Important notes: * When moving pages from Main Namespace to Classic Namespace, leave a redirect behind. * When writing a page which was previously a redirect, please use <nowiki>{{Disambiguation}} </nowiki> tag, in case player is looking for TMW:Classic information. - Forcing players to go back to Google or use Search bars is counter-productive and SEO-harmful. * If you prefer, you can build the page on rEvolt: namespace, and configure main page to look like [[Player Groups|This one]] * Keep in mind The Mana World have two servers, pretty much like Ragnarok have Classic and Renewal servers. Albeit the former is fated to die due to sheer lack of maintenance, prepare the wiki assuming both servers will run forever. <br><br> =====General tasks===== There are many new updates to the wiki at present, so instead of mentioning them one by one, here is a brief description. They are not in chronological order. Some are still under construction or repair. * Confirmation that all items have a page. * Confirmation that all monsters have a page. * Confirmation that all NPCs that are linked to exist and haven't been replaced, and that their coordinates are correct. * Pictures are up-to-date. * [[Walkthrough]] must be written * Information about '''@tutorial''', the ingame 101 book, should be added * [[Stats]] page must be redone as well, refer to [http://irowiki.org/wiki/Stats iRO Wiki] for more imperative information on how they're working. * [[Warrior]], [[Archer]] and [[Mage]] must be written with new gameplay mechanics (mage class might be the hardest to write at this point) * [[Magic]] needs a link to [[Classic:Magic]] for the confused/lost players. At the moment, it is not possible to write this page. * [[Skills]] is very, very similar. Almost the same thing. Need input from Developers.... * [[Quests]] is severely incomplete. The '''@qdebug''' command on Test Server allows a quick insight of the quests currently available and their stages. * [[Item Reference]] - Must be written, see [https://cacic.tmw2.org/items The Automatic Item DB reader] * [[Monster Reference]] - Must be written, see [https://gitlab.com/evol/evol-tools/blob/master/wiki/redesign.py this script] * [https://gitlab.com/evol/evol-web/issues/4 Pages are needed] * [https://gitlab.com/evol/evol-web/issues/3 Pages are outdated] * [[Classic:Game_Masters]] is invalid (The Mana World namespace version shall prevail), and its subpage (Events) can be safely moved to "The Mana World" namespace as well. * [[Dev:Windows10]] is only relevant for Classic Server * [[Translators]] must be updated to Transifex links. Also checkout pages that link to the note template: [[Special:WhatLinksHere/Template:Note]] <br><br> =====Dev pages===== * [[Dev:Monster Design]] and [[Dev:Item db.txt]] probably should be archived * [[Map development]] - Archive the Classic's version (can use both Classic: as Archive: namespaces) and rewrite with new map conventions (which only Micksha knows) * [[GM Commands]] and [[User:Jesusalva/GM]] could be merged; But can get messy quickly. Changes to GM Commands are also rarely announced, which makes updating these a burden. * Mark-up Hercules documentation [https://github.com/HerculesWS/Hercules/tree/master/doc Hercules Docs] - or just replace our documentation pages with link to those. * Or use [https://gitlab.com/evol/evol-docs/tree/master] our own documentation fork which is way more up-to-date than official Hercules' one. * [[Dev:ToDo]] should probably be made in a #REDIRECT to GitLab milestones page. * Proper [[Reporting Bugs]] instructions * [[Dev:SFX]] can be replaced with the [https://gitlab.com/evol/evol-all/issues/77 Sound Design Documentation] * [[Dev:Main]] Need to be divided because Development workflow for Classic and rEvolt are different. Dev pages only relevant to Classic can be safely moved to Classic: namespace leaving a temporary redirect behind. * There's no present interest in actively developing Classic Server; Therefore, redirects from Dev: to Classic: are not required. * [[Dev:Working_With_Git]] needs info about merge conflicts and gitlab specifics (Merge Requests) * [[Dev:Testing_Server]] has been reestructured, both on Classic Test Server as on Official Test Server (LTS have @debug and inheirs GM structure from Classic Official Server, OTS have @commands and only two GM groups) <br><br> =====Manaplus===== * Help with [http://manaplus.org/start Manaplus Wiki] * There's a huge list of ManaPlus improvements in dire need. * There's also the idea of rewriting the client for Mobile (ie. deprecate Guichan) * PM 4144 in [https://web.libera.chat/?channels=#themanaworld IRC] or on the [https://forums.themanaworld.org/ucp.php?i=pm&mode=compose&u=4982 Forums] for an account or information about ManaPlus. <br><br> =====Classic Server===== ''<small>(edited by Speiros, 16 January 2021)</small>''<br> This is an updated list of changes or requirements needed for the Classic wiki. If there are others, please add them here too. Also, please use the [[Dev_talk:Game_Wiki_Work|discussion]] page to talk about changes. <br>'''Here are the steps for what is required on the '''[[Classic:NPCs_(all)]]''' page.''' <br> <small>''(I am currently working on this section)''</small> # All dead links need a page to go to. ''(Completed on 16 February 2021)'' # Any missing NPC's need adding to the page. ''(Completed on 16 February 2021)'' # All NPC's need an individual page (some exceptions where multiple NPC's have one page). # All NPC's need to follow the same format as all other NPC's with a "Y" in the "PP" column. Shops are a little different, but open up a shop NPC with a "Y" on it, and follow the format. # After these things, go over them again, and add the NPC template, adjusting the template if necessary to ensure it covers all needs. # Ensure there is a "[[Category:Classic]]" and a "Category:ClassicNPC]]" typed in the "See Also" or "Other info" section. ::This is not needed when using the [[Template:ClassicNPC|template]] # Each NPC checked to ensure these bits of information are correct: ## Correct picture ## Correct location information ## Complete list of quests to each NPC ## Good spelling, and easy-to-follow instructions # Once this is confirmed, the column "PP" can be removed from the page, as can the "Under Construction" label. <br> [[Classic:Navigation]]''' Things required''' # Confirm there is information regarding every locality on the game in it. Currently, it seems to be missing Asphodel Moor, The Crypt, and a few others. # Fix dead links. # Each locality should have an individual page if there is more information for it than just a paragraph or two. Otherwise, the link should be to a sub-heading in the page from the locality. For instance, on the NPC page, it may link an NPC to a locality. This may mean changing headings in the Navigation page to ensure it can be done. # I haven't looked at it yet, but working out a consistent format that is suitable would be good too. It has been mentioned that the layout of the maps differs from page to page, as in where on the page it is situated. <br> [[Classic:Items]] '''Things required''' # Ensure all items are added - for example, [[Classic:Gwyneth|Gwyneth]] has items in her shop that aren't on the database, at least on the wiki. # Ensure they are all linked to ALL the monsters, shops, quests etc in game that drop them, or sell them. # Ensure that they are in order of value first, and alphabetically second. <br> [[Classic:Quests]] '''Things required''' # Ensure all quests are added # Use the quest format, however that will be. This includes the template. # Have a walkthrough for every quest in a step-by-step fashion. # Go through the pages, and make sure that they all have a link to all [[Classic:Monsters|Monsters]] that will be encountered in the areas that attack. # Ensure all rewards are correct, and linked to (for example, [[Classic:Love Triangle Quest|Love Triangle Quest]] seems to have been in error). # Ensure there is a link to all needed NPC's in the game, so that a player can find how to get there on the wiki. <br> [[Classic:Monsters]] '''Things required''' # Ensure that the monsters are all in the table. # Ensure that the monsters are in the table in the correct order. # Ensure that all drops are accurate, with percentages added. # Confirm that the pictures are up-to-date. <br> [[Classic:Shops]] '''Things required''' # Ensure that all shops are in the list. # Remove information that seems doubled up. There is a sortable list that has sufficient information on it instead of having the information twice like it presently is. # Check that the shop items and prices are correctly stated. # Ensure all links go to the legacy game, and not the new one. # Once completed, go to each NPC, and add a link at the bottom under "Other info", or however it is worded. <br> [[Classic:Geography]] and/or [[Classic:Navigation]] '''Things I'd like to see/do''' # Have all buildings named and mapped, and put into a storyline if possible. At the very least mapped, so people can identify each building by name, and know how to get there. <br> [[Special:Categories]] '''Things that need doing''' # Sifting through the categories and ensuring that none of the pages go to dead links. Ensure that they are filed correctly in the categories first, before moving. I noticed that there are many "Classic" categories with no proper page. So check to see if there is an existing page, or whether the existing page needs updating. Otherwise, a page will need adding for the Classic categories. Check first. <br> '''*Note:''' End of list by Speiros on this date. ===Pages with frequent updates=== Some pages need to be checked frequently if they are up to date, mostly because members listed in them change or pages in their category get added or deleted frequently: * [[Monster Reference]] and [[Items]] * Staff Indexes, namely, [[Contributors]] tend to get outdated frequently * [[:Category:Under Construction]] and [[:Category:Outdated]], but they're not reliable links; Don't count on them. ===Editing tips and tutorials=== * Check out [https://www.youtube.com/watch?v=-rGU6iH3h4w&t Speiros' guide to editing NPC pages] to understand NPC page templates and get a feel for wiki editing in general. ==Wiki Improvement== =====Extensions suggested===== *<s>Image maps: http://www.mediawiki.org/wiki/Extension:ImageMap It would help developers and players to have a better world overview, and a different quest access as well.</s> *Javascript: http://www.mediawiki.org/wiki/Extension:Javascript Manage multiple JavaScript files imports from one place. (It would allow such things as a javascript character stats calculator...) ''not priority 1'' *<s>Spoilers: http://www.mediawiki.org/wiki/Extension:Spoilers The Spoilers extension adds a spoiler tag that will hide a block of text. The spoiler button's show/hide message can be customized for each set.</s> Use https://www.mediawiki.org/wiki/Manual:Collapsible_elements instead. * Variables: https://www.mediawiki.org/wiki/Extension:Variables The Variables extension allows you to define a variable on a page, use it later in that same page or included templates, change its value, possibly to a value given by an expression in terms of the old value, etc. [[Category:Development]] h3u3oxf5lpvrfgbp0zarzlh1pyzdpt2 0 3609 10677 2008-11-11T19:42:21Z Bjørn 3 Maybe this is becoming way too much text... 10677 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv project). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == With git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. It uses ssh's private/public key authentication for identifying committers. * '''Our project page:''' http://gitorious.org/projects/tmwserv On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new 'svn checkout'). For development purposes you should clone the "Push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO fn2qstubebzro77cjeqovavulsn4fya 10678 10677 2008-11-11T19:48:47Z Bjørn 3 /* Pushing */ 10678 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv project). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == With git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. It uses ssh's private/public key authentication for identifying committers. * '''Our project page:''' http://gitorious.org/projects/tmwserv On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new 'svn checkout'). For development purposes you should clone the "Push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO ltzodq79upyet12arqh9sef02n5oq13 10680 10678 2008-11-11T21:48:06Z Jaxad0127 999 /* The primary repository */ add project page for eAthena data 10680 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv project). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == With git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. It uses ssh's private/public key authentication for identifying committers. * '''TMWServ project page:''' http://gitorious.org/projects/tmwserv * '''eAthena data project page:''' http://gitorious.org/projects/tmw-eathena-data On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new 'svn checkout'). For development purposes you should clone the "Push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO fmd7udnyz3017kg2i9ms1rsh6d2pmjx 10681 10680 2008-11-12T07:51:35Z Bjørn 3 Some more words on initial setup and why we're using Gitorious this way 10681 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv and server-data projects). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. It uses ssh's private/public key authentication for identifying committers. * '''TMWServ project page:''' http://gitorious.org/projects/tmwserv * '''eAthena data project page:''' http://gitorious.org/projects/tmw-eathena-data On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new 'svn checkout'). For development purposes you should clone the "Push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</clone> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO devoedlta88br5bt9o0yf7dcxdxgvhd 10682 10681 2008-11-12T12:56:38Z Crush2 1261 format 10682 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv and server-data projects). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. It uses ssh's private/public key authentication for identifying committers. * '''TMWServ project page:''' http://gitorious.org/projects/tmwserv * '''eAthena data project page:''' http://gitorious.org/projects/tmw-eathena-data On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new 'svn checkout'). For development purposes you should clone the "Push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO ltzc8br5f5zpcr8x4jvjihrdqbtuyi8 10683 10682 2008-11-12T20:17:24Z Jaxad0127 999 /* Initial setup */ Add eAthena server 10683 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv and server-data projects). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. It uses ssh's private/public key authentication for identifying committers. * '''TMWServ project page:''' http://gitorious.org/projects/tmwserv * '''eAthena server project page:''' http://gitorious.org/projects/tmw-eathena * '''eAthena data project page:''' http://gitorious.org/projects/tmw-eathena-data On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new 'svn checkout'). For development purposes you should clone the "Push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO gh7qm7avpn4qn0v92tswj3qrcdqe0ic 10684 10683 2008-11-12T21:25:17Z Jaxad0127 999 /* Initial setup */ Add client data project 10684 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv and server-data projects). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. It uses ssh's private/public key authentication for identifying committers. * '''TMW client data:''' http://gitorious.org/projects/tmwdata * '''TMWServ project page:''' http://gitorious.org/projects/tmwserv * '''eAthena server project page:''' http://gitorious.org/projects/tmw-eathena * '''eAthena data project page:''' http://gitorious.org/projects/tmw-eathena-data On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new 'svn checkout'). For development purposes you should clone the "Push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO r1f6egd0zpqr5yk3mxkcgzu5wrwmryr 10686 10684 2008-11-13T03:10:43Z Jaxad0127 999 /* Initial setup */ reorg projects and add clone urls 10686 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv and server-data projects). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. It uses ssh's private/public key authentication for identifying committers. * '''TMW client data:''' :Project page: http://gitorious.org/projects/tmwdata :Clone URLS: ::git://gitorious.org/tmwdata/mainline.git ::http://git.gitorious.org/tmwdata/mainline.git * '''TMWServ project page:''' :Project page: http://gitorious.org/projects/tmwserv :Clone URLS: ::git://gitorious.org/tmwserv/mainline.git ::http://git.gitorious.org/tmwserv/mainline.git * '''eAthena server project page:''' :Project page: http://gitorious.org/projects/tmw-eathena :Clone URLS: ::git://gitorious.org/tmw-eathena/mainline.git ::http://git.gitorious.org/tmw-eathena/mainline.git * '''eAthena data project page:''' :Project page: http://gitorious.org/projects/tmw-eathena-data :Clone URLS: ::git://gitorious.org/tmw-eathena-data/mainline.git ::http://git.gitorious.org/tmw-eathena-data/mainline.git On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new 'svn checkout'). For development purposes you should clone the "Push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO phsbjld3fc1i0j97k1gy86u91i7skrf 10687 10686 2008-11-13T10:04:03Z Kess 1128 /* Initial setup */ Move around a little + push urls 10687 wikitext text/x-wiki This page provides some information about our switch to git (which we're slowly trying to make, starting with the tmwserv and server-data projects). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). * '''TMW client data:''' :Project page: http://gitorious.org/projects/tmwdata :Clone URLs: ::git://gitorious.org/tmwdata/mainline.git ::http://git.gitorious.org/tmwdata/mainline.git :Push URL: git@gitorious.org:tmwdata/mainline.git * '''TMWServ:''' :Project page: http://gitorious.org/projects/tmwserv :Clone URLs: ::git://gitorious.org/tmwserv/mainline.git ::http://git.gitorious.org/tmwserv/mainline.git :Push URL: git@gitorious.org:tmwserv/mainline.git * '''eAthena server:''' :Project page: http://gitorious.org/projects/tmw-eathena :Clone URLs: ::git://gitorious.org/tmw-eathena/mainline.git ::http://git.gitorious.org/tmw-eathena/mainline.git :Push URL: git@gitorious.org:tmw-eathena/mainline.git * '''eAthena data:''' :Project page: http://gitorious.org/projects/tmw-eathena-data :Clone URLs: ::git://gitorious.org/tmw-eathena-data/mainline.git ::http://git.gitorious.org/tmw-eathena-data/mainline.git :Push URL: git@gitorious.org:tmw-eathena-data/mainline.git Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO 8qv8xe59eu4b6r8qotsxr99lxs9l7g2 10696 10687 2008-11-13T22:07:46Z Bjørn 3 Updates 10696 wikitext text/x-wiki This page provides some information about our switch to git (only tmwweb and tmwwebsite remain to be switched). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). * '''TMW client:''' :Project page: http://gitorious.org/projects/tmw :Clone URLs: ::git://gitorious.org/tmw/mainline.git ::http://git.gitorious.org/tmw/mainline.git :Push URL: git@gitorious.org:tmw/mainline.git * '''TMW client data:''' :Project page: http://gitorious.org/projects/tmwdata :Clone URLs: ::git://gitorious.org/tmwdata/mainline.git ::http://git.gitorious.org/tmwdata/mainline.git :Push URL: git@gitorious.org:tmwdata/mainline.git * '''TMWServ:''' :Project page: http://gitorious.org/projects/tmwserv :Clone URLs: ::git://gitorious.org/tmwserv/mainline.git ::http://git.gitorious.org/tmwserv/mainline.git :Push URL: git@gitorious.org:tmwserv/mainline.git * '''eAthena server:''' :Project page: http://gitorious.org/projects/tmw-eathena :Clone URLs: ::git://gitorious.org/tmw-eathena/mainline.git ::http://git.gitorious.org/tmw-eathena/mainline.git :Push URL: git@gitorious.org:tmw-eathena/mainline.git * '''eAthena data:''' :Project page: http://gitorious.org/projects/tmw-eathena-data :Clone URLs: ::git://gitorious.org/tmw-eathena-data/mainline.git ::http://git.gitorious.org/tmw-eathena-data/mainline.git :Push URL: git@gitorious.org:tmw-eathena-data/mainline.git Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO gm39bbiuvr2veqgcmdbh0kkshg3w6oi 10698 10696 2008-11-14T08:38:58Z Bjørn 3 A bit less text by linking to project page from title 10698 wikitext text/x-wiki This page provides some information about our switch to git (only tmwweb and tmwwebsite remain to be switched). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, everybody has his own repository. But of course we will keep a central repository through which we cooperate. This central repository is currently hosted at [http://gitorious.org/ gitorious.org], a friendly website that is also open source. On Gitorious you can have multiple repositories for each project. The main one (and I suggest we keep just one for the moment) is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). * '''[http://gitorious.org/projects/tmw TMW client]''' :Clone URLs: ::git://gitorious.org/tmw/mainline.git ::http://git.gitorious.org/tmw/mainline.git :Push URL: git@gitorious.org:tmw/mainline.git * '''[http://gitorious.org/projects/tmwdata TMW client data]''' :Clone URLs: ::git://gitorious.org/tmwdata/mainline.git ::http://git.gitorious.org/tmwdata/mainline.git :Push URL: git@gitorious.org:tmwdata/mainline.git * '''[http://gitorious.org/projects/tmwserv TMWServ]''' :Clone URLs: ::git://gitorious.org/tmwserv/mainline.git ::http://git.gitorious.org/tmwserv/mainline.git :Push URL: git@gitorious.org:tmwserv/mainline.git * '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' :Clone URLs: ::git://gitorious.org/tmw-eathena/mainline.git ::http://git.gitorious.org/tmw-eathena/mainline.git :Push URL: git@gitorious.org:tmw-eathena/mainline.git * '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' :Clone URLs: ::git://gitorious.org/tmw-eathena-data/mainline.git ::http://git.gitorious.org/tmw-eathena-data/mainline.git :Push URL: git@gitorious.org:tmw-eathena-data/mainline.git Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO 11b03kcvmpro3ogmlhzmyv42a64pyyz 10699 10698 2008-11-14T21:21:30Z Bjørn 3 Updated list of projects 10699 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO qr6ywdr6ap5dw0orxc25bzrx839g56h 10700 10699 2008-11-15T03:36:14Z Octalot 1267 10700 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO 1krer7ux9e09tn6gupqmx9lhcqoj4kx 10701 10700 2008-11-15T16:20:46Z Bjørn 3 Added a section about working on the 0.0 branch 10701 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO mi4o9fetq67fdtr2fm2d3so3nvhe864 10702 10701 2008-11-15T16:35:11Z Bjørn 3 Added some commands and apps that are good to know about 10702 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === TODO === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. 8vimyvxobhx8ac42iba8nfisl2ztfyf 10733 10702 2008-11-16T17:39:38Z Bjørn 3 /* Resolving conflicts */ 10733 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. 8w7fjhlxnvusfjyy5c2mjmwxtit0fok 10738 10733 2008-11-16T19:29:23Z Bjørn 3 Added links to Atom feeds for commits on master branches 10738 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. 4qnhf4l06c0m2le64cnu4f2dx1o60n5 10752 10738 2008-11-17T08:56:58Z Exceptionfault 1227 added lineending issue under msysgit 10752 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice, that all files seem to have changed after doing a fresh clone, this discussion should help you: [http://code.google.com/p/msysgit/issues/detail?id=83]. Find your global git configuration file, normally somewhere under c:\programs\git\etc\gitconfig, and set the parameter ''autocrlf'' in the ''core'' section to ''false''. qcezu2nm1o4p0b1tp4d71w7o8q1cy2d 10753 10752 2008-11-17T08:59:15Z Exceptionfault 1227 /* git on Windows */ 10753 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice, that all files seem to have changed after doing a fresh clone, this discussion should help you: [http://code.google.com/p/msysgit/issues/detail?id=83]. Find your global git configuration file, normally somewhere under c:\programs\git\etc\gitconfig, and set the parameter ''autocrlf'' in the ''core'' section to ''false''. Then remove you last clone and do a nwe fresh clone. h9ygxb6v6x6hprq5bd3gydbfp3la3ip 10796 10753 2008-11-19T22:48:19Z Jaxad0127 999 /* Initial setup */ Add tmwserver-data and tmwart projects 10796 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice, that all files seem to have changed after doing a fresh clone, this discussion should help you: [http://code.google.com/p/msysgit/issues/detail?id=83]. Find your global git configuration file, normally somewhere under c:\programs\git\etc\gitconfig, and set the parameter ''autocrlf'' in the ''core'' section to ''false''. Then remove you last clone and do a nwe fresh clone. 74odg4hbicszfkadkj6s80islx069i6 10802 10796 2008-11-20T23:54:10Z Bjørn 3 Added note about shallow clone 10802 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice, that all files seem to have changed after doing a fresh clone, this discussion should help you: [http://code.google.com/p/msysgit/issues/detail?id=83]. Find your global git configuration file, normally somewhere under c:\programs\git\etc\gitconfig, and set the parameter ''autocrlf'' in the ''core'' section to ''false''. Then remove you last clone and do a nwe fresh clone. mop76qh21yxhj222a4e47n2i4wzc3xf 10847 10802 2008-11-29T20:20:09Z Bjørn 3 Separated repository for TMW eAthena client 10847 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' | git://gitorious.org/tmw/eathena.git | git@gitorious.org:tmw/eathena.git | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata === The TMW 0.0.x client === The 0.0 client may seem a bit hidden, but it exists as a branch just like with Subversion. To continue working on this client you need to checkout the branch and create your own local branch to work on it. This goes as follows: $ git clone git@gitorious.org:tmw/mainline.git tmw $ cd tmw $ git checkout -b 0.0 origin/0.0 With the last command, a new local branch called 0.0 is created. Since it was based on the 0.0 branch in origin (the repository on Gitorious), it will automatically track this remote branch. This means that when you do <code>git pull</code>, git will attempt to automatically merge the latest changes available from this branch with your local 0.0 branch. == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice, that all files seem to have changed after doing a fresh clone, this discussion should help you: [http://code.google.com/p/msysgit/issues/detail?id=83]. Find your global git configuration file, normally somewhere under c:\programs\git\etc\gitconfig, and set the parameter ''autocrlf'' in the ''core'' section to ''false''. Then remove you last clone and do a nwe fresh clone. k65goib7k6f3w0k0lzn8ttmz5x4qwf0 10861 10847 2008-11-30T21:36:35Z Bjørn 3 Removed obsolete info, this client has its own git repository now 10861 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' | git://gitorious.org/tmw/eathena.git | git@gitorious.org:tmw/eathena.git | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice, that all files seem to have changed after doing a fresh clone, this discussion should help you: [http://code.google.com/p/msysgit/issues/detail?id=83]. Find your global git configuration file, normally somewhere under c:\programs\git\etc\gitconfig, and set the parameter ''autocrlf'' in the ''core'' section to ''false''. Then remove you last clone and do a nwe fresh clone. 6iyzq9x1kjihb72v3n8g6ucfcw489yb 11243 10861 2009-01-03T14:41:32Z Bjørn 3 Adjusted note about git on Windows regarding core.autocrlf 11243 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' | git://gitorious.org/tmw/eathena.git | git@gitorious.org:tmw/eathena.git | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 5zxqn19hjtv0j3kmry9gp9456xxymdf 11253 11243 2009-01-06T03:27:03Z Jaxad0127 999 inital description of <code>git format-patch</code> 11253 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' | git://gitorious.org/tmw/eathena.git | git@gitorious.org:tmw/eathena.git | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 3rfar43bbip6unnzpi2gzvimmlktr8f 11802 11253 2009-03-07T20:18:30Z Jaxad0127 999 /* Initial setup */ Make sure the push URL is identified as devs only 11802 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' | git://gitorious.org/tmw/eathena.git | git@gitorious.org:tmw/eathena.git | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. h2ssmlbj0pqsjuw470vypvg28hch5so 11803 11802 2009-03-09T17:54:15Z Terlmann 1534 11803 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- |This branch contains the(to be) fully migrated and merged future client for TMW |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' | git://gitorious.org/tmw/eathena.git | git@gitorious.org:tmw/eathena.git | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- |This branch contains the old, current(downloadable from TMW site) client. This branch contains code from the old client. To allow connections to the old servers , it is being migrated into the new client, allowing the new client to connect to both servers. |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- |This branch contains the universal client data set used by the new client and the eathena client. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- |This branch contains the new homebrew SUPERDUPER server code. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- |This branch contains the new server's data files. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- |This branch contains the code for eAthena, a server written to emulate Ragnarok Online. It's full of bugs, so the new tmw server will be used to replace it. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- |This branch contains the server data for the eathena client. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |- |this branch contains experimental art concepts that have nothing to do whatsoever with actual client content, and in no way represent anything you will ever see in the game or are related to any experimental art concepts that might be in the game eventually. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. sd35wrcstuegdmzee8eufy0i84wsmjp 11804 11803 2009-03-09T21:14:21Z Jaxad0127 999 /* Initial setup */ fix layout of table and descriptions 11804 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the(to be) fully migrated and merged future client for The Mana World |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' | git://gitorious.org/tmw/eathena.git | git@gitorious.org:tmw/eathena.git | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- |colspan=4|This branch contains the old, current client. |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. bhlbuuxlyxb09oi7q5ww3mrckw6zzy8 11879 11804 2009-03-30T19:18:30Z Jaxad0127 999 /* Initial setup */ mark the main client repository as the main one and the eathena one as "do not use" as it ha 11879 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' (do not use) | git://gitorious.org/tmw/eathena.git | git@gitorious.org:tmw/eathena.git | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- |colspan=4|This repository should only be used for reference purposes. Please use the other client repository instead for playing and developing. |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. fvq07maaaamtytw4klmikw4yq9eyvkx 11880 11879 2009-03-30T19:23:54Z Jaxad0127 999 /* Initial setup */ remove push url for eAthena client 11880 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/projects/tmw/repos/eathena TMW eAthena client]''' (do not use) | git://gitorious.org/tmw/eathena.git | (please put all changes in mainline) | [http://gitorious.org/projects/tmw/repos/eathena/logs/0.0/feed.atom Atom] |- |colspan=4|This repository should only be used for reference purposes. Please use the other client repository instead for playing and developing. |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 1ornhyocndd0y3jh41mtewm7lg6n29e 11936 11880 2009-04-22T20:21:07Z Jaxad0127 999 /* Initial setup */ remove eAthena client repository 11936 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw-website/mainline.git | git@gitorious.org:tmw-website/mainline.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/projects/tmw-eathena/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. r3fv8ql53650ddb9krpu3gkogpx8xpb 12104 11936 2009-05-14T12:39:34Z Bjørn 3 Updated the links to the website repository 12104 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/projects/tmw/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/projects/tmwdata/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/projects/tmwserv/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/projects/tmwserv-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/projects/tmwweb/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/projects/tmw-website/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/projects/tmw-eathena-data/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/projects/tmwart/repos/mainline/logs/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. o3xfud1jwioq2n99hljgkp7wk8n1mrb 12144 12104 2009-05-17T07:00:57Z Kess 1128 /* Initial setup */ Directing the atoms to the right places 12144 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command should you your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows something similar to the ChangeLog file. Recent commits on your current branch with a list of the files the touched. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 53ceamtfjr4xxa3rzglri9kgrl8n2oc 12303 12144 2009-06-01T23:46:07Z Kess 1128 /* Good to know */ Wording 12303 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/projects/tmw-website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 032nsiv07qryxzfglva5paxtsxpn1wm 12307 12303 2009-06-02T00:21:16Z Kess 1128 /* Initial setup */ Forgot to change one url last time 12307 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/projects/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/projects/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/projects/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/projects/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/projects/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/projects/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/projects/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/projects/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. ldzg9cng5cqwx3woru8cngrh851hxue 12490 12307 2009-06-30T13:46:13Z Jaxad0127 999 /* Initial setup */ fix gitorious links 12490 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-website tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. s18gwget3n6sepcrxd5wa1by4q4agll 12526 12490 2009-07-04T06:58:25Z LlubNek 1604 Cloning: removed tmw-website from for statement. Website URL is of different form from other projects. 12526 wikitext text/x-wiki This page provides some information about our switch to git (which, as of Nov 14th, has been completed). As an initial comforting note, git really isn't so complicated as some people would have you believe. A few months ago I became familiar with distributed version control by using Mercurial, and since a few weeks we're using git at work. I think we'll benefit a lot from switching to it on the long run. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 70xd8ov8z6dlige1ff36gwp2scyhpix 13287 12526 2009-09-12T11:27:47Z Kess 1128 We‘ve used Git for more than half a year now 13287 wikitext text/x-wiki == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. bhy1rw6lvmksenj8ryu6r0213un0daa 13313 13287 2009-09-16T18:58:05Z Kess 1128 [[Git Repository]] moved to [[Git repository]] 13313 wikitext text/x-wiki == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. bhy1rw6lvmksenj8ryu6r0213un0daa 13317 13313 2009-09-16T19:10:00Z Kess 1128 /* Initial setup */ Added tmwmusic 13317 wikitext text/x-wiki == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. ixkosvdqlay85ljmyysnkuani7oomzh 13531 13317 2009-10-11T19:49:00Z Crush 103 added introductory section 13531 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv TMW server]''' | git://gitorious.org/tmwserv/mainline.git | git@gitorious.org:tmwserv/mainline.git | [http://gitorious.org/tmwserv/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the our own server. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmwweb TMW web frontend]''' | git://gitorious.org/tmwweb/mainline.git | git@gitorious.org:tmwweb/mainline.git | [http://gitorious.org/tmwweb/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the web module for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmwserv/mainline.git tmwserv $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmwserv tmwweb tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. b8drdi9touzmqjy37s6552am7oxe0lc 13797 13531 2009-11-10T13:44:37Z Bjørn 3 Removed some references to relocated repositories 13797 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. sidmdgmnbc814yt6m8hjon0u76fgvq6 13885 13797 2009-12-09T20:22:29Z Kane 1752 13885 wikitext text/x-wiki {{Status_outdated}} We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 3ej3aiesdjpolxp06vhknt14b0wih9i 13886 13885 2009-12-09T20:31:47Z Kane 1752 13886 wikitext text/x-wiki {{Status_outdated}} '''Please note most of the information here is now out of dated, but still great for reference. I suggest you checking out the Mana Source Documentation for more info on the latest repositories.''' http://doc.manasource.org/git_repository We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw TMW client]''' | git://gitorious.org/tmw/mainline.git | git@gitorious.org:tmw/mainline.git | [http://gitorious.org/tmw/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the client for The Mana World |- | '''[http://gitorious.org/tmwdata TMW client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. mfngpdik52t2e42gp001ebbrz0b7tvj 14258 13886 2009-12-15T20:19:46Z Jaxad0127 999 Remove client and tmwserv 14258 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmwdata TMW eAthena client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data for eAthena. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. t5v806hgpp98sp32dhj0f8v7myhod4t 14506 14258 2010-01-06T03:39:57Z Jaxad0127 999 put tmwserv-data back for now 14506 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmwdata TMW eAthena client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data for eAthena. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 0zdqerdgm9r9xry55gpg7ajrww7t7g0 15122 14506 2010-06-09T06:32:01Z Jaxad0127 999 /* Initial setup */ add Mana branding repo 15122 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw/tmw Mana branding]''' | git://gitorious.org/tmw/tm.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[http://gitorious.org/tmwdata TMW eAthena client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data for eAthena. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. olfdsneb6yhaqwu4izh1kr7lxe5oa60 15123 15122 2010-06-10T21:53:39Z Majinsniper 1818 15123 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw/tmw Mana branding]''' | git://gitorious.org/tmw/tmw.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[http://gitorious.org/tmwdata TMW eAthena client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data for eAthena. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. bh2lcyhv8r0f6cueg6fxwblsiqacigi 15204 15123 2010-07-08T16:32:50Z Jaxad0127 999 /* Commit */ Add a sample commit message 15204 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw/tmw Mana branding]''' | git://gitorious.org/tmw/tmw.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[http://gitorious.org/tmwdata TMW eAthena client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data for eAthena. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. 04i1xeu9stwf7sgom3zeh52ifp42sqe 16160 15204 2010-11-22T04:29:13Z Hoogli 1124 16160 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw/tmw Mana branding]''' | git://gitorious.org/tmw/tmw.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[http://gitorious.org/tmwdata TMW eAthena client data]''' | git://gitorious.org/tmwdata/mainline.git | git@gitorious.org:tmwdata/mainline.git | [http://gitorious.org/tmwdata/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the client data for eAthena. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmwserv-data TMW server data]''' | git://gitorious.org/tmwserv-data/mainline.git | git@gitorious.org:tmwserv-data/mainline.git | [http://gitorious.org/tmwserv-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the data for TMWServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw-eathena-data eAthena data]''' | git://gitorious.org/tmw-eathena-data/mainline.git | git@gitorious.org:tmw-eathena-data/mainline.git | [http://gitorious.org/tmw-eathena-data/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has the data for our eAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. [[Category:Reference]] j94jjp26x5t8p4nq15iztnlf52grjzf 18533 16160 2011-05-17T09:05:02Z Jaxad0127 999 /* Initial setup */ Update links 18533 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw/tmw Mana branding]''' | git://gitorious.org/tmw/tmw.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[http://gitorious.org/tmw/tmwa-client-data TMW tmwAthena client data]''' | git://gitorious.org/tmw/tmwa-client-data | git@gitorious.org:tmw/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository has the client data for TMW's tmwAthena. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[http://gitorious.org/tmw/server-data TMW server data]''' | git://gitorious.org/tmw/server-data.git | git@gitorious.org:tmw/server-data.git | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw/tmwa-server-data tmwAthena data]''' | git://gitorious.org/tmw/tmwa-server-data.git | git@gitorious.org:tmw/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository has the data for our tmwAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. [[Category:Reference]] 3b8k2odpfsm84k20tqhj2vljrsx0vee 19218 18533 2011-08-05T15:12:45Z Argul 1858 19218 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw/tmw Mana branding]''' | git://gitorious.org/tmw/tmw.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[http://gitorious.org/tmw/tmwa-client-data TMW tmwAthena client data]''' | git://gitorious.org/tmw/tmwa-client-data | git@gitorious.org:tmw/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository has the client data for TMW's tmwAthena. |- | '''[http://gitorious.org/tmw/music TMW music]''' | git://gitorious.org/tmw/music.git | git@gitorious.org:tmw/music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[http://gitorious.org/tmw/server-data TMW server data]''' | git://gitorious.org/tmw/server-data.git | git@gitorious.org:tmw/server-data.git | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw/tmwa-server-data tmwAthena data]''' | git://gitorious.org/tmw/tmwa-server-data.git | git@gitorious.org:tmw/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository has the data for our tmwAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. [[Category:Reference]] hu41cdr5i9oa33iraajou66b65mjz81 23672 19218 2012-05-03T21:32:00Z Frost 1872 /* Initial setup */ Changed some tmwAthena data repos from gitorious to github 23672 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw/tmw Mana branding]''' | git://gitorious.org/tmw/tmw.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | push access on request | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository has the client data for TMW's tmwAthena. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | push access on request | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw/tmwa-server-data tmwAthena data]''' | git://gitorious.org/tmw/tmwa-server-data.git | git@gitorious.org:tmw/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository has the data for our tmwAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. [[Category:Reference]] r8c0w86i8t1wvndeyp0ungmu8rvxzlb 24696 23672 2012-10-16T21:01:16Z Nard 1877 /* git on Windows */ 24696 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- | '''[http://gitorious.org/tmw/tmw Mana branding]''' | git://gitorious.org/tmw/tmw.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | push access on request | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository has the client data for TMW's tmwAthena. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | push access on request | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository has the background music for the client. |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |- | '''[http://gitorious.org/tmw/website TMW website]''' | git://gitorious.org/tmw/website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository has our website. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[http://gitorious.org/tmw/tmwa-server-data tmwAthena data]''' | git://gitorious.org/tmw/tmwa-server-data.git | git@gitorious.org:tmw/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository has the data for our tmwAthena. |- | '''[http://gitorious.org/tmwart TMW Art]''' | git://gitorious.org/tmwart/mainline.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository has some sources for our artwork. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. === git on MacOS X === MacOSX is an unsix system, BSD derived. Git waorks there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer[http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later ( links are on ths same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. [[Category:Reference]] 5bqqd6m1drddxewpb5aodafdujyc7ma 24697 24696 2012-10-17T16:19:10Z Nard 1877 /* Initial setup */ 24697 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@gitorious.org:tmw/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[http://gitorious.org/tmw-eathena eAthena server]''' | git://gitorious.org/tmw-eathena/mainline.git | git@gitorious.org:tmw-eathena/mainline.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@gitorious.org:tmw/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | push access on request | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@gitorious.org:tmwart/mainline.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | push access on request | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@gitorious.org:tmw/website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. === git on MacOS X === MacOSX is an unsix system, BSD derived. Git waorks there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer[http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later ( links are on ths same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. [[Category:Reference]] g05sqcle2f74gdmaqj20dwnd4kjb14l 24702 24697 2012-10-19T22:53:47Z Nard 1877 /* Initial setup */ 24702 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. === git on MacOS X === MacOSX is an unsix system, BSD derived. Git waorks there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer[http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later ( links are on ths same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. [[Category:Reference]] sagi5ivmtxq9kx4c7si6ryghxy7gvn5 24703 24702 2012-10-20T08:09:29Z Nard 1877 /* Working with git */ 24703 wikitext text/x-wiki We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: [[Working With Git]] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. === git on MacOS X === MacOSX is an unsix system, BSD derived. Git waorks there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer[http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later ( links are on ths same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. ===Glossary=== [[Category:Reference]] 2ii2ext87dqwjdog1yiv388t6z3y41f 24704 24703 2012-10-20T08:39:19Z Nard 1877 24704 wikitext text/x-wiki {{status_construction}} We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the origina documentations at [http://git-scm.com/documentation http://git-scm.com/documentatio]n === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''Cola git gui''' === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer[http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later ( links are on ths same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. ===Glossary=== Branch Clone Commit Fork Merge Patch Pull Push Tree [[Category:Reference]] 4vtcspcdm3qvj4hl5jpdwmrr68lii41 24705 24704 2012-10-20T08:41:10Z Nard 1877 /* Warning */ 24705 wikitext text/x-wiki {{status_construction}} We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''Cola git gui''' === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer[http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later ( links are on ths same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. ===Glossary=== Branch Clone Commit Fork Merge Patch Pull Push Tree [[Category:Reference]] 02cqgexg7yaodk7x99zbduwxj95utfi 24706 24705 2012-10-20T08:43:04Z Nard 1877 /* git on MacOS X */ 24706 wikitext text/x-wiki {{status_construction}} We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''Cola git gui''' === git on Windows === When using git on Windows you might use [http://code.google.com/p/msysgit/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. ===Glossary=== Branch Clone Commit Fork Merge Patch Pull Push Tree [[Category:Reference]] djzx7t9uq4np9yb6g22fnqnxudpzxbd 24707 24706 2012-10-20T08:47:51Z Nard 1877 /* git on Windows */ 24707 wikitext text/x-wiki {{status_construction}} We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''Cola git gui''' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. ===Glossary=== Branch Clone Commit Fork Merge Patch Pull Push Tree [[Category:Reference]] tn83mc68wdn2isyrrxgcuaawak2kpje 24708 24707 2012-10-20T08:50:11Z Nard 1877 /* git on Windows */ 24708 wikitext text/x-wiki {{status_construction}} We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''Cola git gui''' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. Gui for windows: [http://windows.github.com/ http://windows.github.com/] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] GitHub has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. ===Glossary=== Branch Clone Commit Fork Merge Patch Pull Push Tree [[Category:Reference]] cg1uvvhltuuevyswkzh07hj7eyphkeo 24709 24708 2012-10-20T16:25:11Z Nard 1877 /* git on MacOS X */ 24709 wikitext text/x-wiki {{status_construction}} We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''Cola git gui''' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. Gui for windows: [http://windows.github.com/ http://windows.github.com/] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub''' has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== Branch Clone Commit Fork Merge Patch Pull Push Tree [[Category:Reference]] dc7nsa5kk0lin1g7r1yw1s11fn4p00e 24714 24709 2012-10-20T18:43:19Z Nard 1877 24714 wikitext text/x-wiki {{status_construction}} We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to take part in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on [http://gitorious.org/ gitorious.org]. Gitorious is a friendly website that is also open source. On Gitorious the main repository for each project is called ''mainline''. Once you click to the mainline repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [http://gitorious.org/search?q=category%3Athe-mana-world list of The Mana World projects] on Gitorious. The projects have different clone URLs for read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. '''Very outdated! see [[How to Develop]] for more current repositories''' {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://gitorious.org/tmw/client-data TMW client data]''' | git://gitorious.org/tmw/client-data.git | git@gitorious.org:tmw/client-data.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the client data for TMW's ManaServ. |- | '''[https://github.com/themanaworld/tmwa-server-data/ TMW server data]''' | git://github.com/themanaworld/tmwa-server-data.git | push access on request | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the server data for TMW's ManaServ. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on Gitorious using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== * Branch * Clone * Commit * Fork * Merge * Patch * Pull * Push * Tree [[Category:Reference]] 7jujvjhqygsz9gdy5scua1jufpy3nqy 24728 24714 2012-10-22T15:31:41Z Nard 1877 24728 wikitext text/x-wiki {{status_construction}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website that is also open source. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/search?utf8=%E2%9C%93&q=the%20mana%20world&type=Everything&repo=&langOverride=&start_value=1 list of The Mana World projects] on '''github'''. The projects have different fork (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://github.com/mana/mana Mana client]''' | git://github.com/mana/mana.git | git@github.com:mana/mana.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the Mana client sources. |- | '''[http://github.com/mana/manaserv Manaserv]''' | git://github.com/mana/manaserv.git | git@github.com:mana/manaserv.git | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the ManaServ server sources . |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on '''github''' using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Tree [[Category:Reference]] 76y9iwd9urd4glrlea6slsisqvskn6t 24729 24728 2012-10-22T15:44:46Z Nard 1877 github links update for both TMW and Mana projects. 24729 wikitext text/x-wiki {{status_construction}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website that is also open source. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://github.com/mana/mana Mana client]''' | git://github.com/mana/mana.git | git@github.com:mana/mana.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the Mana client sources. |- | '''[http://github.com/mana/manaserv Manaserv]''' | git://github.com/mana/manaserv.git | git@github.com:mana/manaserv.git | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the ManaServ server sources . |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on '''github''' using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Tree [[Category:Reference]] fs51ale2hppsmd3mtyz2iif40y7x9oe 24730 24729 2012-10-22T18:34:21Z Nard 1877 /* Glossary */ 24730 wikitext text/x-wiki {{status_construction}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website that is also open source. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Push URL (Developers only) ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | git@github.com:themanaworld/tmw.git | [http://gitorious.org/tmw/tmw.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | git@github.com:themanaworld/tmwa.git | [http://gitorious.org/tmw-eathena/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | git@github.com:themanaworld/tmwa-server-data.git | [https://gitorious.org/tmw/tmwa-server-data.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | git@github.com:themanaworld/tmwa-client-data.git | [https://gitorious.org/tmw/tmwa-client-data.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | git@github.com:themanaworld/tmw-art.git | [http://gitorious.org/tmwart/mainline/commits/master/feed.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | git@github.com:themanaworld/tmw-music.git | [http://gitorious.org/tmw/music/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | git@github.com:themanaworld/themanaworld-website.git | [http://gitorious.org/tmw/website/commits/master/feed.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://github.com/mana/mana Mana client]''' | git://github.com/mana/mana.git | git@github.com:mana/mana.git | [https://gitorious.org/tmw/client-data.atom Atom] |- |colspan=4|This repository contains the Mana client sources. |- | '''[http://github.com/mana/manaserv Manaserv]''' | git://github.com/mana/manaserv.git | git@github.com:mana/manaserv.git | [https://gitorious.org/tmw/server-data.atom Atom] |- |colspan=4|This repository contains the ManaServ server sources . |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes you should clone the "push url", but this requires that you have: # Signed up to gitorious.org # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on Gitorious === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on '''github''' using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Reference]] 7udxczcf52ehhjog899v5mcbvdlbanu 24732 24730 2012-10-23T18:38:44Z O11c 2047 /* Initial setup */ Fix some stuff from the github conversion 24732 wikitext text/x-wiki {{status_construction}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Manasource: Mana, Manaserv.</span> |- | '''[http://github.com/mana/mana Mana client]''' | git://github.com/mana/mana.git | [https://github.com/mana/mana/commits/master.atom Atom] |- |colspan=4|This repository contains the Mana client sources. |- | '''[http://github.com/mana/manaserv Manaserv]''' | git://github.com/mana/manaserv.git | [https://github.com/mana/manaserv/commits/master.atom Atom] |- |colspan=4|This repository contains the ManaServ server sources . |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on '''github''' using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Reference]] s7e3ky36zoh7osr5xh6hif6xlfoe0ks 26187 24732 2013-04-16T19:23:17Z 4144 1626 /* Initial setup */ 26187 wikitext text/x-wiki {{status_construction}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | git://gitorious.org/manaplus/manaplus.git | [https://gitorious.org/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on '''github''' using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Reference]] bkt7rcmozgkjeqpn29dehznwccra1f6 26611 26187 2013-06-07T13:55:15Z Jaxad0127 999 Jaxad0127 moved page [[Git repository]] to [[Dev:Git repository]] 26611 wikitext text/x-wiki {{status_construction}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | git://gitorious.org/manaplus/manaplus.git | [https://gitorious.org/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page === Cloning === If you simply <code>git clone</code> the URL without any additional arguments, it will create the repository in a directory called "mainline". This is generally not what you want. Hence, after the clone url, you should pass the name of the directory you want to have created (just like with Subversion): $ git clone <clone_url> project If you want to have all projects in one place, you probably want to do something like this: $ mkdir tmw $ cd tmw $ git clone git@gitorious.org:tmw/mainline.git tmw $ git clone git@gitorious.org:tmw-eathena-data/mainline.git eathena-data etc. or for all of them in one go (after the cd tmw step): $ for repo in tmw tmwdata tmw-eathena tmw-eathena-data ; do git clone git://gitorious.org/${repo}/mainline.git $repo ; done The way Gitorious works, we can't have one top-level "tmw" project under which we put all these repositories, since they're really separate projects. Gitorious allows multiple repositories for each project, but they are clones of each other (you can only create new ones by cloning existing ones). This allows anybody (not just the development team) to make clones and start hacking on them. Changes can easily be merged from one one repository to another. So instead of all the inconvenience with TMW forks we had in the past, now comes the time to encourage people to clone! ==== Shallow cloning for non-developers ==== One of our repositories, tmwdata, has grown quite large cause of its long history filled with relatively large binary files. If you are only interested in getting the latest version, and have no need to be able to push back changes, then you can make a shallow clone: $ git clone --depth 1 git://gitorious.org/tmwdata/mainline.git tmwdata == Working with git == === Warning=== All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] === Commit === From now on, a commit is something you do locally. Others won't see your change on Gitorious unless you push it there. You'll notice committing is very fast, and you can commit multiple times before you decide to push. You can also make corrections to your last commit. Before you start committing, it is important to identify yourself to git, so that it can include the correct authorship information with your commit. You are no longer identified with a username, as was the case with Subversion. You can read exactly how to do this, as well as other useful information geared towards people switching from Subversion, on this page: * '''Git - SVN Crash Course:''' http://git.or.cz/course/svn.html Sample commit message: This is the title. Keep this line short. This is a longer description of the commit, if needed. Keep these lines short too. A sample list: <nowiki>* Item 1</nowiki> <nowiki>* Item 2</nowiki> <nowiki>* Item 3</nowiki> Another paragraph in the commit description. Blah blah blah. === Pushing === Once you have committed some stuff, you can push these to the repository on '''github''' using <code>git push</code>. This works since by default the push command pushes to a ''remote'' called ''origin'', and this remote is automatically set up when you clone. However, the push will fail if there have been new commits on the remote repository. In that case, you'll first have to pull in these changes (just like with Subversion, however Subversion allowed this as long as the same files weren't touched, git doesn't). === Pulling === When you want to get the latest changes from the repository on Gitorious, you generally use <code>git pull</code>. However, note that this command does not work when you have local changes. Also, when you have local commits, the pull command will generate a merge commit (and before that you may have to resolve some conflicts). If you don't want to create merge commits, but would rather stack your local commits on top of any incoming commits, you should use <code>git pull --rebase</code>. This ''rebases'' your local commits on top of the incoming ones. You should never do this when you have pushed these commits elsewhere, so only do it when you are sure the commits are only on your machine. If you have local changes and want to update your checkout, then there are several options: * You commit your local changes, and do a pull, optionally with --rebase. * Or you use <code>git stash</code> to place your local changes on a "hidden" stash. Then, after pulling, you apply your changes again with <code>git stash apply</code>. * Or you create a patch of your local changes that you apply again after the pull. This approach sometimes makes sense, but I would say in general it's the more clumsy way to go. There are git commands that help you with this though. === Resolving conflicts === Rather similar to Subversion. When there are conflicts, a merge or a rebase will add conflict markers into files. Use <code>git status</code> to see which files remain in conflict and use <code>git add</code> on files to mark them as resolved. When you did a merge and you have resolved all conflicts, you commit. When you were doing a rebase of several commits, you do <code>git rebase --continue</code> instead. === Patch making === Git has an easy way to send patches to other people to review and commit for you. After you have made a commit, <code>git format-patch</code> will make a patch out of it. The patch includes your author information the commit message you gave, and all the changes to be done. The recipient can just <code>git am [patch file]</code> to apply the commit. After it has been pushed, you'll need to remove the patch from your local repository, <code>git reset --hard HEAD^</code> will do that. If you don't do that, you'll get a conflict when your patch is pulled from the central repository. === Good to know === Git has several useful commands to figure out the current state of your repository, your files and what recently changed. Below is a non-exhaustive list of commands that are useful to know: * '''git branch''': Without any parameters, this command lists your local branches, and indicates which branch you're currently on. * '''git whatchanged''': This shows a list of all commits on the current branch similar to <code>git log</code>, but with a list of the files that have been touched in each commit as well. * '''git status''': This shows all kind of things about your current checkout: which files changed, untracked (unknown) files, added or removed files, files that have conflicts (during merge), etc. It also shows the status of your index, which is what git will commit once you do <code>git commit</code>. If you're new to git I would recommend to wait a bit with learning how to use the index, but not to avoid it forever. There are also additional applications that help you with using git: * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Reference]] bkt7rcmozgkjeqpn29dehznwccra1f6 30733 26611 2014-06-12T02:37:38Z Wushin 2233 /* way up to date */ 30733 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | git://gitorious.org/manaplus/manaplus.git | [https://gitorious.org/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page == Working with git == All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] While the information included here is not false, a more up to date page has been written with the latest information: :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Reference]] 134qlutrg6ontm4b3l3jipet7o4olys 30734 30733 2014-06-12T02:38:02Z Wushin 2233 /* Working with git */ 30734 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | git://gitorious.org/manaplus/manaplus.git | [https://gitorious.org/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page == Working with git == All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Reference]] rw7nwqz5tlrc376bx74bp6xuhxht87t 31837 30734 2014-12-17T16:16:46Z Wushin 2233 /* categorizing */ 31837 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | git://gitorious.org/manaplus/manaplus.git | [https://gitorious.org/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page == Working with git == All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Reference]] [[Category:Development]] cu584tb1xtnpaftco0jfsfb99dh7cy7 33702 31837 2015-03-11T08:24:29Z Cassy 2265 removing category 33702 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | git://gitorious.org/manaplus/manaplus.git | [https://gitorious.org/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page == Working with git == All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] dxmro0fx68tkkw9f8644nc32v2b9upd 39924 33702 2015-11-09T12:36:43Z Gumi 2315 /* Initial setup */ 39924 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | https://gitlab.com/manaplus/manaplus.git | [https://gitlab.com/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page == Working with git == All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] 08zh7wv77mcg6xbv6m7w8cnaiw5mmpb 40601 39924 2016-08-05T18:13:28Z Tomminator 1470 40601 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github and later to gitlab. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- | '''[https://github.com/themanaworld/tmw-branding TMW branding]''' | git://github.com/themanaworld/tmw-branding.git | [https://github.com/themanaworld/tmw-branding/commits/master.atom Atom] |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | https://gitlab.com/manaplus/manaplus.git | [https://gitlab.com/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page == Working with git == All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] s93tma5gsdlsrah37a55nvgu6nfvaml 40609 40601 2016-08-11T01:38:51Z 4144 1626 remove outdated branding link 40609 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github and later to gitlab. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://github.com/ github.com]'''. '''github''' is a friendly website. On '''github''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, so you can easily see the complete [https://github.com/themanaworld list of The Mana World projects] on '''github'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. The list below is for your convenience. {|border="1" cellspacing="0" cellpadding="5" ! Project ! Read-only URL ! Atom feed |- |colspan=4| <span style="color:White; background:Sienna">TMW, TMW eAthena</span> |- |colspan=4|This repository contains the branding files to turn Mana into TMW. |- | '''[https://github.com/themanaworld/tmwa.git eAthena server]''' | git://github.com/themanaworld/tmwa.git | [https://github.com/themanaworld/tmwa/commits/master.atom Atom] |- |colspan=4|This repository contains our hacked up eAthena. |- | '''[https://github.com/themanaworld/tmwa-server-data tmwAthena Server data]''' | git://github.com/themanaworld/tmwa-server-data.git | [https://github.com/themanaworld/tmwa-server-data/commits/master.atom Atom] |- |colspan=4|This repository contains the server data developed for the tmwAthena server and used by The Mana World. |- | '''[https://github.com/themanaworld/tmwa-client-data TMW tmwAthena client data]''' | git://github.com/themanaworld/tmwa-client-data.git | [https://github.com/themanaworld/tmwa-client-data/commits/master.atom Atom] |- |colspan=4|This repository contains the data used by The Mana World clients for the tmwAthena server. . |- | '''[https://github.com/themanaworld/tmw-art TMW Art]''' | git://github.com/themanaworld/tmw-art.git | [https://github.com/themanaworld/tmw-art/commits/master.atom Atom] |- |colspan=4|This repository contains some sources for our artwork. |- | '''[https://github.com/themanaworld/tmw-music TMW music]''' | git://github.com/themanaworld/tmw-music.git | [https://github.com/themanaworld/tmw-music/commits/master.atom Atom] |- |colspan=4|This repository contains the music used by The Mana World clients for the tmwAthena server. |- | '''[https://github.com/themanaworld/themanaworld-website TMW website]''' | git://github.com/themanaworld/themanaworld-website.git | [https://github.com/themanaworld/themanaworld-website/commits/master.atom Atom] |- |colspan=4|This repository contains the website of The Mana World. |- |colspan=4|<span style="color:White; background:Sienna">Official client: ManaPlus.</span> |- | '''[https://gitorious.org/manaplus/manaplus/ ManaPlus client]''' | https://gitlab.com/manaplus/manaplus.git | [https://gitlab.com/manaplus/manaplus.atom Atom] |- |colspan=4|This repository contains the ManaPlus client sources. |} For the Mana (the client) and Manaserv, look at http://doc.manasource.org/git_repository. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to github.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitHub # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page == Working with git == All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] gs45mwon8a8255swgtcssuye61pm7gd 55248 40609 2022-01-23T19:13:30Z Jesusalva 2520 Remove tmwa content and update 55248 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitorious.org/about Gitorious] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github and later to gitlab. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://gitlab.com/ gitlab.com]'''. '''gitlab''' is a friendly website. On '''gitlab''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, as well as the repositories for each project, so you can easily see the complete [https://gitlab.com/themanaworld list of The Mana World projects] on '''gitlab'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. We still host some content on [https://github.com/themanaworld GitHub] and on [https://gitlab.com/evol Evol's GitLab]. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to gitlab.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitLab # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page You can also push over HTTPS but that's not advised, and will require configuring a push token. == Working with git == All TMW specific repositories have been now moved to github:[https://github.com/themanaworld https://github.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] f2da0gvx13gzammt02a0i23r2xwwoyc 55249 55248 2022-01-23T19:16:12Z Jesusalva 2520 GitLab update 55249 wikitext text/x-wiki ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitlab.com/ GitLab] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github and later to gitlab. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://gitlab.com/ gitlab.com]'''. '''gitlab''' is a friendly website. On '''gitlab''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, as well as the repositories for each project, so you can easily see the complete [https://gitlab.com/themanaworld list of The Mana World projects] on '''gitlab'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. We still host some content on [https://github.com/themanaworld GitHub] and on [https://gitlab.com/evol Evol's GitLab]. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to gitlab.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitLab # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page You can also push over HTTPS but that's not advised, and will require configuring a push token. == Working with git == All TMW specific repositories have been moved to github: [https://github.com/themanaworld https://github.com/themanaworld] Most were later moved to GitLab, but not all of them: [https://gitlab.com/themanaworld https://gitlab.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. Commiting Windows Newlines causes changes to be rejected by the linter. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] Both GitHab and GitLab have a Web IDE. === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] bbidwmnllmzarbz8rw46nd05k9sige8 59440 55249 2024-02-12T19:11:08Z Jesusalva 2520 Legacy namespace prevails 59440 wikitext text/x-wiki {{category:outdated}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitlab.com/ GitLab] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github and later to gitlab. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://gitlab.com/ gitlab.com]'''. '''gitlab''' is a friendly website. On '''gitlab''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, as well as the repositories for each project, so you can easily see the complete [https://gitlab.com/themanaworld list of The Mana World projects] on '''gitlab'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. We still host some content on [https://github.com/themanaworld GitHub] and on [https://gitlab.com/evol Evol's GitLab]. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to gitlab.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitLab # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page You can also push over HTTPS but that's not advised, and will require configuring a push token. == Working with git == All TMW specific repositories have been moved to github: [https://github.com/themanaworld https://github.com/themanaworld] Most were later moved to GitLab, but not all of them: [https://gitlab.com/themanaworld https://gitlab.com/themanaworld] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. Commiting Windows Newlines causes changes to be rejected by the linter. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] Both GitHab and GitLab have a Web IDE. === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] m395ksqmh83bxx3769duihla5120c3a 59441 59440 2024-02-13T12:58:56Z Jesusalva 2520 /* Working with git */ Fix missing link 59441 wikitext text/x-wiki {{category:outdated}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitlab.com/ GitLab] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github and later to gitlab. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://gitlab.com/ gitlab.com]'''. '''gitlab''' is a friendly website. On '''gitlab''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, as well as the repositories for each project, so you can easily see the complete [https://gitlab.com/themanaworld list of The Mana World projects] on '''gitlab'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. We still host some content on [https://github.com/themanaworld GitHub] and on [https://gitlab.com/evol Evol's GitLab]. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to gitlab.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitLab # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page You can also push over HTTPS but that's not advised, and will require configuring a push token. == Working with git == All TMW specific repositories have been moved to github: [https://github.com/themanaworld https://github.com/themanaworld] Most were later moved to GitLab, but not all of them: [https://gitlab.com/themanaworld https://gitlab.com/themanaworld] And as of 2024 everything which doesn't use GitHub Pages or GitLab Pages is on [https://git.themanaworld.org/explore/groups https://git.themanaworld.org/explore/groups] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. Commiting Windows Newlines causes changes to be rejected by the linter. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] Both GitHab and GitLab have a Web IDE. === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] igj7w94x7ls2xyke1w41hnex4kn8owt 59488 59441 2024-03-27T03:56:43Z Move page script 2739 Move page script moved page [[Dev:Git repository]] to [[Development:Git repository]]: Rename Dev: to Development: so the miraheze import works 59441 wikitext text/x-wiki {{category:outdated}} ==Git== '''git''' is the name of the program intended to allow a team to work on a set of program sources, keep versions synchrone and make members team work easily known from others. [https://gitlab.com/ GitLab] and [https://github.com/ github] are websites that provide free hosting of public git repositories. At some point we moved the content repositories from gitorious to github and later to gitlab. See this forum topic [http://forums.themanaworld.org/viewtopic.php?p=121526#p121526] for reference. (Note server code was transferred to github since it was written) We are using the version control system Git as our main collaboration tool. You can use it to obtain all the sourcecode and content files you need to participate in the development or to create your own fork. See [http://en.wikipedia.org/wiki/Git_(software) the wikipedia article about Git] and [http://git-scm.com/ the Git homepage] for details about Git. In TMW wiki, information about Git is still located in several places where you may find contradictory information. We do apologize for that and work hard to let you have a clear information: * '''This page''': The actual links to various repositories should be up to date but some information about how to work with it is not.It still contains useful information and GUI's information should be correct. * '''[[How to Develop]]''' also duplicates some info which you can find else where. It will be completely re-written to make it the entry point of the wiki development part. * '''[[Working With Git]]''' contains the most up to date information to use Git with the command line. ''It is the actual reference that you should follow''. It is important to read it even if you plan to use a graphical user interface. == The primary repository == === Initial setup === With Git, we'll have one repository for each project. The central repositories through which we cooperate are hosted on '''[https://gitlab.com/ gitlab.com]'''. '''gitlab''' is a friendly website. On '''gitlab''' the main repository for each project is called ''master''. Once you click to the master repository, you can see several ways to clone it (the new <code>svn checkout</code>). We've categorized all projects related to The Mana World, as well as the repositories for each project, so you can easily see the complete [https://gitlab.com/themanaworld list of The Mana World projects] on '''gitlab'''. The projects have different forks (clone) URLs for browsing, read-only or developer access. The URL for developer access is called the "push URL", since it allows you to push commits into the repository via ssh. We still host some content on [https://github.com/themanaworld GitHub] and on [https://gitlab.com/evol Evol's GitLab]. Git uses ssh's private/public key authentication for identifying committers. For development purposes just clone the read-only URL, it will automatically switch to the push URL if you have: # Signed up to gitlab.com # Generated a private/public ssh keypair (if you haven't got this already) # Filled in your public key in your account details on GitLab # Been added with commit rights to the repository # Followed the directions in the [How to Develop] page You can also push over HTTPS but that's not advised, and will require configuring a push token. == Working with git == All TMW specific repositories have been moved to github: [https://github.com/themanaworld https://github.com/themanaworld] Most were later moved to GitLab, but not all of them: [https://gitlab.com/themanaworld https://gitlab.com/themanaworld] And as of 2024 everything which doesn't use GitHub Pages or GitLab Pages is on [https://git.themanaworld.org/explore/groups https://git.themanaworld.org/explore/groups] :::'''[[Working With Git]]''' You may also have a look to the original documentation at [http://git-scm.com/documentation http://git-scm.com/documentation] * '''gitk''': A simple but effective tool that visualizes the history and some of your current state. Run with <code>--all</code> to have it show all branches, otherwise it will just show stuff relevant to your current branch. * '''tig''': A textual interface, rather similar to an email reader. * '''git gui''': A gui tool like gitk which helps you prepare and perform your commits. Also makes it easier to understand the index concept. * '''Giggle''' * '''qgit''' * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html]' === git on Windows === When using git on Windows you might use [http://msysgit.github.com/ msysgit]. If you notice that some files seem to have changed after doing a fresh clone, you may want to disable <code>core.autocrlf</code> using <code>git config core.autocrlf false</code>. However, this is not recommended for contributors since the setting makes sure you don't commit Windows style newlines into the repository. Commiting Windows Newlines causes changes to be rejected by the linter. When encountering this problem it is usually best to consult other developers about the affected files. GitHub works uses the same tools as Git. :'''GUIs''' * '''GitHub for Windows''' : [http://windows.github.com/ http://windows.github.com/] * '''Git Extensions''' : [http://code.google.com/p/gitextensions/ http://code.google.com/p/gitextensions/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] Both GitHab and GitLab have a Web IDE. === git on MacOS X === MacOSX is an unix system, BSD derived. Git works there mostly as on Linux systems. Go to the [http://git-scm.com/downloads official download site: http://git-scm.com/downloads] and choose the OS X link, download and install. You also may prefer [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/] and add a graphical user interface later (links are on the same pages). Xcode and X11 are required if you want to install from sources. French users may also like: [https://gist.github.com/656299 https://gist.github.com/656299] :'''GUIs''' * '''GitHub for Mac''' github has it's own application that you can find at [http://mac.github.com/ http://mac.github.com/]. Among others, it has a very nice feature to be able to pull and push in one operation. * '''GitX''' : [http://gitx.laullon.com/ http://gitx.laullon.com/] * '''SourceTree''' : [http://www.sourcetreeapp.com/ http://www.sourcetreeapp.com/] * '''git-cola''' : [http://git-cola.github.com/ http://git-cola.github.com/] * '''SmartGit''' : [http://www.syntevo.com/smartgit/index.html http://www.syntevo.com/smartgit/index.html] ===Glossary=== You may like this very nice interactive memo: '''[http://ndpsoftware.com/git-cheatsheet.html git-cheatsheet]''' by [https://github.com/ndp Andrew Patterson] from NDP software. * Branch * Clone * Commit * Fork * Mainline * Master * Merge * Origin * Patch * Pull * Push * Stash * Tree [[Category:Development]] igj7w94x7ls2xyke1w41hnex4kn8owt 0 958 275 2005-05-23T12:45:29Z Mra 2 ported Guidelines page over from old wiki 275 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. ''-Rotonen'' 1gtgbglhrkp7rchza6tn6lhsv0lsqmv 701 275 2005-06-19T22:05:07Z 202.123.18.3 /* Concerning tiles */ 701 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. ''-Rotonen'' *All the tiles in a set needs some coerance: **The direction of the light ''(Sout-West?)'' **''(Please add more guidelines)'' n5ve3l3s0unlny0apphi6lutqsq75gn 703 701 2005-09-06T02:38:05Z Crush 103 /* Concerning tiles */ 703 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *you can find the technical specifications of tilesets under [[Tileset development]] *Please keep in mind that the mapper only got 3 layers from which 2 are under all moving objects and 1 is over all moving objects. *althrough we prefer high quality tiles over low quality ones, please keep in mind that we try to reassemble the look of old SNES games. so please try not to make the tiles too realistic. *All the tiles in a set needs some coerance: **The direction of the light (south-west for outdoor tilesets, diffuse light for indoor tilesets) **The perspective (45° view angel?) **The propotions (a character is one tile wide and two tiles high) **The color style **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. **''(Please add more guidelines)'' 58ykry8392gog7m7eidkgv41idio8ds 724 703 2005-09-06T08:05:26Z ElvenProgrammer 11 typo 724 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *you can find the technical specifications of tilesets under [[Tileset development]] *Please keep in mind that the mapper only got 3 layers from which 2 are under all moving objects and 1 is over all moving objects. *althrough we prefer high quality tiles over low quality ones, please keep in mind that we try to reassemble the look of old SNES games. so please try not to make the tiles too realistic. *All the tiles in a set needs some coerance: **The direction of the light (south-west for outdoor tilesets, diffuse light for indoor tilesets) **The perspective (45° view angle?) **The propotions (a character is one tile wide and two tiles high) **The color style **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. **''(Please add more guidelines)'' 1rlnmk0dwjh1o6uha12bumpf2yenaq7 740 724 2005-09-09T15:02:21Z ElvenProgrammer 11 /* Concerning tiles */ Updated guidelines 740 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid use filters such as blur. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The propotions: a character is one tile wide and two tiles high. **The color style: avoid using weird "alien" colors (keep saturation low :P) **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif ---- All the images have been taken from the [http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools enterbrain tutorial]. I suggest every pixel artist to take a look at it since is both a good tutorial and a style reference. opcol5cj41d2lxjw1hd79njyvvdpmv2 741 740 2005-09-11T16:01:40Z Crush 103 741 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid use filters such as blur. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The propotions: a character is one tile wide and two tiles high. **The color style: avoid using weird "alien" colors (keep saturation low :P) **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif ---- All the images have been taken from the [http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools enterbrain tutorial]. I suggest every pixel artist to take a look at it since is both a good tutorial and a style reference. Another very good tutorial in english language about pixel art is the legendary tutorial [http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. s3vqs0xuc13inkx8ypv77l70um2socd 742 741 2005-09-11T16:24:04Z Crush 103 742 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The propotions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. *[http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/3_01.ht Enterbrain Tutorial] ([http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools translation by google]). all the above images have been taken from this tutorial. niy2zuaj2vajucqia6a9zxb2cxp2m9f 743 742 2005-09-11T16:29:31Z Crush 103 /* Tutorials */ 743 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The propotions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. *([http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools (translated by google)]). all the above images have been taken from this tutorial. oll5oht47qdkwx36iegoljdz9pl608l 744 743 2005-09-11T16:30:15Z Crush 103 /* Tutorials */ 744 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The propotions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. *([http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]). all the above images have been taken from this tutorial. 8pfq7h1ghwhxebay587wab4d5qtg0hb 745 744 2005-09-11T16:30:41Z Crush 103 /* Tutorials */ 745 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The propotions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. pcc2h1n8xbpe8iijpcbg75woc3ubawg 746 745 2005-09-11T16:40:38Z Crush 103 /* Concerning tiles */ 746 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The propotions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. 1kmi2xps5srzjuhnrd8jhwkyr0xven9 2020 746 2005-09-11T16:40:59Z Crush 103 /* Concerning tiles */ 2020 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on freenode 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions: so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic athmosphere, look and color scheme of a certain place or define the looks of an important npc. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The propotions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. 3c3x7vtjljbun2sxy3shtrocjs7jqhc 3010 2020 2005-11-09T03:17:14Z Metalcore 165 english 3010 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. sj6fzn96ysdzh8w29xgqhsa9z7xvxax 3014 3010 2005-11-09T13:53:03Z Modanung 8 Tsugumo's host expired. 3014 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://tsugumo.swoo.net/tutorial/ So You Want To Be A Pixel Artist] by Tsugumo. The domain seems to be expired, Zoggles also hosted this tutorial [http://www.zoggles.co.uk/asp/tutorials.asp?tut=17 here]. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. lx74p0atcop4xj1ouwxgbqd9h2h7809 3024 3014 2005-11-11T02:33:21Z Crush 103 /* Tutorials */ 3024 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.zoggles.co.uk/asp/tutorials.asp?tut=17 So You Want To Be A Pixel Artist] by Tsugumo. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. p1nxgr09undwkyrn5whbapfglkbjyok 4323 3024 2006-07-17T16:36:32Z Modanung 8 Zoggle's site seems to be down. 4323 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. 97drrn4z7fpo7wh2tcmcgdziailnlit 4687 4323 2006-08-16T14:19:51Z Crush 103 /* Concerning tiles */ added guidelines for dropshadows 4687 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **Drop shadows: large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. 93d0rd4jda46x3xd5vgytypmc04ukpd 5146 4687 2006-09-24T19:47:26Z Yosuhara 324 added new tutorials 5146 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **Drop shadows: large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] ehipqqn9h24sxs8jwsl4fj8hlvu4xew 5168 5146 2006-09-29T14:37:39Z VxD 517 /* Tutorials */ 5168 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **Drop shadows: large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] gryexpzbxpo5x6s0bpb35nufntsztgz 5169 5168 2006-09-29T14:43:53Z VxD 517 /* Tutorials */ 5169 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **Drop shadows: large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [www.pixeljoint.com]. 7pyn66ddrl3qeonni3zzsc9srpdxww5 5170 5169 2006-09-29T14:44:25Z VxD 517 /* Tutorials */ 5170 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **Drop shadows: large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com]. orer17drfpstztc1tnkwm2lhyq28vtg 5171 5170 2006-09-29T14:54:27Z VxD 517 /* Tutorials */ 5171 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **Drop shadows: large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. 2ltrmlhx23f1609ljdnvrzh77h3n1u3 5174 5171 2006-09-29T20:59:32Z Yosuhara 324 /* Tutorials */ 5174 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **Drop shadows: large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. 7s971si3iy02eemrxbmfnebpsbkb3ri 5175 5174 2006-09-29T21:07:55Z Yosuhara 324 /* Tutorials */ 5175 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **The direction of the light: south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **The perspective: top-down 45° view angle (if in doubt, take a look at current screenshots or search for Secret of Mana screenshots). **The proportions: a character is one tile wide and two tiles high. **The color style: try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **Drop shadows: large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com/pixels/links.asp?id=2192], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. 5maytmajniajy86exhxcfe6v3vp1xd0 5205 5175 2006-10-03T13:47:02Z Bjørn 3 /* Concerning tiles */ 5205 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **'''Light direction:''' south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **[[Image:Perspective-schematic.png|right|150px]]'''Perspective:''' top-down 45° view angle (see the schematic to the right, the thick gray line is the length with which the side and bottom are perceived, a factor of 0.7 smaller). **'''Proportions:''' a character is approximately one tile wide and two tiles high. **'''Color style:''' try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **'''Drop shadows:''' large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **'''Reuse:''' The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com/pixels/links.asp?id=2192], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. nqijoya5blj0wnrmwtrgp3dgsv8nr8y 5909 5205 2007-01-26T00:36:52Z Yosuhara 324 5909 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **'''Light direction:''' south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **[[Image:Perspective-schematic.png|right|150px]]'''Perspective:''' top-down 45° view angle (see the schematic to the right, the thick gray line is the length with which the side and bottom are perceived, a factor of 0.7 smaller). **'''Proportions:''' a character is approximately one tile wide and two tiles high. **'''Color style:''' try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **'''Drop shadows:''' large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **'''Reuse:''' The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://http://www.spriteart.com/main.html great st0ven's site] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com/pixels/links.asp?id=2192], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. 9esqipavgi0jfr8mk7k8iwwc9ma9wrq 5910 5909 2007-01-26T00:37:06Z Yosuhara 324 5910 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **'''Light direction:''' south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **[[Image:Perspective-schematic.png|right|150px]]'''Perspective:''' top-down 45° view angle (see the schematic to the right, the thick gray line is the length with which the side and bottom are perceived, a factor of 0.7 smaller). **'''Proportions:''' a character is approximately one tile wide and two tiles high. **'''Color style:''' try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **'''Drop shadows:''' large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **'''Reuse:''' The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://http://www.spriteart.com/main.html Great st0ven's site] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com/pixels/links.asp?id=2192], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. 7bvdv6eluwggwprml1isf00ubh2vo7c 5917 5910 2007-01-26T15:12:12Z Crush 103 /* Tutorials */ fixed link 5917 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == *We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. *Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. *You can find the technical specifications of tilesets here: [[Tileset development]] *Please keep in mind that a mapper has got only 3 layers: 2 of them are always displayed below players and monsters while the other one is displayed always above. The lowest layer is usually used for ground tiles/walls, and since the limited number of layers, ground tiles should be non-transparent even if this increase a lot the number of tiles in a tileset. Transparent tiles should be only used for objects you can place in different places with different backgrounds such as plants, barrels, ... It is preferrable that cups, and food and whatever else stands on a table is drawn with the table tile below it. Paintings shouldn't have transparent borders, but wall behind them. (if you plan to use for example paintings in different tileset, save them elsewhere as transparent objects and then reapply them to another tile). *Although we prefer high quality tiles over low quality ones, please keep in mind that we try to resemble the look of old SNES games. So please try not to make the tiles too realistic. This mean please don't use textures you get from reality, such a picture of a wooden piece and use it for your tiles. We strongly encourage you to manually pixelate every tile and avoid to use gradients or filters such as blur too excessive. *All the tileset should use some coherence: **'''Light direction:''' south-west for outdoor tilesets (of course there will be exceptions: different (or special) areas could have a different direction of light to give it a subtle different feeling, such as lava caves with subtle orange light from the bottom, and deep in the dark forest with glowing mushrooms), diffuse light for indoor tilesets diffused light is nice, but overusage could lead into problems with contrast between the inside and the outside. **[[Image:Perspective-schematic.png|right|150px]]'''Perspective:''' top-down 45° view angle (see the schematic to the right, the thick gray line is the length with which the side and bottom are perceived, a factor of 0.7 smaller). **'''Proportions:''' a character is approximately one tile wide and two tiles high. **'''Color style:''' try to use the same color palette for the whole tileset. the selection of color is important for the feeling of the tileset. weak colors with a high amount of grey for example are good for a sad and cold feeling while bright colors create a happy and warm atmosphere. whatever atmosphere you choose: it should be consistent through the whole tileset. avoid using weird "alien" colors (keep saturation low :P). **'''Drop shadows:''' large objects on outdoor tilesets (like buildings, for example) should have drop shadows cast to the northeast. The shadows should be pure black with an opacity of 30%. the edges of the shadows should only have an opacity of 15%. **'''Reuse:''' The tiles in one tileset should be able to be put together in as many different ways as possible to allow the mapper to express his creativity. This is the base requirement for: *** Borders between different heights: http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/05/8.gif ***Fences http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/053.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/052.gif http://www.enterbrain.co.jp/digifami/digiweb/dot_teck/3nen/04/054.gif (please note that the above pictures are only for demonstrational purpose. they are copyrighted and not part of the mana world project). == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com/pixels/links.asp?id=2192], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. bgcmf9ihll34ls150a0rjblj7xx4kj4 5990 5917 2007-02-05T07:44:14Z Crush 103 moved the tileset guidelines to "Tileset development" 5990 wikitext text/x-wiki == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com/pixels/links.asp?id=2192], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. 3n541cgu2a0oxx8xkoaap1jxxpbwmeg 6207 5990 2007-03-04T12:32:39Z Pauan 473 Added in reference template. 6207 wikitext text/x-wiki {{Status_green}} == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *others : [http://www.pixel-arts.org/pixelation/index.php?topic=222.0], [http://www.pixeljoint.com/pixels/links.asp?id=2192], [http://pixel-zone.rpgdx.net/shtml/tutorials.shtml]. qzrr90hrlmtoylusimxyk584o7mbf57 6242 6207 2007-03-06T00:53:10Z Bjørn 3 Removed dead link 6242 wikitext text/x-wiki {{Status_green}} == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] iixa0y5dyeizwdhxal418nuw87cz7yu 9697 6242 2008-07-03T14:47:54Z EJlol 294 /* Tutorials */ 9697 wikitext text/x-wiki {{Status_green}} == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] bfbepsrn2gnadmwl7ybxauul13omee4 10371 9697 2008-10-18T15:02:50Z Octalot 1267 How to get your content in to the game 10371 wikitext text/x-wiki {{Status_green}} == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] l63c71vl7rpjzbvzbxbuwhlp0de5cs1 10630 10371 2008-11-08T22:13:04Z Octalot 1267 Link to EJLol's proposed updated version 10630 wikitext text/x-wiki {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] py1ty4hj2buxkri65cknj2pmhjpr8nk 11050 10630 2008-12-19T07:27:59Z CnaliGetol 1402 varalrolrel 11050 wikitext text/x-wiki vidaracouv {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] cocnx5htv6ub3738lrughufqhtogruf 11057 11050 2008-12-19T15:53:56Z Jaxad0127 999 Revert vandalism 11057 wikitext text/x-wiki {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] py1ty4hj2buxkri65cknj2pmhjpr8nk 11335 11057 2009-01-08T15:32:10Z CnaliGetol 1402 http://spfortne.qsh.eu/20090105-a-term-of-endearment.html 11335 wikitext text/x-wiki [http://spfortne.qsh.eu/20090105-a-term-of-endearment.html a term of endearment movie quotes] [http://golxando.0lx.net/1086026749.html remedy music video code] [http://dronoubr.0lx.net/rip-audio-from.html rip audio from a video] [http://varpasz.is-the-boss.com/article848.htm iowa dot drivers license] [http://chifire.strefa.pl/news-1978.html larry king interview gordon b hinkley video audio] {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] k0zkryrahjfrapw34p3yiv8fvmjnq4q 11396 11335 2009-01-08T16:20:39Z EJlol 294 Undo revision 11335 by [[Special:Contributions/CnaliGetol|CnaliGetol]] ([[User talk:CnaliGetol|Talk]]) 11396 wikitext text/x-wiki {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] py1ty4hj2buxkri65cknj2pmhjpr8nk 11665 11396 2009-02-15T08:07:08Z Haay 1512 11665 wikitext text/x-wiki {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist] by Tsugumo. (more recent version [http://www.geocities.com/skulkraken2002/]) *[http://translate.google.com/translate?u=http%3A%2F%2Fwww.enterbrain.co.jp%2Fdigifami%2Fdigiweb%2Fdot_teck%2F3nen%2F3_01.html&langpair=ja%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Enterbrains Tutorial (translated from Japanese by Google)]. all the above images have been taken from this tutorial. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://derekyu.com/extras/pixel01.html Derek Yu's Pixel Art Tutorial] *[http://www.spriteart.com/main.html Great st0ven's site] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] *[http://www.youtube.com/watch?v=01cwLgigJRc&feature=related| Pixel Art Tutorial: Tree (Youtube Video)] l2uig904je17x3hqywmoj7j4m4oa86r 11666 11665 2009-02-15T12:25:35Z Crush2 1261 Removed/updated dead tutorial links, removed the youtube video which just sucks art-wise. 11666 wikitext text/x-wiki {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.geocities.com/skulkraken2002/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] 4on7myddxy9f20t1te82v6ttupsy2rg 11822 11666 2009-03-12T11:17:23Z Irukard 32 /* Tutorials */ New link to tutorial 11822 wikitext text/x-wiki {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.geocities.com/skulkraken2002/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] tty29wz8rvfj97meks67htb70qmx0ac 13831 11822 2009-11-23T19:48:59Z Crush 103 fixed broken link 13831 wikitext text/x-wiki {{Status_green}} A new revision of this page is being developed in [[User:EJlol/Guidelines]] == In general == *Don't be afraid to show us your unfinished pieces, we are there to guide and help you through the process. *If possible, hang around the #tmwart channel on irc.freenode.net 24/7. *When you're available / doing work on tmw related stuff, please contact me on the previously mentioned channel. *We're soon going to have a centralized repository for all the art related stuff where we're going to archive all of your versions, so you can just start to contribute there without the need to track down a dev. The details on the repository and the preferred version numbering are coming soon. EDIT(20050419): Ask me for details, it's up now. *Preferred formats: .png and .ogg == Concerning conceptual art == *You can always come up with new ideas to present to the team. Actually that's preferred and we like that. *With conceptual art you might want to define important places, capture the generic atmosphere, look, and color scheme of a certain place or define the looks of an important NPC. == Concerning tiles == We REALLY need a LOT of these, so if you think you can do ANYTHING, please give it a shot. Especially on these actively seek out our attention so we can assign new tasks to you. The fact that we won't contact you personally every day doesn't mean we don't need your efforts. You can find the technical specifications of tilesets and further tile related guidelines in the article [[Tileset development]]. == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 1i87tfscxsq6kzmm0azbnx5y2pbg6cs 13874 13831 2009-12-05T20:20:26Z Crush 103 replaced the guidelines with the new version we developed under supervision of EJlol 13874 wikitext text/x-wiki {{Status_green}} When you create pixel art for TMW please follow these guidelines. Pixelart which does not follow these guidelines has less chance to get into the game. === General === * All graphics must be released under the GNU General Public License or a compatible license. * Try to hang around in our art development IRC channel #tmw-art on irc.freenode whenever possible * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing * Do not be afraid to show us your pixelart, we are there to guide and help you. Pixelart being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * A list of pixelart tutorials can be found [[User:EJlol/Tutorials|here]]. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Outlines: 1px, Coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Beings(players,monsters) and item icons level: stands out the most (heavily saturated with dark outlines) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Light Direction: South-West ([[:Image:Lightdirection.png|Example]]) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti Aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * You may mirror the creature sprites, as long as the lighting is correct * There is no size restriction, please go berserk === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPC's should be in the same style as the player sprites. ** NPC's do not and should not be constrained by player pose and body shape. For example, the startrek sprites are done in the same style as players, but strike a different pose. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. ** Some NPCs not in the same style as the player sprites may be accepted if appropriate. (For example, Santa) === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the New Forest Tileset as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for 'here is nothing' indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: New Forest Tileset ** Indoor: ??? ** Dungeons: ??? * All tiles on a single tileset should have the same warm / cold feeling. * When contributing to a other tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] s2y09g2bujsgut9ofxl1oefpualnac8 14481 13874 2009-12-31T21:28:23Z Bcs86 1568 /* General */ 14481 wikitext text/x-wiki {{Status_green}} When you create pixel art for TMW please follow these guidelines. Pixelart which does not follow these guidelines has less chance to get into the game. === General === * All graphics must be released under the GNU General Public License or a compatible license. * Try to hang around in our art development IRC channel #tmw-art on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing. * Do not be afraid to show us your pixelart, we are there to guide and help you. Pixelart being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * A list of pixelart tutorials can be found [[User:EJlol/Tutorials|here]]. * The pixel art should be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Outlines: 1px, Coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Beings(players,monsters) and item icons level: stands out the most (heavily saturated with dark outlines) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Light Direction: South-West ([[:Image:Lightdirection.png|Example]]) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti Aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * You may mirror the creature sprites, as long as the lighting is correct * There is no size restriction, please go berserk === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPC's should be in the same style as the player sprites. ** NPC's do not and should not be constrained by player pose and body shape. For example, the startrek sprites are done in the same style as players, but strike a different pose. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. ** Some NPCs not in the same style as the player sprites may be accepted if appropriate. (For example, Santa) === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the New Forest Tileset as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for 'here is nothing' indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: New Forest Tileset ** Indoor: ??? ** Dungeons: ??? * All tiles on a single tileset should have the same warm / cold feeling. * When contributing to a other tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 3y2kdr1bdj3fd6gdwmlmeep8lizpne0 14482 14481 2009-12-31T21:50:33Z Bcs86 1568 /* Tilesets */ 14482 wikitext text/x-wiki {{Status_green}} When you create pixel art for TMW please follow these guidelines. Pixelart which does not follow these guidelines has less chance to get into the game. === General === * All graphics must be released under the GNU General Public License or a compatible license. * Try to hang around in our art development IRC channel #tmw-art on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing. * Do not be afraid to show us your pixelart, we are there to guide and help you. Pixelart being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * A list of pixelart tutorials can be found [[User:EJlol/Tutorials|here]]. * The pixel art should be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Outlines: 1px, Coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Beings(players,monsters) and item icons level: stands out the most (heavily saturated with dark outlines) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Light Direction: South-West ([[:Image:Lightdirection.png|Example]]) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti Aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * You may mirror the creature sprites, as long as the lighting is correct * There is no size restriction, please go berserk === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPC's should be in the same style as the player sprites. ** NPC's do not and should not be constrained by player pose and body shape. For example, the startrek sprites are done in the same style as players, but strike a different pose. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. ** Some NPCs not in the same style as the player sprites may be accepted if appropriate. (For example, Santa) === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for 'here is nothing' indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: New Forest Tileset ** Indoor: ??? ** Dungeons: ??? * All tiles on a single tileset should have the same warm / cold feeling. * When contributing to a other tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] gdnwcaxtxxz1vozt8vtrrh24atfz3wm 14485 14482 2010-01-01T17:42:35Z Crush 103 this is a must, not a should requirement. also removed redundant link to tutorials. 14485 wikitext text/x-wiki {{Status_green}} When you create pixel art for TMW please follow these guidelines. Pixelart which does not follow these guidelines has less chance to get into the game. === General === * All graphics must be released under the GNU General Public License or a compatible license. * Try to hang around in our art development IRC channel #tmw-art on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing. * Do not be afraid to show us your pixelart, we are there to guide and help you. Pixelart being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Outlines: 1px, Coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Beings(players,monsters) and item icons level: stands out the most (heavily saturated with dark outlines) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Light Direction: South-West ([[:Image:Lightdirection.png|Example]]) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti Aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * You may mirror the creature sprites, as long as the lighting is correct * There is no size restriction, please go berserk === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPC's should be in the same style as the player sprites. ** NPC's do not and should not be constrained by player pose and body shape. For example, the startrek sprites are done in the same style as players, but strike a different pose. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. ** Some NPCs not in the same style as the player sprites may be accepted if appropriate. (For example, Santa) === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for 'here is nothing' indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: New Forest Tileset ** Indoor: ??? ** Dungeons: ??? * All tiles on a single tileset should have the same warm / cold feeling. * When contributing to a other tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] g8ptziptwyy2uyqopdhdfj5l8fmi29j 17905 14485 2011-02-06T12:35:23Z Crush 103 clarified that NPCs are like beings 17905 wikitext text/x-wiki {{Status_green}} When you create pixel art for TMW please follow these guidelines. Pixelart which does not follow these guidelines has less chance to get into the game. === General === * All graphics must be released under the GNU General Public License or a compatible license. * Try to hang around in our art development IRC channel #tmw-art on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing. * Do not be afraid to show us your pixelart, we are there to guide and help you. Pixelart being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Outlines: 1px, Coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Light Direction: South-West ([[:Image:Lightdirection.png|Example]]) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti Aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * You may mirror the creature sprites, as long as the lighting is correct * There is no size restriction, please go berserk === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPC's should be in the same style as the player sprites. ** NPC's do not and should not be constrained by player pose and body shape. For example, the startrek sprites are done in the same style as players, but strike a different pose. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. ** Some NPCs not in the same style as the player sprites may be accepted if appropriate. (For example, Santa) === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for 'here is nothing' indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: New Forest Tileset ** Indoor: ??? ** Dungeons: ??? * All tiles on a single tileset should have the same warm / cold feeling. * When contributing to a other tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] imw0jtfwq7szyo0fj66el94slg7ii4m 18294 17905 2011-04-08T07:11:22Z Wombat 1239 /* General */ irc #tmw-art changed to #tmw-dev 18294 wikitext text/x-wiki {{Status_green}} When you create pixel art for TMW please follow these guidelines. Pixelart which does not follow these guidelines has less chance to get into the game. === General === * All graphics must be released under the GNU General Public License or a compatible license. * Try to hang around in our art development IRC channel #tmw-dev on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing. * Do not be afraid to show us your pixelart, we are there to guide and help you. Pixelart being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Outlines: 1px, Coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Light Direction: South-West ([[:Image:Lightdirection.png|Example]]) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti Aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * You may mirror the creature sprites, as long as the lighting is correct * There is no size restriction, please go berserk === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPC's should be in the same style as the player sprites. ** NPC's do not and should not be constrained by player pose and body shape. For example, the startrek sprites are done in the same style as players, but strike a different pose. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. ** Some NPCs not in the same style as the player sprites may be accepted if appropriate. (For example, Santa) === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for 'here is nothing' indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: New Forest Tileset ** Indoor: ??? ** Dungeons: ??? * All tiles on a single tileset should have the same warm / cold feeling. * When contributing to a other tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == The best way to do this is yet to be decided, but this should work: *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Create a new report in [http://mantis.themanaworld.org/ Mantis] to request that it be included in the game. == Tutorials == When you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] m6e43yyo1z0s5ebtkb25b9getn4d5b4 20061 18294 2011-09-12T02:25:46Z Enchilado 1753 a little cleaning up of details (though I'll probably do more work on this later) 20061 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #tmw-dev on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Direction: South-West to North-East ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] jjhqpsz6fs7p8e5suznk0b819n5apmd 22246 20061 2011-10-28T20:39:12Z O11c 2047 /* General Guidelines */ clarify direction 22246 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #tmw-dev on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] n32ly68zkw1l04c87305racbp40erlt 22734 22246 2011-11-14T17:58:24Z EJlol 294 Added information about dyeing 22734 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #tmw-dev on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Please use our task tracking system [http://mantis.themanaworld.org Mantis] to manage graphical tasks you are doing. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] s21zk11ld9gzyt65vdo13dzoe9xmljx 25320 22734 2013-01-26T09:36:17Z Jenalya 1876 /* General */ Remove the request to use Mantis, as it isn't in use anymore. 25320 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #tmw-dev on [irc://irc.themanaworld.org irc.themanaworld.org] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] fk5vtpqlh29xnyij22krsghm9k0zz08 26477 25320 2013-05-28T16:04:48Z Jaxad0127 999 Update IRC info. 26477 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] ngcxer2iov1b8z1e7a6hn28pjmpagqm 26478 26477 2013-05-28T16:50:02Z Wushin 2233 26478 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == ===Trello Method=== (prefered method) * PM Jenalya to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] d3ghjn8snynp6q5nxrf6bdd61f2euin 26479 26478 2013-05-28T16:50:21Z Wushin 2233 /* How to get your content in to the game */ 26479 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == ===Trello Method=== * PM Jenalya to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] lrrm93olcumv5seqk5f38wboa0pz9fy 26615 26479 2013-06-07T13:55:25Z Jaxad0127 999 Jaxad0127 moved page [[Guidelines]] to [[Dev:Guidelines]] 26615 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == ===Trello Method=== * PM Jenalya to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] lrrm93olcumv5seqk5f38wboa0pz9fy 28496 26615 2013-10-27T17:24:16Z Wushin 2233 /* Development Guidelines Changing to Match RC1 & TMWA Goals */ 28496 wikitext text/x-wiki {{status_construction}} {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** Shadows should NOT be used for NPCs, shadows are reserved for large objects or flying creatures. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling == How to get your content in to the game == ===Trello Method=== * PM Jenalya to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Change the [WIP] thread's title to [WIP]>[FND] (finished), and make it clear which is the final version. *Wait for the thread to marked [RC] (release candidate) by a developer and then pushed and marked [GIT] by another. Your work will then be included in the next update. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] guxezl62ez3mrfhxp7kt2262l00enzq 28497 28496 2013-10-27T17:42:43Z Wushin 2233 /* New Methods to Constrain avenues art can come in so we don't lose so much again */ 28497 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** NPCs should be a nude model. ** Appearance is changed by adding clothing layers. ** Shadow is either a particle effect or clothing. ** Fringe Items are to be added as either a particle effect or clothing. ** Shadows are NOT to be used on the Nude Models. ** Mob Sprites Can be used for NPCs as well ** Player Sprite Sheets can be used to create NPCs ** NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) ** Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Jenalya to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 1fruampjlcr0zinolfc3t77c8xduc2g 28498 28497 2013-10-27T17:44:10Z Wushin 2233 /* Trello Method */ 28498 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** NPCs should be a nude model. ** Appearance is changed by adding clothing layers. ** Shadow is either a particle effect or clothing. ** Fringe Items are to be added as either a particle effect or clothing. ** Shadows are NOT to be used on the Nude Models. ** Mob Sprites Can be used for NPCs as well ** Player Sprite Sheets can be used to create NPCs ** NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) ** Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Jenalya or wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 60ch1rh8486mqyzme26i5yytj0yhpb7 28906 28498 2013-11-25T12:00:03Z Wushin 2233 /* General Guidelines */ 28906 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya or Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** NPCs should be a nude model. ** Appearance is changed by adding clothing layers. ** Shadow is either a particle effect or clothing. ** Fringe Items are to be added as either a particle effect or clothing. ** Shadows are NOT to be used on the Nude Models. ** Mob Sprites Can be used for NPCs as well ** Player Sprite Sheets can be used to create NPCs ** NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) ** Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Jenalya or wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] o7mcy04b0imm0l9bsjoxoe2m9bpebvy 28907 28906 2013-11-25T12:04:18Z Wushin 2233 /* NPCs */ Redid NPC constraints. The same but different. Basically the NPC is now submitted in layers. 28907 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya or Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === ** NPCs must be in the same style as the player sprites. ** NPCs do not and should not be constrained by player pose and body shape. ** NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) ** NPCs should be a base nude model. ** Appearance is changed by adding clothing layers. ** NPCs clothing is a separate sheet. ** Shadow is either a particle effect or clothing. ** Fringe Items are to be added as either a particle effect or clothing. ** Shadows are NOT to be used on the Nude Models. ** Mob Sprites Can be used for NPCs as well ** Player Sprite Sheets can be used to create NPCs ** NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) ** Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Jenalya or wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] jil9l6s21bjd0xvty1flwlh38icm86u 28908 28907 2013-11-25T12:05:10Z Wushin 2233 /* NPCs */ 28908 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya or Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Jenalya or wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 30ysbkg0mjbm2ngm0c80gbny9fk0o0p 29386 28908 2014-02-20T03:16:37Z Wushin 2233 /* Trello Method */ 29386 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya or Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [http://forums.themanaworld.org/viewforum.php?f=18 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] a0nbr9mkxhk0hfjm9fmjc7bhwfvywlj 29387 29386 2014-02-20T03:22:54Z Wushin 2233 /* Forum Method */ 29387 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya or Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [http://gitorious.org/tmwdata/mainline/blobs/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 4kanhvtaem60jwd6xjfcw3e5rcp5la2 29388 29387 2014-02-20T03:57:09Z Wushin 2233 /* Tilesets */ 29388 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=8 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya or Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] rph8et9ngrfr0x411au8ivqqb5e59qa 29389 29388 2014-02-20T04:04:40Z Wushin 2233 /* General */ 29389 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya or Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[Monsterset development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] q4nsugat1r4toxco527402drti3kh44 29390 29389 2014-02-20T04:06:47Z Wushin 2233 /* Creatures */ 29390 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Jenalya or Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[https://trello.com/b/rNnx513z/art-development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 73pueiyzyuphgj75lsi7l6faa4s0wce 29391 29390 2014-02-20T04:07:18Z Wushin 2233 /* General Guidelines */ 29391 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [[https://trello.com/b/rNnx513z/art-development]] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 02kz1bvl1daofpbycxsifddkou9d5ut 29392 29391 2014-02-20T04:07:29Z Wushin 2233 /* Creatures */ 29392 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] 9oh2zdmmpodnragzdrwes0rbasfhvu6 29393 29392 2014-02-20T04:08:05Z Wushin 2233 /* Creatures */ 29393 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [http://trello.com/b/rNnx513z/art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] j1vfo4usf276iafv6u9tcy0tr1b26ij 29394 29393 2014-02-20T04:08:30Z Wushin 2233 /* Creatures */ 29394 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/Forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] hkfyw7o01kqp0w2298bwd7wwnyub321 31101 29394 2014-07-25T02:59:43Z Gshlvr 2318 Changed capital 'F' in link to lowercase, fixing a 404. 31101 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] h42cngiii9azgypkqn4on9t4yghawrz 31850 31101 2014-12-17T16:21:25Z Wushin 2233 /* categorizing */ 31850 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] [[Category:Reference]] [[Category:Development]] 0nyype1gpm9h2dflwdmsua88g9vrg94 33700 31850 2015-03-11T08:24:03Z Cassy 2265 removing category 33700 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Trello Method=== * PM Wushin to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] * Read Cards [https://trello.com/c/l69ummKJ Graphics Progress Tags] and [https://trello.com/c/rDMARAHU General Graphic Tags] * Start a card in [cpt] with an png image of tile * Discuss it with the other art members about possible use case * Move it to [WIP] and begin to finish the graphic. * Once you are satisfied with the result move it to [FND] awaiting completion * Once it's been moved into [RC] you'll will see it in game. ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] [[Category:Development]] tw7wret0q4ovr3yxvlij7w6im57ndyo 46109 33700 2019-10-09T20:09:39Z Jesusalva 2520 Trello Method Removed 46109 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *Move it to trello once it is less of a concept and has physical art. *Please only use the forum to dicuss [CPT] and [REQ]. [WIP], [FND] and [RC] should be made into trello cards. *Art will no longer move from the forums into game. NOTE: We lost too much good art we had to dig out because threads would get buried waiting for content to add them == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] [[Category:Development]] 7difuczv91vp4o9rdy4hpvzsg5aq3ac 46110 46109 2019-10-09T20:11:36Z Jesusalva 2520 Forum Method: Remove Trello references, mention GitLab 46110 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released under the GNU General Public License or a compatible license. * Try to hang around in our development IRC channel #themanaworld-art on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on (Usually tagged with [WIP], for work in progress) can be posted on the [http://trello.com/board/art-development/4ea730ee9982b463f800497e trello] or the [http://forums.themanaworld.org/viewforum.php?f=2 forums]. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *You can bump your post if it gets buried too deep and reviewers cannot find it anymore, but don't abuse. *If you don't want your art to get lost, submit it on GitLab directly. *It'll be pushed to master once it's final version is approved. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] [[Category:Development]] ionynp1e7dhh6qe3u8g2ywhy5uiyny5 46111 46110 2019-10-09T20:13:42Z Jesusalva 2520 General: No Trello 46111 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === General === * All graphics '''must''' be released with dual license, under the GNU General Public License and Creative Commons Attribution Share Alike, or a compatible license. * Try to hang around in our development IRC channel #evol-dev on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on can be posted on the [http://forums.themanaworld.org/viewforum.php?f=2 forums] or on GitLab. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *You can bump your post if it gets buried too deep and reviewers cannot find it anymore, but don't abuse. *If you don't want your art to get lost, submit it on GitLab directly. *It'll be pushed to master once it's final version is approved. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] [[Category:Development]] l4qydqsw2yrn2edn4r2xxjwyn86cqco 53197 46111 2020-12-31T23:44:13Z Speiros 2726 I added in the Prelude - a link to a more up-to-date article. 53197 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === Prelude === This article may be a little out of date. If so, here is a link that may help. https://wiki.themanaworld.org/index.php/Dev:Joining_the_project. [[User:Speiros|Speiros]] ([[User talk:Speiros|talk]]) 23:44, 31 December 2020 (UTC) === General === * All graphics '''must''' be released with dual license, under the GNU General Public License and Creative Commons Attribution Share Alike, or a compatible license. * Try to hang around in our development IRC channel #evol-dev on [irc://irc.freenode.net irc.freenode.net] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on can be posted on the [http://forums.themanaworld.org/viewforum.php?f=2 forums] or on GitLab. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *You can bump your post if it gets buried too deep and reviewers cannot find it anymore, but don't abuse. *If you don't want your art to get lost, submit it on GitLab directly. *It'll be pushed to master once it's final version is approved. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] [[Category:Development]] mzt173vdjp7jk4w0arttfap0q3j08cd 54980 53197 2021-05-28T21:24:26Z Jesusalva 2520 Text replacement - "irc.freenode.net" to "irc.libera.chat" 54980 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === Prelude === This article may be a little out of date. If so, here is a link that may help. https://wiki.themanaworld.org/index.php/Dev:Joining_the_project. [[User:Speiros|Speiros]] ([[User talk:Speiros|talk]]) 23:44, 31 December 2020 (UTC) === General === * All graphics '''must''' be released with dual license, under the GNU General Public License and Creative Commons Attribution Share Alike, or a compatible license. * Try to hang around in our development IRC channel #evol-dev on [irc://irc.libera.chat irc.libera.chat] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on can be posted on the [http://forums.themanaworld.org/viewforum.php?f=2 forums] or on GitLab. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *You can bump your post if it gets buried too deep and reviewers cannot find it anymore, but don't abuse. *If you don't want your art to get lost, submit it on GitLab directly. *It'll be pushed to master once it's final version is approved. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] [[Category:Development]] ce10ylz6bsqpdv9zc6xl9qk4l3ymb66 59490 54980 2024-03-27T03:56:43Z Move page script 2739 Move page script moved page [[Dev:Guidelines]] to [[Development:Guidelines]]: Rename Dev: to Development: so the miraheze import works 54980 wikitext text/x-wiki {{Status_green}} When creating pixel art for TMW, please make sure to follow these guidelines. Pixel art which does not will have a much-lessened chance of getting into the game. === Prelude === This article may be a little out of date. If so, here is a link that may help. https://wiki.themanaworld.org/index.php/Dev:Joining_the_project. [[User:Speiros|Speiros]] ([[User talk:Speiros|talk]]) 23:44, 31 December 2020 (UTC) === General === * All graphics '''must''' be released with dual license, under the GNU General Public License and Creative Commons Attribution Share Alike, or a compatible license. * Try to hang around in our development IRC channel #evol-dev on [irc://irc.libera.chat irc.libera.chat] whenever possible. * Do not be afraid to show us your pixel art, we are here to guide and help you. Pixel art being worked on can be posted on the [http://forums.themanaworld.org/viewforum.php?f=2 forums] or on GitLab. * The pixel art '''must''' be made by you or derived from TMW's existing graphics. We will never accept pixel art ripped from other games nor from undisclosed sources. * The following games can be used as inspiration: **Secret of Mana 2 **Final Fantasy VI (Named Final Fantasy III in North America) **Chrono Trigger **Ragnarok Online === General Guidelines === * Light Source: Above, from South-West. For tilesets, this roughly means from the bottom-left corner; for items, the top-left. ([[:Image:Lightdirection.png|Example]]) * Perspective: top-down 45° view angle. ([[:Image:Perspective_Reference.png|Example]]) * Dyeable Images: Images can be dyed, see [[Image dyeing]] for more information * Outlines: 1px, coloured. We use 3 kinds of different outlines: **Ground level: should have the dullest colors (no outlines everything blends into each other) ([[:Image:Outlines_ground.png|Example]]) **Objects level: stands out from the ground level (with more contrast and maybe even a light outline) **Sprites (characters, monsters etc.) and item icons level: stands out the most (heavily saturated with dark outlines) ** Objects should be fully lit ([[:Image:Lighting fill.png|Example]]) * Wind Direction: From West to East * Proportions: A character is approximately one tile wide (32px) and two tiles high (64px) ([[:Image:Size.png|Example]]) * Drop Shadows: **Large objects on outdoor tilesets have a drop shadow to the northeast **Flying creatures have a drop shadow ([[:Image:Dropshadow.png|Example]]) **Shadows should be pure black (#000000), and have a opacity of 30%, the edges have a opacity of 15% * Anti-aliasing: Only if it does not look smooth without it * Blood: May only be used if it spice up certain environments that needs to be extra creepy. ([[:Image:No_blood_new.png|Example]]) * Quality of art required is relative to what it is meant to add or replace and content it is going to be paired with. Always reference the current art ingame as reference. [https://github.com/themanaworld/tmwa-client-data/tree/master/graphics Current Game Art for reference.] ** PM Wushin on the forums to get added to the art trello [https://trello.com/board/art-development/4ea730ee9982b463f800497e Art trello for TMWA] === Creatures === [https://trello.com/b/rNnx513z/art-development art-development] * Mirroring the shape of a sprite is acceptable, provided the shading is correct on each frame. * There is no size restriction, although the "attackable" area of a monster is only 1*1 tile. === Icons === [[User:EJlol/Guidelines/Icon examples|Icon Development]] * Use other icons as examples if possible ([[:Image:Icons.png|Example]]) === NPCs === * NPCs must be in the same style as the player sprites. * NPCs do not and should not be constrained by player pose and body shape. * NPCs oversized objects (forges,looms,etc.) are animated tiles (see maps) * NPCs should be a base nude model. * Appearance is changed by adding clothing layers. * NPCs clothing is a separate sheet. * Shadow is either a particle effect or clothing. * Fringe Items are to be added as either a particle effect or clothing. * Shadows are NOT to be used on the Nude Models. * Mob Sprites Can be used for NPCs as well * Player Sprite Sheets can be used to create NPCs * NPC Animations can be done by combining Player Sprite Sheet actions (i.e. chopping a log is the same as axe attack) * Npcs are still not yet mobile. === Tilesets === [[Tileset development]] * All tilesets should have the same amount of texture. Use the [https://github.com/themanaworld/tmwa-client-data/blob/master/graphics/tiles/forest.png New Forest Tileset] as reference * Do not use visible outlines * Do not use vanishing point projection. All objects have to be drawn in zero-point perspective ([[:Image:Vanishing point perspective.png|Example]]) * Use pure black (#000000) for "nothing"; eg, the tiles surrounding indoor or dungeon areas. * Try to match the brightness and contrast of the reference tileset ** Outdoor: Woodland tileset ** Indoor: Woodland Indoor tileset ** Dungeons: Cave tileset * All tiles on a single tileset should have the same warmth to them, unless it should specifically be otherwise. * When adding to an existing tileset, try to use the same colours as much as possible to get the same feeling * Sets need to be mapping complete (i.e. indoor.png, indoor_x2.png, etc.) to allow for fringe layering and to fix Scythe & Christmas Tree hat. * When adding a set naming convention should describe the terrain of the tiles not that location or content using all lowercase and - (i.e. woodland-graveyard-x2) * Check Existing tilesets before creating a new tileset to see if you can extend current content. == How to get your content in to the game == ===Forum Method=== *Start a thread in the [https://forums.themanaworld.org/viewforum.php?f=2 forum], with a subject line beginning [WIP] (work in progress). *Discuss it and edit it a few times until it's ready. *You can bump your post if it gets buried too deep and reviewers cannot find it anymore, but don't abuse. *If you don't want your art to get lost, submit it on GitLab directly. *It'll be pushed to master once it's final version is approved. == Tutorials == If you are not very experienced at creating pixel art, you should take a look at the following tutorials. You can learn many interesting tricks from them. *[http://www.petesqbsite.com/sections/tutorials/tuts/tsugumo/ So You Want To Be A Pixel Artist by Tsugumo]. *[http://www.natomic.com/hosted/marks/mpat/ Mark's Pixel Art Tutorial] *[http://www.derekyu.com/?page_id=218 Derek Yu's Pixel Art Tutorial] *[http://pixel-zone.rpgdx.net/shtml/tutorials.shtml Pixel-Zone Tutorials] *[http://www.pixeljoint.com/pixels/links.asp?id=2192 Pixel Art Links] *[http://mruk.wordpress.com/2008/04/06/the-mana-world-pixelart-tutorial-desert-well/ Mruk's Desert Well Tutorial] * [http://mruk.wordpress.com/2009/03/12/the-mana-world-tutorial-challanging-an-imposible-shape/ Mruk's Impossible Shape Design Tutorial] [[Category:Development]] ce10ylz6bsqpdv9zc6xl9qk4l3ymb66 0 8160 33299 2015-03-06T11:57:00Z Alexanderlime 2382 Alexanderlime moved page [[Dev:Hercules server]] to [[Dev:Evol-Hercules server]] 33299 wikitext text/x-wiki #REDIRECT [[Dev:Evol-Hercules server]] 7xmv7jpim7yz82bjaz2hjw84qyy8st2 36407 33299 2015-04-21T15:38:55Z Bock 2299 double redirect 36407 wikitext text/x-wiki #REDIRECT [[User:Alexanderlime/Evol-Hercules_server]] mz9lko1p1u0ai61wf1r7aouuo8v8qjp 59492 36407 2024-03-27T03:56:44Z Move page script 2739 Move page script moved page [[Dev:Hercules server]] to [[Development:Hercules server]]: Rename Dev: to Development: so the miraheze import works 36407 wikitext text/x-wiki #REDIRECT [[User:Alexanderlime/Evol-Hercules_server]] mz9lko1p1u0ai61wf1r7aouuo8v8qjp 0 12710 52901 2020-11-12T11:31:03Z Jesusalva 2520 Redirected page to [[Dev:Main]] 52901 wikitext text/x-wiki #REDIRECT [[Dev:Main]] jyk7vnv5m5t5gum6xovs3w8uc2ytkp3 59494 52901 2024-03-27T03:56:44Z Move page script 2739 Move page script moved page [[Dev:Home]] to [[Development:Home]]: Rename Dev: to Development: so the miraheze import works 52901 wikitext text/x-wiki #REDIRECT [[Dev:Main]] jyk7vnv5m5t5gum6xovs3w8uc2ytkp3 0 5220 18725 2011-06-10T19:50:29Z Wombat 1239 added how to develop info from Wombat user page 18725 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. # Open a command line terminal (e.g. xterm or konsole). # mkdir ~/tmw-ea (or other name you prefer your directory to be called). # cd ~/tmw-ea # git clone git://gitorious.org/tmw-eathena/mainline.git eathena # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-client-test.git tmwdata # cd eathena # make # cd ../eathena-data # ln -s ../eathena/{char-server,login-server,map-server,ladmin} . # for F in *.example; do cp $F ${F/.example/}; done # cp save/account.txt.example save/account.txt # Edit conf/char_local.conf and change login_ip and char_ip to 127.0.0.1 # Edit conf/map_local.conf and change char_ip and map_ip to 127.0.0.1 # Edit conf/ladmin_local.conf and change login_ip to 127.0.0.1, login_port to 6901, and admin_pass to p1 # TODO give instructions about lan_support.conf and opening your server to access from other computers. # cd conf # ./build-magic # Edit the second column of conf/spells-build to give usable names to spells. # ./build-magic (again) == Start the servers == # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./char-server # Repeat steps 1 and 2 # ./login-server # Repeat steps 1 and 2. # ./map-server This should run all three of your servers. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. # cd ~/tmw-ea/eathena-data/tools/tmwcon # ant # ln -s ../.. server-data # ln -s ../../../tmwdata tmwdata # java Converter ==Making Monster, Item and Equipment Content== ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making Git Patches and Submitting them For Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= ehy268uvzf6ex90r0fgu8nobfq2jr8b 18740 18725 2011-06-12T20:17:21Z Wombat 1239 added link to testing server and the mana world workshop manual 18740 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. # Open a command line terminal (e.g. xterm or konsole). # mkdir ~/tmw-ea (or other name you prefer your directory to be called). # cd ~/tmw-ea # git clone git://gitorious.org/tmw-eathena/mainline.git eathena # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-client-test.git tmwdata # cd eathena # make # cd ../eathena-data # ln -s ../eathena/{char-server,login-server,map-server,ladmin} . # for F in *.example; do cp $F ${F/.example/}; done # cp save/account.txt.example save/account.txt # Edit conf/char_local.conf and change login_ip and char_ip to 127.0.0.1 # Edit conf/map_local.conf and change char_ip and map_ip to 127.0.0.1 # Edit conf/ladmin_local.conf and change login_ip to 127.0.0.1, login_port to 6901, and admin_pass to p1 # TODO give instructions about lan_support.conf and opening your server to access from other computers. # cd conf # ./build-magic # Edit the second column of conf/spells-build to give usable names to spells. # ./build-magic (again) == Start the servers == # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./char-server # Repeat steps 1 and 2 # ./login-server # Repeat steps 1 and 2. # ./map-server This should run all three of your servers. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. # cd ~/tmw-ea/eathena-data/tools/tmwcon # ant # ln -s ../.. server-data # ln -s ../../../tmwdata tmwdata # java Converter ==Making Monster, Item and Equipment Content== ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making Git Patches and Submitting them For Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 3njvzsc5trwntmndtenlaypb94x3j6q 18775 18740 2011-06-19T02:56:14Z Wombat 1239 /* Making Monster, Item and Equipment Content */ 18775 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. # Open a command line terminal (e.g. xterm or konsole). # mkdir ~/tmw-ea (or other name you prefer your directory to be called). # cd ~/tmw-ea # git clone git://gitorious.org/tmw-eathena/mainline.git eathena # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-client-test.git tmwdata # cd eathena # make # cd ../eathena-data # ln -s ../eathena/{char-server,login-server,map-server,ladmin} . # for F in *.example; do cp $F ${F/.example/}; done # cp save/account.txt.example save/account.txt # Edit conf/char_local.conf and change login_ip and char_ip to 127.0.0.1 # Edit conf/map_local.conf and change char_ip and map_ip to 127.0.0.1 # Edit conf/ladmin_local.conf and change login_ip to 127.0.0.1, login_port to 6901, and admin_pass to p1 # TODO give instructions about lan_support.conf and opening your server to access from other computers. # cd conf # ./build-magic # Edit the second column of conf/spells-build to give usable names to spells. # ./build-magic (again) == Start the servers == # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./char-server # Repeat steps 1 and 2 # ./login-server # Repeat steps 1 and 2. # ./map-server This should run all three of your servers. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. # cd ~/tmw-ea/eathena-data/tools/tmwcon # ant # ln -s ../.. server-data # ln -s ../../../tmwdata tmwdata # java Converter ==Making Monster, Item and Equipment Content== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Art Director makes art + xml for it with an [RC] tag. * A2. Any developer, including the Art Director, can add [RC] content through a patch. * A3. Art Director marks topic as [GIT]. * B. Art Director commits art and xml, then marks as [GIT]. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making Git Patches and Submitting them For Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] lbw8b6rscdihvp7vncpal39n38vadq8 18776 18775 2011-06-19T04:08:41Z Wombat 1239 /* Making Monster, Item and Equipment Content */ 18776 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. # Open a command line terminal (e.g. xterm or konsole). # mkdir ~/tmw-ea (or other name you prefer your directory to be called). # cd ~/tmw-ea # git clone git://gitorious.org/tmw-eathena/mainline.git eathena # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-client-test.git tmwdata # cd eathena # make # cd ../eathena-data # ln -s ../eathena/{char-server,login-server,map-server,ladmin} . # for F in *.example; do cp $F ${F/.example/}; done # cp save/account.txt.example save/account.txt # Edit conf/char_local.conf and change login_ip and char_ip to 127.0.0.1 # Edit conf/map_local.conf and change char_ip and map_ip to 127.0.0.1 # Edit conf/ladmin_local.conf and change login_ip to 127.0.0.1, login_port to 6901, and admin_pass to p1 # TODO give instructions about lan_support.conf and opening your server to access from other computers. # cd conf # ./build-magic # Edit the second column of conf/spells-build to give usable names to spells. # ./build-magic (again) == Start the servers == # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./char-server # Repeat steps 1 and 2 # ./login-server # Repeat steps 1 and 2. # ./map-server This should run all three of your servers. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. # cd ~/tmw-ea/eathena-data/tools/tmwcon # ant # ln -s ../.. server-data # ln -s ../../../tmwdata tmwdata # java Converter ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Art Director makes art + xml for it with an [RC] tag. * A2. Any developer, including the Art Director, can add [RC] content through a patch. * A3. Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making Git Patches and Submitting them For Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] jykw23tapbed848bap3jp1iz2m9nwhw 18777 18776 2011-06-19T04:10:58Z Wombat 1239 /* Steps */ 18777 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. # Open a command line terminal (e.g. xterm or konsole). # mkdir ~/tmw-ea (or other name you prefer your directory to be called). # cd ~/tmw-ea # git clone git://gitorious.org/tmw-eathena/mainline.git eathena # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-client-test.git tmwdata # cd eathena # make # cd ../eathena-data # ln -s ../eathena/{char-server,login-server,map-server,ladmin} . # for F in *.example; do cp $F ${F/.example/}; done # cp save/account.txt.example save/account.txt # Edit conf/char_local.conf and change login_ip and char_ip to 127.0.0.1 # Edit conf/map_local.conf and change char_ip and map_ip to 127.0.0.1 # Edit conf/ladmin_local.conf and change login_ip to 127.0.0.1, login_port to 6901, and admin_pass to p1 # TODO give instructions about lan_support.conf and opening your server to access from other computers. # cd conf # ./build-magic # Edit the second column of conf/spells-build to give usable names to spells. # ./build-magic (again) == Start the servers == # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./char-server # Repeat steps 1 and 2 # ./login-server # Repeat steps 1 and 2. # ./map-server This should run all three of your servers. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. # cd ~/tmw-ea/eathena-data/tools/tmwcon # ant # ln -s ../.. server-data # ln -s ../../../tmwdata tmwdata # java Converter ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Art Director makes art + xml for it with an [RC] tag. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making Git Patches and Submitting them For Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] h34mkjgwanwtpx40t00xkvvazmpzvq6 18778 18777 2011-06-19T04:15:06Z Wombat 1239 /* Steps */ more minor clean up, entry is new art process and further clarifications on steps were made. 18778 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. # Open a command line terminal (e.g. xterm or konsole). # mkdir ~/tmw-ea (or other name you prefer your directory to be called). # cd ~/tmw-ea # git clone git://gitorious.org/tmw-eathena/mainline.git eathena # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data # git clone git://gitorious.org/+tmw-admins/tmw/tmwa-client-test.git tmwdata # cd eathena # make # cd ../eathena-data # ln -s ../eathena/{char-server,login-server,map-server,ladmin} . # for F in *.example; do cp $F ${F/.example/}; done # cp save/account.txt.example save/account.txt # Edit conf/char_local.conf and change login_ip and char_ip to 127.0.0.1 # Edit conf/map_local.conf and change char_ip and map_ip to 127.0.0.1 # Edit conf/ladmin_local.conf and change login_ip to 127.0.0.1, login_port to 6901, and admin_pass to p1 # TODO give instructions about lan_support.conf and opening your server to access from other computers. # cd conf # ./build-magic # Edit the second column of conf/spells-build to give usable names to spells. # ./build-magic (again) == Start the servers == # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./char-server # Repeat steps 1 and 2 # ./login-server # Repeat steps 1 and 2. # ./map-server This should run all three of your servers. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. # cd ~/tmw-ea/eathena-data/tools/tmwcon # ant # ln -s ../.. server-data # ln -s ../../../tmwdata tmwdata # java Converter ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making Git Patches and Submitting them For Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] kjuv1ap242z2zcgntff3e5oi3ta63d4 18805 18778 2011-06-24T11:42:14Z Wombat 1239 /* Set Up */ added Ali-G's Development Guide + Link to README.mv.txt 18805 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== Here are the steps I use all the time when I want to make a new, fresh local testing server. * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * Close terminal. * Open ~/tmw-ea/eathena-data/login/conf folder. * Open '''login_local.conf.example''' and save it at the same place under '''login_local.conf'''. * Open ~/tmw-ea/eathena-data/world/conf folder. * Open '''char_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''char_local.conf'''. * Open ~/tmw-ea/eathena-data/world/map/conf folder. * Open '''help.txt.example''' and save it at the same place under '''help.txt'''. * Open '''map_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''map_local.conf'''. * Open ~/tmw-ea/eathena-data/login/save folder. * Open '''account.txt.example''' and save it at the same place under '''account.txt'''. You can now launch your test server. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana -u -d ~/tmw-ea/eathena-data/client-data'' You are now ready and able to do anything on your local test server. This should run all three of your servers. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. # cd ~/tmw-ea/eathena-data/tools/tmwcon # ant # ln -s ../.. server-data # ln -s ../../../tmwdata tmwdata # java Converter ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making Git Patches and Submitting them For Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 02x59bxxmy8c447ljrru0gis3r0e2tx 18806 18805 2011-06-25T21:40:02Z Alige 1888 updated according to o11c's help 18806 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== Here are the steps I use all the time when I want to make a new, fresh local testing server. * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * Close terminal. * Open ~/tmw-ea/eathena-data/login/conf folder. * Open '''login_local.conf.example''' and save it at the same place under '''login_local.conf'''. * Open ~/tmw-ea/eathena-data/world/conf folder. * Open '''char_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''char_local.conf'''. * Open ~/tmw-ea/eathena-data/world/map/conf folder. * Open '''help.txt.example''' and save it at the same place under '''help.txt'''. * Open '''map_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''map_local.conf'''. * Open ~/tmw-ea/eathena-data/login/save folder. * Open '''account.txt.example''' and save it at the same place under '''account.txt'''. * ''cd'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git checkout master'' * Close the terminal. You can now launch your test server. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana -u -d ~/tmw-ea/eathena-data/client-data'' You are now free to do some changes, first close the client and your servers. * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ../eathena-data'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' This should run all three of your servers. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] i8h19k4z68bov13j8xn301ef0c1eonb 18807 18806 2011-06-25T21:43:34Z Alige 1888 18807 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== Here are the steps to use when creating a new local testing server. * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * Close terminal. * Open ~/tmw-ea/eathena-data/login/conf folder. * Open '''login_local.conf.example''' and save it at the same place under '''login_local.conf'''. * Open ~/tmw-ea/eathena-data/world/conf folder. * Open '''char_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''char_local.conf'''. * Open ~/tmw-ea/eathena-data/world/map/conf folder. * Open '''help.txt.example''' and save it at the same place under '''help.txt'''. * Open '''map_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''map_local.conf'''. * Open ~/tmw-ea/eathena-data/login/save folder. * Open '''account.txt.example''' and save it at the same place under '''account.txt'''. * ''cd'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git checkout master'' * Close the terminal. '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ../eathena-data'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 0f1g5vfay7e4u5owxirlu0eq4ifopqg 18808 18807 2011-06-25T21:44:29Z Alige 1888 18808 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== Here are the steps to use when creating a new local testing server. * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * Close terminal. * Open ~/tmw-ea/eathena-data/login/conf folder. * Open '''login_local.conf.example''' and save it at the same place under '''login_local.conf'''. * Open ~/tmw-ea/eathena-data/world/conf folder. * Open '''char_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''char_local.conf'''. * Open ~/tmw-ea/eathena-data/world/map/conf folder. * Open '''help.txt.example''' and save it at the same place under '''help.txt'''. * Open '''map_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''map_local.conf'''. * Open ~/tmw-ea/eathena-data/login/save folder. * Open '''account.txt.example''' and save it at the same place under '''account.txt'''. * ''cd'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git checkout master'' * Close the terminal. '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ../eathena-data'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 8jahvr1zdc94br0grqjdk71cgmfwfuh 18812 18808 2011-06-26T08:40:37Z Alige 1888 18812 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== Here are the steps to use when creating a new local testing server. * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * ''cd'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git checkout master'' * Close terminal. * Open ~/tmw-ea/eathena-data/login/conf folder. * Open '''login_local.conf.example''' and save it at the same place under '''login_local.conf'''. * Open ~/tmw-ea/eathena-data/world/conf folder. * Open '''char_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''char_local.conf'''. * Open ~/tmw-ea/eathena-data/world/map/conf folder. * Open '''help.txt.example''' and save it at the same place under '''help.txt'''. * Open '''map_local.conf.example''', change the '''81.161.192.4''' to '''127.0.0.1''' and save it at the same place under '''map_local.conf'''. * Open ~/tmw-ea/eathena-data/login/save folder. * Open '''account.txt.example''' and save it at the same place under '''account.txt'''. '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ../eathena-data'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 8ocpypz5q2wque2kf8beyd1b1slmd7f 18813 18812 2011-06-26T08:43:18Z Alige 1888 18813 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== Here are the steps to use when creating a new local testing server. * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * ''cd'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git checkout master'' * Close terminal. * Open ~/tmw-ea/eathena-data/world/conf folder. * Open '''char_local.conf.example''' and save it at the same place under '''char_local.conf'''. * Open ~/tmw-ea/eathena-data/login/conf folder. * Open '''login_local.conf.example''' and save it at the same place under '''login_local.conf'''. * Open ~/tmw-ea/eathena-data/world/map/conf folder. * Open '''map_local.conf.example''' and save it at the same place under '''map_local.conf'''. * Open '''help.txt.example''' and save it at the same place under '''help.txt'''. * Open ~/tmw-ea/eathena-data/login/save folder. * Open '''account.txt.example''' and save it at the same place under '''account.txt'''. '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ../eathena-data'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 9ofyzljht04e21jw23zv5wf5olhfrbt 18814 18813 2011-06-26T08:46:39Z Alige 1888 18814 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * ''cd'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git checkout master'' * Close terminal. * Open ~/tmw-ea/eathena-data/world/conf folder. * Open '''char_local.conf.example''' and save it at the same place under '''char_local.conf'''. * Open ~/tmw-ea/eathena-data/login/conf folder. * Open '''login_local.conf.example''' and save it at the same place under '''login_local.conf'''. * Open ~/tmw-ea/eathena-data/world/map/conf folder. * Open '''map_local.conf.example''' and save it at the same place under '''map_local.conf'''. * Open '''help.txt.example''' and save it at the same place under '''help.txt'''. * Open ~/tmw-ea/eathena-data/login/save folder. * Open '''account.txt.example''' and save it at the same place under '''account.txt'''. '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ../eathena-data'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 3chpy2u4j5cb8yd8z3u75iol9bgevnj 18832 18814 2011-06-27T08:24:39Z Wombat 1239 /* Set Up Own Server */ 18832 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * ''cd'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git submodule update --init'' * ''git checkout master'' * Close terminal. * Open ~/tmw-ea/eathena-data/world/conf folder. * Open '''char_local.conf.example''' and save it at the same place under '''char_local.conf'''. * Open ~/tmw-ea/eathena-data/login/conf folder. * Open '''login_local.conf.example''' and save it at the same place under '''login_local.conf'''. * Open ~/tmw-ea/eathena-data/world/map/conf folder. * Open '''map_local.conf.example''' and save it at the same place under '''map_local.conf'''. * Open '''help.txt.example''' and save it at the same place under '''help.txt'''. * Open ~/tmw-ea/eathena-data/login/save folder. * Open '''account.txt.example''' and save it at the same place under '''account.txt'''. '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ../eathena-data'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] r1vqc25oebr9nvjvw4uiffbhgtcmuqj 18850 18832 2011-06-27T20:17:59Z O11c 2047 /* Set Up Own Server */ Simplify 18850 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)'' ) * ''git commit'' * ''git push'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data # ./ladmin # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] tjs77xjjnuxditl71seyb5zfetypp6y 18851 18850 2011-06-27T20:21:51Z O11c 2047 Add ladmin steps 18851 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)'' ) * ''git commit'' * ''git push'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] e630jhzkgj2dq1k6x2uekoa3wqm9zsd 18868 18851 2011-06-28T17:47:56Z Alige 1888 added how to pull data 18868 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)'' ) * ''git commit'' * ''git push'' * Close the terminal. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== ===Steps=== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ====Handling General Content Team [REQ]s==== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Git Repositories= ==Making and Submitting Git Patches for Review== ==Reviewing Git Patches and Pushing== ==Git Branches, Git Merging== =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] mgki6ujq7v25u9s7xv38rqucmo1gnkd 18869 18868 2011-06-28T20:37:33Z Wombat 1239 step on adding patches and some cleanup based on current layout 18869 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' '''*''' * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)'' ) * ''git commit'' * ''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. * ''git push'' '''*''' * Close the terminal. '''* :''' a step for those with commit access to the gitorious repositories. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Making Art Content== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and makes/requests xml for it. * A1. Once the .png and .xml is ready, the Art Directory can mark as [RC]. * A2. Any developer, including the Art Director, can add [RC] content through a patch, or push if they have commit access. * A3. Once pushed, Art Director marks topic as [GIT]. * or * B. Art Director commits art and xml, then marks as [GIT]. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file, art .png and xml added to appropriate sub-directory in the graphics directory. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] kg5k7koseyvpj6ig0bipyctodk0drj0 18870 18869 2011-06-29T09:23:16Z Wombat 1239 /* Making Art Content */ process clarified and amended on art content 18870 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' '''*''' * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)'' ) * ''git commit'' * ''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. * ''git push'' '''*''' * Close the terminal. '''* :''' a step for those with commit access to the gitorious repositories. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] fgl1frdwc0w6lvnp1jb4lkfc7bqis10 18871 18870 2011-06-29T19:02:54Z Wombat 1239 /* Set Up Own Server */ cleanup 18871 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' '''*''' * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' '''*''' * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)'' ) * ''git commit'' * ''git push'' '''*''' * Close the terminal. '''* :''' a step for those with commit access to the gitorious repositories. For others, please make a patch on marked steps. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 01hogfhzwcu4nvms6g3uc2gjagdm990 18872 18871 2011-06-29T19:05:34Z Wombat 1239 /* Set Up Own Server */ Further clarification. 18872 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' '''*''' * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' '''*''' * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)'' ) * ''git commit'' * ''git push'' '''*''' * Close the terminal. '''* :''' a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 5xs2st9157y0c306eb1goa1o38077c5 18889 18872 2011-07-04T10:15:46Z Wombat 1239 /* Set Up Own Server */ Making a GM guide added 18889 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' '''*''' * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' * Launch your test server and register an account. * Open a text editor. * Open ~/tmw-ea/eathena-data/login/save/account.txt and ../gm_account.txt. * Copy the ''2000000'' from your account.txt next to your account name and paste it on the second line of gm_account.txt, hit spacebar, enter ''99'' so it reads on the second line: ''2000000 99''. The 2000000 is an account number, other accounts can be made GM by copying their account number and giving the account an appropriate amount of permissions on your server. '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' '''*''' * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)'' ) * ''git commit'' * ''git push'' '''*''' * Close the terminal. '''* :''' a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] 3prk9v6ifyfi1hlqgmye50mgmv425gx 18898 18889 2011-07-04T23:00:14Z O11c 2047 /* Set Up Own Server */ Fix footnotes and "add GM" method 18898 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {ref|push} {ref|once} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] sjswfhlmwoicfkuethyewz4zhub7vin 18899 18898 2011-07-07T12:37:22Z Argul 1858 Add troubleshoot section linking to other artcles 18899 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {ref|push} {ref|once} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] ==Trouble Shooting== see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] eqgafdni4fs4yuihw7p7s4rt3vb0bz6 18900 18899 2011-07-07T12:37:41Z Argul 1858 /* Trouble Shooting */ 18900 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {ref|push} {ref|once} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 8ix1m8aq1hmqkv3pky2gg8lhwdtou2s 18901 18900 2011-07-07T19:45:13Z Wombat 1239 /* Set Up Own Server */ 18901 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {ref|push} {ref|once} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administation == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] tapev6cpnxedrhubxwyrt90kvanjg4u 18928 18901 2011-07-10T11:11:00Z Freeyorp 1501 Fix a typo 18928 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {ref|push} {ref|once} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 8u2nqgao81ezaprz8emgo3hvgan4d9y 18930 18928 2011-07-11T18:34:56Z Wombat 1239 formatting issues fix 18930 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] st6dsl51w8k9xrgywd2t47j9npg8ymx 18937 18930 2011-07-13T19:34:54Z Wombat 1239 /* Set Up Own Server */ 18937 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu 10.04 on amd64 and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. '''Dependencies:''' Throughout this tutorial, I do not address dependencies. Bison and Flex are needed, as are other dependencies. This will be inserted with time. ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 8oe2j9163wv111yhz5vhefqf4tj0msd 18974 18937 2011-07-24T12:54:31Z Hal9000 2105 /* Set Up */ 18974 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== Bison, Flex and zLib dependencies are usually needed. '''Ubuntu 11.04:''' * Open a terminal. * ''sudo apt-get install zlib1g-dev flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C HEAD^'' * pastebin the patch and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 88m8lqzhzbnr8yydw7j2ivlqriimjvg 19762 18974 2011-08-22T18:06:35Z O11c 2047 /* Set Up Own Server */ Clarify the rules for multi-patch changes 19762 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== Bison, Flex and zLib dependencies are usually needed. '''Ubuntu 11.04:''' * Open a terminal. * ''sudo apt-get install zlib1g-dev flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 8vr2w8ngq4bw0l6egj9g7xp1xt0uv40 20115 19762 2011-09-16T00:36:11Z O11c 2047 /* Dependencies */ Update dependencies to be more accurate, and remove zlib since the update 20115 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] fte2g5hfgt8er4r3u8yhz33gdcqei1d 20116 20115 2011-09-16T00:38:57Z O11c 2047 /* Set Up Own Server */ Add note about make 3.82 20116 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * If you are running and older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] f53wgpvlicrq7lm80wms8z4or0n05d8 20612 20116 2011-09-25T20:40:27Z Frost 1872 /* Set Up Own Server */ Added more operating systems which don't have GNU make 3.82. In fact, few distros do have it. 20612 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * If you are running and older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian, Ubuntu, Redhat, SuSE, Knoppix, and Cygwin in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ~/tmw-ea/eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * ''git submodule update --merge'' * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] pdk5z9gksb57ol311f8g62u91tpr5db 21600 20612 2011-10-15T22:16:09Z O11c 2047 /* Set Up Own Server */ Add symlinked git hooks 21600 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' * ''cd eathena/'' * If you are running and older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian, Ubuntu, Redhat, SuSE, Knoppix, and Cygwin in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 6gp1mkzk60j1arp3kufsvd7nbzvu6z2 22272 21600 2011-10-31T16:21:11Z O11c 2047 /* Set Up Own Server */ fix instructions regarding git hooks so you're in the correct directory. 22272 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://gitorious.org/+tmw-admins/tmw/tmwa-server-test.git eathena-data'' * ''cd eathena/'' * If you are running and older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian, Ubuntu, Redhat, SuSE, Knoppix, and Cygwin in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the gitorious repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 4ohiw0degkfbt2rfu0ckpzmp9zuou5l 23502 22272 2012-02-16T20:30:25Z Jenalya 1876 Update the url for the content repository 23502 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running and older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian, Ubuntu, Redhat, SuSE, Knoppix, and Cygwin in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] nzdoeopmgratnn1xpezqdp7a29idddo 23625 23502 2012-03-31T16:43:22Z Frost 1872 /* Set Up Own Server */ RH and Cygwin now have make 3.82. Also added step for cygwin lex->flex 23625 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running and older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * If you use cygwin, run the following command now: ''ln -s flex /usr/bin/lex'' * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 1p7q2vof8efagz5vld1ozzbje5zn208 23635 23625 2012-04-21T19:40:50Z O11c 2047 /* Set Up Own Server */ Update instructions (flex fix pushed and an github pushinsteadof for main contributors (although they obviously haven't had any problems so far)) 23635 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running and older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''git config --global url.git@github.com:.pushInsteadOf git://github.com'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] 8ujmvbqphqteznts2poddogtrt6qid0 23675 23635 2012-05-06T09:07:01Z Peablog 2134 /* Set Up Own Server */ 23675 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running an older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''git config --global url.git@github.com:.pushInsteadOf git://github.com'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Java Converter Tool=== This has been my experience on running the java Converter tools, which takes map data from client-data and applies it to the server-data. The README addresses dependencies for using this tool. It suggests there are other ways it can work in the README, if this method does work for you. Edit your map and save it. You can push the client data now. Now, you need to run the converter. # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] bzpe9ehz5psom2auzakqe7ts5ivkcog 24034 23675 2012-07-21T16:41:40Z O11c 2047 /* Java Converter Tool */ was rewritten in python 24034 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running an older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo cp login-server char-server map-server ladmin /usr/local/bin/'' * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''git config --global url.git@github.com:.pushInsteadOf git://github.com'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Python Converter Tool=== After editing maps for the client, you need to generate the walkmaps and imports for the server. To run it, just do: # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] okvbe0t06jgulbhdrbwgcprf90o1srd 24064 24034 2012-08-02T05:12:49Z O11c 2047 /* Set Up Own Server */ update instructions a bit 24064 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running an older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo make install'' (you can use prefix=/path to install somewhere other than /usr/local) * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''git config --global url.git@github.com:.pushInsteadOf git://github.com'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/'' (git 1.7.8 or newer) ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' (git 1.7.7 or older) * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. (This is kind of outdated; with github it's often easier to do patches on branches there) '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== ===Python Converter Tool=== After editing maps for the client, you need to generate the walkmaps and imports for the server. To run it, just do: # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] =Using the Test Server= *[[Testing Server]] =Using The Mana World Workshop= *[http://locke.suu.edu/~adams/mana/workshop/manual/ The Mana World Workshop Manual] =Trouble Shooting= see [http://wiki.themanaworld.org/index.php/Setting_up_eAthena_on_Linux#Troubleshooting for Linux Troubleshooting] teclpd1w35l9eexl1aiibwr5nn2c1s3 24065 24064 2012-08-02T05:15:44Z O11c 2047 Remove dead link and old link, and link to [[Mapping Tutorial]] 24065 wikitext text/x-wiki =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running an older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo make install'' (you can use prefix=/path to install somewhere other than /usr/local) * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''git config --global url.git@github.com:.pushInsteadOf git://github.com'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/'' (git 1.7.8 or newer) ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' (git 1.7.7 or older) * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. (This is kind of outdated; with github it's often easier to do patches on branches there) '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== See [[Mapping Tutorial]]. ===Python Converter Tool=== After editing maps for the client, you need to generate the walkmaps and imports for the server. To run it, just do: # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] bvk0kc4ghqob3uylyhdp2rjf5cinkyj 24070 24065 2012-08-04T19:29:21Z Jenalya 1876 Add link to Working_With_Git 24070 wikitext text/x-wiki We're using Git as version control system for our source files and content. Have a look at our [http://wiki.themanaworld.org/index.php/Working_With_Git Tutorial] about how to use git. =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running an older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo make install'' (you can use prefix=/path to install somewhere other than /usr/local) * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''git config --global url.git@github.com:.pushInsteadOf git://github.com'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/'' (git 1.7.8 or newer) ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' (git 1.7.7 or older) * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. (This is kind of outdated; with github it's often easier to do patches on branches there) '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== See [[Mapping Tutorial]]. ===Python Converter Tool=== After editing maps for the client, you need to generate the walkmaps and imports for the server. To run it, just do: # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] b9adc7gvkw3krws5f2grstruen0gv7z 24071 24070 2012-08-04T19:29:55Z Jenalya 1876 Use upper case for 'Git' 24071 wikitext text/x-wiki We're using Git as version control system for our source files and content. Have a look at our [http://wiki.themanaworld.org/index.php/Working_With_Git Tutorial] about how to use Git. =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://gitorious.org/tmw-eathena/mainline.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running an older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo make install'' (you can use prefix=/path to install somewhere other than /usr/local) * ''git config --global url.git@gitorious.org:.pushInsteadOf git://gitorious.org'' {{ref|push}} {{ref|once}} * ''git config --global url.git@github.com:.pushInsteadOf git://github.com'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/'' (git 1.7.8 or newer) ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' (git 1.7.7 or older) * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open another terminal. * ''mana --server localhost --port 6901 -u -d ~/tmw-ea/eathena-data/client-data'' This should run all three of your servers and the client. '''Make yourself a GM so you can test changes made.''' See [[#Administration]] '''See also:''' [[GM Commands]] '''You are now free to do some changes, first close the client and your servers.''' '''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.''''' * Make your modifications (e.g. Change a map) and save them. * Open a terminal. * ''cd ~/tmw-ea/eathena-data/client-data'' * ''git status'' * ''git add [modified files]'' * ''git commit'' * ''git push'' {{note|push}} * ''cd ..'' * ''make maps'' (if you changed a map) * ''git status'' * ''git add [modified files]'' * ''git add client-data'' (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''') * ''git commit'' * ''git push'' {{note|push}} * Close the terminal. {{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested. {{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories. *''git format-patch -M -C origin/master'' * pastebin the patch(es) and post for review at irc.themanaworld.org channel: #tmw-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. (This is kind of outdated; with github it's often easier to do patches on branches there) '''You can also pull the data which has been modified.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data'' * ''git pull'' * If you haven't installed the hook, ''git submodule update --merge'' at toplevel (for client-data) and in client-data (for music) * Close the terminal. '''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music. == Administration == # Start the servers. # Open a command line terminal. # cd ~/tmw-ea/eathena-data/login # ladmin (not ./ladmin) # add username M password # gm username 99 == Connecting == # Open a command line terminal. # Run your client pointing to your client data and your local server. E.g. mana -u -d ~/tmw-ea/tmwdata --server localhost --port 6901 If all goes well, you are now ready to test new content and participate with development. =Making Content= ==Making Map Content== See [[Mapping Tutorial]]. ===Python Converter Tool=== After editing maps for the client, you need to generate the walkmaps and imports for the server. To run it, just do: # cd ~/tmw-ea/eathena-data/ # make maps After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself. ==Getting Art Content Into The Game== * Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum]. * Work with the Art Director and collaborators on getting the art consistent. * When finished, edit topic as [FND]. * Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT]. * XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT]. ::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition. * Project developer requests database entry reservations from a General Content Team developer. ::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory. ::* Map entry client data affected: .tmx files in the maps directory. ::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made. ::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory. ::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file. ===Handling General Content Team [REQ]s=== * General Content Team member adds a [REQ] topic to the graphics development forum. * General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page. * Art Director attempts to network with other artists to assign the art to an artist. ==Bit Masking== Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing. [http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script] de5vfxr5841aid8e8daeeogwq1ph4wf 24700 24071 2012-10-19T21:18:50Z O11c 2047 Change tmw-eathena on gitorious to tmwa on github 24700 wikitext text/x-wiki We're using Git as version control system for our source files and content. Have a look at our [http://wiki.themanaworld.org/index.php/Working_With_Git Tutorial] about how to use Git. =Set Up= This is a how to help content development for official TMW-eA using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwdata), server-data (eathena-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting. ==Dependencies== In addition to the basic build tools (GCC, Make, headers, ...), Bison, and Flex are needed. '''Debian derivates (including Ubuntu)''' * Open a terminal. * ''sudo apt-get install build-essential flex bison'' ==Set Up Own Server== '''Here are the steps to use when creating a new local testing server.''' * Open a terminal. * ''mkdir ~/tmw-ea'' * ''cd ~/tmw-ea/'' * ''git clone git://github.com/themanaworld/tmwa.git eathena'' * ''git clone --recursive git://github.com/themanaworld/tmwa-server-data.git eathena-data'' * ''cd eathena/'' * If you are running an older version of make: ''mkdir -p obj/{common,login,char,map,ladmin,tool}''. Debian and Ubuntu, in particular are famous for still not having Make 3.82, which is a much more compliant implementation. If you are technically inclined, I recommend installing it in /usr/local. -o11c * ''make'' * ''sudo make install'' (you can use prefix=/path to install somewhere other than /usr/local) * ''git config --global url.git@github.com:.pushInsteadOf git://github.com'' {{ref|push}} {{ref|once}} * ''cd ../eathena-data'' * Preferably, add the update hooks. ** ''ln -s ../../git/hooks/post-merge .git/hooks/'' ** ''ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/'' (git 1.7.8 or newer) ** ''ln -s ../../../git/hooks/post-merge client-data/.git/hooks/'' (git 1.7.7 or older) * ''make conf'' * ''cd client-data'' * ''git checkout master'' * ''cd music'' * ''git checkout master'' '''You can now launch your test server.''' * Open a terminal. * ''cd ~/tmw-ea/eathena-data/'' * ''./char-server& ./login-server& ./map-server&'' * Open