The Mana World - User contributions [en]

User talk:Crush

2009-08-31T17:00:47Z

Crush2: another test

another test

User talk:Crush

2009-08-31T16:58:26Z

Crush2: just a test

test

Archive:Magic system/Implementation

2009-07-03T21:52:09Z

Crush2: /* Special IDs */

==Roadmap==
Proposed roadmap for integration of spellcasting
# Implement the ability for any player to cast a single damage spell of each targeting mode at any time for testing purpose
#* <strike>Netcode for casting spells and notifying players about cast spells</strike>
#* Server-sided handling of spell damage
#* Client-sided handling of spell visualisation
#* <strike>Provisoric user interface for casting spells (command line based?)</strike>
# Implement multiple damage spells of each kind
#* Client- and Serversided XML files for spell properties
# Implement restrictions for spellcasting
#* Implementation of spell scrolls for unlocking spells
#* Keeping track of unlocked spells in the server database
#* Implement equipment pieces with runes
#* Implement runewriting
#* <strike>Implement spell recharging system</strike>
#* Implement netcode to inform the player about available spells <strike>and spell recharge</strike> of its character
#* Spellcasting GUI
# Implement spell skill system
#* Implement skill exp gain for spells
#* Use spell skill level for restricting scroll and spell usage
#* Use spell skill level for damage calculation
# Increase spell variety
#* Implement healing spells
#* Implement ability increase/decrease spells
#* Implement status effect spells
#* Implement scripted spells (for very obscure effects)
# Implement spellcasting ability for AI controlled monsters
# Public beta test to improve balance

== Special IDs ==
Special IDs have to cover magic, weapon-based special attacks and other applications for the special systems (emotes?). They are 32bit long. The first 2 bits decide if it is a spell, physical attack move or something else. How the other applications of the special system use the remaining 30 bit is up to them. Here is how the magic system is going to use them:

0 -- This is a spell and not something else (4 possible)
1 -
2 -- application syllable (64 possibilities, 45 in reserve)
3 -
4 -
5 -
6 -
7 -
8 -- effect syllable element (16 possibilities, 8 in reserve)
9 -
10 -
11 -
12 -- effect syllable power level (16 possibilities, 12 in reserve)
13 -
14 -
15 -
16 -- enhancement syllables bitfield (16 bool values, 9 in reserve)
17 -
18 -
19 -
20 -
20 -
21 -
22 -
23 -
24 -
25 -
26 -
27 -
28 -
29 -
30 -
31 -

Healing spells use different application syllables than attack spells, the element bits are ignored for them and the power level bits are used as-is. Most of the current enhancement syllables don't make sense for healing spells, but I could imagine some new enhancements which do make sense in this context. Maybe we can use these 16 bits for healing-specific enhancements which have a different meanings than the offensive enhancements which use the same bits.

Archive:Magic system/Implementation

2009-07-03T21:40:38Z

Crush2: specialID bit pattern - i have to document this somewhere

==Roadmap==
Proposed roadmap for integration of spellcasting
# Implement the ability for any player to cast a single damage spell of each targeting mode at any time for testing purpose
#* <strike>Netcode for casting spells and notifying players about cast spells</strike>
#* Server-sided handling of spell damage
#* Client-sided handling of spell visualisation
#* <strike>Provisoric user interface for casting spells (command line based?)</strike>
# Implement multiple damage spells of each kind
#* Client- and Serversided XML files for spell properties
# Implement restrictions for spellcasting
#* Implementation of spell scrolls for unlocking spells
#* Keeping track of unlocked spells in the server database
#* Implement equipment pieces with runes
#* Implement runewriting
#* <strike>Implement spell recharging system</strike>
#* Implement netcode to inform the player about available spells <strike>and spell recharge</strike> of its character
#* Spellcasting GUI
# Implement spell skill system
#* Implement skill exp gain for spells
#* Use spell skill level for restricting scroll and spell usage
#* Use spell skill level for damage calculation
# Increase spell variety
#* Implement healing spells
#* Implement ability increase/decrease spells
#* Implement status effect spells
#* Implement scripted spells (for very obscure effects)
# Implement spellcasting ability for AI controlled monsters
# Public beta test to improve balance

== Special IDs ==
Special IDs have to cover magic, weapon-based special attacks and other applications for the special systems (emotes?). They are 32bit long. The first 2 bytes decide if it is a spell, physical attack move or something else. How the other applications of the special system use the remaining 30 bit is up to them. Here is how the magic system is going to use them:

0 -- This is a spell and not something else (4 possible)
1 -
2 -- application syllable (64 possibilities, 45 in reserve)
3 -
4 -
5 -
6 -
7 -
8 -- effect syllable element (16 possibilities, 8 in reserve)
9 -
10 -
11 -
12 -- effect syllable power level (16 possibilities, 12 in reserve)
13 -
14 -
15 -
16 -- enhancement syllables bitfield (16 bool values, 9 in reserve)
17 -
18 -
19 -
20 -
20 -
21 -
22 -
23 -
24 -
25 -
26 -
27 -
28 -
29 -
30 -
31 -

Healing spells use different application syllables than attack spells, the element bits are ignored for them and the power level bits are used as-is. Most of the current enhancement syllables don't make sense for healing spells, but I could imagine some new enhancements which do make sense in this context. Maybe we can use these 16 bits for healing-specific enhancements which have a different meanings than the offensive enhancements which use the same bits.

Archive:Magic system/Implementation

2009-07-03T20:51:41Z

Crush2: updated to current state of the art

Proposed roadmap for integration of spellcasting
# Implement the ability for any player to cast a single damage spell of each targeting mode at any time for testing purpose
#* <strike>Netcode for casting spells and notifying players about cast spells</strike>
#* Server-sided handling of spell damage
#* Client-sided handling of spell visualisation
#* <strike>Provisoric user interface for casting spells (command line based?)</strike>
# Implement multiple damage spells of each kind
#* Client- and Serversided XML files for spell properties
# Implement restrictions for spellcasting
#* Implementation of spell scrolls for unlocking spells
#* Keeping track of unlocked spells in the server database
#* Implement equipment pieces with runes
#* Implement runewriting
#* <strike>Implement spell recharging system</strike>
#* Implement netcode to inform the player about available spells <strike>and spell recharge</strike> of its character
#* Spellcasting GUI
# Implement spell skill system
#* Implement skill exp gain for spells
#* Use spell skill level for restricting scroll and spell usage
#* Use spell skill level for damage calculation
# Increase spell variety
#* Implement healing spells
#* Implement ability increase/decrease spells
#* Implement status effect spells
#* Implement scripted spells (for very obscure effects)
# Implement spellcasting ability for AI controlled monsters
# Public beta test to improve balance

Setting up a server

2009-07-03T13:55:03Z

Crush2: added FreeBSD article

TMW currently uses two different servers. The Ragnarok Online server emulator eAthena for the current official server and the new experimental server TMWServ which is still in development.
*[[Setting up TMWServ]]
*[[Setting up eAthena on Linux]]
*[[Setting up eAthena on FreeBSD]]
*[[Setting up eAthena on Windows]]

Development:Mapping Tutorial

2009-06-26T13:09:24Z

Crush2: slight rewording

{{Status_green}}

== Basics ==
Making maps for The Mana World is not a task that requires a lot of knowledge but is a very good way to become creative and help the game to become more attractive. But getting started can be a little frustrating. Here is a guide that will help you to learn how to make maps.

=== Folders ===
You need to use a certain folder structure when mapping for TMW:
*(some folder)
**graphics
***tiles
****(the tilesets you want)
**maps
***(your map goes here)

=== How to get Tiled ===
The map editor we are using is called Tiled. You can find it at http://mapeditor.org/.

Tiled is a java application. That means it runs on every system that got a Java Runtime Environment. But you need the latest Java Runtime Environment installed on your system. You can get it at http://www.java.com/getjava/.

To start Tiled just click the ''Start Now!'' link on mapeditor.org or download Tiled and open ''tiled.jar'' with the ''java'' binary in your java folder with the additional parameter ''-jar''.

=== Setting up the data files ===

To create the map we need some graphics first, as well as the existing maps to use for reference.

You can get all the files, in the right directory structure, by cloning the "tmwdata" project from our [[Git Repository]].

Alternatively, you can use the data files that are downloaded while playing the game. When you downloaded TMW as an installer packet all map graphics are downloaded at the first start of TMW from the update server and stored in the subfolder "\.tmw\updates" of your home directory as zip archives. Unpack these into the "data" subfolder of your tmw installation.

=== Setting up Tiled for making TMW Maps ===

Tiled is a map editor that isn't made especially for TMW. That means it got a lot of options and settings we don't need.
[[Image:Maptutorial_Newmap.png|right|Settings for a new tmw map]]
To create a new map, press File->New. Use the following settings:

* Map Type: Orthogonal
* Tile Size: 32x32
* Tile Spacing: 0
* Map Size: Should be at least 60x60 but not larger than 200x200 (although the theoretical maximum is much higher). A 20 tile border around the outside of every map is needed ([[Map development/Border|diagram]]). Additionally, a 20 tile border is recommended between rooms for indoor maps, to prevent more than one room from showing at a time on the client.
** In the Argaes woodland, outdoor maps should be 150x120 including the 20 tile border.

=== Importing tilesets ===
[[Image:Maptutorial_Newtileset.png|right|Settings for importing a tileset]]
Now you have to choose the tilesets we want to use on the map. To import a tileset select Tilesets->New Tileset and set the following options:

* Name: (doesn't matter, but it helps if it's decsriptive)
* Tile width: 32
* Tile height: 32 (64 for _x2 tilesets and 96 for _x3 tilesets. [[#Over_sized_tiles|see below]])
* Reference tileset image: checked
* Tile spacing: 0
* Use transparent color: unchecked

Now push the browse button and browse to your TMW folder and then the sub folder graphics/tiles/. Here you will find all tilesets that are used by TMW saved as PNG graphics. Select the one you want.

Please only import the tilesets you want to use. Don't forget to import the Tileset "Collision.png", too. It has a very important purpose that will be explained later.

=== Starting to map ===
Now you can finally start to map. To place tiles on the map select the pen tool from the toolbox to the left. Then select a tile from the tile palette. Now you can place the tiles on the map. Please watch out on what layer you are drawing on because the layers play different roles:
*Use a layer beneath the "Fringe" layer for tiles without transparency. The layers beneath fringe have to be filled completely before you can call the map finished. When there are partially transparent tiles without completely opaque tiles on a layer below strange graphic bugs will appear in the empty area.
*The "Fringe" Layer itself is for oversized tiles which have to be drawn in front or behind moving objects depending on their location. This sorting takes CPU time. Thus you should only use it for the tiles which have to use it.
*Layers above the "Fringe" layer are always drawn over the map sprites. It should be used for objects which are meant to look as if they are far above the game area. Keep in mind that there are monsters which are larger than player characters.
*The "Collision" Layer isn't displayed in the game. It contains the information which parts of the map are walkable and which aren't. Don't put any tiles on it except for the red collision tiles from the collision tileset.

When you are finished with your map you have to determine which tiles are walkable and which aren't. To do so mark all tiles you want to be blocked with the red square from the collision tileset on the collision layer. Be careful that even if a tile is not reachable, but it's walkable, the server can spawn monsters there which can not be killed by the players because they can't reach them. This will lead to all monsters accumulating in the unreachable area until there are no monsters left in the reachable area.

You can check if you did this properly by saving the map, zooming out until the whole map is visible, hiding all layers except for the collision layer, and then using the flood fill tool with the cross tile on the empty area. Any tiles which are still unmarked were not reachable by the players.

Be aware that you need a border of about 20 tiles in every direction that may not be walkable but should be designed properly ([[Map development/Border|diagram]]). Portals to other maps should only be some tiles wide. You can't define the portals with Tiled, by the way. Leave this to the server administrators. The same applies to monster population, NPCs and other interactive objects.

=== Testing your map ===

To test your map you have to replace one of the maps in your TMW folder (in the sub folder data/maps). When you start the game and go to the map you replaced you will see your new map. You will see monsters and other players on the map but don't worry. The other players still see their version of the map and they won't see you walk through walls. Just ignore them while you explore your map.

Sometimes your changed map is overridden by a new version of the map in the updates. In that case you won't see any changes when you change or even remove a map. When you encounter this problem either skip the update loading by starting tmw with the parameter "-u" or delete the file you want to change in all the zip archives you find in the subfolder /updates/.

== Intermediate topics ==

=== Over sized tiles ===

You might have noticed the tilesets ending with _x2.png or _x3.png in the tmw folder containing objects that are two or three tiles high. The new version of tiled allows you to place them with one click. The TMW graphic engine recognizes these over sized tiles when placed on the object layer and automatically draws sprites in front of them when they are south of them and behind them when they are north of them. When importing a _x2 tileset, set the tile height to 64 and when importing a _x3 tileset set it to 96. You should never put an over sized tile on another layer but the object layer.

=== The Stamp ===

The Stamp Feature is a powerful feature of tiled that is hard to find but can save a lot of time. It allows you very quick copy&pasting of a part of a layer. This allows you to draw objects consisting of multiple tiles very quick. Just select the pen tool, press the right mouse button and drag the mouse over the tiles you want to copy. Now you can draw the whole square of tiles over and over again with a single left click. To return to the normal drawing mode just select the pen tool again or choose a tile from the tile palette.

=== Making two maps with a fluent transition ===

When you create an outdoor map it is most likely supposed to be adjacent to an existing map. In this case the transmission from one map to the other should be as seamless as possible. This can only be reached when the border areas of both maps are identical. Unfortunately Tiled can't copy&paste between different maps (OK, it is possible, but it only works correctly when both maps use exactly the same tilesets in exactly the same order). So we developed a command-line based program called TMXcopy for this task. You can find the sourcecode on the Git repository in the folder http://gitorious.org/tmw/mainline/trees/master/tools/tmxcopy A compiled windows binary can be found at http://www.crushnet.org/TempFiles/tmw/tmxcopy.zip

How to use this program is described in its [http://gitorious.org/tmw/mainline/blobs/HEAD/tools/tmxcopy/readme.txt readme file].

To create a map adjacent to an existing one you should:
# Create the new map as described above and save it.
# Use TMXcopy to copy the border area of the old map to the opposite side of the new map. The area should have the double width of the unwalkable area.
# Open the new map and check if the copying worked correctly. Then modify the lower three layers of the copied area to fit into your map. While doing so you should focus on the half of the new area that is inside the walkable area of your map. The half that lies in the border zone of your map should not be modified too much because it is part of the old map.
# Use TMXCopy to copy the new area from the new map back to the old map.
# Update the collision layers on both maps.

Now the border area should be visually identical on both maps. The only difference should be that the unwalkable areas are switched. When sending the map to the team remember to include the new version of the old map.

=== Ambient effects ===
[[Image:Maptutorial_Overlayproperties.png|right|Example for 3 independent scrolling overlays]]
Ambient Effects are a new feature in TMW 0.0.21. They are transparent graphics that will be drawn over your map. All these graphics can scroll independent. They can be used to create a variety of special effects like weather, darkness etc.

To add overlays to your map open your map with Tiled and click Map->Properties to open the map properties dialog. The dialog is a little bit buggy in the current version of Tiled, so make sure that the property has really been set before you save the map. Pressing enter after entering each key and value helps... sometimes.

First you have to choose an image. Do so by adding a key ''overlay0image'' and set its value to the path of the image that you want to use relative to the data directory. For the spotlight effect for example enter ''/graphics/images/ambient/spotlight.png''.

When you want the image to move permanently add the new keys ''overlay0scrollX'' and ''overlay0scrollY'' followed by a number (can be a decimal value). ''overlay0scrollX'' determines the scroll speed to the right (negative values mean scrolling to the left) and ''overlay0scrollY'' the scroll speed down (negative values mean up). both values are in pixels per frame.

You can also define a ''overlay0parallax'' parameter. This parameter affects how much the overlay scrolls when the screen scrolls. A value of 1.0 means that the overlay will stay relative to the ground when the screen scrolls. A value of 0.0 means that the overlay stays relative to the "camera" and is not affected by scrolling. It is a decimal value so you can set it to values between 1 and 0 to create the three dimensional illusion of a layer between the "camera" and the map.

You can create any number of independent overlay graphics. To define a 2nd one create keys with 1 instead of 0, for a 3rd one 2, and so on.

The overlays won't appear in Tiled. They will only appear in the game.

When it doesn't work please check that all key names are written correctly (they are cAsEsEnSiTiVe) and that the numbers of the overlays are consecutive starting from 0.

When you want to create overlay images yourself (transparent 32bit png graphics of any size) please don't forget to make them transparent with your image manipulation program. Otherwise the player won't be able to see the map under it. An opacity of 50% should be the absolute maximum. When you want to create effects that are not meant to obstruct the players view use an opacity between 10% and 20%.

=== Particle effects ===

Check out the article about the [[Particle engine]] for a description about how to add particle effects to your map and how to create new particle effects when the effect you need doesn't exist yet.

=== Animated tiles ===
To make a type of tiles animated go to Tilesets->Tileset Manager. Then select the tileset with the tile and all of its animation frames (they have to be on one tileset) and click on the icon with a pencil on a piece of paper (the tooltip reads "Edit...").

Select the tile you want to be animated on the list to the left. You should see a table on the right with two columns named "Name" and "Value". You have to describe the animation of the tile in this table. Here an example for a 3-phase animation:

NAME VALUE
animation-frame0 0
animation-delay0 100
animation-frame1 16
animation-delay1 100
animation-frame2 48
animation-delay2 100

animation-frameX is the Tile number (as shown in the list on the left) and animation-delayX is how long it is shown (100 is equal to one second).

The animation does not show up in Tiled.

== Creating a Minimap ==

The Creation of a minimap is a task that requires an image manipulation software that supports multiple layers and the PNG format (we recommend [http://www.gimp.org GIMP]). When you are not familiar with using one you should ask one of the artists to create a minimap for your map. When you want to create your own minimap then you should exactly follow the following steps to ensure to stay in style with the rest of the minimaps:
#Open your map with tiled, zoom out until the whole map is visible and use the "save as image" option.
#Open the image with your image manipulation program.
#Resize it so that one pixel represents one tile. When your map is for example 160x100 tiles large (including border zone) your picture should be 160x100 pixels large.
#Create a new transparent layer over the existing one.
#Select the pencil tool with a brush size of 1x1 pixel and with the color #000000 (pure black). Anti aliasing should be deactivated when available.
#Now draw lines on the new layer along the following map features:
#*Cliffs and walls (lower and upper edge)
#*River/lake shores
#*Roads (both sides of the road as single lines)
#*The border of any other large map structure that you feel should be on the map
#Trees or other objects can be represented by single pixels with 50% alpha transparency when there are so many that they affect the game play on the map.
#When you are finished remove the background layer. Now only the black lines should be visible
#Resize the image so the sides are half (50%) as long. You should use the best image filtering method available (cubic filtering in GIMP).
#Save your finished minimap as a PNG image with 32bit color depth and alpha transparency as *your_tmw_folder*/data/graphics/minimaps/*mapname*.png.
#Open your map with Tiled, click Map->Properties in the menu bar and add a new property with the key "minimap" and the value "/graphics/minimaps/*mapname*.png". The properties dialog is a little bit buggy in the current version of Tiled, so make sure that the property has really been set before you save the map.
#Send us both the map and the minimap image

''While this is indeed exactly the way I also created the earlier cave and desert minimaps, I am not entirely happy with this method. Mostly because the final result is a really tiny image, without the ability to easily make versions of it on other scales. I would therefore suggest we try to create future minimaps in vector format using Inkscape. The technique would be similar, placing a scaled down version of the map in the background and drawing black lines on top. The result should however be an image that can take any scale. This would allow us both to put more detail in the minimap for larger scales, and to include a zooming feature (or similar) in the game so that notes and other marks can be placed on the map with higher precision.'' --[[User:BjÃ¸rn|BjÃ¸rn]] 16:04, 16 August 2006 (CEST)

== Sending the map to the dev team ==

There are many ways to send us your map so we can include it in the next release.
;E-Mail: Mail your map to the developers mailing list themanaworld-devel@lists.sourceforge.net. Before you can do so you have to subscribe to it. This is a precaution against spam. You can do so on https://lists.sourceforge.net/lists/listinfo/themanaworld-devel
;IRC: Join our [irc://irc.freenode.net/themanaworld IRC Channel]. When you are not familiar with irc you can find a guide in this [http://forums.themanaworld.org/viewtopic.php?t=747 Forum Thread]. When you are in the channel ask a developer if you can send him your map using DCC or upload your map to a webspace or one click hoster and give us the link.
;Forum: Upload your map to any webspace or one click hoster. An overview graphic (can be created with Tileds "Save as Image" feature) would be nice, too. Visit our [http://forums.themanaworld.org/viewforum.php?f=9 Forum] and register a new account. Then open a new thread, introduce yourself and post a link to your map.

Please understand that we will most likely have some details we would like to have changed before we release your map. so please check back or leave some information how to contact you.

== Hints for good mapping ==

* Before you start with a map you should have a loose idea of the layout. Making a sketch of the map on a piece of paper can be very useful.
* Try to avoid choke points like bridges, mountain passes or corridors that are only one tile wide. They can be blocked very easily.
* Don't put too many similar objects on one screen. Very eye catching tiles should only be used sparingly. Try to break up large areas with the same tile over and over again by throwing in some objects.
* Avoid regular patterns in natural environments. Trees usually don't grow in grid patterns. Rivers, mountain ridges or corridors in caves should never be completely straight.
* Don't map too functional. Give the players something to look at, even when it hasn't got any relevance for the gameplay.
* But keep the playability in mind.

{|-
| A bad mapping style:
| A better mapping style:
|-
| [[Image:Badmap.png]]
| [[Image:Goodmap.png]]
|-
|}

Servers

2009-06-14T14:16:34Z

Crush2: updated for client merge

{{Category_playerinfo}}
{{Status_green}}
 

When you set up your own TMW server and want it to be open for public playing feel free to add it here. To create your own server read [[Setting up a server]]. All servers/projects on this page work with the official client. Servers/Projects listed on [[forks]] are incompatible with the official TMW client, though they are based on it.

== eAthena servers for 0.0.x clients ==

These servers run on eAthena. You can connect to them with the official client from the [http://themanaworld.org/downloads download page].

'''''Security Warning:'' Do not use the same username and password on two different servers. The server admins can read all of them in clear text and nothing stops them from trying them on other servers. It happened a lot in the past that users of the official server got â€œhackedâ€ because they ignored this important precaution.'''

=== Official server ===

The official public server of The Mana World project.

* Hostname: server.themanaworld.org
* Port: 6901 TCP
* Administration: [[User:ElvenProgrammer|Eugenio Favalli]], [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]



===BBB's Server===

An unofficial server hosted by Baseballboy.

* Hostname: BBBs.game-host.org
* Port: 6901 TCP
* Administration: [[User:baseballboy|Baseballboy]]

===The Alternate World===
An unofficial server with different rules. Stable.

* Hostname: tmw.cosmic-cow.net
* Port: 6901 TCP
* Administration: DarkWind

=== The Mana World Brazil ===
There have new maps, New items, New npc's, New quests, new monsters. All There are very welcome.
* Hostname: server.themanaworld.com.br
* Port: 6901 TCP
* Website: http://www.themanaworld.com.br
* Administration: Dark Knight, Gui, Diogorbg.



== TMWServ servers for 0.1 client ==
You can connect to these servers with a client compiled from source when using the TMWServ build target. Note that TMWServ is still in development and doesn't offer real gameplay yet. As a player you will have much more fun on an eAthena server.

=== Official test server ===

The semi-official test server for the new server <code>tmwserv</code>. The server runs in gdb so that we'll even have a chance of finding those rare crashes, but hence may not always be available.

* Hostname: testing.themanaworld.org
* Port: 9601 UDP
* Administration: [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Invertika server ===

A German fork of TMW based on tmwserv with a completely new game world. The server is in alpha status. Downtimes are possible.

* Hostname: server.invertika.org
* Port: 9601 UDP
* Website: http://invertika.org
* Administration: [[User:Seeseekey|seeseekey]]

Servers

2009-06-14T14:09:09Z

Crush2: *sigh* seems like he is not going to learn.

{{Category_playerinfo}}
{{Status_green}}
 

When you set up your own TMW server and want it to be open for public playing feel free to add it here. To create your own server read [[Setting up a server]]. All servers/projects on this page work with the official client. Servers/Projects listed on [[forks]] are incompatible with the official TMW client, though they are based on it.

== eAthena servers for 0.0.x clients ==

These servers run on eAthena. You can connect to them with a client compiled from the <code>0.0</code> branch or with any 0.0.x release.

'''''Security Warning:'' Do not use the same username and password on two different servers. The server admins can read all of them in clear text and nothing stops them from trying them on other servers. It happened a lot in the past that users of the official server got â€œhackedâ€ because they ignored this important precaution.'''

=== Official server ===

The official public server of The Mana World project.

* Hostname: server.themanaworld.org
* Port: 6901 TCP
* Administration: [[User:ElvenProgrammer|Eugenio Favalli]], [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]



===BBB's Server===

An unofficial server hosted by Baseballboy.

* Hostname: BBBs.game-host.org
* Port: 6901 TCP
* Administration: [[User:baseballboy|Baseballboy]]

===The Alternate World===
An unofficial server with different rules. Stable.

* Hostname: tmw.cosmic-cow.net
* Port: 6901 TCP
* Administration: DarkWind

=== The Mana World Brazil ===
There have new maps, New items, New npc's, New quests, new monsters. All There are very welcome.
* Hostname: server.themanaworld.com.br
* Port: 6901 TCP
* Website: http://www.themanaworld.com.br
* Administration: Dark Knight, Gui, Diogorbg.



== TMWServ servers for 0.1 client ==
You can connect to these servers with a client compiled from <code>trunk</code>. Note that TMWServ is still in development and doesn't offer real gameplay yet. As a player you will have much more fun with the 0.0.x client on an eAthena server.

=== Official test server ===

The semi-official test server for the new server <code>tmwserv</code>. The server runs in gdb so that we'll even have a chance of finding those rare crashes, but hence may not always be available.

* Hostname: testing.themanaworld.org
* Port: 9601 UDP
* Administration: [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Invertika server ===

A German fork of TMW based on tmwserv with a completely new game world. The server is in alpha status. Downtimes are possible.

* Hostname: server.invertika.org
* Port: 9601 UDP
* Website: http://invertika.org
* Administration: [[User:Seeseekey|seeseekey]]

Servers

2009-06-14T00:02:20Z

Crush2: Reverted changes by "GUI tmw brasil" 1. removed another server without permission, 2. posted in portugese, 3. posted in messy format

{{Category_playerinfo}}
{{Status_green}}
 

When you set up your own TMW server and want it to be open for public playing feel free to add it here. To create your own server read [[Setting up a server]]. All servers/projects on this page work with the official client. Servers/Projects listed on [[forks]] are incompatible with the official TMW client, though they are based on it.

== eAthena servers for 0.0.x clients ==

These servers run on eAthena. You can connect to them with a client compiled from the <code>0.0</code> branch or with any 0.0.x release.

'''''Security Warning:'' Do not use the same username and password on two different servers. The server admins can read all of them in clear text and nothing stops them from trying them on other servers. It happened a lot in the past that users of the official server got â€œhackedâ€ because they ignored this important precaution.'''

=== Official server ===

The official public server of The Mana World project.

* Hostname: server.themanaworld.org
* Port: 6901 TCP
* Administration: [[User:ElvenProgrammer|Eugenio Favalli]], [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]



===BBB's Server===

An unofficial server hosted by Baseballboy.

* Hostname: BBBs.game-host.org
* Port: 6901 TCP
* Administration: [[User:baseballboy|Baseballboy]]

===The Alternate World===
An unofficial server with different rules. Stable.

* Hostname: tmw.cosmic-cow.net
* Port: 6901 TCP
* Administration: DarkWind



== TMWServ servers for 0.1 client ==
You can connect to these servers with a client compiled from <code>trunk</code>. Note that TMWServ is still in development and doesn't offer real gameplay yet. As a player you will have much more fun with the 0.0.x client on an eAthena server.

=== Official test server ===

The semi-official test server for the new server <code>tmwserv</code>. The server runs in gdb so that we'll even have a chance of finding those rare crashes, but hence may not always be available.

* Hostname: testing.themanaworld.org
* Port: 9601 UDP
* Administration: [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Invertika server ===

A German fork of TMW based on tmwserv with a completely new game world. The server is in alpha status. Downtimes are possible.

* Hostname: server.invertika.org
* Port: 9601 UDP
* Website: invertika.org
* Administration: [[User:Seeseekey|seeseekey]]

User:Kage/Combat Skills

2009-06-12T23:10:43Z

Crush2: removed from contra

{{Status_red}}
{{Opinions
|

{{Pro|Kage}}

|
}}

Currently for weapon skills on TMWServ, we are using weapons (I.E. Knives, Sword, Staff, Axe, Mace, Etc). The issue with this system is that it limits the types of weapons we have. Say if we wanted to have [http://en.wikipedia.org/wiki/Nunchaku Nunchakus] there is no way for us to include them without creating a entirely new weapon skill.

I purpose a system based on not weapons, but weapon classes.

Also this article addresses the issue with defensive skills. Our current system only uses weapons and does not take into account any type of defensives abilities.

Note: things on this page could change to account of balancing.

== Concept ==
Having weapons skills based on what, and how the weapon (or shield) works.

Some weapons can fall into different classes. I.E. Nunchakus would be precision and blunt. Meaning a Nunchaku could use special attacks from both classes.

== Classes ==

=== Slice ===

Weapons that cut your target. Basically cutting attacks fall into this. Almost all swords would fall into this class. Highly effective, but easy to absorb or counter.

=== Puncture ===

Weapons designed penetrate deep into your target. Things like spears would belong to this category.

=== Blunt ===

Blunt weapons neither cut, nor puncture the target. But rather "Smashes" it. A Mace would fall into this.

=== Precision ===

Precision weapons are more like "ninja weapons". Things like knives, daggers, darts, nunchakus, etc. Weapons are not a matter of how hard you hit, but where.

=== Polearm ===

Polearms are in fact a class of weapons. Pretty much anything on a stick, or long, can be consider a polearm. Including staffs, helberds, spears, etc. Polearms take strong hands to handle. But are good for medium range attacks (longer then a sword, shorter then a bow).

=== Ranged ===

Ranged are anything that is thrown or shot at a target. Mainly bows, but can include to crossbars, throwing knifes, etc.

=== Absorb ===

Absorb are mainly your shields. Absorb can also include completely blocked attacks (prehaps though a special)

=== Counter ===

Counters are best described as a defensive/offensive skill. Can be things like parrying, also even turning your opponents damage back towards them.

== Weapon Examples ==

Its important to note that many weapons can belong to many (more then 2) classes. While we should have the option of adding them to more then one, I warn against doing so. Remember we should focus more on fun game play then realism.

These examples are all from my mind, and don't have to reflect the final implementation.

{|border="1"
!Weapon
!Class 1
!Class 2
!Note
|-
|2H Swords
|Slice
|Blunt
|-
|Long Swords
|Slice
|-
|Swords
|Slice
|Counter
|-
|Short Swords
|Slice
|Puncture
|-
|Axes
|Slice
|Blunt
|-
|Maces
|Blunt
|-
|Staffs
|Polearm
|Blunt
|-
|Nunchukes
|Blunt
|Precision
|-
|Spears
|Polearm
|Puncture
|-
|Halberds
|Polearm
|Slice
|-
|Dagger
|Precision
|-
|Bows
|Ranged
|Puncture
|-
|Swing Shots
|Ranged
|Blunt
|-
|Throwing Knives
|Ranged
|Precision
|-
|Shields
|Absorb
|}
As you can see, this system can account for about any weapon you can think of. :-)

== Comments ==
Also see the discussion page.

Development:Mapping Tutorial

2009-06-12T22:20:16Z

Crush2: link to "HEAD" revision of TMXCopy readme file.

{{Status_green}}

== Basics ==
Making maps for The Mana World is not a task that requires a lot of knowledge but is a very good way to become creative and help the game to become more attractive. But getting started can be a little frustrating. Here is a guide that will help you to learn how to make maps.

=== Folders ===
You need to use a certain folder structure when mapping for TMW:
*(some folder)
**graphics
***tiles
****(the tilesets you want)
**maps
***(your map goes here)

=== How to get Tiled ===
The map editor we are using is called Tiled. You can find it at http://mapeditor.org/.

Tiled is a java application. That means it runs on every system that got a Java Runtime Environment. But you need the latest Java Runtime Environment installed on your system. You can get it at http://www.java.com/getjava/.

To start Tiled just click the ''Start Now!'' link on mapeditor.org or download Tiled and open ''tiled.jar'' with the ''java'' binary in your java folder with the additional parameter ''-jar''.

=== Setting up Tiled for making TMW Maps ===

Tiled is a map editor that isn't made especially for TMW. That means it got a lot of options and settings we don't need.
[[Image:Maptutorial_Newmap.png|right|Settings for a new tmw map]]
To create a new map, press File->New. Use the following settings:

* Map Type: Orthogonal
* Tile Size: 32x32
* Tile Spacing: 0
* Map Size: Should be at least 60x60 but not larger than 200x200 (although the theoretical maximum is much higher). A 20 tile border around the outside of every map is needed ([[Map development/Border|diagram]]). Additionally, a 20 tile border is recommended between rooms for indoor maps, to prevent more than one room from showing at a time on the client.
** In the Argaes woodland, outdoor maps should be 150x120 including the 20 tile border.

=== Importing tilesets ===
[[Image:Maptutorial_Newtileset.png|right|Settings for importing a tileset]]
The Map is now ready to be created. But to create it we need some graphics first. When you downloaded TMW as an installer packet all map graphics are downloaded at the first start of TMW from the update server and stored in the subfolder "\.tmw\updates" of your home directory as zip archives. Unpack these into the "data" subfolder of your tmw installation. Alternatively, you can get all the tiles from our [[Git Repository]].

To import a tileset select Tilesets->New Tileset and set the following options:

* Name: (doesn't matter, but it helps if it's decsriptive)
* Tile width: 32
* Tile height: 32 (64 for _x2 tilesets and 96 for _x3 tilesets. [[#Over_sized_tiles|see below]])
* Reference tileset image: checked
* Tile spacing: 0
* Use transparent color: unchecked

Now push the browse button and browse to your TMW folder and then the sub folder graphics/tiles/. Here you will find all tilesets that are used by TMW saved as PNG graphics. Select the one you want.

Please only import the tilesets you want to use. Don't forget to import the Tileset "Collision.png", too. It has a very important purpose that will be explained later.

=== Starting to map ===
Now you can finally start to map. To place tiles on the map select the pen tool from the toolbox to the left. Then select a tile from the tile palette. Now you can place the tiles on the map. Please watch out on what layer you are drawing on because the layers play different roles:
*Use a layer beneath the "Fringe" layer for tiles without transparency. The layers beneath fringe have to be filled completely before you can call the map finished. When there are partially transparent tiles without completely opaque tiles on a layer below strange graphic bugs will appear in the empty area.
*The "Fringe" Layer itself is for oversized tiles which have to be drawn in front or behind moving objects depending on their location. This sorting takes CPU time. Thus you should only use it for the tiles which have to use it.
*Layers above the "Fringe" layer are always drawn over the map sprites. It should be used for objects which are meant to look as if they are far above the game area. Keep in mind that there are monsters which are larger than player characters.
*The "Collision" Layer isn't displayed in the game. It contains the information which parts of the map are walkable and which aren't. Don't put any tiles on it except for the red collision tiles from the collision tileset.

When you are finished with your map you have to determine which tiles are walkable and which aren't. To do so mark all tiles you want to be blocked with the red cross from the collision tileset on the collision layer. Be careful that even if a tile is not reachable, but it's walkable, the server can spawn monsters there which can not be killed by the players because they can't reach them. This will lead to all monsters accumulating in the unreachable area until there are no monsters left in the reachable area.

You can check if you did this properly by saving the map, zooming out until the whole map is visible, hiding all layers except for the collision layer, and then using the flood fill tool with the cross tile on the empty area. Any tiles which are still unmarked were not reachable by the players.

Be aware that you need a border of about 20 tiles in every direction that may not be walkable but should be designed properly ([[Map development/Border|diagram]]). Portals to other maps should only be some tiles wide. You can't define the portals with Tiled, by the way. Leave this to the server administrators. The same applies to monster population, NPCs and other interactive objects.

=== Testing your map ===

To test your map you have to replace one of the maps in your TMW folder (in the sub folder data/maps). When you start the game and go to the map you replaced you will see your new map. You will see monsters and other players on the map but don't worry. The other players still see their version of the map and they won't see you walk through walls. Just ignore them while you explore your map.

Sometimes your changed map is overridden by a new version of the map in the updates. In that case you won't see any changes when you change or even remove a map. When you encounter this problem either skip the update loading by starting tmw with the parameter "-u" or delete the file you want to change in all the zip archives you find in the subfolder /updates/.

== Intermediate topics ==

=== Over sized tiles ===

You might have noticed the tilesets ending with _x2.png or _x3.png in the tmw folder containing objects that are two or three tiles high. The new version of tiled allows you to place them with one click. The TMW graphic engine recognizes these over sized tiles when placed on the object layer and automatically draws sprites in front of them when they are south of them and behind them when they are north of them. When importing a _x2 tileset, set the tile height to 64 and when importing a _x3 tileset set it to 96. You should never put an over sized tile on another layer but the object layer.

=== The Stamp ===

The Stamp Feature is a powerful feature of tiled that is hard to find but can save a lot of time. It allows you very quick copy&pasting of a part of a layer. This allows you to draw objects consisting of multiple tiles very quick. Just select the pen tool, press the right mouse button and drag the mouse over the tiles you want to copy. Now you can draw the whole square of tiles over and over again with a single left click. To return to the normal drawing mode just select the pen tool again or choose a tile from the tile palette.

=== Making two maps with a fluent transition ===

When you create an outdoor map it is most likely supposed to be adjacent to an existing map. In this case the transmission from one map to the other should be as seamless as possible. This can only be reached when the border areas of both maps are identical. Unfortunately Tiled can't copy&paste between different maps (OK, it is possible, but it only works correctly when both maps use exactly the same tilesets in exactly the same order). So we developed a command-line based program called TMXcopy for this task. You can find the sourcecode on the Git repository in the folder http://gitorious.org/tmw/mainline/trees/master/tools/tmxcopy A compiled windows binary can be found at http://www.crushnet.org/TempFiles/tmw/tmxcopy.zip

How to use this program is described in its [http://gitorious.org/tmw/mainline/blobs/HEAD/tools/tmxcopy/readme.txt readme file].

To create a map adjacent to an existing one you should:
# Create the new map as described above and save it.
# Use TMXcopy to copy the border area of the old map to the opposite side of the new map. The area should have the double width of the unwalkable area.
# Open the new map and check if the copying worked correctly. Then modify the lower three layers of the copied area to fit into your map. While doing so you should focus on the half of the new area that is inside the walkable area of your map. The half that lies in the border zone of your map should not be modified too much because it is part of the old map.
# Use TMXCopy to copy the new area from the new map back to the old map.
# Update the collision layers on both maps.

Now the border area should be visually identical on both maps. The only difference should be that the unwalkable areas are switched. When sending the map to the team remember to include the new version of the old map.

=== Ambient effects ===
[[Image:Maptutorial_Overlayproperties.png|right|Example for 3 independent scrolling overlays]]
Ambient Effects are a new feature in TMW 0.0.21. They are transparent graphics that will be drawn over your map. All these graphics can scroll independent. They can be used to create a variety of special effects like weather, darkness etc.

To add overlays to your map open your map with Tiled and click Map->Properties to open the map properties dialog. The dialog is a little bit buggy in the current version of Tiled, so make sure that the property has really been set before you save the map. Pressing enter after entering each key and value helps... sometimes.

First you have to choose an image. Do so by adding a key ''overlay0image'' and set its value to the path of the image that you want to use relative to the data directory. For the spotlight effect for example enter ''/graphics/images/ambient/spotlight.png''.

When you want the image to move permanently add the new keys ''overlay0scrollX'' and ''overlay0scrollY'' followed by a number (can be a decimal value). ''overlay0scrollX'' determines the scroll speed to the right (negative values mean scrolling to the left) and ''overlay0scrollY'' the scroll speed down (negative values mean up). both values are in pixels per frame.

You can also define a ''overlay0parallax'' parameter. This parameter affects how much the overlay scrolls when the screen scrolls. A value of 1.0 means that the overlay will stay relative to the ground when the screen scrolls. A value of 0.0 means that the overlay stays relative to the "camera" and is not affected by scrolling. It is a decimal value so you can set it to values between 1 and 0 to create the three dimensional illusion of a layer between the "camera" and the map.

You can create any number of independent overlay graphics. To define a 2nd one create keys with 1 instead of 0, for a 3rd one 2, and so on.

The overlays won't appear in Tiled. They will only appear in the game.

When it doesn't work please check that all key names are written correctly (they are cAsEsEnSiTiVe) and that the numbers of the overlays are consecutive starting from 0.

When you want to create overlay images yourself (transparent 32bit png graphics of any size) please don't forget to make them transparent with your image manipulation program. Otherwise the player won't be able to see the map under it. An opacity of 50% should be the absolute maximum. When you want to create effects that are not meant to obstruct the players view use an opacity between 10% and 20%.

=== Particle effects ===

Check out the article about the [[Particle engine]] for a description about how to add particle effects to your map and how to create new particle effects when the effect you need doesn't exist yet.

=== Animated tiles ===
To make a type of tiles animated go to Tilesets->Tileset Manager. Then select the tileset with the tile and all of its animation frames (they have to be on one tileset) and click on the icon with a pencil on a piece of paper (the tooltip reads "Edit...").

Select the tile you want to be animated on the list to the left. You should see a table on the right with two columns named "Name" and "Value". You have to describe the animation of the tile in this table. Here an example for a 3-phase animation:

NAME VALUE
animation-frame0 0
animation-delay0 100
animation-frame1 16
animation-delay1 100
animation-frame2 48
animation-delay2 100

animation-frameX is the Tile number (as shown in the list on the left) and animation-delayX is how long it is shown (100 is equal to one second).

The animation does not show up in Tiled.

== Creating a Minimap ==

The Creation of a minimap is a task that requires an image manipulation software that supports multiple layers and the PNG format (we recommend [http://www.gimp.org GIMP]). When you are not familiar with using one you should ask one of the artists to create a minimap for your map. When you want to create your own minimap then you should exactly follow the following steps to ensure to stay in style with the rest of the minimaps:
#Open your map with tiled, zoom out until the whole map is visible and use the "save as image" option.
#Open the image with your image manipulation program.
#Resize it so that one pixel represents one tile. When your map is for example 160x100 tiles large (including border zone) your picture should be 160x100 pixels large.
#Create a new transparent layer over the existing one.
#Select the pencil tool with a brush size of 1x1 pixel and with the color #000000 (pure black). Anti aliasing should be deactivated when available.
#Now draw lines on the new layer along the following map features:
#*Cliffs and walls (lower and upper edge)
#*River/lake shores
#*Roads (both sides of the road as single lines)
#*The border of any other large map structure that you feel should be on the map
#Trees or other objects can be represented by single pixels with 50% alpha transparency when there are so many that they affect the game play on the map.
#When you are finished remove the background layer. Now only the black lines should be visible
#Resize the image so the sides are half (50%) as long. You should use the best image filtering method available (cubic filtering in GIMP).
#Save your finished minimap as a PNG image with 32bit color depth and alpha transparency as *your_tmw_folder*/data/graphics/minimaps/*mapname*.png.
#Open your map with Tiled, click Map->Properties in the menu bar and add a new property with the key "minimap" and the value "/graphics/minimaps/*mapname*.png". The properties dialog is a little bit buggy in the current version of Tiled, so make sure that the property has really been set before you save the map.
#Send us both the map and the minimap image

''While this is indeed exactly the way I also created the earlier cave and desert minimaps, I am not entirely happy with this method. Mostly because the final result is a really tiny image, without the ability to easily make versions of it on other scales. I would therefore suggest we try to create future minimaps in vector format using Inkscape. The technique would be similar, placing a scaled down version of the map in the background and drawing black lines on top. The result should however be an image that can take any scale. This would allow us both to put more detail in the minimap for larger scales, and to include a zooming feature (or similar) in the game so that notes and other marks can be placed on the map with higher precision.'' --[[User:BjÃ¸rn|BjÃ¸rn]] 16:04, 16 August 2006 (CEST)

== Sending the map to the dev team ==

There are many ways to send us your map so we can include it in the next release.
;E-Mail: Mail your map to the developers mailing list themanaworld-devel@lists.sourceforge.net. Before you can do so you have to subscribe to it. This is a precaution against spam. You can do so on https://lists.sourceforge.net/lists/listinfo/themanaworld-devel
;IRC: Join our [irc://irc.freenode.net/themanaworld IRC Channel]. When you are not familiar with irc you can find a guide in this [http://forums.themanaworld.org/viewtopic.php?t=747 Forum Thread]. When you are in the channel ask a developer if you can send him your map using DCC or upload your map to a webspace or one click hoster and give us the link.
;Forum: Upload your map to any webspace or one click hoster. An overview graphic (can be created with Tileds "Save as Image" feature) would be nice, too. Visit our [http://forums.themanaworld.org/viewforum.php?f=9 Forum] and register a new account. Then open a new thread, introduce yourself and post a link to your map.

Please understand that we will most likely have some details we would like to have changed before we release your map. so please check back or leave some information how to contact you.

== Hints for good mapping ==

* Before you start with a map you should have a loose idea of the layout. Making a sketch of the map on a piece of paper can be very useful.
* Try to avoid choke points like bridges, mountain passes or corridors that are only one tile wide. They can be blocked very easily.
* Don't put too many similar objects on one screen. Very eye catching tiles should only be used sparingly. Try to break up large areas with the same tile over and over again by throwing in some objects.
* Avoid regular patterns in natural environments. Trees usually don't grow in grid patterns. Rivers, mountain ridges or corridors in caves should never be completely straight.
* Don't map too functional. Give the players something to look at, even when it hasn't got any relevance for the gameplay.
* But keep the playability in mind.

{|-
| A bad mapping style:
| A better mapping style:
|-
| [[Image:Badmap.png]]
| [[Image:Goodmap.png]]
|-
|}

Development:Mapping Tutorial

2009-06-12T02:23:48Z

Crush2: /* Hints for good mapping */ added example pictures for good and bad mapping

{{Status_green}}

== Basics ==
Making maps for The Mana World is not a task that requires a lot of knowledge but is a very good way to become creative and help the game to become more attractive. But getting started can be a little frustrating. Here is a guide that will help you to learn how to make maps.

=== Folders ===
You need to use a certain folder structure when mapping for TMW:
*(some folder)
**graphics
***tiles
****(the tilesets you want)
**maps
***(your map goes here)

=== How to get Tiled ===
The map editor we are using is called Tiled. You can find it at http://mapeditor.org/.

Tiled is a java application. That means it runs on every system that got a Java Runtime Environment. But you need the latest Java Runtime Environment installed on your system. You can get it at http://www.java.com/getjava/.

To start Tiled just click the ''Start Now!'' link on mapeditor.org or download Tiled and open ''tiled.jar'' with the ''java'' binary in your java folder with the additional parameter ''-jar''.

=== Setting up Tiled for making TMW Maps ===

Tiled is a map editor that isn't made especially for TMW. That means it got a lot of options and settings we don't need.
[[Image:Maptutorial_Newmap.png|right|Settings for a new tmw map]]
To create a new map, press File->New. Use the following settings:

* Map Type: Orthogonal
* Tile Size: 32x32
* Tile Spacing: 0
* Map Size: Should be at least 60x60 but not larger than 200x200 (although the theoretical maximum is much higher). A 20 tile border around the outside of every map is needed ([[Map development/Border|diagram]]). Additionally, a 20 tile border is recommended between rooms for indoor maps, to prevent more than one room from showing at a time on the client.
** In the Argaes woodland, outdoor maps should be 150x120 including the 20 tile border.

=== Importing tilesets ===
[[Image:Maptutorial_Newtileset.png|right|Settings for importing a tileset]]
The Map is now ready to be created. But to create it we need some graphics first. When you downloaded TMW as an installer packet all map graphics are downloaded at the first start of TMW from the update server and stored in the subfolder "\.tmw\updates" of your home directory as zip archives. Unpack these into the "data" subfolder of your tmw installation. Alternatively, you can get all the tiles from our [[Git Repository]].

To import a tileset select Tilesets->New Tileset and set the following options:

* Name: (doesn't matter, but it helps if it's decsriptive)
* Tile width: 32
* Tile height: 32 (64 for _x2 tilesets and 96 for _x3 tilesets. [[#Oversized_tiles|see below]])
* Reference tileset image: checked
* Tile spacing: 0
* Use transparent color: unchecked

Now push the browse button and browse to your TMW folder and then the sub folder graphics/tiles/. Here you will find all tilesets that are used by TMW saved as PNG graphics. Select the one you want.

Please only import the tilesets you want to use. Don't forget to import the Tileset "Collision.png", too. It has a very important purpose that will be explained later.

=== Starting to map ===
Now you can finally start to map. To place tiles on the map select the pen tool from the toolbox to the left. Then select a tile from the tile palette. Now you can place the tiles on the map. Please watch out on what layer you are drawing on because the layers play different roles:
*Use a layer beneath the "Fringe" layer for tiles without transparency. The layers beneath fringe have to be filled completely before you can call the map finished. When there are partially transparent tiles without completely opaque tiles on a layer below strange graphic bugs will appear in the empty area.
*The "Fringe" Layer itself is for oversized tiles which have to be drawn in front or behind moving objects depending on their location. This sorting takes CPU time. Thus you should only use it for the tiles which have to use it.
*Layers above the "Fringe" layer are always drawn over the map sprites. It should be used for objects which are meant to look as if they are far above the game area. Keep in mind that there are monsters which are larger than player characters.
*The "Collision" Layer isn't displayed in the game. It contains the information which parts of the map are walkable and which aren't. Don't put any tiles on it except for the red collision tiles from the collision tileset.

When you are finished with your map you have to determine which tiles are walkable and which aren't. To do so mark all tiles you want to be blocked with the red cross from the collision tileset on the collision layer. Be careful that even if a tile is not reachable, but it's walkable, the server can spawn monsters there which can not be killed by the players because they can't reach them. This will lead to all monsters accumulating in the unreachable area until there are no monsters left in the reachable area.

You can check if you did this properly by saving the map, zooming out until the whole map is visible, hiding all layers except for the collision layer, and then using the flood fill tool with the cross tile on the empty area. Any tiles which are still unmarked were not reachable by the players.

Be aware that you need a border of about 20 tiles in every direction that may not be walkable but should be designed properly ([[Map development/Border|diagram]]). Portals to other maps should only be some tiles wide. You can't define the portals with Tiled, by the way. Leave this to the server administrators. The same applies to monster population, NPCs and other interactive objects.

=== Testing your map ===

To test your map you have to replace one of the maps in your TMW folder (in the sub folder data/maps). When you start the game and go to the map you replaced you will see your new map. You will see monsters and other players on the map but don't worry. The other players still see their version of the map and they won't see you walk through walls. Just ignore them while you explore your map.

Sometimes your changed map is overridden by a new version of the map in the updates. In that case you won't see any changes when you change or even remove a map. When you encounter this problem either skip the update loading by starting tmw with the parameter "-u" or delete the file you want to change in all the zip archives you find in the subfolder /updates/.

== Intermediate topics ==

=== Over sized tiles ===

You might have noticed the tilesets ending with _x2.png or _x3.png in the tmw folder containing objects that are two or three tiles high. The new version of tiled allows you to place them with one click. The TMW graphic engine recognizes these over sized tiles when placed on the object layer and automatically draws sprites in front of them when they are south of them and behind them when they are north of them. When importing a _x2 tileset, set the tile height to 64 and when importing a _x3 tileset set it to 96. You should never put an over sized tile on another layer but the object layer.

=== The Stamp ===

The Stamp Feature is a powerful feature of tiled that is hard to find but can save a lot of time. It allows you very quick copy&pasting of a part of a layer. This allows you to draw objects consisting of multiple tiles very quick. Just select the pen tool, press the right mouse button and drag the mouse over the tiles you want to copy. Now you can draw the whole square of tiles over and over again with a single left click. To return to the normal drawing mode just select the pen tool again or choose a tile from the tile palette.

=== Making two maps with a fluent transition ===

When you create an outdoor map it is most likely supposed to be adjacent to an existing map. In this case the transmission from one map to the other should be as seamless as possible. This can only be reached when the border areas of both maps are identical. Unfortunately Tiled can't copy&paste between different maps (OK, it is possible, but it only works correctly when both maps use exactly the same tilesets in exactly the same order). So we developed a command-line based program called TMXcopy for this task. You can find the sourcecode on the SVN repository in the folder http://themanaworld.svn.sourceforge.net/viewvc/themanaworld/tmw/branches/0.0/tools/tmxcopy/ A compiled windows binary can be found at http://www.crushnet.org/TempFiles/tmw/tmxcopy.zip

How to use this program is described in its [http://themanaworld.svn.sourceforge.net/viewvc/*checkout*/themanaworld/tmw/branches/0.0/tools/tmxcopy/readme.txt readme file].

To create a map adjacent to an existing one you should:
# Create the new map as described above and save it.
# Use TMXcopy to copy the border area of the old map to the opposite side of the new map. The area should have the double width of the unwalkable area.
# Open the new map and check if the copying worked correctly. Then modify the lower three layers of the copied area to fit into your map. While doing so you should focus on the half of the new area that is inside the walkable area of your map. The half that lies in the border zone of your map should not be modified too much because it is part of the old map.
# Use TMXCopy to copy the new area from the new map back to the old map.
# Update the collision layers on both maps.

Now the border area should be visually identical on both maps. The only difference should be that the unwalkable areas are switched. When sending the map to the team remember to include the new version of the old map.

=== Ambient effects ===
[[Image:Maptutorial_Overlayproperties.png|right|Example for 3 independent scrolling overlays]]
Ambient Effects are a new feature in TMW 0.0.21. They are transparent graphics that will be drawn over your map. All these graphics can scroll independent. They can be used to create a variety of special effects like weather, darkness etc.

To add overlays to your map open your map with Tiled and click Map->Properties to open the map properties dialog. The dialog is a little bit buggy in the current version of Tiled, so make sure that the property has really been set before you save the map. Pressing enter after entering each key and value helps... sometimes.

First you have to choose an image. Do so by adding a key ''overlay0image'' and set its value to the path of the image that you want to use relative to the data directory. For the spotlight effect for example enter ''/graphics/images/ambient/spotlight.png''.

When you want the image to move permanently add the new keys ''overlay0scrollX'' and ''overlay0scrollY'' followed by a number (can be a decimal value). ''overlay0scrollX'' determines the scroll speed to the right (negative values mean scrolling to the left) and ''overlay0scrollY'' the scroll speed down (negative values mean up). both values are in pixels per frame.

You can also define a ''overlay0parallax'' parameter. This parameter affects how much the overlay scrolls when the screen scrolls. A value of 1.0 means that the overlay will stay relative to the ground when the screen scrolls. A value of 0.0 means that the overlay stays relative to the "camera" and is not affected by scrolling. It is a decimal value so you can set it to values between 1 and 0 to create the three dimensional illusion of a layer between the "camera" and the map.

You can create any number of independent overlay graphics. To define a 2nd one create keys with 1 instead of 0, for a 3rd one 2, and so on.

The overlays won't appear in Tiled. They will only appear in the game.

When it doesn't work please check that all key names are written correctly (they are cAsEsEnSiTiVe) and that the numbers of the overlays are consecutive starting from 0.

When you want to create overlay images yourself (transparent 32bit png graphics of any size) please don't forget to make them transparent with your image manipulation program. Otherwise the player won't be able to see the map under it. An opacity of 50% should be the absolute maximum. When you want to create effects that are not meant to obstruct the players view use an opacity between 10% and 20%.

=== Particle effects ===

Check out the article about the [[Particle engine]] for a description about how to add particle effects to your map and how to create new particle effects when the effect you need doesn't exist yet.

=== Animated tiles ===
To make a type of tiles animated go to Tilesets->Tileset Manager. Then select the tileset with the tile and all of its animation frames (they have to be on one tileset) and click on the icon with a pencil on a piece of paper (the tooltip reads "Edit...").

Select the tile you want to be animated on the list to the left. You should see a table on the right with two columns named "Name" and "Value". You have to describe the animation of the tile in this table. Here an example for a 3-phase animation:

NAME VALUE
animation-frame0 0
animation-delay0 100
animation-frame1 16
animation-delay1 100
animation-frame2 48
animation-delay2 100

animation-frameX is the Tile number (as shown in the list on the left) and animation-delayX is how long it is shown (100 is equal to one second).

The animation does not show up in Tiled.

== Creating a Minimap ==

The Creation of a minimap is a task that requires an image manipulation software that supports multiple layers and the PNG format (we recommend [http://www.gimp.org GIMP]). When you are not familiar with using one you should ask one of the artists to create a minimap for your map. When you want to create your own minimap then you should exactly follow the following steps to ensure to stay in style with the rest of the minimaps:
#Open your map with tiled, zoom out until the whole map is visible and use the "save as image" option.
#Open the image with your image manipulation program.
#Resize it so that one pixel represents one tile. When your map is for example 160x100 tiles large (including border zone) your picture should be 160x100 pixels large.
#Create a new transparent layer over the existing one.
#Select the pencil tool with a brush size of 1x1 pixel and with the color #000000 (pure black). Anti aliasing should be deactivated when available.
#Now draw lines on the new layer along the following map features:
#*Cliffs and walls (lower and upper edge)
#*River/lake shores
#*Roads (both sides of the road as single lines)
#*The border of any other large map structure that you feel should be on the map
#Trees or other objects can be represented by single pixels with 50% alpha transparency when there are so many that they affect the game play on the map.
#When you are finished remove the background layer. Now only the black lines should be visible
#Resize the image so the sides are half (50%) as long. You should use the best image filtering method available (cubic filtering in GIMP).
#Save your finished minimap as a PNG image with 32bit color depth and alpha transparency as *your_tmw_folder*/data/graphics/minimaps/*mapname*.png.
#Open your map with Tiled, click Map->Properties in the menu bar and add a new property with the key "minimap" and the value "/graphics/minimaps/*mapname*.png". The properties dialog is a little bit buggy in the current version of Tiled, so make sure that the property has really been set before you save the map.
#Send us both the map and the minimap image

''While this is indeed exactly the way I also created the earlier cave and desert minimaps, I am not entirely happy with this method. Mostly because the final result is a really tiny image, without the ability to easily make versions of it on other scales. I would therefore suggest we try to create future minimaps in vector format using Inkscape. The technique would be similar, placing a scaled down version of the map in the background and drawing black lines on top. The result should however be an image that can take any scale. This would allow us both to put more detail in the minimap for larger scales, and to include a zooming feature (or similar) in the game so that notes and other marks can be placed on the map with higher precision.'' --[[User:BjÃ¸rn|BjÃ¸rn]] 16:04, 16 August 2006 (CEST)

== Sending the map to the dev team ==

There are many ways to send us your map so we can include it in the next release.
;E-Mail: Mail your map to the developers mailing list themanaworld-devel@lists.sourceforge.net. Before you can do so you have to subscribe to it. This is a precaution against spam. You can do so on https://lists.sourceforge.net/lists/listinfo/themanaworld-devel
;IRC: Join our [irc://irc.freenode.net/themanaworld IRC Channel]. When you are not familiar with irc you can find a guide in this [http://forums.themanaworld.org/viewtopic.php?t=747 Forum Thread]. When you are in the channel ask a developer if you can send him your map using DCC or upload your map to a webspace or one click hoster and give us the link.
;Forum: Upload your map to any webspace or one click hoster. An overview graphic (can be created with Tileds "Save as Image" feature) would be nice, too. Visit our [http://forums.themanaworld.org/viewforum.php?f=9 Forum] and register a new account. Then open a new thread, introduce yourself and post a link to your map.

Please understand that we will most likely have some details we would like to have changed before we release your map. so please check back or leave some information how to contact you.

== Hints for good mapping ==

* Before you start with a map you should have a loose idea of the layout. Making a sketch of the map on a piece of paper can be very useful.
* Try to avoid choke points like bridges, mountain passes or corridors that are only one tile wide. They can be blocked very easily.
* Don't put too many similar objects on one screen. Very eye catching tiles should only be used sparingly. Try to break up large areas with the same tile over and over again by throwing in some objects.
* Avoid regular patterns in natural environments. Trees usually don't grow in grid patterns. Rivers, mountain ridges or corridors in caves should never be completely straight.
* Don't map too functional. Give the players something to look at, even when it hasn't got any relevance for the gameplay.
* But keep the playability in mind.

{|-
| A bad mapping style:
| A better mapping style:
|-
| [[Image:Badmap.png]]
| [[Image:Goodmap.png]]
|-
|}

File:Goodmap.png

2009-06-12T02:17:52Z

Crush2: Example of a good mapping style

Example of a good mapping style

File:Badmap.png

2009-06-12T02:17:11Z

Crush2: Example of a bad mapping style

Example of a bad mapping style

Archive:Magic system

2009-06-12T00:35:12Z

Crush2: add link to Adamaixs description of the eAthena magic system.

{{Status_yellow}}
This is the magic system we decided to use for the new mana world server. For an overview of the magic system of the current server please refer to [[User:Adamaix/Magic_walkthrough]].

Short synopsis: All mage equipment has runes. Every rune holds one spell. The runes are discharged when the spell is cast and has to be recharged before it can be used again. Recharge happens automatically. The recharge speed is based on intelligence. The skill levels decides what kind of runes the character can have in its equipment and thus what kind of spells it can cast. High level equipment can have more and better runes than low level equipment. Willpower is important for the damage or success chance of the spells cast.

For a game-lore explanation of how magic works see [[The nature of mana and magic]].

==Recharge bar instead of magic points==
There are no magic points. Instead of that every single spell has its own recharge bar. When a spell is cast its recharge bar has to be filled again before the spell can be cast again.

The character got a constant "mana flow" that recharges its spells. The intensity of this flow is mainly influenced by intelligence but other factors might influence it, too. The mana flow is divided evenly between all spells that are currently recharged. Recharge of each spell can be switched on and off by the player. That means the character may decide to deactivate the recharge of some spells to recharge others more quickly. Advanced spells require more mana flow points to recharge them than simple ones.

Characters can have the same spell multiple times allowing them to cast them multiple times in a row (see below for details) but only one of them can be recharged at the same time. All spells have a short after cast delay time in which no new spells can be cast to avoid spamming spells very fast. The more powerful the spell the longer the after cast delay.

==Available spells==
The spells that are available to a character depend on the spell runes written on his currently worn equipment. Every rune represents one spell. Runes can be created by players by combining different rune syllables. For a description of the rune combination system see [[Rune combination]]. The character can only use spells when he 1. has the minimum skill level for the rune and 2. learned all the syllables of the rune by doing the quests to obtain them. When the character does not fulfill these requirements the rune is ignored.

===Runes===
The spells that are available for the character at the moment depend on the magic runes that are written on /engraved in its currently worn equipment.

All equipment for spellcasters (and maybe some non-spellcaster equipment) has rune slots. These slots can be engraved with runes. Every rune represents one charge of a specific spell.

Runes of advanced spells fill multiple rune slots in the same equipment piece. Equipment with enough rune slots to hold the runes of advanced spells should be restricted to characters that reached a high magical skill level and/or high magic related attributes.

The most spell runes can be written on robes closely followed by wands. Then comes headgears and then other equipment pieces (assuming that they all have similar requirements and rareness). Other weapons can usually not have runes with the exception of some special "rune" weapons (which have usually sub-par combat abilitys compared with weapons with similar requirements and rareness). That means hybrid characters will most likely wear fighter armor with a magican headgear and maybe a rune weapon.

Characters can theoretically extend their spell palette by carrying multiple equipment pieces with different runes in their inventory and switch them. But when an equipment piece is taken off all its slots are uncharged.

To write runes on a piece of equipment one needs the "runewriting" crafting skill and needs to learn the rune syllables. The success chance depends on the minimum skill level to cast the spell and the runewriting skill of the crafter. When the runewriting fails the equipment piece might be destroyed.

:'''Example:''' When a character wants to have 3 charges of a flame bolt spell he needs:
:* Fire Magic Skill level 25
:* Knowledge of the "Flame" and the "Bolt" rune accquired through quests
:* 3 flame bolt runes written on equipment pieces he is wearing

==Damage calculation==
The damage of spells and the success rate of spells that can fail depend on the characters willpower and skill level in the magic discipline of the spell and the targets willpower. See [[Damage calculation]] for details.

Efficiency of support spells like attribute increases (buffs in MMORPG jargon) or healing spells should not be based on willpower but on skill level alone. That way I want to archieve that the ideal attribute build of a supportive mage (cleric) is different from that of an offensive mage.

:'''Example:''' A typical offensive spellcaster character with a mix of willpower and intelligence could function as a backup healer by taking some healing runes in its equipment. But it could cast its healing spells much less frequently than a character that is focused on intelligence alone. A character focused on intelligence, on the other hand, could cast offensive spells frequently but they would do almost no damage. So the character would be better of with focusing on heal and support spells that aren't affected by willpower.

==GUI==
Here a mockup of the OSD that shows the current magic status:

[[Image:Magicdemo.png]]
# Firewall spell - fully charged and ready, will be recharged immediately after use.
# Lightning Bolt spell - not charged, currently not recharged.
# Fire rain spell - recharge in progress and half finished.
# Three fireball spells - one ready, one partially charged but recharge currently deactivated.
# Four lightning strike spells - two ready, one partially charged and recharge in progress.

The background of each spell icon doubles as a progress bar. The color of the icon itself indicates the element of the spell and the charge level. When the color of the icon itself is bright, recharge is activated. When the color is dark, recharge is deactivated. When a spell is fully charged and ready for use it is indicated by a particle effect on the icon.

Spell icons of the same spell are grouped in one frame and sorted by recharge level. The charge activation status of spells it the whole group is linked although only one spell is recharged at the same time.

The letters in the upper-left corner of the spell icons are the hotkeys for the spells. It should be possible to redefine those in the keyboard gui (setting a key for every spell in the game would be overkill. Instead of that keys should be defined for spell 1, spell 2, spell 3 etc.)

===Controls===
;Mouse:Left-click on a spell icon uses the spell, right-click activates/deactivates its recharge.
;Gamepad: One button opens a spell ring menu to select a spell. Another press of this button uses the selected spell. A 2nd button activates/deactivates the recharge of the spell. A 3rd button closes the menu without casting a spell.
;Keyboard: Each spell has a hotkey. Pressing the hotkey casts it. Pressing shift + the hotkey toggles recharge. The ring menu can be used as an alternative casting method.

==Types of spells==

=== Effects ===
These are some examples of effects that can be caused by spells.

====Negative====
;Damage: Just plain old damage to a single target.
;Splash damage: Hurts the target and targets around it with reduced power.
;Damage over time: Hurts the target at regular intervals
;Attribute reduction: Reduction of an attribute by percentual or absolute value or affects the victim with a negative status effect. Might or might not stack.

====Positive:====
;Healing: self-explaining.
;Healing over time: A temporary status effect that heals the target at regular intervals.
;Attribute increase: A temporary status effect that increases an attribute by a percentual or absolute value.
;Restore: Attempts to removes a negative status effect.

=== Targeting modes===
Different spells have different ways of determining what targets are affected by it.

;Single-targeted spells: Targeted spells are spells that hit exactly one target that has to be selected when the spell is cast.
;Area-targeted spells: Area spells can be cast on any position the caster has a sightline to. The position has to be selected when the spell is cast.
;Area-persisten spells: Like area spells but stay active for a while and do their effect every game tick.
;Untargeted spells: Spells that have a fixed damage zone based on the position and heading of the caster. They don't require to set a target.
;Untargeted persistent spells: Like untargeted spells but stay active for a while and do their effect every game tick. When the caster moves the effect area moves with him/her.
;Projectile spells: Spells that are cast like single-targeted spells but fly towards the target and hit the first enemy they collide with. They don't require to select a target.

User:John Pyle/Woodland Cemetery

2009-06-11T21:29:38Z

Crush2: I would like to have an excuse to place a few zombies on the swamp maps near the graveyard.

{{Status_red}}
{{Category_worldconcept}}

The Woodland Cemetery, south-west of [[User:John Pyle/Hurnscald|Hurnscald]], is the only place there exists undead monsters. Once a beautifully peaceful and quiet place, Magicians practicing necromancy unintentionally filled the cemetery's dead with new life. The living dead creatures were violent, and the town of Hurnscald was at risk. Out of desperation, the magicians cast a spell that condemned the creatures within the confines of the cemetery.

==Lore==
===The Risen===

Twenty years ago, a well respected guild of magicians claimed that mana could be used for necromancy. Early during their study of the art, still theoretical, Sir Truk Dermish, the great hero of [[User:John Pyle/Tempus|Tempus]], was killed in battle. The citizens and leaders of Hurnscald knew of the magicians studies and demanded that they take action and resurrect their fallen hero. Facing expulsion from the emotionally erratic people, the guild gathered in the cemetery.

As the clan of magicians read from the [[Magic system|runes]] they had fashioned, they poured all of their hope and energy into the magic of [[The nature of mana and magic|mana]] to bring back Sir Truk. They did not realize the power of their spells, however. The ground suddenly began to shake as remains of the dead began unearthing themselves from the ground. Lost spirits materialized and risen bodies angrily attacked the magicians and the crowd of onlookers.

The undead chased the townspeople back toward Hurnscald as warriors and magicians rallied to fight back the small horde. They fought for many hours and pushed the creatures back to the cemetery. To their dismay, any of the creatures that they dispatched quickly returned to fight again.

For days fighters held the undead horde within the limits of the cemetery, stalling as the magicians scrambled to find a way to end the terror they had unleashed. The magicians managed a cursing spell to bind all of the creatures to the grounds of the cemetery, which they cast as all of the warriors retreated through the gate of the cemetery.

===Today===

While to this day we do not know how long the creatures will haunt the cemetery, if not forever, the guild that is now referred to as the Black Magicians has all but given up hope of finding a way to reverse the spell. It is unclear as to why the reanimated creatures do not act as humans; if they are human souls or just corpses puppeted by the unknown. They do not respond to the living, they only fight and kill.

(note that the Black Magicians are named as such not after their robes, but their reputation from the horrific cemetery incident. They are in no way 'evil' nor do they still practice the dark art of necromancy. They are even regaining much of their respect in recent years for their aid of Keshlam in the Modern War for Tonori)

In the last months a few zombies have been spotted outside of the cemetery. This is a sign that the power of the curse which binds the undeads to the cemetery seems to diminish.

==Game Play==
===NPCs===
====The Caretaker====

The Caretaker was inadvertently bound by the curse set by the magicians. He had not wanted to leave the grave site of his recently deceased wife while the townspeople were fighting the horde, and had not been aware of the magicians' plan. He now watches as she wanders as one of the undead. He protects her from being killed by the many warriors who come to fight the reanimated corpses.

Airlia, a clerk for Hurnscald Town Hall, is the caretaker's daughter whom the caretaker sends letters to with the help of willing adventurers.

====The Fighters of the Undead====

Three "honorable" warriors and members of the Warrior Guild, these men are on a dedicated mission to kill and re-kill the skeletons and zombies of the cemetery. It is the belief of the Warrior Guild that each time on of the creatures falls it loses of its mana, eventually becoming completely depleted.

Each of the warriors has a story as to why they are involved in this quest, and although they are too weak to face him alone, they believe that Sir Truk is the leader of the undead and that his mana feeds the rest of his army.

==Notes==
Please provide comments, suggestions, or questions here.

Classic:Maps

2009-06-11T05:42:31Z

Crush2: /* Existing maps */ reserved map numbers for graveyard

{{Status_green}}
Maps are an important part of The Mana World.

== Guidelines ==
You can build a map for The Mana World using [http://mapeditor.org Tiled]

* '''Size:''' around 200x200 tiles is good in practice, though the theoretical maximum is 2048x2048
** In the Argaes woodland, outdoor maps should be 150x120 including the 20 tile border. 
* '''Tile size:''' 32x32
* '''Map border:''' you have to leave an empty border around the map of at least 20 tiles ([[Map development/Border|Diagram]])
* '''Walls/players proportions:''' a normal door for a player is 2 tiles in height
* '''Indoor/Outdoor proportions:''' it is not required that inside view of buildings has to fit the size in outside view
* '''Path reference:''' please use tmw folder structure to keep references to tilesets working
* '''Transparent color:''' tilesets use alpha so no need to set a transparent color
* '''Layers:''' each map can have many layers. Two layers are special:
** ''Fringe:'' this layer is drawn simultaneously with items and beings, where tiles above a being are drawn below the being and tiles below the being are drawn above. Hence this layer is suitable for adding static objects to a map like plants or statues.
** ''Collision:'' this is a special layer for which you have to use the collision tileset. Use the red collision tile where you want a tile to be unwalkable. Be careful that even if a tile is not reachable, but it's walkable, the server can spawn monsters there, so you won't be able to reach them, or you can cause weird situations. For example fill a wall with collision tiles, not only the borders, or you could have monsters spawning inside the wall.

In a good style of mapping, please always use the lowest layer as possible (this is also in the interests of performance, since it keeps down overdraw).

==Existing maps==

Here a list of all existing maps:

{|
!colspan=2|Map
! Description
|-
| 001
| 1
| Tulimshar
|-
|
| 2
| Tulimshar indoor
|-
|
| 3
| Tulimshar arena
|-
| 002
| 1
| Sandstorm, south of Tulimshar
|-
|
| 3
| Desert mines, level 1
|-
|
| 4
| Desert mines, level 2
|-
| 003
| 1
| Beach leading to woodlands
|-
| 004
| 1
| Beach west of Tulimshar
|-
|
| 2
| Beach house
|-
| 005
| 1
| Snake desert, SW of Tulimshar
|-
|
| 3
| Snake pit
|-
| 006
| 1
| Desert mountains
|-
|
| 3
| Desert mountains caves
|-
| 007
| 1
| South east woodland
|-
| 008
| 1
| Woodland around Hurnscald
|-
| 009
| 1
| Hurnscald
|-
|
| 2
| Hurnscald indoor
|-
|
| 3
| Cave beneath Hurnscald
|-
| 010
| 1
| South woodland
|-
|
| 2
| Dimond's Cove
|-
| 011
| 1
| Central woodland
|-
|
| 3
| Hermit's cave
|-
|
| 4
| Lake cave
|-
| 012
| 1
| North woodland
|-
|
| 3
| North woodland caves
|-
| 013
| 1
| North east woodland
|-
|
| 2
| Magic house
|-
|
| 3
| Cave
|-
| 014
| 1
| West woodland
|-
|
| 3
| West woodland caves
|-
| 015
| 1
| South west woodland
|-
| 016
| 1
| Southernmost woodlands
|-
| 017
| 1
| North woodland mountains
|-
|
| 3
| North woodland mountain caves
|-
| 018
| 1
| Woodland mines (outdoor)
|-
|
| 2
| Woodland mines (mining camp indoor)
|-
|
| 3
| Woodland mines level 1
|-
| 019
| 1
| Snow field
|-
| 020
| 1
| Snow town
|-
|
| 2
| Snow town indoor
|-
|
| 3
| Snow town cave level 1
|-
|
| 4
| Snow town cave level 2
|-
| 021
| 1
| Central Tulimshar
|-
|
| 2
| Central Tulimshar Indoor **
|-
| 022
| 1
| Tulimshar Docks **
|-
| 023
| 1
| Beach Cliffs **
|-
| 024
| 1
| Tulimshar Canyon **
|-
|
| 2
| Tulimshar Magic School **
|-
| 025
| 1
| Graveyard Swamp East *
|-
| 026
| 1
| Graveyard Swamp West *
|-
| 027
| 1
| Graveyard **
|-
|}

(<nowiki>*</nowiki>) Map pending release
(<nowiki>**</nowiki>) Map planned or under construction

== How to map ==

When you want to make maps for The Mana World but you don't know how to start, read the [[Mapping Tutorial]].

== Map naming ==
The naming scheme we're using at the moment is described in it's own article here: [[EAthena Map Names]].

On the new server we will be able to have a much more convenient map names. Refer to the [[Map Naming]] article for details.

== Needed maps ==

The current priority is the expansion of the woodland area and transform it to the northern area of the [[Argaes]] continent. The plan is to expand the current area to the northeast. A tileset for the trade city is currently in development. This time should be used to close the gap between Hurnscald (map 18) and the new trade city and map the trade cities surrounding.

[[Image:Argaes-north-development.png]]

You can visit the following [http://forums.themanaworld.org/viewtopic.php?f=13&t=4268 forum thread] for currently needed mapping tasks.

User:Crush

2009-06-02T16:05:04Z

Crush2: added link to my kaizai article

:::''"A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects."''
::::-- Robert A. Heinlein

I am contributing to many different aspects of the project. Pixel artist, mapper, programmer, game concepts and i even tried to compose music, although with minor success. My credo is "when you want something to be done properly, do it yourself".

I am always concerned about the opinions of other developers and the fan base. So i am usually showing a lot of unfinished work on the forum.

==Projects I took part in==

=== Pixel Art ===
These pieces of art are mostly made by me:
* Woodland tileset
* Woodland Village indoor and outdoor tilesets
* Pink monster
* Ambient GFX
* Female version of cotton shirt
* Some tuneups at female player set
* The following Headgear sprites: Miners helm, Fancy hat, Headbands, Santa hat
* Light platemail armor

I also made some minor improvements at the following pieces:
* Desert tileset
* Dropshadow of the bats
* Shading of the mushroom monster.

=== Maps ===
The maps made by me in chronological order of creation:
* new_9-1.tmx.gz (first woodland map)
* new_4-1.tmx.gz (Bat Cave)
* new_14-1.tmx.gz (woodland map released with 0.0.21)
* new_15-1.tmx.gz (desert map released with 0.0.21)
* new_16-1.tmx.gz (woodland map released with 0.0.21)
* new_18-1.tmx.gz (woodland village surrounding)
* new_19-1.tmx.gz (woodland village outdoor)
* new_20-1.tmx.gz (woodland village indoor)

=== Programming ===
These are the subsystems where i was the major programmer:
====Client====
* XML based animation system
* Ambient overlays
* Smooth scrolling
* XML based client-sided equipment sprite database and monster database
* [[User:Crush/Particle engine|Particle engine]]
====TMWServ====
* Provisoric monster AI
* Attacking
* Attribute handling

==Current projects==
I am currently most involved in server programming.

== Subpages==
*[[User:Crush/Crafting]] (notes)
*[[User:Crush/Scripting]] (notes)
*[[User:Crush/Weather]] (draft)
*[[User:Crush/Special_Attacks]] (draft)
*[[User:Crush/Economy]] (notes)
*[[User:Crush/Food]] (draft)
*[[User:Crush/Alcohol]] (draft)
*[[User:Crush/Particle Engine Tutorial]] (draft)
*[[User:Crush/Move_Code_Rewrite]] (notes)
*[[User:Crush/Customized_Equipment_Technical]] (concept)
*[[User:Crush/Kaizai]] (draft)

User:Kage/Combat Skills

2009-05-29T10:49:21Z

Crush2:

{{Status_red}}
{{Opinions
|

{{Pro|Kage}}

|
{{Contra|Crush}}
}}

Currently for weapon skills on TMWServ, we are using weapons (I.E. Knives, Sword, Staff, Axe, Mace, Etc). The issue with this system is that it limits the types of weapons we have. Say if we wanted to have [http://en.wikipedia.org/wiki/Nunchaku Nunchakus] there is no way for us to include them without creating a entirely new weapon skill.

I purpose a system based on not weapons, but weapon classes.

Also this article addresses the issue with defensive skills. Our current system only uses weapons and does not take into account any type of defensives abilities.

Note: things on this page could change to account of balancing.

== Concept ==
Having weapons skills based on what, and how the weapon (or shield) works.

Some weapons can fall into different classes. I.E. Nunchakus would be precision and blunt. Meaning a Nunchaku could use special attacks from both classes.

Classes also use very different stats. For example precision weapons do not require a lot of strength to use. While slice weapons do not require a lot of dexterity. This can be done by use formulas to increase the amount of damage based on stats, similar to how it already works.

== Classes ==

=== Slice ===

Weapons that cut your target. Basically cutting attacks fall into this. Almost all swords would fall into this class. Highly effective, but easy to absorb or counter.

{|border="1"
!Stat
!Effect
|-
|Str
|Medium
|-
|Agi
|Medium
|-
|Vit
|None
|-
|Dex
|Low
|-
|Int
|None
|-
|Wil
|Low
|}

=== Puncture ===

Weapons designed penetrate deep into your target. Things like spears would belong to this category.

{|border="1"
!Stat
!Effect
|-
|Str
|Low
|-
|Agi
|High
|-
|Vit
|None
|-
|Dex
|Low
|-
|Int
|None
|-
|Wil
|Low
|}

=== Blunt ===

Blunt weapons neither cut, nor puncture the target. But rather "Smashes" it. A Mace would fall into this.

{|border="1"
!Stat
!Effect
|-
|Str
|High
|-
|Agi
|Low
|-
|Vit
|None
|-
|Dex
|Low
|-
|Int
|None
|-
|Wil
|Low
|}

=== Precision ===

Precision weapons are more like "ninja weapons". Things like knives, daggers, darts, nunchakus, etc. Weapons are not a matter of how hard you hit, but where.

{|border="1"
!Stat
!Effect
|-
|Str
|Low
|-
|Agi
|High
|-
|Vit
|None
|-
|Dex
|High
|-
|Int
|Medium
|-
|Wil
|Low
|}

=== Polearm ===

Polearms are in fact a class of weapons. Pretty much anything on a stick, or long, can be consider a polearm. Including staffs, helberds, spears, etc. Polearms take strong hands to handle. But are good for medium range attacks (longer then a sword, shorter then a bow).

{|border="1"
!Stat
!Effect
|-
|Str
|Medium
|-
|Agi
|Medium
|-
|Vit
|None
|-
|Dex
|High
|-
|Int
|None
|-
|Wil
|Low
|}

=== Ranged ===

Ranged are anything that is thrown or shot at a target. Mainly bows, but can include to crossbars, throwing knifes, etc.

{|border="1"
!Stat
!Effect
|-
|Str
|Medium
|-
|Agi
|Medium
|-
|Vit
|None
|-
|Dex
|High
|-
|Int
|None
|-
|Wil
|Low
|}

=== Absorb ===

Absorb are mainly your shields. Absorb can also include completely blocked attacks (prehaps though a special)

{|border="1"
!Stat
!Effect
|-
|Str
|High
|-
|Agi
|Medium
|-
|Vit
|High
|-
|Dex
|Low
|-
|Int
|None
|-
|Wil
|Low
|}

=== Counter ===

Counters are best described as a defensive/offensive skill. Can be things like parrying, also even turning your opponents damage back towards them.

{|border="1"
!Stat
!Effect
|-
|Str
|Low
|-
|Agi
|High
|-
|Vit
|Medium
|-
|Dex
|High
|-
|Int
|Low
|-
|Wil
|Low
|}

== Weapon Examples ==

Its important to note that many weapons can belong to many (more then 2) classes. While we should have the option of adding them to more then one, I warn against doing so. Remember we should focus more on fun game play then realism.

These examples are all from my mind, and don't have to reflect the final implementation.

{|border="1"
!Weapon
!Class 1
!Class 2
!Note
|-
|2H Swords
|Slice
|Blunt
|-
|Long Swords
|Slice
|-
|Swords
|Slice
|Counter
|-
|Short Swords
|Slice
|Puncture
|-
|Axes
|Slice
|Blunt
|-
|Maces
|Blunt
|-
|Staffs
|Polearm
|Blunt
|-
|Nunchukes
|Blunt
|Precision
|-
|Spears
|Polearm
|Puncture
|-
|Halberds
|Polearm
|Slice
|-
|Dagger
|Precision
|-
|Bows
|Ranged
|-
|Arrows
|Puncture
|
|Might be a good idea to keep arrows and bow apart, since blunt end arrows do exist
|-
|Throwing Knives
|Ranged
|Precision
|-
|Shields
|Absorb
|}
As you can see, this system can account for about any weapon you can think of. :-)

== Comments ==
Also see the discussion page.

User talk:Kage/Combat Skills

2009-05-28T15:26:08Z

Crush2: small clarification

==Damage calculation==
''Classes also use very different stats. For example precision weapons do not require a lot of strength to use. While puncture weapons do not require a lot of agility. This can be done by use formulas to increase the amount of damage based on stats, similar to how it already works.''

This will be a balancing nightmare. When we designed the [[Attributes|attribute system]] we explicitely decided to avoid having this to keep it simple. As an alternative approach I would suggest to use minimum attributes to be able to equip weapons (or use them without a severe penalty).
--[[User:Crush2|Crush]] 12:55, 28 May 2009 (UTC)

User talk:Kage/Combat Skills

2009-05-28T12:55:05Z

Crush2: New page: ==Damage calculation== ''Classes also use very different stats. For example precision weapons do not require a lot of strength to use. While puncture weapons do not require a lot of agilit...

==Damage calculation==
''Classes also use very different stats. For example precision weapons do not require a lot of strength to use. While puncture weapons do not require a lot of agility. This can be done by use formulas to increase the amount of damage based on stats, similar to how it already works.''

This will be a balancing nightmare. When we designed the [[Attributes|attribute system]] we explicitely decided to avoid having this to keep it simple. As an alternative approach I would suggest to use attributes as prerequisites to be able to use weapons.
--[[User:Crush2|Crush]] 12:55, 28 May 2009 (UTC)

Archive:Afterlife

2009-05-27T21:06:05Z

Crush2: ...christians...

{{status_red}}
==Dying in the mana world==
When a characters hit point reach zero or another situation causes the demise of a player character the character lies on the ground lifeless and unable to act. The player can either wait for another character to cast a revive spell on his character or just give up and accept the death of the character.

==The realm of death==
When a character dies it is teleported to the realm of death. The realm of death is a dark, surreal and eerie location where the laws of physics don't apply. Dominant colors: dark blue and purple. Design ideas: a) cave, b) glass floors floating over fractal background, c) 19th century look like the "end of time" in chrono trigger.

People in the realm of death have no access to their inventory, can not attack, use magic, craft or use any other active abilities. The characters actions are limited to moving around and communicating with NPCs and other characters. There is no way to die in the realm of death. The character is already dead, after all. Luckily the realm of death is not the final resting place for a poor adventurers soul. A cunning adventurer can find his way out of the death realm and back into the world of the living.

==The Grim Reaper==
As soon as the character awakes in the death realm he/she is greeted by the grim reaper. The grim reaper NPC counts how often the character died and responds accordingly. The first time the character dies he will just explain the situation. The next few times the reaper will give the character some useful tips for staying alive.

When the death count increases (and it will increase) the purpose of Reaper's greeting shifts from information to cheering up the player after its defeat using sarcastic remarks, dark humor and occasional 4th wall breaking. Example phrases:
*Died again? That was quick.
*Oh, you again? Did you miss me that much?
*You really seem to enjoy dying.
*Did you bring me a present?
*Wow, of all your 37 deaths this one was by far the most hillarious.
*You died 50 times in a row. This qualifies you for our frequent dier program.
*dingdingding! You died for the 100th time! PARTY!
*Why don't you just activate the god mode cheat? You don't know it? Did you try up, up, down, down, left, right, left, right, B, A?
*The god mode cheat didn't work? Maybe you entered it at the wrong moment?
*Oh dear, you used up all of your extra lifes. Now you have to stay here forever. Do you want to delete this character and create a new one? Just kidding, you know the way.
*Congratualtions! You died 1000 times!

==Escape==
To escape the world of death the character has to find its way through a maze. The maze is randomly generated for each character and each visit in the death realm, so memorizing it or consulting guides does not help. This is implemented by using a map containing of multiple rooms connected by smart warp scripts. The maze has multiple exits which represent the location where the character will reenter the world of the living. The most desirable location is the one which is furthest away from the players start location in the maze. Exits ordered by increasing desirability:
*respawn at first town
*respawn in last visited town
*respawn on the entrance of the map where the player died
*respawn at the exact location of death

The purpose of the maze is to punish the player by stopping the progress of its character for a short time but to keep the player occupied and entertained during this forced time-out period.

==Technical implementation of maze==
===maze generation===

The script engine randomly-generates a maze of 7x7 elements (or maybe larger - we have to see how the players react on it). Possible element types are:
[[Image:Labyrinth-elements.png|right]]
*straight (x2)
*curve (x4)
*t-crossing (x4)
*crossing (x1)
*dead end (x4)
[[Image:Examplelabyrinth.png|right]]
The algorithmn has to make sure that every element of the maze is reachable and it has to generate the maze based on a random seed. The algorithmn must produce the same maze when receiving the same seed. Potential algorithmns are explained in this wikipedia article: http://en.wikipedia.org/wiki/Maze_generation_algorithm

The start location is the center (a crossing). The exits are the corners of the maze (dead ends facing clockwise). The algorithmn assigns the desirability rating of each exit based on the length of the optimal route to the start.

===Representation of the maze in the game===
The layout of the map the player walks on while exploring the maze does not represent the real layout of the maze. Instead of that there are 20 single, isolated rooms - one for the possible 15 element types + 5 additional rooms for the start and the 4 exits. Each one is used to represent every instance of that element in the labyrinth. The real layout of the maze is "virtual". It is only known to the script.

When the player is, for example, in the south/west curve room of the map he could be in any south/west curve of the virtual maze. Only the script knows the real location inside the virtual maze. When the player leaves the room through the west exit the script checks the type of element in the virtual maze one element to the west and teleports the character to the eastern exit of the appropriate room.

===Effect on gameplay experience===
All characters who are currently trying to get back into the world of the living are technically on the same map. This means that it is possible to meet other characters while traveling through the maze. But the warp connections work differently for everyone. So when both characters leave the room they met in through the same exit they will most likely lose each other.

===Saving the maze===
To make sure that the character does not get trapped when the server is rebooted while the character is in the maze the state of the maze has to be saved as quest variables in the database. Only two variables are necessary to do so: Location inside the maze and the seed used by the random number generator for generating the maze.

Servers

2009-05-27T14:11:54Z

Crush2: /* eAthena servers for 0.0.x clients */ grammar

{{Category_playerinfo}}
{{Status_green}}
 

When you set up your own TMW server and want it to be open for public playing feel free to add it here. To create your own server read [[Setting up a server]]. All servers/projects on this page work with the official client. Servers/Projects listed on [[forks]] are incompatible with the official TMW client, though they are based on it.

== eAthena servers for 0.0.x clients ==

These servers run on eAthena. You can connect to them with a client compiled from the <code>0.0</code> branch or with any 0.0.x release.

'''''Security Warning:'' Do not use the same username and password on two different servers. The server admins can read all of them in clear text and nothing stops them from trying them on other servers. It happened a lot in the past that users of the official server got â€œhackedâ€ because they ignored this important precaution.'''

=== Official server ===

The official public server of The Mana World project.

* Hostname: server.themanaworld.org
* Port: 6901 TCP
* Administration: [[User:ElvenProgrammer|Eugenio Favalli]], [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Official test server ===

The official test and experimentation server regularly used for balancing new game play changes.

* Hostname: (same as official)
* Port: (same as official)
* Administration: [[User:BjÃ¸rn|BjÃ¸rn]], [[User:Jaxad0127|jaxad0127]]

=== Neo644's Sandbox Server ===

It's back, new and improved.. 15 people at one time, many commands enabled by default.

* Hostname: neo644lap.dyndns.org
* Port: 6901 TCP (default)
* Administration: [[User:neo644|Neo644]], dark magician

=== Taiwan local Server ===

An unofficial server for Chinese Downtimes possible.

* Hostname: tmw.servegame.org
* IP:219.85.59.36
* Port: 6901 TCP
* Administration: --[[User:Netwareboss|Netwareboss]] 00:57, 2 May 2009 (UTC)

===BBB's Server===

An unofficial server hosted by Baseballboy.

* Hostname: BBBs.game-host.org
* Port: 6901 TCP
* Administration: [[User:baseballboy|Baseballboy]]



== TMWServ servers for 0.1 client ==
You can connect to these servers with a client compiled from <code>trunk</code>. Note that TMWServ is still in development and doesn't offer real gameplay yet. As a player you will have much more fun with the 0.0.x client on an eAthena server.

=== Official test server ===

The semi-official test server for the new server <code>tmwserv</code>. The server runs in gdb so that we'll even have a chance of finding those rare crashes, but hence may not always be available.

* Hostname: testing.themanaworld.org
* Port: 9601 UDP
* Administration: [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Invertika server ===

A German fork of TMW based on tmwserv with a completely new game world. The server is in alpha status. Downtimes are possible.

* Hostname: server.invertika.org
* Port: 9601 UDP
* Website: invertika.org
* Administration: [[User:Seeseekey|seeseekey]]

Servers

2009-05-27T12:27:03Z

Crush2: clarification of security warning

{{Category_playerinfo}}
{{Status_green}}
 

When you set up your own TMW server and want it to be open for public playing feel free to add it here. To create your own server read [[Setting up a server]]. All servers/projects on this page work with the official client. Servers/Projects listed on [[forks]] are incompatible with the official TMW client, though they are based on it.

== eAthena servers for 0.0.x clients ==

These servers run on eAthena. You can connect to them with a client compiled from the <code>0.0</code> branch or with any 0.0.x release.

'''''Security Warning:'' Do not use the same username and password on two different servers. The server admins can read all usernames and passwords in clear text and nothing stops them from trying them on other servers. There were a lot of cases in the past where users of the official server got â€œhackedâ€ because they ignored this important precaution.'''

=== Official server ===

The official public server of The Mana World project.

* Hostname: server.themanaworld.org
* Port: 6901 TCP
* Administration: [[User:ElvenProgrammer|Eugenio Favalli]], [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Official test server ===

The official test and experimentation server regularly used for balancing new game play changes.

* Hostname: (same as official)
* Port: (same as official)
* Administration: [[User:BjÃ¸rn|BjÃ¸rn]], [[User:Jaxad0127|jaxad0127]]

=== Neo644's Sandbox Server ===

It's back, new and improved.. 15 people at one time, many commands enabled by default.

* Hostname: neo644lap.dyndns.org
* Port: 6901 TCP (default)
* Administration: [[User:neo644|Neo644]], dark magician

=== Taiwan local Server ===

An unofficial server for Chinese Downtimes possible.

* Hostname: tmw.servegame.org
* IP:219.85.59.36
* Port: 6901 TCP
* Administration: --[[User:Netwareboss|Netwareboss]] 00:57, 2 May 2009 (UTC)

===BBB's Server===

An unofficial server hosted by Baseballboy.

* Hostname: BBBs.game-host.org
* Port: 6901 TCP
* Administration: [[User:baseballboy|Baseballboy]]



== TMWServ servers for 0.1 client ==
You can connect to these servers with a client compiled from <code>trunk</code>. Note that TMWServ is still in development and doesn't offer real gameplay yet. As a player you will have much more fun with the 0.0.x client on an eAthena server.

=== Official test server ===

The semi-official test server for the new server <code>tmwserv</code>. The server runs in gdb so that we'll even have a chance of finding those rare crashes, but hence may not always be available.

* Hostname: testing.themanaworld.org
* Port: 9601 UDP
* Administration: [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Invertika server ===

A German fork of TMW based on tmwserv with a completely new game world. The server is in alpha status. Downtimes are possible.

* Hostname: server.invertika.org
* Port: 9601 UDP
* Website: invertika.org
* Administration: [[User:Seeseekey|seeseekey]]

Archive:Housing

2009-05-26T15:52:37Z

Crush2: status template, format, small corrections

{{Status_red}}
==Instancing Solutions==
Feel free to add your own.

===Inverse Skyscraper===
To have a credible instancing just use the skyscraper idea(*) the other way round:
Have houses placed in a mine UNDER the ground.
The first level is a cave map. There is a gnome that sells houses at his desk, and another gnome that offers you to take you in his cart (he is a clerk gnome).
Imagine you live in house number 384:
# You speak to the gnome, you tell him you live in floor 38
# You enter his cart, and you see an animation in the animation you go through a series of passages and labyrinths underground.
# you arrive at a cave which YOU ASSUME must be floor 38, in this cave the gnome is on an edge of the map so you can go back (or to another floor), there are 10 houses on the cave, you enter number 4 (remember your house is 384), you have a key to enter.

You only need a key when the door is locked. If you leave it open your friends (or anyone) may pass to see you whenever they want, of course you can borrow or copy the key.

In this system floor 38, would actually exist, and floor 38 always has the same 10 houses, so you can get to know your neighbors or cross them by, the only thing that is fictional is the path to floor 38, which is the same path for all the 100 or 1000 floors.

It would be better if players DIDN'T chose their house number and got consecutive ones
in order to have less floor maps.

At first you would only have floor one, then as players started requesting houses, gnomes would start caving more and adding levels downer and downer.

---------------------
NOTES:
(*)''Anarchy Online - a science fiction themed MMO - solved the problem with instances and "Hilbert Hotel Skyscrapers". There are high-rise apartment buildings in the game with elevators. When you step into the elevator it brings you to the floor with your flat. Every floor is one instance. But because you never know on which floor you are you never know how many virtual floors the building really has. But this solution to explain instancing is not suitable as skyscrapers are quite misplaced in fantasy themed MMORPGs. (Posted by Crush on the Forums)''

===Property Issues===
The property is based on a special paper not on the key, the idea is that this paper is not sell able to a NPC but you can sell your house to another person, the owner of the paper has the right to ask for more keys of the house to the gnome, and has the possibility to take keys away from other players in game that may have keys of the same house.

===Technical Data===

===Effects on Gameplay and Economy===

===Discussion===

The Mana World:Screenshots

2009-05-24T13:32:59Z

Crush2: thanks, but we already got a screenshot of the storage window. Also, this client does not seem to be the 0.0.29 release version.

== Version 0.0.29 ==
{{Screenshot|Image:Screenshot_partysystem.png|[[Party system]]}}
{{Screenshot|Image:TMW-0.0.29-Storage.png|Putting Things in Storage at the twins' bank}}
{{Screenshot|Image:TMW_Screenshot_2.png|Colours}}
{{Screenshot|Image:Mana_World_0.0.29.PNG|Hurnscald Woodlands}}

 

== Developer Screenshots ==


Work in progress screenshots from developer versions that have not been released to the public or from unofficial forks.
{{Screenshot|Image:TMW Screenshot 24.png|[http://qoal.110mb.com QOALs modified client 0.0.29.Q]}}
{{Screenshot|Image:TMW Screenshot 6.png|The HMC guys are testing TMWServ}}
{{Screenshot|Image:Recolor_Screenshot_1.png|experimenting with changing the colors of images at runtime}}
{{Screenshot|Image:Particleengine_Screenshot_2.png|Crushs particle engine.}}
{{Screenshot|Image:Particleengine_Screenshot_1.png|Crushs particle engine.}}
{{Screenshot|Image:TMW Screenshot svn210606-fog-smooth-scrolling.png|Fog and smooth scrolling from Crushs GFX branch.}}
{{Screenshot|Image:TMW Screenshot svn210606-boobs.png|SVN 21.06.06 The first time a female character appeared on screen.}}
{{Screenshot|Image:Assparade.png|Assparade!!! - first version of the new playerset that has not been released.}}
 

== Version 0.0.28 ==
{{Screenshot|Image:TMW_Screenshot_15.png|TTF font rendering and speech bubbles}}
 

== Version 0.0.26 ==
{{Screenshot|Image:TMW_Screenshot_8.png|Showing off all the new content since 0.0.23}}
 

== Version 0.0.23 ==
{{Screenshot|Image:Halloween_2007.png|Halloween in the woodland village}}
 
{{Screenshot|Image:TMW Screenshot 0.0.23-particles.png|The new particle engine}}
{{Screenshot|Image:Screenshot_HurnscaldVillage.png|New Village}}
{{Screenshot|Image:Screenshot_HurnscaldInn.png|New Village}}
 

== Version 0.0.22 - Christmas version ==
{{Screenshot|Image:TMW Screenshot 0.0.22-christmastree.png|Christmas tree}}
{{Screenshot|Image:TMW Screenshot 0.0.22-helpersanta.png|Helper Santa (NPC)}}
{{Screenshot|Image:TMW Screenshot 0.0.22-buyselldialog.png|new buy/sell dialog...}}

 

== Version 0.0.21.1 - Halloween version ==
{{Screenshot|Image:Login wallpaper halloween.png|Lovely Halloween login wallpaper by [[User:Irukard|Irukard]] }}
{{Screenshot|Image:TMW Screenshot halloween1.png|Skulls desert}}
{{Screenshot|Image:TMW Screenshot halloween2.png|Ghosts...}}

 

== Version 0.0.20 ==
{{Screenshot|Image:Tmw_0.0.20.png|Family photo on 0.0.20!}}
{{Screenshot|Image:Icecave-screen.png|The new icecave}}
{{Screenshot|Image:Female character1.png|The new official female character}}
{{Screenshot|Image:Clothes.png|Now you can see the clothes!}}
 

== Version 0.0.19 ==

{{Screenshot|Image:TMW screenshot 0.0.19-batcave.png|The new batcave}}
{{Screenshot|Image:TMW screenshot 0.0.19-firemonsters.png|Danger! Hot!}}
 

== Old Playerset ==

{{Screenshot|Image:TMW_screenshot_0.0.18-cvs_xmas.png|The new Xmas Map}}
{{Screenshot|Image:TMW_screenshot_0.0.18-cvs_woodland.png|Woodland}}
{{Screenshot|Image:TMW_screenshot_0.0.18-cvs_casino.png|The casino}}
{{Screenshot|Image:TMW_screenshot_0.0.18-cvs_inn.png|The inn}}
{{Screenshot|Image:TMW screenshot 0.0.15-cvs.png|A crowd in front of the gates to Tulimshar palace}}
{{Screenshot|Image:TMW screenshot 0.0.15 - snake invasion 1.png|A snake invasion was announced}}
{{Screenshot|Image:TMW screenshot 0.0.15 - snake invasion 2.png|First snakes started coming}}
{{Screenshot|Image:TMW screenshot 0.0.15 - snake invasion.png|Snake invasion went out of control}}
 

== Ancient ==

{{Screenshot|Image:TMW ancient matt bug2.jpg|Matt shows us a bug in the map}}
{{Screenshot|Image:TMW ancient login.png|The login screen just after porting it to Guichan}}
{{Screenshot|Image:Tmw-0.0.10CVS.png|Pathfinding was reimplemented in 0.0.10}}
{{Screenshot|Image:TMW screenshot 0.0.10.png|Purple all on his own on 0.0.10 release}}
{{Screenshot|Image:TMW screenshot 0.0.12-family-shot.png|A family shot taken in front of Tulimshar palace gate}}
{{Screenshot|Image:TMW screenshot 0.0.12-cave.png|The cave was new with 0.0.12}}
 

__NOTOC__

Servers

2009-05-23T23:17:25Z

Crush2: added warning about using the same login and password on two different servers.

{{Category_playerinfo}}
{{Status_green}}
 

When you set up your own TMW server and want it to be open for public playing feel free to add it here. To create your own server read [[Setting up a server]]. All servers/projects on this page work with the official client. Servers/Projects listed on [[forks]] are incompatible with the official TMW client, though they are based on it.

== eAthena servers for 0.0.x clients ==

These servers run on eAthena. You can connect to them with a client compiled from the <code>0.0</code> branch or with any 0.0.x release.

'''''Security Warning:'' Do not use the same username and password on two different servers. The server admin can read all passwords in clear text. There were a lot of cases in the past were users of the official server got "hacked" because they ignored this important precaution.'''

=== Official server ===

The official public server of The Mana World project.

* Hostname: server.themanaworld.org
* Port: 6901 TCP
* Administration: [[User:ElvenProgrammer|Eugenio Favalli]], [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Official test server ===

The official test and experimentation server regularly used for balancing new game play changes.

* Hostname: (same as official)
* Port: (same as official)
* Administration: [[User:BjÃ¸rn|BjÃ¸rn]], [[User:Jaxad0127|jaxad0127]]

=== Neo644's Sandbox Server ===

An unofficial server in which everyone can try anything out. Limit 10 users online at a time. Downtimes possible.
UPDATE: The server has been down for a while now. Luckily, I am setting up a new server.
* Hostname: 74.177.110.163 (This is a dynamic IP so it might change)
* Port: 6901 TCP (default)
* Administration: [[User:neo644|Neo644]]
=== Taiwan local Server ===

An unofficial server for Chinese Downtimes possible.

* Hostname: tmw.servegame.org
* IP:219.85.59.36
* Port: 6901 TCP
* Administration: --[[User:Netwareboss|Netwareboss]] 00:57, 2 May 2009 (UTC)

===BBB's Server===

An unofficial server hosted by Baseballboy.

* Hostname: 75.91.23.96
* Port: 6901 TCP
* Administration: [[User:baseballboy|Baseballboy]]



== TMWServ servers for 0.1 client ==
You can connect to these servers with a client compiled from <code>trunk</code>. Note that TMWServ is still in development and doesn't offer real gameplay yet. As a player you will have much more fun with the 0.0.x client on an eAthena server.

=== Official test server ===

The semi-official test server for the new server <code>tmwserv</code>. The server runs in gdb so that we'll even have a chance of finding those rare crashes, but hence may not always be available.

* Hostname: testing.themanaworld.org
* Port: 9601 UDP
* Administration: [[User:BjÃ¸rn|BjÃ¸rn Lindeijer]]

=== Invertika server ===

A German fork of TMW based on tmwserv with a completely new game world. The server is in alpha status. Downtimes are possible.

* Hostname: server.invertika.org
* Port: 9601 UDP
* Website: invertika.org
* Administration: [[User:Seeseekey|seeseekey]]

File:Area argaes raster.jpg

2009-05-22T18:21:59Z

Crush2: uploaded a new version of "Image:Area argaes raster.jpg"

Argaes map with map raster. Black sectors are sectors which do not require a map. White sectors are already mapped.

Main Page

2009-05-21T13:41:45Z

Crush2: moved party system to player information

__NOTOC__ __NOEDITSECTION__
{| cellspacing="3" cellpadding="3" width="100%"
| colspan="2" style="border: 1px solid lightgrey;" |
{| cellspacing="0" cellpadding="0"
| style="vertical-align: center; text-align: center; padding: 0px 20px 0px 20px; font-style: italic;" | Welcome to The Mana World wiki! This wiki is meant to provide information to our players, to provide an easy way to contribute to the development of certain parts of the game and to improve collaboration between people on the development team. We hope you will find what you are looking for. To be able to edit you have to login, but signing up is free and requires no activation.
| [[Image:Tmw logo.png|100px]]
|}
|-
| style="border: 1px solid #e0c8b8; color: #000; background-color: #faeee6" valign="top" |
==For players==
===General information===
*[[Project description]]
*[[Screenshots]]
*[[Developers|List of developers]]
*[[Game_Masters|List of game masters]]
*[[System requirements]]
*[[Servers|List of servers]]
*[[Guilds|List of player groups]]
*[[Forks|List of other games based on TMW]]

===Newbie information===
*[[Getting started]]
*[[Party system]]
*[[Walkthrough]]
*[[FAQ]]

===In-depth information===
*[[Monster reference|List of monsters]]
*[[Item reference|List of items]]
*[[NPC|List of NPCs]]
*[[Stats|Overview of player statistics]]
*[[Config settings|Game configuration]]
*[[Provisorical Alchemy System|Alchemy]]
*[[In-game_world_map|World map]]
*[[Walkthrough/Quests|Quests]]

===Feedback===
*[[Suggestions|Suggest features or modifications]]
*[[Bugs|Report bugs]]

===Customization===
*[[Customization|gui graphic]]

| rowspan="2" style="width: 50%; border: 1px solid #c9c9ff; color: #000; background-color: #f3f3ff" valign="top" |
==For developers==
===General information===
:''Development'': [[Joining the project]] - [[Roadmap]] - [[Git Repository]]

===Concepts and story===
:''Story'': [[Backstory]]
:''World'': [[Geography]] - [[Creatures]] - [[Organizations]] - [[Elements]]

===Game content===
:[[Content|''List of content being worked on'']]
:''General'': [[Guidelines]] - [[Concept art]] - [[Assignments]] - [[:Special:Newimages|Recently uploaded images]]
:''Characters'': [[Playerset development|Playersets]] - [[Equipment development|Equipment sheets]] - [[Equipment in development]] - [[Hairset development|Hairsets]] - [[NPC development]]
:''Creatures'': [[Creature proposal]] - [[Monsterset development|Monster sheets]]
:''Graphics'': [[Tileset development|Tilesets]] - [[Animations]] - [[Particle engine|Particle effects]] - [[Image dyeing]]
:''Mapping'': [[Map development]] - [[Mapping Tutorial]]
:''Sound and music'': [[SFX|Sound effects]] - [[Music]]
:''Miscellaneaous'': [[Translations]] - [[Friendly Bots]]

===Gameplay===
:''Combat'': [[Game systems]] - [[Weapons]]
:''User input'': [[GUI development]] - [[Keyboard usage]] - [[Menu interface system]]

===Programming===
:[[Hacking|Source code guidelines]]
:[[eAthena Scripting Standards]]
:[[Dependencies]]
:[[Ports]]
:[http://mantis.themanaworld.org Bug tracker]
:[http://bjorn.platinum.linux.pl/tmw-docs/ Source code documentation (Doxygen)]
:''RFCs'': [[Rendering]] - [[Action layers]] - [[Improvement of the collision layer system|Collision system]] - [[Being movement system|Movement system]] - [[Logging]]
:''Reference'': [[Server development]] - [[Realtime action combat protocol|Realtime combat]] - [[Monster Database]]
:''Releases'': [[Making a new release]] - [[How to release an update]]
|}

Archive:TMWServ party system

2009-05-21T13:39:28Z

Crush2: moved from "party system" to separate it from the eAthena party system.

{{Category_gameconcept}}
{{Category_programming}}
{{Status_red}}

==Party system==
A character can create a party at any time by inviting another player to join. The character that created the party becomes the party leader. If the party leader leaves the party, the first character who joined the party afterwards becomes party leader. If this character already left, the next who joined becomes the leader, and so on.

Party members can fight monsters together and share the combat skill experience reward of the monsters they fight, because the killsteal protection time (the time after an attack in which attacks of other characters don't qualify them for a share of the experience of the monster) is ignored between party members. For further details regarding experience distribution see [[skill system]].

If a monster that was killed by a party drops loot, any member of the party may pick up the loot immediately.

A party is temporary and dies when the last party member leaves. A player can choose to leave their party at any time, or the party leader can remove them from the party. Players leave their party automatically when disconnected from the server.

When the party is created a chat channel for the party is automatically created and all party members automatically join it. Non party members cannot join, and party members cannot leave. In the game this channel is simply called the "Party" channel, and it is identified by a special color (say, purple).

== Implementation ==

=== Introduction ===

Since parties members can be on different maps at the same time, either the account or the chat server needs to keep track of parties. Since parties are mainly temporary social gatherings, interested in each other's status and being able to communicate, the chat server seems the most logical place for the authority on parties.

=== Responsibility of each peer ===

==== Client ====

Needs to be able to:

* Display whether other players on the screen are part of your party
* Display the list of party members and their health status
* Display potentially their current map and their position on the minimap (even when they are not visible on the screen)
* Display an invite to a party from another player
* Allow party leaders to invite others to a party
* Allow party leaders to remove others from a party

Information needed:

* Either party ID of each player on screen (would allow identification of other parties) or boolean saying whether they are in your party
* List of party members (with their name, map, position and health)
* Party channel ID of local player (may be derivable from or same as party ID)

==== Game server ====

* The party affects combat mechanics
* The party affects potentially whether map location is sent to another player

Information needed:

* The party ID for each player on the server

==== Chat server ====

* Creates/removes parties and keeps track of their leader
* Has authority on players joining/leaving parties
* The party is able to chat in private
* Party members are potentially aware of the map of the other members
* Party members know each other's health
* Party members get notified when others leave/join the party

Information needed:

* The list of members for each party
* The list of invited members for each party
* The party ID for all players
* Potentially the name of the map each player occupies
* Health information for all players

=== Messaging (semi-chronological) ===

==== A player invites another player ====

<pre>
client A -- PARTY_INVITE -----> chat server (id)
"checks location and authority"
chat server ----- INVITE ----------> client B (name)
chat server <---- INVITE_RESPONSE -- client B
"either remove invitation or add member"
client A <- INVITE_RESPONSE --- chat server
clients <-- PARTY_JOIN -------- chat server (id, name, map, health)
chat server -- PLAYER_PARTY_ID --> game server (id, party_id)
</pre>

==== A player removes another player (or himself) ====

<pre>
client A -- PARTY_REMOVE -----> chat server (id)
"checks authority"
client A <-- REMOVE_RESPONSE -- chat server
clients <-- PARTY_LEAVE ------- chat server (id)
chat server -- PLAYER_PARTY_ID --> game server (id, party_id)
</pre>

==== The game server sends new player information ====

<pre>
chat server <-- PLAYER_INFO ------ game server (id, map, health)
clients <-- PARTY_MEMBER ------ chat server (id, map, health)
</pre>

==== Players chat ====

Chat messages are the same as on regular chat channels.

The Mana World:Screenshots

2009-05-17T17:31:12Z

Crush2: added picture by doorsman, some tidying up.

== Version 0.0.29 ==
{{Screenshot|Image:TMW_Screenshot_2.png|Colours}}
{{Screenshot|Image:Mana_World_0.0.29.PNG|Hurnscald Woodlands}}
{{Screenshot|Image:Screenshot_partysystem.png|Party System}}

 

== Developer Screenshots ==


Work in progress screenshots from developer versions that have not been released to the public or from unofficial forks.
{{Screenshot|Image:TMW Screenshot 24.png|[http://qoal.110mb.com QOALs modified client 0.0.29.Q]}}
{{Screenshot|Image:TMW Screenshot 6.png|The HMC guys are testing TMWServ}}
{{Screenshot|Image:Recolor_Screenshot_1.png|experimenting with changing the colors of images at runtime}}
{{Screenshot|Image:Particleengine_Screenshot_2.png|Crushs particle engine.}}
{{Screenshot|Image:Particleengine_Screenshot_1.png|Crushs particle engine.}}
{{Screenshot|Image:TMW Screenshot svn210606-fog-smooth-scrolling.png|Fog and smooth scrolling from Crushs GFX branch.}}
{{Screenshot|Image:TMW Screenshot svn210606-boobs.png|SVN 21.06.06 The first time a female character appeared on screen.}}
{{Screenshot|Image:Assparade.png|Assparade!!! - first version of the new playerset that has not been released.}}
 

== Version 0.0.28 ==
{{Screenshot|Image:TMW_Screenshot_15.png|TTF font rendering and speech bubbles}}
 

== Version 0.0.26 ==
{{Screenshot|Image:TMW_Screenshot_8.png|Showing off all the new content since 0.0.23}}
 

== Version 0.0.23 ==
{{Screenshot|Image:Halloween_2007.png|Halloween in the woodland village}}
 
{{Screenshot|Image:TMW Screenshot 0.0.23-particles.png|The new particle engine}}
{{Screenshot|Image:Screenshot_HurnscaldVillage.png|New Village}}
{{Screenshot|Image:Screenshot_HurnscaldInn.png|New Village}}
 

== Version 0.0.22 - Christmas version ==
{{Screenshot|Image:TMW Screenshot 0.0.22-christmastree.png|Christmas tree}}
{{Screenshot|Image:TMW Screenshot 0.0.22-helpersanta.png|Helper Santa (NPC)}}
{{Screenshot|Image:TMW Screenshot 0.0.22-buyselldialog.png|new buy/sell dialog...}}

 

== Version 0.0.21.1 - Halloween version ==
{{Screenshot|Image:Login wallpaper halloween.png|Lovely Halloween login wallpaper by [[User:Irukard|Irukard]] }}
{{Screenshot|Image:TMW Screenshot halloween1.png|Skulls desert}}
{{Screenshot|Image:TMW Screenshot halloween2.png|Ghosts...}}

 

== Version 0.0.20 ==
{{Screenshot|Image:Tmw_0.0.20.png|Family photo on 0.0.20!}}
{{Screenshot|Image:Icecave-screen.png|The new icecave}}
{{Screenshot|Image:Female character1.png|The new official female character}}
{{Screenshot|Image:Clothes.png|Now you can see the clothes!}}
 

== Version 0.0.19 ==

{{Screenshot|Image:TMW screenshot 0.0.19-batcave.png|The new batcave}}
{{Screenshot|Image:TMW screenshot 0.0.19-firemonsters.png|Danger! Hot!}}
 

== Old Playerset ==

{{Screenshot|Image:TMW_screenshot_0.0.18-cvs_xmas.png|The new Xmas Map}}
{{Screenshot|Image:TMW_screenshot_0.0.18-cvs_woodland.png|Woodland}}
{{Screenshot|Image:TMW_screenshot_0.0.18-cvs_casino.png|The casino}}
{{Screenshot|Image:TMW_screenshot_0.0.18-cvs_inn.png|The inn}}
{{Screenshot|Image:TMW screenshot 0.0.15-cvs.png|A crowd in front of the gates to Tulimshar palace}}
{{Screenshot|Image:TMW screenshot 0.0.15 - snake invasion 1.png|A snake invasion was announced}}
{{Screenshot|Image:TMW screenshot 0.0.15 - snake invasion 2.png|First snakes started coming}}
{{Screenshot|Image:TMW screenshot 0.0.15 - snake invasion.png|Snake invasion went out of control}}
 

== Ancient ==

{{Screenshot|Image:TMW ancient matt bug2.jpg|Matt shows us a bug in the map}}
{{Screenshot|Image:TMW ancient login.png|The login screen just after porting it to Guichan}}
{{Screenshot|Image:Tmw-0.0.10CVS.png|Pathfinding was reimplemented in 0.0.10}}
{{Screenshot|Image:TMW screenshot 0.0.10.png|Purple all on his own on 0.0.10 release}}
{{Screenshot|Image:TMW screenshot 0.0.12-family-shot.png|A family shot taken in front of Tulimshar palace gate}}
{{Screenshot|Image:TMW screenshot 0.0.12-cave.png|The cave was new with 0.0.12}}
 

__NOTOC__

Main Page

2009-05-15T18:08:28Z

Crush2: removed link to alliances (redundant)

__NOTOC__ __NOEDITSECTION__
{| cellspacing="3" cellpadding="3" width="100%"
| colspan="2" style="border: 1px solid lightgrey;" |
{| cellspacing="0" cellpadding="0"
| style="vertical-align: center; text-align: center; padding: 0px 20px 0px 20px; font-style: italic;" | Welcome to The Mana World wiki! This wiki is meant to provide information to our players, to provide an easy way to contribute to the development of certain parts of the game and to improve collaboration between people on the development team. We hope you will find what you are looking for. To be able to edit you have to login, but signing up is free and requires no activation.
| [[Image:Tmw logo.png|100px]]
|}
|-
| style="border: 1px solid #e0c8b8; color: #000; background-color: #faeee6" valign="top" |
==For players==
===General information===
*[[Project description]]
*[[Screenshots]]
*[[Developers|List of developers]]
*[[Game_Masters|List of game masters]]
*[[System requirements]]
*[[Servers|List of servers]]
*[[Guilds|List of player groups]]
*[[Forks|List of other games based on TMW]]

===Newbie information===
*[[Getting started]]
*[[Walkthrough]]
*[[FAQ]]

===In-depth information===
*[[Monster reference|List of monsters]]
*[[Item reference|List of items]]
*[[NPC|List of NPCs]]
*[[Stats|Overview of player statistics]]
*[[Config settings|Game configuration]]
*[[Provisorical Alchemy System|Alchemy]]
*[[In-game_world_map|World map]]
*[[Walkthrough/Quests|Quests]]

===Feedback===
*[[Suggestions|Suggest features or modifications]]
*[[Bugs|Report bugs]]

| rowspan="2" style="width: 50%; border: 1px solid #c9c9ff; color: #000; background-color: #f3f3ff" valign="top" |
==For developers==
===General information===
:''Development'': [[Joining the project]] - [[Roadmap]] - [[Git Repository]]

===Concepts and story===
:''Story'': [[Backstory]]
:''World'': [[Geography]] - [[Creatures]] - [[Organizations]] - [[Elements]]

===Game content===
:[[Content|''List of content being worked on'']]
:''General'': [[Guidelines]] - [[Concept art]] - [[Assignments]] - [[:Special:Newimages|Recently uploaded images]]
:''Characters'': [[Playerset development|Playersets]] - [[Equipment development|Equipment sheets]] - [[Equipment in development]] - [[Hairset development|Hairsets]] - [[NPC development]]
:''Creatures'': [[Creature proposal]] - [[Monsterset development|Monster sheets]]
:''Graphics'': [[Tileset development|Tilesets]] - [[Animations]] - [[Particle engine|Particle effects]] - [[Image dyeing]]
:''Mapping'': [[Map development]] - [[Mapping Tutorial]]
:''Sound and music'': [[SFX|Sound effects]] - [[Music]]
:''Miscellaneaous'': [[Translations]] - [[Friendly Bots]]

===Gameplay===
:''Combat'': [[Game systems]] - [[Weapons]]
:''User input'': [[GUI development]] - [[Keyboard usage]] - [[Menu interface system]]

===Programming===
:[[Hacking|Source code guidelines]]
:[[eAthena Scripting Standards]]
:[[Dependencies]]
:[[Ports]]
:[http://mantis.themanaworld.org Bug tracker]
:[http://bjorn.platinum.linux.pl/tmw-docs/ Source code documentation (Doxygen)]
:''RFCs'': [[Rendering]] - [[Action layers]] - [[Improvement of the collision layer system|Collision system]] - [[Being movement system|Movement system]] - [[Logging]] - [[Party system]]
:''Reference'': [[Server development]] - [[Realtime action combat protocol|Realtime combat]] - [[Monster Database]]
:''Releases'': [[Making a new release]] - [[How to release an update]]
|}

Player Groups

2009-05-15T18:01:29Z

Crush2:

{{Category_playerinfo}}
Please, try not to be chaotic when editing, try to keep the format, and don't create derived articles for your guilds. Here you have enough space to make your guilds.
==The Holy Mana Clan==

'''The Holy Mana clan mission statement.'''

'''Our purpose'''

The holy mana clan is created mainly to add another flavor to the game. The idea is to have a social network between players for the purpose of organizing in-game events as well as for helping newer players find their way. Membership is completely free. That means it doesn't matter whether you play one hour a week or 5 hours a day. Inactive players might be put on ghost status after a while, but they can immediately be put back once they are active again. Secondly that means you can quit the clan whenever you get tired of it, no strings attached. And finally it also means we do not ask for fees. Prizes for events will depend on donations of "richer" members. We used to keep a registry of the donated gold and items on-line, so people could check and see that this isn't just a scam to make money, but it became to time consuming as the clan grew bigger.

'''Our policy'''

Although the purpose of the clan is to make the game more fun, we are serious about our image. If members of the clan act obnoxious it will reflect poorly on all members. Therefore we have a strict policy; we will not accept known trouble makers and we will not hesitate to ban those who are destroying the concept. The idea is to unite as an open group and enjoy the game under the banner with integrity, not to create a closed group that acts superior to non-members. So be on your best behavior.

'''Our future'''

Since our options are quite limited on the current server we obviously only have a small influence on the game and on gameplay. Yet we are hoping that we can build this clan to a respectable size by the time new options become available. Until then we will probably keep an easygoing mood, and hold our best ideas for later.

'''For more informations such as:'''

*'''member list''' (more then 250 members; half is active, the other half drops in once in a while)
*'''news about events and meetings'''(join the fun)
*'''How to join, and clan-policy'''
*'''our Perk Point System''' (a system to reward active members with items)
*'''Contacting other members by forum or IRC''' (ask for advice or help, or just get to know each other)
*'''Screenshots and videos'''
*'''Walktrough''' (quests, stat-configuration, useful tips; more up to date than wiki)
*'''Usefull links''' (who's online, top stats, manabay, forums, player homesites, ...)
'''visit us at: [http://holymanaclan.webs.com/ http://holymanaclan.webs.com/]'''

'''Contacting the leaders'''

Every clan is supposed to have leaders and members, to prevent chaos. Although some of them have authority and some don't; the clan needs both of them to survive! Luckily the leaders of this clan are open to suggestions of their members. Is there anything you would like the clan to have, something about the clan you dislike? Do you have any questions? Do you want your home page or favorite page to be added to our "links" page? Do you have any suggestions for the web page or forum? Do you want to be notified of upcoming events? Do you think we could use your help with something you're good at? Do you have a nice screenshot you want to add? For all those things we made a clan e-mail address:

TheHolyManaClan@gmail.com

==Los Viscerales==

Los Viscerales are wizards, warriors and archers that seek to build a community that enjoys player organized activities and events. We support competitive game elements, the player driven market and seek to build alliances with others so that our small gaming community can thrive and continue to grow. If you are interested in organizing "player versus player" (pvp) or "raid" activities contact "Wombat" in game.

'''Webpage'''

Los Viscerales provides information on tactics, strategies, events and activities on our webpage. To keep our group connected, we also provide a forum and a community portal to '''The Mana World''' and other MMORPGs of interest. You can reach the webpage by going [http://wombat.arawakcity.org/losviscerales here] or to [http://www.tinyurl.com/streetgang tinyurl.com/streetgang]

==BrasilTeaM==

BrasilTeaM is a BR group that seeks to bring together Brazilians and others who play TMW. Our webpage is in Portuguese, check us out there or get in contact with one of the members on our list.

We welcome all BR's with open arms.

'''List:'''

Zuua, -Mihawk-, K2F5, SakaSurf, La FiTi, Fitipaldi, ckara, MiniMister,

'''This Decision them. / Esta a DecisÃ£o deles.'''

Soldado, sadaf, Autarquia, Lord Voldemort

[http://www.orkut.com/Main#Community.aspx?cmm=81542873&refresh=1 Webpage]

==The Sunshine Clan==

Our hopes for this clan is to hold events and fun games that the players can play.
The type of games we will hold will be like hide and seek, scavenger hunt, and whatever the players want, we will take suggestions. There will be prizes awarded to the winners.

Clan Leaders

1. Porter
2. Alexi Laiho

Visit the Sunshine Clan on the [http://sites.google.com/site/justinportermw/clan-info Web].

== xDeathofFatex ==
Info: A guild for the members of the [xDeathofFatex] clan, which can be found across the web and in many games.

Leaders:
* Apoca
* xSekereiGodx

 [xDeathofFatex] 

The [xDeathofFatex] guild will try to make its community (and the Mana World's) a more entertaining community (if not better). As the Mana World's development continues, the guild will try to create contests, events or other fun activities for its members. The guild welcomes anyone with open hands.
See you online!

Members: (Just edit your name in! We would be happy to accept you)
* Apoca
* xSekereiGodx

Visit our forum at [http://xdeathoffatex.heavenforum.com/the-mana-world-guild-forum-f19 xDeathofFatex]. See you there...

==The Mana World Player Community==

This is a non-affiliated alliance for the benefit of TMW Player Community. This page is to help create a contact list for affiliated and non-affiliated players that want to help enrich TMW player community. Individuals can be added here as long as what they do is for the player community at large.



{|-
!Character Name
!Other Player Groups
!Roles
!Descriptions and Scheduled Times
!Other Information
!Contact
|-
|Wombat
|[http://tinyurl.com/streetgang Los Viscerales]
|Event Organizer, TMW Wiki Helper
|[http://forums.themanaworld.org/viewtopic.php?f=12&t=6723 Crusaders versus Warlords] Team PvP. Sundays 20:00 UTC.
|Wombat also will help players add information to TMW wiki pages like [[Player Groups]]. Wombat is also interested in raids and will join parties when he is willing and available.
|Whisper "Wombat" in Game, Player Talk Forums or Private Message "Wombat"
|-
|}

Player Groups

2009-05-15T17:59:41Z

Crush2: moved "The Mana World Player Community" from "Alliances" page

{{Category_playerinfo}}
Please, try not to be chaotic when editing, try to keep the format, and don't create derived articles for your guilds. Here you have enough space to make your guilds.
==The Holy Mana Clan==

'''The Holy Mana clan mission statement.'''

'''Our purpose'''

The holy mana clan is created mainly to add another flavor to the game. The idea is to have a social network between players for the purpose of organizing in-game events as well as for helping newer players find their way. Membership is completely free. That means it doesn't matter whether you play one hour a week or 5 hours a day. Inactive players might be put on ghost status after a while, but they can immediately be put back once they are active again. Secondly that means you can quit the clan whenever you get tired of it, no strings attached. And finally it also means we do not ask for fees. Prizes for events will depend on donations of "richer" members. We used to keep a registry of the donated gold and items on-line, so people could check and see that this isn't just a scam to make money, but it became to time consuming as the clan grew bigger.

'''Our policy'''

Although the purpose of the clan is to make the game more fun, we are serious about our image. If members of the clan act obnoxious it will reflect poorly on all members. Therefore we have a strict policy; we will not accept known trouble makers and we will not hesitate to ban those who are destroying the concept. The idea is to unite as an open group and enjoy the game under the banner with integrity, not to create a closed group that acts superior to non-members. So be on your best behavior.

'''Our future'''

Since our options are quite limited on the current server we obviously only have a small influence on the game and on gameplay. Yet we are hoping that we can build this clan to a respectable size by the time new options become available. Until then we will probably keep an easygoing mood, and hold our best ideas for later.

'''For more informations such as:'''

*'''member list''' (more then 250 members; half is active, the other half drops in once in a while)
*'''news about events and meetings'''(join the fun)
*'''How to join, and clan-policy'''
*'''our Perk Point System''' (a system to reward active members with items)
*'''Contacting other members by forum or IRC''' (ask for advice or help, or just get to know each other)
*'''Screenshots and videos'''
*'''Walktrough''' (quests, stat-configuration, useful tips; more up to date than wiki)
*'''Usefull links''' (who's online, top stats, manabay, forums, player homesites, ...)
'''visit us at: [http://holymanaclan.webs.com/ http://holymanaclan.webs.com/]'''

'''Contacting the leaders'''

Every clan is supposed to have leaders and members, to prevent chaos. Although some of them have authority and some don't; the clan needs both of them to survive! Luckily the leaders of this clan are open to suggestions of their members. Is there anything you would like the clan to have, something about the clan you dislike? Do you have any questions? Do you want your home page or favorite page to be added to our "links" page? Do you have any suggestions for the web page or forum? Do you want to be notified of upcoming events? Do you think we could use your help with something you're good at? Do you have a nice screenshot you want to add? For all those things we made a clan e-mail address:

TheHolyManaClan@gmail.com

==Los Viscerales==

Los Viscerales are wizards, warriors and archers that seek to build a community that enjoys player organized activities and events. We support competitive game elements, the player driven market and seek to build alliances with others so that our small gaming community can thrive and continue to grow. If you are interested in organizing "player versus player" (pvp) or "raid" activities contact "Wombat" in game.

'''Webpage'''

Los Viscerales provides information on tactics, strategies, events and activities on our webpage. To keep our group connected, we also provide a forum and a community portal to '''The Mana World''' and other MMORPGs of interest. You can reach the webpage by going [http://wombat.arawakcity.org/losviscerales here] or to [http://www.tinyurl.com/streetgang tinyurl.com/streetgang]

==BrasilTeaM==

BrasilTeaM is a BR group that seeks to bring together Brazilians and others who play TMW. Our webpage is in Portuguese, check us out there or get in contact with one of the members on our list.

We welcome all BR's with open arms.

'''List:'''

Zuua, -Mihawk-, K2F5, SakaSurf, La FiTi, Fitipaldi, ckara, MiniMister,

'''This Decision them. / Esta a DecisÃ£o deles.'''

Soldado, sadaf, Autarquia, Lord Voldemort

[http://www.orkut.com/Main#Community.aspx?cmm=81542873&refresh=1 Webpage]

==The Sunshine Clan==

Our hopes for this clan is to hold events and fun games that the players can play.
The type of games we will hold will be like hide and seek, scavenger hunt, and whatever the players want, we will take suggestions. There will be prizes awarded to the winners.

Clan Leaders

1. Porter
2. Alexi Laiho

Visit the Sunshine Clan on the [http://sites.google.com/site/justinportermw/clan-info Web].

== xDeathofFatex ==
Info: A guild for the members of the [xDeathofFatex] clan, which can be found across the web and in many games.

Leaders:
* Apoca
* xSekereiGodx

 [xDeathofFatex] 

The [xDeathofFatex] guild will try to make its community (and the Mana World's) a more entertaining community (if not better). As the Mana World's development continues, the guild will try to create contests, events or other fun activities for its members. The guild welcomes anyone with open hands.
See you online!

Members: (Just edit your name in! We would be happy to accept you)
* Apoca
* xSekereiGodx

Visit our forum at [http://xdeathoffatex.heavenforum.com/the-mana-world-guild-forum-f19 xDeathofFatex]. See you there...

==The Mana World Player Community==

This is a non-affiliated alliance for the benefit of TMW Player Community. This page is to help create a contact list for affiliated and non-affiliated players that want to help enrich TMW player community. Individuals can be added here as long as what they do is for the player community at large.



{|-
!Character Name
!Player Group
!Roles
!Descriptions and Scheduled Times
!Other Information
!Contact
|-
|Wombat
|[http://tinyurl.com/streetgang Los Viscerales]
|Event Organizer, TMW Wiki Helper
|[http://forums.themanaworld.org/viewtopic.php?f=12&t=6723 Crusaders versus Warlords] Team PvP. Sundays 20:00 UTC.
|Wombat also will help players add information to TMW wiki pages like [[Player Groups]] and [[Alliances]]. Wombat is also interested in raids and will join parties when he is willing and available.
|Whisper "Wombat" in Game, Player Talk Forums or Private Message "Wombat"
|-
|}

Alliances

2009-05-15T17:59:08Z

Crush2: just another type of player group

#REDIRECT [[Player_Groups]]

Development:Developers

2009-05-12T20:59:47Z

Crush2: fixed colors

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}}
|}

User:Viann

2009-05-07T20:06:23Z

Crush2: Viann moved to User:Viann: user pages belong to the user namespace

[[Image:Viann]]

User:Groosse merde

2009-05-07T20:05:59Z

Crush2: Groosse merde moved to User:Groosse merde: user pages belong into the user namespace

[[Image:Groosse merde]]

User:Crush/Customized Equipment Technical

2009-05-07T18:43:02Z

Crush2: format fix

== Database ==
Layout for the SQL table to store customized equipment
{{beginsqltable|tmw_item_instances}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | tmw_item_instances_modifiers.id, tmw_item_instances_runes.id | unique identifier}}
{{sqltablerow | archetype-id | INTEGER | | | entry from items.xml to determine the slot the item is equipped in, the used sprite, item icon and description. In case of weapons it also affects the weapon category (used skill) and the attack zone.}}
{{sqltablerow | color | TEXT | | | colorization string}}
{{sqltablerow | name | TEXT | | | item name}}
{{sqltablerow | inscription | TEXT | | | custom description which can be added by the crafting character}}
{{sqltablerow | durability | INTEGER | | | remaining durability of the item}}
{{sqltablerow | initial-durability | INTEGER | | | initial durability of the item}}
{{sqltablerow | weight | INTEGER | | | weight}}
{{sqltablerow | value | INTEGER | | | price NPCs pay for this item}}
{{sqltablerow | rune-slots | INTEGER | | | number of slots for spell runes}}
{{endsqltable}}

Stat modifiers during item creation. Also includes elemental modifiers.
{{beginsqltable|tmw_item_instances_modifiers}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | attribute | BYTE | | | affected character attribute or modified element}}
{{sqltablerow | absolute | INTEGER | | | linear attribute modifier}}
{{sqltablerow | multiplier | FLOAT | | | attribute multiplier in case of character attribute. Elemental damage multiplier in case of element attribute.}}
{{sqltablerow | stackgroup | INTEGER | | | Stack group of the modifier effect. Every item may only have one effect from each stack group (with the exception of stack group 0) to avoid having multiple effects which are not supposed to stack. A weapon enchantment from a player would, for example, come from a specific stack group number which translates to "player weapon attack buff" making it impossible to apply it multiple times to the same weapon. }}
{{sqltablerow | time | INTEGER | | | time when the modifier wears off (for temporary enchantments)}}
{{endsqltable}}

Spell runes engraved in the item.
{{beginsqltable|tmw_item_instances_runes}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | spell | INTEGER | | | spell of the rune }}
{{endsqltable}}

Custom variables for use in item scripts
{{beginsqltable|tmw_item_instances_vars}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | key | TEXT | | | key }}
{{sqltablerow | value | TEXT | | | value}}
{{endsqltable}}

== Netcode ==

* Item IDs are 32 bit unsigned integers
* Item IDs 1 - 65.535 are non-customized generic items which may exist multiple times
* Item IDs 65.536 - 4.294.967.296 are unique equipment items which may only exist once in the game.
* When sending the inventory data to a character, every high id is followed by its archetype-id and colorization string. All other information about the item can be requested on demand with an additional message.
* When sending look information about other characters the archetype-id and the colorisation are transfered
* Colorisations are sent in a compressed format:
** 1 Byte bitfield of the used colorisation channels. For each channel:
*** 1 Byte for number of entries in the color ramp. for every entry:
**** 3 Byte for red, green and blue component of color
== Script API ==

;tmw.create_item_instance(archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Creates a custom item in the server database. Returns the ID of the item.
;tmw.change_item_instance(id, archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Changes the values of a custom item in the server database. Every argument may be NULL to leave it as it is.
;tmw.add_modifier_to_item_instance(id, attribute, absolute, multiplier, stack, time): Adds a modifier to an item.
;tmw.add_rune_to_item_instance(id, spell): Adds a spell rune to an item.
;tmw.get_item_instance(id): Returns a table with the attributes of the item.
;tmw.get_item_instance_modifiers(id): Returns a table of tables with the modifier data of the item.
;tmw.get_item_instance_runes(id): Returns a table of tables with the rune data of the item.
;tmw.get_item_instance_var(id, key): Returns the string stored in "key" in the var table of the item
;tmw.set_item_instance_var(id, key, value): Sets the string stored in "key" in the var table of the item.

(function names not checked for consistency with the rest of the api)

User:Crush/Customized Equipment Technical

2009-05-07T18:41:38Z

Crush2: added anti stacking precaution to stat modifiers

== Database ==
Layout for the SQL table to store customized equipment
{{beginsqltable|tmw_item_instances}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | tmw_item_instances_modifiers.id, tmw_item_instances_runes.id | unique identifier}}
{{sqltablerow | archetype-id | INTEGER | | | entry from items.xml to determine the slot the item is equipped in, the used sprite, item icon and description. In case of weapons it also affects the weapon category (used skill) and the attack zone.}}
{{sqltablerow | color | TEXT | | | colorization string}}
{{sqltablerow | name | TEXT | | | item name}}
{{sqltablerow | inscription | TEXT | | | custom description which can be added by the crafting character}}
{{sqltablerow | durability | INTEGER | | | remaining durability of the item}}
{{sqltablerow | initial-durability | INTEGER | | | initial durability of the item}}
{{sqltablerow | weight | INTEGER | | | weight}}
{{sqltablerow | value | INTEGER | | | price NPCs pay for this item}}
{{sqltablerow | rune-slots | INTEGER | | | number of slots for spell runes}}
{{endsqltable}}

Stat modifiers during item creation. Also includes elemental modifiers.
{{beginsqltable|tmw_item_instances_modifiers}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | attribute | BYTE | | | affected character attribute or modified element}}
{{sqltablerow | absolute | INTEGER | | | linear attribute modifier}}
{{sqltablerow | multiplier | FLOAT | | | attribute multiplier in case of character attribute. Elemental damage multiplier in case of element attribute.}}
{{sqltablerow | stackgroup | INTEGER | | | Stack group of the modifier effect. Every item may only have one effect from each stack group (with the exception of stack group 0) to avoid having multiple effects which are not supposed to stack. A weapon enchantment from a player would, for example, come from a specific stack group number which translates to "player weapon attack buff" making it impossible to apply it multiple times to the same weapon.
{{sqltablerow | time | INTEGER | | | time when the modifier wears off (for temporary enchantments)}}
{{endsqltable}}

Spell runes engraved in the item.
{{beginsqltable|tmw_item_instances_runes}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | spell | INTEGER | | | spell of the rune }}
{{endsqltable}}

Custom variables for use in item scripts
{{beginsqltable|tmw_item_instances_vars}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | key | TEXT | | | key }}
{{sqltablerow | value | TEXT | | | value}}
{{endsqltable}}

== Netcode ==

* Item IDs are 32 bit unsigned integers
* Item IDs 1 - 65.535 are non-customized generic items which may exist multiple times
* Item IDs 65.536 - 4.294.967.296 are unique equipment items which may only exist once in the game.
* When sending the inventory data to a character, every high id is followed by its archetype-id and colorization string. All other information about the item can be requested on demand with an additional message.
* When sending look information about other characters the archetype-id and the colorisation are transfered
* Colorisations are sent in a compressed format:
** 1 Byte bitfield of the used colorisation channels. For each channel:
*** 1 Byte for number of entries in the color ramp. for every entry:
**** 3 Byte for red, green and blue component of color
== Script API ==

;tmw.create_item_instance(archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Creates a custom item in the server database. Returns the ID of the item.
;tmw.change_item_instance(id, archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Changes the values of a custom item in the server database. Every argument may be NULL to leave it as it is.
;tmw.add_modifier_to_item_instance(id, attribute, absolute, multiplier, stack, time): Adds a modifier to an item.
;tmw.add_rune_to_item_instance(id, spell): Adds a spell rune to an item.
;tmw.get_item_instance(id): Returns a table with the attributes of the item.
;tmw.get_item_instance_modifiers(id): Returns a table of tables with the modifier data of the item.
;tmw.get_item_instance_runes(id): Returns a table of tables with the rune data of the item.
;tmw.get_item_instance_var(id, key): Returns the string stored in "key" in the var table of the item
;tmw.set_item_instance_var(id, key, value): Sets the string stored in "key" in the var table of the item.

(function names not checked for consistency with the rest of the api)

User:Crush/Customized Equipment Technical

2009-05-07T18:30:58Z

Crush2: replaced customitem with item_instance

== Database ==
Layout for the SQL table to store customized equipment
{{beginsqltable|tmw_item_instances}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | tmw_item_instances_modifiers.id, tmw_item_instances_runes.id | unique identifier}}
{{sqltablerow | archetype-id | INTEGER | | | entry from items.xml to determine the slot the item is equipped in, the used sprite, item icon and description. In case of weapons it also affects the weapon category (used skill) and the attack zone.}}
{{sqltablerow | color | TEXT | | | colorization string}}
{{sqltablerow | name | TEXT | | | item name}}
{{sqltablerow | inscription | TEXT | | | custom description which can be added by the crafting character}}
{{sqltablerow | durability | INTEGER | | | remaining durability of the item}}
{{sqltablerow | initial-durability | INTEGER | | | initial durability of the item}}
{{sqltablerow | weight | INTEGER | | | weight}}
{{sqltablerow | value | INTEGER | | | price NPCs pay for this item}}
{{sqltablerow | rune-slots | INTEGER | | | number of slots for spell runes}}
{{endsqltable}}

Stat modifiers during item creation. Also includes elemental modifiers.
{{beginsqltable|tmw_item_instances_modifiers}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | attribute | BYTE | | | affected character attribute or modified element}}
{{sqltablerow | absolute | INTEGER | | | linear attribute modifier}}
{{sqltablerow | multiplier | FLOAT | | | attribute multiplier in case of character attribute. Elemental damage multiplier in case of element attribute.}}
{{sqltablerow | time | INTEGER | | | time when the modifier wears off (for temporary enchantments)}}
{{endsqltable}}

Spell runes engraved in the item.
{{beginsqltable|tmw_item_instances_runes}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | spell | INTEGER | | | spell of the rune }}
{{endsqltable}}

Custom variables for use in item scripts
{{beginsqltable|tmw_item_instances_vars}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | key | TEXT | | | key }}
{{sqltablerow | value | TEXT | | | value}}
{{endsqltable}}

== Netcode ==

* Item IDs are 32 bit unsigned integers
* Item IDs 1 - 65.535 are non-customized generic items which may exist multiple times
* Item IDs 65.536 - 4.294.967.296 are unique equipment items which may only exist once in the game.
* When sending the inventory data to a character, every high id is followed by its archetype-id and colorization string. All other information about the item can be requested on demand with an additional message.
* When sending look information about other characters the archetype-id and the colorisation are transfered
* Colorisations are sent in a compressed format:
** 1 Byte bitfield of the used colorisation channels. For each channel:
*** 1 Byte for number of entries in the color ramp. for every entry:
**** 3 Byte for red, green and blue component of color
== Script API ==

;tmw.create_item_instance(archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Creates a custom item in the server database. Returns the ID of the item.
;tmw.change_item_instance(id, archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Changes the values of a custom item in the server database. Every argument may be NULL to leave it as it is.
;tmw.add_modifier_to_item_instance(id, attribute, absolute, multiplier, time): Adds a modifier to an item.
;tmw.add_rune_to_item_instance(id, spell): Adds a spell rune to an item.
;tmw.get_item_instance(id): Returns a table with the attributes of the item.
;tmw.get_item_instance_modifiers(id): Returns a table of tables with the modifier data of the item.
;tmw.get_item_instance_runes(id): Returns a table of tables with the rune data of the item.
;tmw.get_item_instance_var(id, key): Returns the string stored in "key" in the var table of the item
;tmw.set_item_instance_var(id, key, value): Sets the string stored in "key" in the var table of the item.

(function names not checked for consistency with the rest of the api)

User:Crush/Customized Equipment Technical

2009-05-07T18:28:43Z

Crush2: added script variables (former tmw_item_attributes)

== Database ==
Layout for the SQL table to store customized equipment
{{beginsqltable|tmw_customitem}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | tmw_customitem_modifiers.id, tmw_customitem_runes.id | unique identifier}}
{{sqltablerow | archetype-id | INTEGER | | | entry from items.xml to determine the slot the item is equipped in, the used sprite, item icon and description. In case of weapons it also affects the weapon category (used skill) and the attack zone.}}
{{sqltablerow | color | TEXT | | | colorization string}}
{{sqltablerow | name | TEXT | | | item name}}
{{sqltablerow | inscription | TEXT | | | custom description which can be added by the crafting character}}
{{sqltablerow | durability | INTEGER | | | remaining durability of the item}}
{{sqltablerow | initial-durability | INTEGER | | | initial durability of the item}}
{{sqltablerow | weight | INTEGER | | | weight}}
{{sqltablerow | value | INTEGER | | | price NPCs pay for this item}}
{{sqltablerow | rune-slots | INTEGER | | | number of slots for spell runes}}
{{endsqltable}}

Stat modifiers during item creation. Also includes elemental modifiers.
{{beginsqltable|tmw_customitem_modifiers}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | attribute | BYTE | | | affected character attribute or modified element}}
{{sqltablerow | absolute | INTEGER | | | linear attribute modifier}}
{{sqltablerow | multiplier | FLOAT | | | attribute multiplier in case of character attribute. Elemental damage multiplier in case of element attribute.}}
{{sqltablerow | time | INTEGER | | | time when the modifier wears off (for temporary enchantments)}}
{{endsqltable}}

Spell runes engraved in the item.
{{beginsqltable|tmw_customitem_runes}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | spell | INTEGER | | | spell of the rune }}
{{endsqltable}}

Custom variables for use in item scripts
{{beginsqltable|tmw_customitem_vars}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | key | TEXT | | | key }}
{{sqltablerow | value | TEXT | | | value}}
{{endsqltable}}

== Netcode ==

* Item IDs are 32 bit unsigned integers
* Item IDs 1 - 65.535 are non-customized generic items which may exist multiple times
* Item IDs 65.536 - 4.294.967.296 are unique equipment items which may only exist once in the game.
* When sending the inventory data to a character, every high id is followed by its archetype-id and colorization string. All other information about the item can be requested on demand with an additional message.
* When sending look information about other characters the archetype-id and the colorisation are transfered
* Colorisations are sent in a compressed format:
** 1 Byte bitfield of the used colorisation channels. For each channel:
*** 1 Byte for number of entries in the color ramp. for every entry:
**** 3 Byte for red, green and blue component of color
== Script API ==

;tmw.create_custom_item(archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Creates a custom item in the server database. Returns the ID of the item.
;tmw.change_custom_item(id, archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Changes the values of a custom item in the server database. Every argument may be NULL to leave it as it is.
;tmw.add_modifier_to_item(id, attribute, absolute, multiplier, time): Adds a modifier to an item.
;tmw.add_rune_to_item(id, spell): Adds a spell rune to an item.
;tmw.get_custom_item(id): Returns a table with the attributes of the item.
;tmw.get_custom_item_modifiers(id): Returns a table of tables with the modifier data of the item.
;tmw.get_custom_item_runes(id): Returns a table of tables with the rune data of the item.
;tmw.get_custom_item_var(id, key): Returns the string stored in "key" in the var table of the item
;tmw.set_custom_item_var(id, key, value): Sets the string stored in "key" in the var table of the item.

(function names not checked for consistency with the rest of the api)

User:Crush/Customized Equipment Technical

2009-05-07T17:03:28Z

Crush2: about compression of colorisations

== Database ==
Layout for the SQL table to store customized equipment
{{beginsqltable|tmw_customitem}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | tmw_customitem_modifiers.id, tmw_customitem_runes.id | unique identifier}}
{{sqltablerow | archetype-id | INTEGER | | | entry from items.xml to determine the slot the item is equipped in, the used sprite, item icon and description. In case of weapons it also affects the weapon category (used skill) and the attack zone.}}
{{sqltablerow | color | TEXT | | | colorization string}}
{{sqltablerow | name | TEXT | | | item name}}
{{sqltablerow | inscription | TEXT | | | custom description which can be added by the crafting character}}
{{sqltablerow | durability | INTEGER | | | remaining durability of the item}}
{{sqltablerow | initial-durability | INTEGER | | | initial durability of the item}}
{{sqltablerow | weight | INTEGER | | | weight}}
{{sqltablerow | value | INTEGER | | | price NPCs pay for this item}}
{{sqltablerow | rune-slots | INTEGER | | | number of slots for spell runes}}
{{endsqltable}}

Stat modifiers during item creation. Also includes elemental modifiers.
{{beginsqltable|tmw_customitem_modifiers}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | attribute | BYTE | | | affected character attribute or modified element}}
{{sqltablerow | absolute | INTEGER | | | linear attribute modifier}}
{{sqltablerow | multiplier | FLOAT | | | attribute multiplier in case of character attribute. Elemental damage multiplier in case of element attribute.}}
{{sqltablerow | time | INTEGER | | | time when the modifier wears off (for temporary enchantments)}}
{{endsqltable}}

Spell runes engraved in the item.
{{beginsqltable|tmw_customitem_runes}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | spell | INTEGER | | | spell of the rune }}
{{endsqltable}}

== Netcode ==

* Item IDs are 32 bit unsigned integers
* Item IDs 1 - 65.535 are non-customized generic items which may exist multiple times
* Item IDs 65.536 - 4.294.967.296 are unique equipment items which may only exist once in the game.
* When sending the inventory data to a character, every high id is followed by its archetype-id and colorization string. All other information about the item can be requested on demand with an additional message.
* When sending look information about other characters the archetype-id and the colorisation are transfered
* Colorisations are sent in a compressed format:
** 1 Byte bitfield of the used colorisation channels. For each channel:
*** 1 Byte for number of entries in the color ramp. for every entry:
**** 3 Byte for red, green and blue component of color
== Script API ==

;tmw.create_custom_item(archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Creates a custom item in the server database. Returns the ID of the item.
;tmw.change_custom_item(id, archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Changes the values of a custom item in the server database. Every argument may be NULL to leave it as it is.
;tmw.add_modifier_to_item(id, attribute, absolute, multiplier, time): Adds a modifier to an item.
;tmw.add_rune_to_item(id, spell): Adds a spell rune to an item.
;tmw.get_custom_item(id): Returns a table with the attributes of the item.
;tmw.get_custom_item_modifiers(id): Returns a table of tables with the modifier data of the item.
;tmw.get_custom_item_runes(id): Returns a table of tables with the rune data of the item.

(function names not checked for consistency with the rest of the api)

User:Crush

2009-05-07T16:44:26Z

Crush2: /* Subpages */ removed canonized articles

User:Crush2/Customized Equipment Technical

2009-05-07T16:43:30Z

Crush2: User:Crush2/Customized Equipment Technical moved to User:Crush/Customized Equipment Technical: wrong userspace

#REDIRECT [[User:Crush/Customized Equipment Technical]]

User:Crush/Customized Equipment Technical

2009-05-07T16:43:29Z

Crush2: User:Crush2/Customized Equipment Technical moved to User:Crush/Customized Equipment Technical: wrong userspace

== Database ==
Layout for the SQL table to store customized equipment
{{beginsqltable|tmw_customitem}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | tmw_customitem_modifiers.id, tmw_customitem_runes.id | unique identifier}}
{{sqltablerow | archetype-id | INTEGER | | | entry from items.xml to determine the slot the item is equipped in, the used sprite, item icon and description. In case of weapons it also affects the weapon category (used skill) and the attack zone.}}
{{sqltablerow | color | TEXT | | | colorization string}}
{{sqltablerow | name | TEXT | | | item name}}
{{sqltablerow | inscription | TEXT | | | custom description which can be added by the crafting character}}
{{sqltablerow | durability | INTEGER | | | remaining durability of the item}}
{{sqltablerow | initial-durability | INTEGER | | | initial durability of the item}}
{{sqltablerow | weight | INTEGER | | | weight}}
{{sqltablerow | value | INTEGER | | | price NPCs pay for this item}}
{{sqltablerow | rune-slots | INTEGER | | | number of slots for spell runes}}
{{endsqltable}}

Stat modifiers during item creation. Also includes elemental modifiers.
{{beginsqltable|tmw_customitem_modifiers}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | attribute | BYTE | | | affected character attribute or modified element}}
{{sqltablerow | absolute | INTEGER | | | linear attribute modifier}}
{{sqltablerow | multiplier | FLOAT | | | attribute multiplier in case of character attribute. Elemental damage multiplier in case of element attribute.}}
{{sqltablerow | time | INTEGER | | | time when the modifier wears off (for temporary enchantments)}}
{{endsqltable}}

Spell runes engraved in the item.
{{beginsqltable|tmw_customitem_runes}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | spell | INTEGER | | | spell of the rune }}
{{endsqltable}}

== Netcode ==

* Item IDs are 32 bit unsigned integers
* Item IDs 1 - 65.535 are non-customized generic items which may exist multiple times
* Item IDs 65.536 - 4.294.967.296 are unique equipment items which may only exist once in the game.
* When sending the inventory data to a character, every high id is followed by its archetype-id and colorization string. All other information about the item can be requested on demand with an additional message.
* When sending look information about other characters the archetype-id and the colorisation are transfered

== Script API ==

;tmw.create_custom_item(archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Creates a custom item in the server database. Returns the ID of the item.
;tmw.change_custom_item(id, archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Changes the values of a custom item in the server database. Every argument may be NULL to leave it as it is.
;tmw.add_modifier_to_item(id, attribute, absolute, multiplier, time): Adds a modifier to an item.
;tmw.add_rune_to_item(id, spell): Adds a spell rune to an item.
;tmw.get_custom_item(id): Returns a table with the attributes of the item.
;tmw.get_custom_item_modifiers(id): Returns a table of tables with the modifier data of the item.
;tmw.get_custom_item_runes(id): Returns a table of tables with the rune data of the item.

(function names not checked for consistency with the rest of the api)

User:Crush

2009-05-07T16:43:01Z

Crush2: /* Subpages */

:::''"A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects."''
::::-- Robert A. Heinlein

I am contributing to many different aspects of the project. Pixel artist, mapper, programmer, game concepts and i even tried to compose music, although with minor success. My credo is "when you want something to be done properly, do it yourself".

I am always concerned about the opinions of other developers and the fan base. So i am usually showing a lot of unfinished work on the forum.

==Projects I took part in==

=== Pixel Art ===
These pieces of art are mostly made by me:
* Woodland tileset
* Woodland Village indoor and outdoor tilesets
* Pink monster
* Ambient GFX
* Female version of cotton shirt
* Some tuneups at female player set
* The following Headgear sprites: Miners helm, Fancy hat, Headbands, Santa hat
* Light platemail armor

I also made some minor improvements at the following pieces:
* Desert tileset
* Dropshadow of the bats
* Shading of the mushroom monster.

=== Maps ===
The maps made by me in chronological order of creation:
* new_9-1.tmx.gz (first woodland map)
* new_4-1.tmx.gz (Bat Cave)
* new_14-1.tmx.gz (woodland map released with 0.0.21)
* new_15-1.tmx.gz (desert map released with 0.0.21)
* new_16-1.tmx.gz (woodland map released with 0.0.21)
* new_18-1.tmx.gz (woodland village surrounding)
* new_19-1.tmx.gz (woodland village outdoor)
* new_20-1.tmx.gz (woodland village indoor)

=== Programming ===
These are the subsystems where i was the major programmer:
====Client====
* XML based animation system
* Ambient overlays
* Smooth scrolling
* XML based client-sided equipment sprite database and monster database
* [[User:Crush/Particle engine|Particle engine]]
====TMWServ====
* Provisoric monster AI
* Attacking
* Attribute handling

==Current projects==
I am currently most involved in server programming.

== Subpages==
*[[User:Crush/Crafting]] (notes)
*[[User:Crush/Rune_combination]] (draft)
*[[User:Crush/Scripting]] (notes)
*[[User:Crush/Weather]] (draft)
*[[User:Crush/Special_Attacks]] (draft)
*[[User:Crush/Economy]] (notes)
*[[User:Crush/Food]] (draft)
*[[User:Crush/Alcohol]] (draft)
*[[User:Crush/Particle Engine Tutorial]] (draft)
*[[User:Crush/The_nature_of_mana_and_magic]]
*[[User:Crush/Move_Code_Rewrite]] (notes)
*[[User:Crush/Customized_Equipment_Technical]] (concept)

User:Crush/Customized Equipment Technical

2009-05-07T16:19:29Z

Crush2: script api

== Database ==
Layout for the SQL table to store customized equipment
{{beginsqltable|tmw_customitem}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | tmw_customitem_modifiers.id, tmw_customitem_runes.id | unique identifier}}
{{sqltablerow | archetype-id | INTEGER | | | entry from items.xml to determine the slot the item is equipped in, the used sprite, item icon and description. In case of weapons it also affects the weapon category (used skill) and the attack zone.}}
{{sqltablerow | color | TEXT | | | colorization string}}
{{sqltablerow | name | TEXT | | | item name}}
{{sqltablerow | inscription | TEXT | | | custom description which can be added by the crafting character}}
{{sqltablerow | durability | INTEGER | | | remaining durability of the item}}
{{sqltablerow | initial-durability | INTEGER | | | initial durability of the item}}
{{sqltablerow | weight | INTEGER | | | weight}}
{{sqltablerow | value | INTEGER | | | price NPCs pay for this item}}
{{sqltablerow | rune-slots | INTEGER | | | number of slots for spell runes}}
{{endsqltable}}

Stat modifiers during item creation. Also includes elemental modifiers.
{{beginsqltable|tmw_customitem_modifiers}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | attribute | BYTE | | | affected character attribute or modified element}}
{{sqltablerow | absolute | INTEGER | | | linear attribute modifier}}
{{sqltablerow | multiplier | FLOAT | | | attribute multiplier in case of character attribute. Elemental damage multiplier in case of element attribute.}}
{{sqltablerow | time | INTEGER | | | time when the modifier wears off (for temporary enchantments)}}
{{endsqltable}}

Spell runes engraved in the item.
{{beginsqltable|tmw_customitem_runes}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | spell | INTEGER | | | spell of the rune }}
{{endsqltable}}

== Netcode ==

* Item IDs are 32 bit unsigned integers
* Item IDs 1 - 65.535 are non-customized generic items which may exist multiple times
* Item IDs 65.536 - 4.294.967.296 are unique equipment items which may only exist once in the game.
* When sending the inventory data to a character, every high id is followed by its archetype-id and colorization string. All other information about the item can be requested on demand with an additional message.
* When sending look information about other characters the archetype-id and the colorisation are transfered

== Script API ==

;tmw.create_custom_item(archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Creates a custom item in the server database. Returns the ID of the item.
;tmw.change_custom_item(id, archetype-id, color, name, inscription, durability, initial-durability, weight, value, runeslots): Changes the values of a custom item in the server database. Every argument may be NULL to leave it as it is.
;tmw.add_modifier_to_item(id, attribute, absolute, multiplier, time): Adds a modifier to an item.
;tmw.add_rune_to_item(id, spell): Adds a spell rune to an item.
;tmw.get_custom_item(id): Returns a table with the attributes of the item.
;tmw.get_custom_item_modifiers(id): Returns a table of tables with the modifier data of the item.
;tmw.get_custom_item_runes(id): Returns a table of tables with the rune data of the item.

(function names not checked for consistency with the rest of the api)

User:Crush/Customized Equipment Technical

2009-05-07T16:09:44Z

Crush2: netcode notes

== Database ==
Layout for the SQL table to store customized equipment
{{beginsqltable|tmw_customitem}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | tmw_customitem_modifiers.id, tmw_customitem_runes.id | unique identifier}}
{{sqltablerow | category | BYTE | | | slot the item is equipped in}}
{{sqltablerow | archetype-id | INTEGER | | | entry from items.xml to determine the used sprite, item icon and description. In case of weapons it also affects the weapon category (used skill) and the attack zone.}}
{{sqltablerow | color | TEXT | | | colorization string}}
{{sqltablerow | name | TEXT | | | item name}}
{{sqltablerow | inscription | TEXT | | | custom description which can be added by the crafting character}}
{{sqltablerow | durability | INTEGER | | | remaining durability of the item}}
{{sqltablerow | initial-durability | INTEGER | | | initial durability of the item}}
{{sqltablerow | weight | INTEGER | | | weight}}
{{sqltablerow | value | INTEGER | | | price NPCs pay for this item}}
{{sqltablerow | rune-slots | INTEGER | | | number of slots for spell runes}}
{{endsqltable}}

Stat modifiers during item creation. Also includes elemental modifiers.
{{beginsqltable|tmw_customitem_modifiers}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | attribute | BYTE | | | affected character attribute or modified element}}
{{sqltablerow | absolute | INTEGER | | | linear attribute modifier}}
{{sqltablerow | multiplier | FLOAT | | | attribute multiplier in case of character attribute. Elemental damage multiplier in case of element attribute.}}
{{sqltablerow | time | INTEGER | | | time when the modifier wears off (for temporary enchantments)}}
{{endsqltable}}

Spell runes engraved in the item.
{{beginsqltable|tmw_customitem_runes}}
{{sqltablerow | id | INTEGER | PRIMARY KEY | | id of the custom item affected}}
{{sqltablerow | spell | INTEGER | | | spell of the rune }}
{{endsqltable}}

== Netcode ==

* Item IDs are 32 bit unsigned integers
* Item IDs 1 - 65.535 are non-customized generic items which may exist multiple times
* Item IDs 65.536 - 4.294.967.296 are unique equipment items which may only exist once in the game.
* When sending the inventory data to a character, every high id is followed by its archetype-id and colorization string. All other information about the item can be requested on demand with an additional message.
* When sending look information about other characters the archetype-id and the colorisation are transfered