User:Bonchan

2006-10-07T03:45:50Z

Bonchan:

new units:
Medusa Lv2
race: umanoid
movement:5
attacks:claws4-2
eyes 0-1pietrification
hp:34
res:pietrification 100%
fire -20%
others 0%
-------------------------------------------------------------------------------
Succubus Lv2
race:demon
movament:7(winged)
attacks:death kiss 20-1absorb
charming 0-1(the unit change team)
hp:37
res:charme 100%
holy -100%
others 30%
-------------------------------------------------------------------------------
Hydra Lv0 Hydra Lv1 Hydra Lv2 Hydra Lv3 Hydra Lv4 Hydra Lv5
race:monster
movement:5/7(in water)
attacks:bite 3-2 bite 4-4 bite 5-6 bite 6-8 bite 7-10 bite 8-12
hp:40 50 60 70 80 90
res:fire -50%
holy 0% ability: regeneration
sword -30%
others 30%
--------------------------------------------------------------------------------
Imp Lv0 Lesser Demon Lv1 Lesser Devil Lv1
race:demon
movement:7(winged)
attacks:claws 3-2 sword punch 7-2 impact claws 6-2 sword
tail 2-1 venom head 18-1 charge tail 6-1 venom
provocate 0-3(berserk fury) terror wawe 12-1(cold) fire ball 12-1(fire)
hp:15 30 27
res:holy -50% -50% -50%
fire 0% -20% 50%
ice 0% 50% -20%
others 0% ??? ???
Demon Lv2 Devil Lv2
punch 10-2 impact claws 6-3 sword
head 24-1 charge tail 8-1 venom
terror wawe 12-2(cold) fire ball 12-2(fire)
hp: 40 35
High Demon Lv3 High Devil Lv3
punch 12-2 impact claws 6-4 sword
head 30-1 charge tail 10-1 venom
terror wawe 12-3(cold) fire ball 12-3(fire)
hp: 50 43
Demon Lord Lv4 Devil Lord Lv4
punch 15-2 impact claws 6-5 sword
head 35-1 charge tail 12-1 venom
terror wawe 12-4(cold) fire ball 12-4(fire)
hp: 60 51
Demon's King Lv5 Devil's King Lv5
punch 20-2 impact claws 7-6 sword
head 47-1 charge tail 20-1 venom
terror wawe 15-5(cold) fire ball 15-5(fire)
hp: 70 59
res:holy -20% -20
fire 50% 100%
ice 100% 50%
ability: command command
--------------------------------------------------------------------------------

BuildingUnits

2006-10-06T18:48:28Z

Bonchan: units

Ma'''Bold text'''''Italic text''[[Link title]][http://www.example.com link title]
== Headline text ==
king new units is fairly easy. Unit configuration files are plain text files that you can edit with any editor such as Notepad, TextEdit, gedit, pico, vi, emacs, etc. You will need to become familiar with [[UnitWML|WML]] in order to make a new unit. This page contains a more in-depth discussion of Unit WML syntax and will walk you through the creation of a new unit and discuss how you can use it in-game.

== Recommended procedure ==
The easiest way to make a new unit is to copy and paste an existing unit, then modify it. Navigate to the game's data/units directory and copy any unit. When you are editing the unit, attention to detail is key. If you forget to modify each key (for example, the unique id key), problems will result.

P.S. Make sure you use gimp to create a blank background.

== Using your new unit ==
Any unit in the game's ./data/units directory or ''userdata''/data/units will be recognized by the game. However, just because you made a new unit does NOT mean you can use it in game yet. Each scenario and multiplayer era has a specific recruit list. If your unit is not on the list, you can't use it. This means you need to modify the ''recruit='' key in the appropriate configuration file. [[BuildingMultiplayer]] describes different ways you do this for multiplayer. To add a unit to a campaign, read about scenarios, sides, and recruit lists in [[BuildingScenarios]].

== Distributing your unit ==
If you made a single unit, post it on the [http://www.wesnoth.org/forum forum]. If you made a whole group of units, you can make them into a multiplayer faction or you can upload a unit pack.

If you want to make a faction, follow the instructions in the [[BuildingFactions]] article. You should create a new era and add your units as one of the factions. You will not be able to add your units to any era that ships with the game.

If you want to make a unit pack, the procedure is easier. Unit packs are distributed for campaign writers who want to use your units in their campaigns/eras. They download your unit pack and copy/paste the units and images into their campaign/era.
* Navigate to the ''userdata''/data/campaigns directory. Everything from now on will occur relative to here. The era we'll use as an example will be called MyUnitPack
* Create a text file called MyUnitPack.cfg. Add the following lines:
# #define USE_MYUNITS #<- replace MYUNITS with something descriptive
# #enddef
# #ifdef USE_MYUNITS #<- replace MYUNITS with something descriptive
# {@campaigns/MyUnitPack/}
# #endif
:* These lines are commented out (with the #). That way when the unit pack ships it won't affect the game. If someone wants the game to be able to see these units, he can uncomment those lines and it will work. However, this usually causes problems in multiplayer (you will be using units no one else has), but it can be fun for campaigns.
:* NOTE: the commenting/uncommenting trick will only work if the units branch off of an existing unit. Custom L1 units will NOT show up in game automatically without editing another configuration file somewhere (scenario config file or multiplayer.cfg)
* Create another text file called MyUnitPack.pbl. (See [[PblWML]] for more details about *.pbl files.) Add the following lines to it:
author="''your name''"
icon="''any image file in the game's ./images directory''"
version="1.0"
title="My Awesome Unit Pack"
description="New race of lizard men."
* Create a folder called MyUnitPack. Navigate to it.
* Create two subdirectories: units and images. Place your unit cfg files and artwork into those subdirectories
* Create a text file called MyUnitPack.cfg (or another name of your choosing). Add the following lines:
[binary_path]
path=data/campaigns/MyUnitPack
[/binary_path]
[+units]
{@campaigns/MyUnitPack/units}
[/units]
* You should be ready to distribute your unit pack on the campaign server now
* PLEASE change the names to something unique before you publish

== Unit WML discussion ==

Units are enclosed in '''[unit]''' tags.

This section only provides some tips and pointers in making a unit. Feel free to add pointers of your own. For the full, current, complete WML reference on what to put in your [unit], see and frequently revisit [[UnitWML|The Unit WML reference page]].
* The first attribute of a unit is the ''id'' key, which is a unique identifier for the unit. As value of the ''type'' attribute for these units, the ''id'' key is used. (See [[BuildingScenarios]]).
* When referencing the unit in a ''type'' key, the id must be reproduced verbatim, without typos, and in a case-sensitive manner. If you don't do this, the key won't work. If you can't recruit in a scenario, it's probably because you have a typo in one of the unit ids and the ''recruit'' key was invalidated.
* It also has a ''name'' key, which is the (translatable) name of the unit, and is displayed on the Status Table when a unit of this type is selected. It does not need to be unique (but it helps).
* Do not set movement to 0. It creates weird infinite movement behavior. This might be fixed in the future. For now, to make an immobile unit, set movement to 1 use [movement_costs] to make it unable to move onto any terrain.
* Also, make sure you give the unit at least one [attack]. If not, there is a bug in the game code that will cause the game to crash when it attempts to find attacks. This may also be fixed in the future.
* See [[BuildingScenariosIntermediate]] for more information on attacks.

== See Also ==

* [[Create]]
* [[EditingWesnoth]]
* [[Creating Unit Art]]
* [[CampaignServerWML]]
* [[PblWML]]
* [[BuildingCampaignsThePBLFile]]
* [[Team_Color_Shifting]]

{{Create}}

The Battle for Wesnoth Wiki - User contributions [en]

User:Bonchan

BuildingUnits