Spring - User contributions [en]

Trouble-shooting s3o units

2007-07-15T14:39:59Z

Erom:

This page assumes you have a working knowledge of Spring unit creation, and will address some common pitfalls in creating s30 units.

=Invisible Unit=
'''Problem:'''
Unit spawns projectiles, engine flare, and other fx, as well as functioning correctly, but the model is invisible at any view distance.

'''Check:'''
* That your s3o has both a radius and height set in Upspring.

=Disappearing Unit=
'''Problem:'''
Unit operates correctly, including being visible at low zoom levels, but disappears at higher zoom levels, often leaving a small grey blob. Example:
http://img54.imageshack.us/img54/1278/problemga6.jpg

'''Check:'''
* The reduction to grey blob is done by the LOD (Level Of Detail) process in spring. For 3do units, this nicely scales down a full 3d unit to a sprite as you scale out. For s3o, this doesn't work as nicely. There are two things you can do:
** 1: Make sure your unit has a radius that reflect the model size accurately. The view distance at which LOD kicks in is proportional to unit radius.
** 2: Make sure your LOD setting in Spring is high enough to actually display the unit correctly.

Trouble-shooting s3o units

2007-07-15T14:29:47Z

Erom: New page: [URL=http://imageshack.us][img]http://img54.imageshack.us/img54/1278/problemga6.jpg[/img][/URL]

[URL=http://imageshack.us][img]http://img54.imageshack.us/img54/1278/problemga6.jpg[/img][/URL]

Game and Unit development

2007-07-15T14:29:12Z

Erom: /* s3o units */

=Mod development=
Mods, next to Maps, is the content used in Spring. 
A mod is simply a combined file containing a small structure of files and directories holding all the data required. 

[[Mod_Development | Mod Development]] wiki is a starting page, linking to very useful information on the files included in a mod, their hierarchy and more.
 

Almost the entire mod developing is the creation of units. Which isn't an easy job. 
Information about the creation of units are everywere, but not combined. 
This is a gathered list of all Tutorials and helpfull forums threads I could find: 

===General===
*http://taspring.clan-sy.com/wiki/Create_units - old Wiki 
*[[Mod Development]]
*[[Mod specification]] 
*[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6015 What do I need to create a mod]

===Unit Development===
*[http://taspring.clan-sy.com/wiki/Unit_Development Global informations about units]

====s3o units====
* [http://lassie.student.utwente.nl/vliet/springtut.pdf Maestro's tutorial of Upspring and textures].
* [[Basic s3o unit making guide]]
* [[Simple Mod Tutorial]]
* [[Units:CreateModel|UV Mapping in Wings3D]]
* [http://spring.clan-sy.com/phpbb/viewtopic.php?t=10947 Texturing Tutorial]
* [http://spring.clan-sy.com/phpbb/viewtopic.php?t=10612 Wings UV Mapping Tutorial]
* [http://taspring.clan-sy.com/phpbb/viewtopic.php?p=75495 various things about unit making. (Also contains an illustrated alpha-channel tut)]
* [http://spring.clan-sy.com/phpbb/viewtopic.php?t=10503 Runecrafter's 3DS Max UV Mapping Tutorial]
* [[Trouble-shooting s3o units]]

====Scripting and Animation====
* [http://taspring.clan-sy.com/phpbb/viewtopic.php?p=132943#132943 GPL-compliant sourcecode, scripting code examples, and other things.]
* GET/SET MAX_SPEED works once again. GET/SET ACTIVATION also works (which means you can turn radar jamming, energy production, radar, metal proudction, energy/metal use as defined in the fbi off and on via script)

====FBI Files====
*[[Units:FBI]]
*[[All_FBI-variable_values:_min,_max,_default,_type|Units:FBI (variables)]]

====TDF Files====
*[[Units:Download TDF]]
*[[Units:Weapons]] : Various informations about weapons
*[[All_Weapons_variable_values:_min,_max,_default,_type|Units:Weapons (variables)]]
*[[Weapon Variables]] : This is the most up to date

====Lua====
*[[Units:LuaCOB]] - how to interface COB with LUA

====Misc====
*[[Units:WeaponMainDir]]
*[[Units:Design]]
*[[Units:Buildpics]]
*[[Units:High-poly]]
*[[Units:Textures]]
*[[Mod Development:Armor]]
*[[Mod Development:Spawn]]
*[[Mod Development:Cursors]]
*[[Mod Development:Archives]]
*[[Mod Development:Sidepics]]
*[[CustomExplosionGenerators|Mod Development:Custom explosions]]
*[[CustomUnitIcons|Mod Development:Custom unit icons]]

====3do units====
* [http://www.tauniverse.com/forum/forumdisplay.php?s=

Water Height: Mapconv vs. Heightmap

2007-05-12T20:52:56Z

Erom: /* The Problem */

===The Problem===

It has come up as a source of confusion as to what shade of grey in your heightmap is water level. The simple answer is that there isn't a simple answer, but don't worry it really isn't all that hard. It is determined by your height input parameters to mapconv (Does none of this make sense? You probably want to stop here, go back and read some of the [http://taspring.clan-sy.com/wiki/Map_development tutorials]. ) ''Note this assumes you have both 0% and 100% grey (black and white, respectively) on your heightmap, which should be the case (this maximises the range of greys you can play with for your heightmap)''

the '''-x''' value in mapconv is the altitude (in elmos?) of a 100% white surface

the '''-n''' value is the altitude of a 0% white surface

To find the altitude of an intermediate shade of grey, do this,

'''n+(y*(x-n)) = a''' or, simplified, '''y*x + (1-y)*n = a'''

Where '''y''' is your value (in percent or in RGB value / 255)
'''x''' and '''n''' are the parameters from mapconv
and '''a''' is the altitude of that value

'''The water level is always assumed to be 0 in mapconv''', so anything with a negative '''a''' value will be underwater.

===An Example===

So to make 50% grey underwater, you could for example set your water line at 55% grey. Then, some values for mapconv that would work are:

-x 82 -n -100 <- this would produce very low mountains
-x 205 -n -250 <- this would probably be better

User:Erom

2006-09-18T23:34:01Z

Erom:

You'll find me, like most people, on the [http://taspring.clan-sy.com/phpbb/index.php messageboard] more often than here.

Not a common player on line, my internet connection at home is unreliable

===Current Projects===

Cursors for [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6851 Lego Spring]

===Goodies===

[http://www.fileuniverse.com/?p=showitem&ID=3472 Map:Crossfire]

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6150 Content:Cursors Set]

Map Control

2006-09-15T19:50:48Z

Erom:

Always a part of well-balanced RTS games, Map Control (commonly referred to as MC) is the amount of control you exert on the map. At the simplest level this can refer to the amount of map that you have expanded to cover, to access a greater resource base. However, there can also exist "controlled" territory that has not yet been expanded into - an area covered by an air force, for example. Converting Controlled territory to Expansion territory effectively is one of the cornerstones of effective play.

Map Control is '''ESSENTIAL''' in almost all maps/mods, however it cannot be the sole method of achieving victory, considering the economic infeasibility of maintaining it inviolate of assault.

The conundrum is this- if left unchallenged, economic growth is exponential with territory acquisition. The more you expand, the more resource points you control, and the more room you have to build up your on resource or logistics points. However, the more you expand, the more thinly your defenses are spread to protect against raiding. Your opponent also has more choices for targets to mobilize an assault against, making the "guessing game" elements of this strategy more difficult for the expanding player. Expansion alone is not a winning strategy - you must combine expansion with good use of the additional resources, flexible force control that can react quickly and effectively to widespread attacks, and plenty of scouting so you can keep up with where and when your opponent is planning an attack.

A common mistake of the beginner player is to expand too slowly, and be crushed by the superior military machine of his opponent. A common mistake of the intermediate player is to expand too quickly and leave a vital hole in his defenses that the enemy can exploit. Mastering the rate of expansion, which varies from map to map and mod to mod, is quite possibly the most difficult and most rewarding strategic problem a player has to face.

User:Erom

2006-06-23T13:37:58Z

Erom:

You'll find me, like most people, on the [http://taspring.clan-sy.com/phpbb/index.php messageboard] more often than here. Recently deprived of my fat pipe due to summer, so you won't see me online often.

===Goodies===

[http://www.fileuniverse.com/?p=showitem&ID=3472 Map:Crossfire]

User:Erom

2006-06-23T13:28:49Z

Erom:

You'll find me, like most people, on the [http://www.example.com messageboard] more often than here. Recently deprived of my fat pipe due to summer, so you won't see me only often.

===Goodies===

[http://www.example.com Map:Crossfire]

Map Reviews

2006-06-23T13:25:15Z

Erom: /* Brazilian Battlefield */

If anyone else wants to do more work on this, it might be useful to have the maps sorted by size.

==Normal Maps==

===2 Valleys===

Deci: Mostly an air map, as not even kbots can climb the plateus, mex radius is also too small for the metal layout.

===4 skulls===

Deci: Simply too much metal, otherwise a solid map. Try lowering the metal income on the hills to around 1.5 or lower.

FizWizz: Interesting map, funny metal but fun to play. However, the metalmap is really bright.

===Alaska===

AF: Needs stuff on the corner bits, preferrably custom snowy tree like features and other assortments, and a small open space, otherwise looks nice but a bit plain.

===Ancient Arena===

Deci: I have heard that this is an excellent FFA map, though I myself do not normally play FFA

Sehk: Very good for FFA and small but numerous team games (5 teams of 2 comes to mind) if completely dependent on the center. Height map issues may arise, and the water in the corners offers another viable few strategies most players shouldn't need to deal with.

===Anglo-Saxon Starfish===

Deci: Too much metal, otherwise a good combo of land and sea.

===Ashap Plateau===

--[[User:Egarwaen|Egarwaen]] 00:55, 16 Apr 2006 (W. Europe Daylight Time): Apparently an old favourite for 1v1s and 2v2s. The ground is covered with spires that really muck up most units' pathfinding and firing.

===Ashpen===

Gnome: Good, not too big and not too much metal. Wouldn't mind a slightly larger one with more topography, but it's still good.

===Atlantic===

Deci: A strange map, as amphibious units are near useless due to mountainous shorelines and air and naval power rule the day. This is another map that would benefit from a larger mex radius.

===Azure Rampart===

Deci: Probably the most played FFA map, not much to say about this one.

Sehk: Not pretty, not very varied, but functional. Good for FFA, but with limited enjoyment and flexibility.

===Blue Planet===

Sehk: Water map, with central metal in the water and lesser metal on land. Once you have the center, it becomes far too easy, and the map doesn't have an incredible amount of replay value. Smaller than I would like.

===Brazilian Battlefield===

AF: Too many trees in one corner makes AI testing on this map unfair. Make a bigger version though, it's somewhat smaller than I would have liked.

--[[User:Egarwaen|Egarwaen]] 00:55, 16 Apr 2006 (W. Europe Daylight Time): Good for quick games.

--[[User:Erom|Erom]] The many mountains make this an easy map to porc heavily on. However, it is one of the few small maps, so if you are looking for a quick game, it is a good option.

===Caldera===

Deci: Basically a larger version of Ashpen

===Castles===

Deci: the ultimate seige map, I don't play this one much anymore, but it is still fun sometimes when the game doesn't slow down.

--[[User:Egarwaen|Egarwaen]] 00:55, 16 Apr 2006 (W. Europe Daylight Time): Massive porcfest.

2k4: HUGE metal in water

Targ Collective: Excellent siege map, although the 'Lake of Gold' has less tactical value than it could. Placing an even moderate metal distribution over most of the map, including the grassy areas, allows players to expand resource operations over most of the map, where it could play better confined to the castles and lake solely to force confrontations.

===Cathralda V10===

--[[User:Egarwaen|Egarwaen]] 00:10, 25 Apr 2006 (W. Europe Daylight Time): A fun map. Wind is good but very unpredictable. Medium level of metal, quite spread-out. Easily-accessible geothermals, mostly near the center of the map. Rolling hills with some chokepoints, but too open to porc effectively. Vehicles seem to be able to climb all of the hills. The one problem is that it's a little hard to gauge hill heights in the default TA view.

===Cliff Down===

Deci: A good FFA map if the players start at the entrances to the canyon, the starts should probably be changed to reflect this

Gnome: Good metal layout, but it's so big that there's too much available. Also very easy to porc out on (secure your two chokepoints, dot the rest of your base with AA). The game I played on this one became a drawn out stalemate that lasted over three hours because it's simply too damn big.

===Cliff Run===

Deci: too small to really play on.

Gnome: I disagree. It's good for a quick game, the action is quick and it really keeps you on your toes. The hills really add to the map. The trees are somewhat annoying, but area reclaim works.

--[[User:Egarwaen|Egarwaen]] 00:55, 16 Apr 2006 (W. Europe Daylight Time): Great fun for 1v1, though watch the water.

===CometCatcher and Green Comet===

Deci: one of the much-loved maps, it isn't my personal favorite, but it's a solid map.

Min3mat: Godlike! accept no substitutues!

Forboding Angel: Too damn flat. Heightmap needs to be redone badly.

--[[User:Egarwaen|Egarwaen]] 00:55, 16 Apr 2006 (W. Europe Daylight Time): Great maps, if a little flat. I prefer Green Comet for its left-vs-right setup, but the original's still great.

===Core Pyramid===

Deci: A map with actual low metal, these are rare goodies

===CorrosivePits===

Deci: apparently there is a version 4 out for this map that I haven't played yet.

===Crossings_v4===

--[[User:Egarwaen|Egarwaen]] 20:09, 25 Apr 2006 (W. Europe Daylight Time): Fun "push the middle" map. Low metal near start locations, lots in the middle. Assaulting up the ramps is a little annoying at the end, but once you push the enemy out of the middle, you're practically guaranteed a win.

===Crystal-Harbor===

Targ Collective - A fun water map with perhaps just a bit too much metal. Metal spots are used throughout and the centre has a very high metal spot, which in itself accounts for at least half the metal on the map. South has an advantage in land (slight) and Geo spots (two extra), so the choice is a balanced if cramped East vs West, or an unbalanced yet easier teamwise North vs South.

If one team can consistently hold the centre, that team will gain a huge tactical advantage. Therefore, pummelling the centre with artillery if you lose it is advised.

All teams start on land, so the more durable aircraft are available. Specialist seaplanes, esp. torpedo launchers, should see plenty of use.

2k4: you might as well quit if you dont have the center on start

===Crystal-World===

Deci: Mex radius is far too small, it should be doubled or tripled at least.

===Desert Dunes===

Deci: too much metal, otherwise good

FizWizz: This map is Ace. The metal is much higher than a typical map, but I still wuvs it =)

===Egypt===

Sehk: Fairly realistic and fun to play, but rather imbalanced due to the placement of water. Metal is plentiful and gameplay is quick.

===EuroGreen===

Forboding Angel: Honestly, it's ugly and a comm swapfest imo. Small maps are good if the are done correcty. Unfortunately this map does not have enough real chokepoints to be viable.

===EvergreenHaven===

--[[User:Egarwaen|Egarwaen]] 00:55, 16 Apr 2006 (W. Europe Daylight Time): Nice hilly map. Good balance between chokepoints and openness. Similar gameplay to GreenHaven.

===Greenhaven===

Deci: One of the popular maps of spring, somewhat rough terrain, while still allowing vehicles.

===Greenriver===

Min3mat: awesome. IMO the best water map out there

===Hamburger Hill===

Deci: Open-area tank warfare, barely deserves to be called a hill

===Hill Haven===

FizWizz: My favorite map of the River Dale set. It looks absolutely beautiful, it is simple, but it is not a plain map. It is balanced too, which is a little bit harder to say about the other maps in this series.

===Hills and Valleys===

Deci: a good vehicle and kbot map, I really don't know why this one isn't played more.

===Island in the Sun===

FizWizz: A good naval map, the only island-hopper besides Gods of War II remake, I wish I could see more maps like this on FU.

===Island Alpha===

Deci- decent 1v1 map

===Lava Highground===

Deci: extremely focused on the center, not sure if that's a good thing or a bad thing for this map

===Lava Rivers===

Deci: Only one land route is generally bad for gameplay

===Martian Desert===

Gnome: Decent for 1v1, probably a little too much metal for that a lot of the time though. Probably very good for 2v2. Not too big either.

===Mountain Seige===

Deci: a good kbot map, probably the one that would benefit most from lvl2 kbots having good anti-air.

FizWizz: I love this map, it is beautiful and it plays well too, but it really needs to have a couple of the pathways broadened and leveled some so that they can actually accept traffic.

===Nightscape===

Deci: a personal favorite of mine, this map manages to feel huge even though it isn't.

===Oki River===

Deci: this map has only one real problem, there is too much metal in the water, on this map, the water would probably still be valuable even if there were no metal in it.

2k4: agreed, half the metal should be plenty

===Painted Desert Remake===

Deci: no qualms with this one, solid map

Min3mat: Probably the prettiest map out there with good gameplay. Faithful port by NoiZe ^-^

===Pathways===

Deci: now weighs in at only 15 meg!

===Pax Prime===

Deci: an interesting map simply because of it's color

===PincushionRemake===

Kixxe: This map has a great feel towards the different maps. It's low metal makes expanding a must, constantly fighting over more of the map and more resources. A peewee corpse can be a god's blessing. The pins can be used to place LLT's and radars, but they block much of the radar to, meaning you have to build several on different pins to get a full view. This is a wonderful map, but it can be hard to adapt to since it has "no metal".

===Plains and Passes===

Deci: this map could use a metal reduction, there are so many metal patches that the maxmetal should probably be lowered by a third or so. Also, mex radius is so small that it doesn't even cover the entire metal patch.

Forboding Angel: Nice map, too much metal imo. If I don't have over 300 metal income by the end of the game on this map I've done something wrong.

2k4: increase mex radius, decrease metalspots by 75%

===Rainbow Land===

Deci: as far as I can tell, this is a joke map

===Redhaven===

Deci: rarely played because Greenhaven is easier on the eyes.

===River Dale===

Deci: excellent 3v3 map, though the host needs to be careful where the start boxes are to keep it fair.

2k4: GREAT map

===Road to War===

Deci: my map, so I don't think I can comment

===Shore to Shore===

FizWizz: I have never played an enjoyable game on this map, it just does not conduce itself to anything other than porcing, aircraft spamming, or massing battleships, that I have seen.

===Sparewood===

Gnome: Excellent for 3FFAs, small and in your face like sherwood, only minus the severely annoying trees at the start points. Not bad for 1v1 either. Perhaps a little too much metal, but it plays very fairly and well.

===Splintered 4x4===

Deci: Absolute annihilation units cannot cross the fords, and therefore it doesn't get played by a very large chunk of spring's players. The speed boost on the ford is also a bit rediculous.

2k4: too high tidal

===Sunken Outpost===

Deci: an often-played ffa or team map, would be a bit linear if it weren't for the water

===Swamp Island===

Deci: mohos cannot easily be placed on the metal, making this map a bit of a pain to play

===Tendril Mountain===

Deci: another of my maps, it has way too much metal and I plan on fixing it eventually

===The Hunters===

Forboding Angel: All in all it's a solid map. A little low on metal for my tastes but still quite solid. It has large lake type bodies of water running through it. Lakes are large enough to put ships in if you so desire :D

I havn't played this map myself. Only spectated, but I like the layout quite a bit and the atmospheric colors are beautiful. It is rather flat which IMO kinda sucks but regardless it's a rather fun map.

Sehk: The gameplay here is varied, though the terrain is rather feeble. If you want to run a game with every type of unit, this is the place... hovers, tanks, ships, amphibious vehicles, k-bots and planes are all viable, though you would have a hard time with submarines.

===The Abyss===

Deci: Giant filesize makes this one a pain to download

FizWizz: Absolutely destitute of metal, until you reach the crater in the middle. However, I had one of my most fun games of Spring in memory on this map.

===The Cold Place===

Deci: works for teams or FFA

Gnome: Good, faithful port of the original.

2k4: solid map

===Volcano Island===

Deci: subs have some difficulty getting though certain areas, should be changed

==Metal Maps==

===Core Prime Industrial Area===

FizWizz: The metal concentration on the North/South Pyramids is ridiculous. Being both a metal map and a classic OTA map, it ought to have even metal distribution throughout, but as it is now, the strategic importance of the four walled forts is greatly diminished.

Min3mat: Awful metal map which would be better with even displacement of metal

===Metal Isles===

FizWizz: Being both a metal map and a classic OTA map, it ought to have even metal distribution, but there is zero metal in the water. Not a crimp on gameplay, but something which should have been remedied.

==Unreviewed Maps==

If you've played one of these maps, please contribute your opinion and move it into the appropriate category above!

4B Facility

Acid Bridge

AcidQuadratic

Appleville Two

BallerBurg

Battle Lines

Clear a Ditch

Caustic Realm

County Crossing

Crust

Death Valley

Dueling Bases

Dueling Forts

Duggans Metal Map

Duggans Metal Map Two

Fizzy Lakes

Foothill Basin

Foothills

Gods of War two remake

Grassy Paradox

Grad

Green River

Hell's Pass

IceArena

Icebergs

Island Hopping

King of the Castle

Marshlands

MetalHeck

MicroMetalAlpha

Monolith NaAr

Mountain Range

Omega

PCB

Proving Grounds

Rockies

Rolling Hills

Rush Hour

Rusted Divide

Scrap Metal

Snowscape

Speedymetal2

Spring-Islands

Stone Bridges

The Highlands

The Pass

Tidal War

Tri-Vega

Valles Marineris

Valley of Death

Water-Ways

WideOpenCombat

Windswept Desert

XantheTerra

[[Category:Maps]]

Water Height: Mapconv vs. Heightmap

2006-06-23T13:18:58Z

Erom: /* The Problem */

===The Problem===

It has come up as a source of confusion as to what shade of grey in your heightmap is water level. The simple answer is that there isn't a simple answer, but don't worry it really isn't all that hard. It is determined by your height input parameters to mapconv (Does none of this make sense? You probably want to stop here, go back and read some of the [http://taspring.clan-sy.com/wiki/Map_development tutorials]. ) ''Note this assumes you have both 0% and 100% grey (black and white, respectively) on your heightmap, which should be the case (this maximises the range of greys you can play with for your heightmap)''

the '''-x''' value in mapconv is the altitude (in elmos?) of a 100% white surface

the '''-n''' value is the altitude of a 0% white surface

To find the altitude of an intermediate shade of grey, do this,

'''n+(y*(x-n)) = a''' or, simplified, '''y*x + (1-y)*n = a'''

Where '''y''' is your value (in percent or in RGB value / 255)
'''x''' and '''n''' are the parameters from mapconv
and '''a''' is the altitude of that value

The water level is always assumed to be 0 in mapconv, so anything with a negative '''a''' value will be underwater.

===An Example===

So to make 50% grey underwater, you could for example set your water line at 55% grey. Then, some values for mapconv that would work are:

-x 82 -n -100 <- this would produce very low mountains
-x 205 -n -250 <- this would probably be better

Water Height: Mapconv vs. Heightmap

2006-06-23T13:14:05Z

Erom: /* The Problem */

===The Problem===

It has come up as a source of confusion as to what shade of grey in your heightmap is water level. The simple answer is that there isn't a simple answer, but don't worry it really isn't all that hard. It is determined by your height input parameters to mapconv (Does none of this make sense? You probably want to stop here, go back and read some of the [[tutorials]]. ) ''Note this assumes you have both 0% and 100% grey (black and white, respectively) on your heightmap, which should be the case (this maximises the range of greys you can play with for your heightmap)''

the '''-x''' value in mapconv is the altitude (in elmos?) of a 100% white surface

the '''-n''' value is the altitude of a 0% white surface

To find the altitude of an intermediate shade of grey, do this,

'''n+(y*(x-n)) = a''' or, simplified, '''y*x + (1-y)*n = a'''

Where '''y''' is your value (in percent or in RGB value / 255)
'''x''' and '''n''' are the parameters from mapconv
and '''a''' is the altitude of that value

The water level is always assumed to be 0 in mapconv, so anything with a negative '''a''' value will be underwater.

===An Example===

So to make 50% grey underwater, you could for example set your water line at 55% grey. Then, some values for mapconv that would work are:

-x 82 -n -100 <- this would produce very low mountains
-x 205 -n -250 <- this would probably be better

Water Height: Mapconv vs. Heightmap

2006-06-23T13:11:41Z

Erom: /* Water Height FAC */

===The Problem===

It has come up as a source of confusion as to what shade of grey in your heightmap is water level. The simple answer is that there isn't a simple answer, but don't worry it really isn't all that hard. It is determined by your height input parameters to mapconv (Does none of this make sense? You probably want to stop here, go back and read some of the [[tutorials]]. ) ''Note this assumes you have both 0% and 100% grey (black and white, respectively) on your heightmap, which should be the case (this maximises the range of greys you can play with for your heightmap)''

the '''-x''' value in mapconv is the altitude (in elmos?) of a 100% white surface

the '''-n''' value is the altitude of a 0% white surface

To find the altitude of an intermediate shade of grey, do this,

'''n+(y*(x-n)) = a''' or, simplified, '''y*x + (1-y)*n = a'''

Where '''y''' is your value (in percent or in RGB value / 255)
'''x''' and '''n''' are the parameters from mapconv
and '''a''' is the altitude of that value

===An Example===

So to make 50% grey underwater, you could for example set your water line at 55% grey. Then, some values for mapconv that would work are:

-x 82 -n -100 <- this would produce very low mountains
-x 205 -n -250 <- this would probably be better

Water Height: Mapconv vs. Heightmap

2006-06-23T13:11:14Z

Erom:

=Water Height FAC=

===The Problem===

It has come up as a source of confusion as to what shade of grey in your heightmap is water level. The simple answer is that there isn't a simple answer, but don't worry it really isn't all that hard. It is determined by your height input parameters to mapconv (Does none of this make sense? You probably want to stop here, go back and read some of the [[tutorials]]. ) ''Note this assumes you have both 0% and 100% grey (black and white, respectively) on your heightmap, which should be the case (this maximises the range of greys you can play with for your heightmap)''

the '''-x''' value in mapconv is the altitude (in elmos?) of a 100% white surface

the '''-n''' value is the altitude of a 0% white surface

To find the altitude of an intermediate shade of grey, do this,

'''n+(y*(x-n)) = a''' or, simplified, '''y*x + (1-y)*n = a'''

Where '''y''' is your value (in percent or in RGB value / 255)
'''x''' and '''n''' are the parameters from mapconv
and '''a''' is the altitude of that value

===An Example===

So to make 50% grey underwater, you could for example set your water line at 55% grey. Then, some values for mapconv that would work are:

-x 82 -n -100 <- this would produce very low mountains
-x 205 -n -250 <- this would probably be better

Map development

2006-06-23T13:01:21Z

Erom: /* Reference and FAQs */

=Map making=
Maps, are a complex mixture of heightmaps and textures.
Fortunatly, there are several people who share their knowledge with us.
There few tutorials will make your life as mapper a lot better.

== Full Guides For Map Making ==

*[[Create_maps|aGorm's map creating Guide]]
*[[Map_Making_Guide|aGorms Ultimate Map Making Guide(unfinished)]]
*[[IceXuick_Map_Design_Help|IceXuicks Map creating Guide]]
*[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3941 Forboding Angel's map creating Tutorial]
*[[Maps:Tutorial|Another tutorial from a designing point of view]]
*[[A_Complete_Map_Making_Tutorial|A Complete Map Making Tutorial (under construction)]]
*[[Runecrafter|Runecrafter's Map Tutorial]]

== Specific Guides ==

*[[Maps:SMD|Everything about .SMD]]
*[[Maps:Compiling|Everything about Compiling your map]]
*[[MapsBalance|Some things about map balance]]

Features. Stones, rocks, trees, for your map can be found in [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=4047 This thread] 

== Mappers Clan ==
[[Map Making Guild]]: That weird fish aGorm set up a clan for poor mappers that can't get into a clan on there gaming merit... (Mainly for himself therefor...)

== Reference and FAQs ==

* [[Maps:Noob Mistakes]]
* [[Water Height: Mapconv vs. Heightmap]]

----
TIPS:

A useful tip, on almost every map in a 1v1 you will start opposite your opponent unless you choose your position. this is because random order simply randomly distributes players at the default start points which in almost every map are opposite each other. One exception that I know of is flooded desert where you both start on the left hand island.
----

[[Category:Map development]]