Spring - User contributions [en]

Community news

2006-12-01T18:44:10Z

NOiZE:

On this page, you can post news items that will be seen in the top right section of the frontpage. You can use this to post if you have created or found something of interest to the Spring community, such as a new map, a useful tool or perhaps a new useful page in the wiki. Details on how to update this page can be found [[Community_news_editing | here]].

----

===2006-12-01 New Balanced Annihilation version!!!===
No more Weaselspam, Kbots are viable, Custom uniticons, faster gameplay, Overall better gameplay --> Balanced Annihilation v4.2 <-- get decent games now! --> [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=8163 Info and downloadlinks] <--

===2006-10-28 XTA v8.1 Release posted===
All new and shiny XTA! Look [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=8212 here]!

===2006-10-27 NanoBlobz v0.64 Release posted===
Awesome new graphics! Look [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=8089 here]!

===2006-11-25 RAI v0.35 Released (Skirmish AI)===
[http://www.fileuniverse.com/?p=show&a=it&id=4030 Download Link]

===2006-10-27 XTA - Final v8 Release posted===
All new and shiny XTA! Look [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=7806 here]!

===2006-10-20 Absolute Annihilation 2.23 posted===
Download here: [http://aaspring.tk aaspring.tk]

===2006-10-14 AAI 0.76 released===
Look here: http://taspring.clan-sy.com/phpbb/viewtopic.php?t=7539

===2006-08-30 TSI 0.11 Released===
New version of new AI. Many bugfixes and improvemnts.
http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6787

===2006-08-18 NTai XE9RC22 Released===
Lots of changes and improvements, look here:
http://www.darkstars.co.uk

===2006-07-19 AAI 0.70 Released===
Win + Linux version, look here:
http://taspring.clan-sy.com/phpbb/viewtopic.php?p=102040#102040

===2006-06-30 Absolute Annihilation 2.11 now available===
Download here: http://aaspring.tk

===2006-06-20 NTai XE9 RC19 Released===
Uber AI FTW!!! http://www.darkstars.co.uk

===2006-06-20 KAI v0.11 Released===
Update released fixing most crash bugs (hopefully!)

http://taspring.clan-sy.com/phpbb/viewtopic.php?t=5500

===2006-05-18 Gundam 1.0 achieved and released!===
After over a year of work I have acomplished what I have set out to do.

http://www.fileuniverse.com/?p=showitem&ID=3208

===2006-06-16 Absolute Annihilation 2.0 Released===
2.0 Released, full 0.72 compatibility; Download here: http://aaspring.tk

===2006-05-18 Gundam 1.0 achieved and released!===
After over a year of work I have acomplished what I have set out to do.

http://www.fileuniverse.com/?p=showitem&ID=3208

===2006-05-13 NTai XE8 and NanoBlobs 0.4 Final Released===
5 new groupAI's, a powerful skirmish AI, 2 maps, and The last Nanoblobz!!!
Download here: www.darkstars.co.uk
Manual / Unit Guide here: http://taspring.clan-sy.com/phpbb/viewtopic.php?t=4276
Argh/AF

===2006-05-01 Absolute Annihilation 1.46 Released===
1.46 Released. Download here: http://aaspring.tk Mod homepage here: http://ta-aa.sourceforge.net Unit Guide here: http://ta-aa.sourceforge.net/modweb

===2006-05-01 Modweb Generator v0.4 Released===
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3842 Get it here!]
This will create a set of HTML pages about your mod, units, and weapons. Check it out.

===2006-04-18 Expand and Exterminate .152 Released!===
[http://tinyurl.com/pmrhf Get it here!]
Completely original mod, not based on OTA!

===2006-04-18 OTAI 1.13===
Minor Changes and Bugfixes.
[http://www.fileuniverse.com/?p=showitem&ID=2994 DLLs] [http://www.fileuniverse.com/?p=showitem&ID=2993 Source]

===2006-04-17 AAI 0.63 released===
Minor improvements but a lot of bugfixes :)
[http://taspring.clan-sy.com/phpbb/viewtopic.php?p=70404#70404 Look here].

===2006-04-16 Xect vs. Mynn v0.6 released, 100% legal===
[http://www.ta-spring.com/mods/xectvsmynn/ Get it here],
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3005&postdays=0&postorder=asc&start=80 discuss it here].

===2006-04-15 XTA Pimped Edition V5.5===
[http://tinyurl.com/p4mtc Read and Grab it here!]

===2006-04-10 AAI 0.60 released===
Experimental water support, linux support and a lot more... [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=4509 Look here]

===2006-04-05 FF v1.15===
New Version of Final Frontier [http://tinyurl.com/q3u3e Here]

===2006-03-30 OTAI v1.12===
With working command buffering [http://tinyurl.com/e8fuh Here]

===2006-03-27 XTA Pimped Edition V5===
[http://tinyurl.com/kr95f Grab it here].

===2006-03-26 NTai XE7.5 Skirmish AI===
[http://www.darkstars.co.uk/ Get it here]. - AF

===NanoBlobs 0.31(beta)===
Exponential game design. Updated. Smaller. Faster. Even cooler. Get it [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=4276 Here]

===2006-03-06 OTAI 1.10===
Now works in 0.70, fixed nanostall somewhat. Get it [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3412 Here]

===2006-02-25 AAI 0.55===
A rather small release mainly adding support for the modified ai interface [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3886 get it here].

===2006-02-25 NTAI XE6 for 0.70b1 Skirmish AI===
Universal mod support, statistical unit learning, freeform buildtrees [http://www.darkstars.co.uk/index.php Get them here]. - AF

===2006-02-19 AAI 0.52===
AAI 0.52 is only a small bugfix release [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3886 get it here].

===2006-02-13 Absolute Annihilation 1.44===
AA 1.44 completed and uploaded.[http://www.planetannihilation.com/aa AA Homepage].
.
[[SWTA]] [[Final_Frontier]] [[Absolute_Annihilation]]

===2006-2-19 AAI 0.52 Released===
AAI 0.52 is only a small bugfix release for AAI 0.5 - hopefully all crashes are gone now
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3886 click here].

===2006-2-15 NTAI XE 3 Released===
XE 3 has support map specific build data, 9 new keywords, StarWars/Gundam support, numerous fixes, and should run a lot faster ^^ [http://www.darkstars.co.uk/index.php here]. - AF

===2006-02-13 Absolute Annihilation 1.44 Released===
AA 1.44 completed and uploaded. Readme and changelog available at the [http://www.planetannihilation.com/aa AA Homepage].

===2006-2-06 OTAI 1.08 Released===
Now uses multithreading to reduce freezing!
[http://taspring.clan-sy.com/phpbb/viewtopic.php?p=55624#55624 Forum] [http://www.fileuniverse.com/?p=showitem&ID=2354 Download]

===2006-02-01 World Domination 5B62 Released===
This version fixes the crashes related to missing .cob-files.
Download [http://www.fileuniverse.com/?p=showitem&ID=2311 here].

===2006-1-31 Star Wars Spring Manual Released===
[http://spring.clan-sy.com/wiki/SWTA_Manual Read the SWS Manual right now!] It contains everything you would ever want to know about SWS, including: Installation Guide, In-Depth Unit Guide as well as a Strategy & Tactics section.

===2006-1-27 OTAI 1.07 Released===
Veylon released OTAI version 1.07. Now builds Dragon's Teeth and crashes less!
Download [http://www.geocities.com/veylon_ii/TASpring/ here].

===2006-11-19 UpSpring Tutorial Released===
Maestro R Setiawan released [http://tinyurl.com/cd25b a very comprehensive tutorial] to UpSpring, the application to import new models to Spring. Now you won't have any excuse to not use UV mapped S3O!

===2006-01-16 NTAI 0.29a Released===
NTAI 0.29a released, go get it here [http://taspring.clan-sy.com/phpbb/viewtopic.php?p=50716#50716 Download]

===2006-01-16 Absolute Annihilation 1.42 Released===
AA 1.42 completed and uploaded. Readme and changelog available at the [http://www.planetannihilation.com/aa AA Homepage].

[http://prdownloads.sourceforge.net/ta-aa/AASpring142.zip?download Download] (9 mb)

===2006-01-12 AAI 0.4 Released===
AAI 0.4 now supports air units as well as construction units assisting others.
Edit: Small Bugfix Version AAI 0.42 released
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3527 AAI v0.42].

===2006-1-07 Gundam Annihilation 0.98.sd7 Released===
This is a .sd7 for your spring lobby usage. I have corrected a few of the spring specific bugs in this release. Enjoy. [http://www.planetannihilation.com/gundam/ Gundam annihilation homepage]

[http://www.planetannihilation.com/gundam/shots/screen039.jpg http://www.planetannihilation.com/gundam/shots/screen039_thumb.gif] [http://www.planetannihilation.com/gundam/shots/screen012.jpg http://www.planetannihilation.com/gundam/shots/screen012_thumb.gif]

===2005-12-15 AAI 0.3 Released===
AAI 0.3 includes a lot of bug fixes and placement of defence buildings. [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3195 AAI v0.3].

===2005-12-14 Absolute Annihilation 1.35 Released===
AA 1.35 completed and uploaded. Readme and changelog available at the [http://www.planetannihilation.com/aa AA Homepage].

[http://prdownloads.sourceforge.net/ta-aa/AASpring135.zip?download Download] (16 mb)

===2005-12-13 OTAI 1.03b Released===
A fixed version of OTAI 1.03 now available.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3184 Forum Thread]
[http://www.geocities.com/veylon_ii/TASpring/OTAI_v103b.zip Download]

===2005-12-13 The Lost Legacy v1.04 Released===
The Lost Legacy Race, originally by M3G, ported to Spring by NOiZE.

This is the TA:Spring version of the masterpiece race created by the TA creation veterans M3G and Nik. Striving for perfection, they have completed an astoundishing number of 150 new units. This is by far the most expanded and carefully balanced race that has been created to this point. Explore the strategic values of the new submarine pens, defensive constructions and the many supersized monsters that let you toy with the opponent.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2860 Forum Thread]
[http://www.fileuniverse.com/?p=showitem&ID=1967 Download]

===2005-12-07 Star Wars: Spring 1.0 Released===
The well known Star Wars TC for TA has been ported to Spring.

One of the most complete TCs that existed for TA has now been fully ported to Spring - all of the bugs that plagued the quick and dirty earlier port have been fixed. Some balancing issues that came up in Spring has also been taken care of, along with a few other minor modifications, to ensure that this modification is made specifically for the Spring engine, so that you can enjoy it as such. Furthermore, many of the uglier low-polygon units for SWTA have been remodelled for Spring, so that you can now enjoy high-poly infantry units, as well as a few other vehecular changes.

Feel free to come join us on our own chat channel (itself a good 5 years old), where you can organise games, discuss balance, and report bugs:

Server: irc.gnug.org

Channel: #SWTA

An in-depth manual, with help regarding strategies and unit descriptions can be located [http://www.planetannihilation.com/swta/readme.asp here], however, bear in mind that while much of this will be very helpful, it was originally intended for the Original Total Annihilation release, and so is not 100% accurate or reliable with regards to the Spring release. A Spring-specific manual is in the works.

SWS features around 130 units ranging from all six movies and the expanded universe for the Galactic Empire and Rebel Alliance. Join this galaxy spanning war today, download SWS!

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3166 Forum Thread]
[http://www.fileuniverse.com/?p=showitem&ID=1988 Download]
[http://www.planetannihilation.com/swta/ SWTA Homepage]

===2005-12-07 The Lost Legacy v1.03 Released===
The Lost Legacy Race, originally by M3G, ported to Spring by NOiZE.

This is the TA:Spring version of the masterpiece race created by the TA creation veterans M3G and Nik. Striving for perfection, they have completed an astoundishing number of 150 new units. This is by far the most expanded and carefully balanced race that has been created to this point. Explore the strategic values of the new submarine pens, defensive constructions and the many supersized monsters that let you toy with the opponent.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2860 Forum Thread]
[http://www.fileuniverse.com/?p=showitem&ID=1967 Download]

===2005-12-05 NTAI 0.28.10+ installer FIXED)===
Counter attacking, and numrous fixes, modifications. All who've downlaoded it redownload as I made a terrible mistake copying the wrong files over. - Alantai

[http://www.fileuniverse.com/?p=showitem&ID=1950 Download Installer]
[http://img479.imageshack.us/img479/8186/screen0121oq.jpg Screenshot]

===2005-12-01 NTAI 0.28Beta 7 Released===
Working Attack code, vastly improved building, Xect, Rhyoss, Mynn, TLL, XTA and AA support. - Alantai

[http://www.fileuniverse.com/?p=showitem&ID=1909 Download]
[http://img479.imageshack.us/img479/8186/screen0121oq.jpg Screenshot]

===2005-12-01 OTAI for 0.67 Released===
Veylons latest installment of OTAI, with a slew of improovements.
[http://www.geocities.com/veylon_ii/TASpring/OTAI_v102.zip Downlaod]

===2005-11-11 Cursor groupAI Released===
Show Allies what untis you have selected and where your mouse cursor is.

[http://www.fileuniverse.com/?p=showitem&ID=1873 Link]
[http://img479.imageshack.us/img479/8186/screen0121oq.jpg Screenshot]

(This is a new version from beta 6.5 released yesterday)

===2005-11-12 NTAI 028BETA 7.1 Released===
Full ARM + TLL support, and improved attacking.

[http://www.fileuniverse.com/?p=showitem&ID=1887 Linky]
[http://www.fileuniverse.com/?p=showimage&ID=1755 Screenshot]

(This is a new version from beta 6.5 released yesterday)

===2005-11-12 - NTAI 0.27 Released===
Water map support, krogoths, vehicles, aircraft, and more!
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2829 Details]
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2827 Screenshots]

===2005-10-29 - NTAI 0.25 Released===
The latest version of NTAI released today with many new abilities, such as a greatly improved attack system, and the ability to scout.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2687 Forum Thread]

===2005-10-20 - Absolute Annihilation: Spring Released===
The highly popular OTA mod, Absolute Annihilation, has now been fully converted for compatibility with Spring. Unlike the original Spring version released some months ago, the new version is fully compatible with the mod switching system. It also features many visual and strategic enhancements only possible in Spring, and uses the latest version of the AA dataset, 6.0.

Already a new version is available, 1.25, which corrects several major bugs.

[http://files.filefront.com/AASpring125zip/;4417183;;/fileinfo.html Direct Download (1.25)]

[http://prdownloads.sourceforge.net/ta-aa/AATrailer.zip?download Mod Trailer]

[http://www.planetannihilation.com/aa AA Homepage]

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2633 Forum Thread]

===2005-10-16 - KuroTA v0.45 Released===
This is the second public release of this fairly popular mod. It all started out as a bunch of custom units in a TA installation from years gone by, but thanks to dedication it's been turned into a playable and fairly balanced mod for everyone to play on Spring. For more info at [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2514 read this thread]. And it can be downloaded from [http://www.fileuniverse.com/?p=showitem&ID=1646 FileUniverse].

===2005-10-15 - UberHack, SpringVersion1.3 Released===
This port of the famous balance mod for TA, done by NOiZE, has been made as good as bug free now. This mod would not have been possible without help from: zwzsg, Gnome and Kuroneko. For more info at [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2540 read this thread]. And it can be downloaded from [http://www.fileuniverse.com/?p=showitem&ID=1633 FileUniverse].

===2005-10-12 - Maelstroms SMD Creator===
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2420 Maelstroms SMD Creator] has been relesed, to help people create SMD Map files with an easy to use GUI.

===2005-10-11 - JCAI 0.20 Released===
[http://spring.clan-sy.com/phpbb/viewtopic.php?p=33275#33275 JCAI 0.20 skirmish AI] is released for Spring 0.64b1 with a modified spring exe, it is much more stable now. JCAI 0.20 is included in current release (0.65b1)

===2005-09-28 - UberHack, SpringVersion1.2 Released===
This port of the famous balance mod for TA, done by NOiZE, has been made as good as bug free now. This mod would not have been possible without help from: zwzsg, Gnome and Kuroneko. For more info at [http://spring.clan-sy.com/phpbb/viewtopic.php?t=2364 read this thread]. And it can be downloaded from [http://www.fileuniverse.com/?p=showitem&ID=1552 FileUniverse].

===2005-08-20 - wiki Button Added===
As you probably already have noticed, the SY's have added a wiki button (Made by aGorm) to the Navigation bar. Hopefully, this will make people more aware of the wiki, as some have never even heard of it! More info on [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=1917 this thread]. If you don't see the wiki button, empty the cache of your browser and refresh.

===2005-08-16 - JCAI Released===
Zaphod has released alpha 1 of his skirmish AI JCAI for spring,[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=1920 see forum post]
TAI code has been released but doesnt work. [http://www.fileuniverse.com/?p=showitem&ID=1322 Get it here]

===2005-08-03 - Mods and Maps===
zwzsg made a 3.6MB mod package with: OTA balance, Evolva models, UTASP Buildpics. Install and use easy thanks to the new mod switcher introduced in Spring 0.60b1.
 - [http://spring.clan-sy.com/phpbb/viewtopic.php?t=1843 More info and discussion]
 - [http://www.fileuniverse.com/?p=showitem&ID=1257 Download link]

[http://zwzsg.hosted.luckz.de/img/spring/Azure%20Rampart%20-%20evnbp%20-%20Bomber.png http://www.fileuniverse.com/images/Azure%20Rampart%20-%20evnbp%20-%20Bomber.jpg-thumb.png][http://www.fileuniverse.com/images/causticscreenshot.jpg http://www.fileuniverse.com/images/causticscreenshot.jpg-thumb.png]

Spring 0.60b1 made all previous maps obsolete, but as the pictures above show, there's a steadily increasing [http://www.fileuniverse.com/?p=listing&ID=121 choice of new maps], either old ones converted to the new format or brand new.

How to be good at 1v1

2006-09-28T15:04:08Z

NOiZE:

== Intro==
I thought i'd try and throw down in text all the thoughts in my head and how I think when playing high level games. But i'm afraid after writing this it comes out as tiny patches only scratching the surface of various areas.

Please dont take this as a comprehensive guide, as Meta-gaming is something you have to really learn yourself, as I echo a few times through this

== Opening Quote ==

''Post by Swiftspear pretty much summing up how you move from being a good player to an elite player''
<blockquote>
I'll put up any boxer who has gone through a proper training routine against any boxer who just fights with people constantly. The boxer with the training routine will always win. If you want to be the best you have to train, not just crunch hourage. You will take WAY longer to intellectualize the game if you just play and don't study it. The best player is the best player because their reflexes are honed, they know exactly what happens in every situation, and they know what their opponent knows so they can counter him. Ability to play a game at the high level breaks down into 3 areas: Mastery of the interface, mastery of the numbers, and mastery of the mind game. If your game plan for improving is "Play the game alot" you only really improve your mastery of the interface, and even then you will likely be worse at that then someone who has improved all three area's at once through proper training because you're relying on accidentally discovering the optimums rather then knowing the optimums because you have crunched the numbers and developed the theory.
</blockquote>
*<blockquote>
If you want to be the best at the game, you study replays, analyze in depth what was done right, what was done wrong, analyze where you are spending your time and what you are letting slip, then take the knowledge gained and replay and get new replays. Also test out units, see which units can shoot over DT and which can not, which units can crush which corpses and which can not, which units can get through which bottlenecks and how easily, if you know the game theoretically you don't have to make the mistakes the first time to learn from them. Finally study your opponents and learn what makes them tick. Know what an opponent is most likely to do just for statistical convenience, figure out a counter. Know your opponents strengths and weaknesses, know the counter to every counter and the counter to every counter counter in and out and know exactly what if you do you are weak to, and how you can minimalize the risk.
</blockquote>
<blockquote>
Ask any great chess player how they learned to play the game, weather it was more beneficial to them to talk with other players about the strategy of the game and read over the theory books, or weather it was more beneficial to them to just play the game over and over and over, they have all done both. While it's objective, you need to play to win, that doesn't mean you will win if all you ever to is play alot. Being the best is alot of boring work as well as the fun of playing.</blockquote>

The first step to being an elite player is you have to want to be a good player, I dont mean "I wouldnt mind being a elite player", you have to be willing to learn everything it takes.

Being a top player isnt something you can be instructed on, you become an elite player when you can train yourself. Luckily, you can be taught to train yourself.

== Reading Material ==

http://www.sirlin.net/Features/feature_PlayToWinPart1.htm
Playing to win, this is the bible of playing competetively, breaking the barriers in yourself described in the article you are already double the player you were before.

'''The Art of War'''
http://www.chinapage.com/sunzi-e.html

Though I highly reccomend the whole thing, the part most pertaining to playing TA is the chapter 'Tactical Dispositions'

'' 7. The general who is skilled in defense hides in the
most secret recesses of the earth; he who is skilled in
attack flashes forth from the topmost heights of heaven.
Thus on the one hand we have ability to protect ourselves;
on the other, a victory that is complete.''

==Getting started==

First you need to watch people better than you do what you want to do, watch their tactics, their build orders, their micro.

Analyze their moves, find why they are being used instead of other ones, think of ways they could be changed to be more powerful. Assess the impacts of every move on every level.
''How much metal is this tactic costing compared to how much damage it is doing?''
''How much concentration does this need?''
''How much micromanagement?''
''How much micromanagement and concentration does it leech from the enemy?''
''Does it make the opponent act irrationally?''

I cannot teach you all the questions because being an elite player means being able to teach yourself the questions.

Being able to watch how a tactic went wrong in a replay is a thousand times easier than to predict how a tactic will go wrong when you are playing in real time.

Now you have to do the tricky part, lose alot of games. The biggest way to stall in climbing the mountain of being a great player is to be afraid of losing. Dont forget this, because the higher you get the worse the fear can become.

Every game you lose, find out what beat you, then work back.
20 Instigators leveled my base and destroyed my commander
*How did they slip through
*How did my opponent stop this happening to him
*How did my opponent get the metal to do this
*How did my opponent know where to strike

== Know Thy Enemy ==
Keep a profile in your head of every player, check the 'Recent games' as often as you can on the ladder site, see the outcome of the tournaments. Watch every game of every player worth watching.

Know your opponents to the point you can be half way through a game and know exactly what they are doing. Until you know what every radar blip they are sending at you is gonna be.
Every player has a style, every player weighs risk versus reward differently

Skill as a player is not only knowing your opponents, but not allowing them to know you

== Summing up in nice dot points ==

*Dont use a tactic because it is what someone better than you does, use it because you know why they use it

*Tactics have to be used with the intent of winning the game. Dont tech unless the tactical options for winning on the current tech level are exauhsted

*Hold yourself responsible. No tactic is lame. It dosent matter if your teammates are noobs. The only way to improve yourself is to find what you did wrong.

*Keep your cool. Look at everything objectively. Dont let yourself change tactics from "Seeking to win" to "Prolonging Defeat".

''' [[Strategy_and_Tactics|<- Back to Strategy and Tactics page]]'''

Nanoblobs

2006-08-06T15:31:55Z

NOiZE:

== Project conceptual notes, by Argh ==

Here's a unit breakdown, based on current balance. This is all likely to change- NanoBlobs is in a bit of a transition period.

=Economy=

'''Lords''' are your commanders. They have a powerful weapon that kills things on the ground, are pretty tough, and can build things quickly, but they are very vulnerable to some units (Knights and Demons, especially). Lords can hover on the surface of water.

'''Sheep''' are your economy and your principal way to multiply your build-power. Sheep are very likely to either disappear entirely... or change in role, soon, but for now they are still in the same role they've always been- weak, defenseless, and totally necessary. Sheep can hover on the surface of water.

'''Autofacs''' build armies automatically (with "repeat on" and queues, of course). Nothing special about them... right now. This is also likely to change, but I'm not getting into that until I have the new things done.

=Defense=

'''Holders''' are stationary, not-so-powerful towers. They can kill Wolves and other light units easily, but fall to Knights. Massed, they can stop small rushes, and backed up with SpireRooks and MegaSheep, they can stand anything but a Demon, but not by themselves. Like everything in NanoBlobs, they have strengths and weaknesses.

'''SpireRooks''' are slow, powerful units that shoot infrequently, but their weapons can kill Knights in a hit or two, and they are more than cost-effective against SquareRooks and Demons. Their main weakness is that they are very slow and large targets, but they also are specifically weak against Striders. SpireRooks are completely amphibious, and can go underwater.

'''MegaSheep''' are defensive plasma artillery. While they can be used on offensive operations, they are slow, and they produce resources, so they are often better kept behind a line of Holders, where they do a great job of killing Striders, Knights, and TriRooks.

=Offense=

'''Wolves''' are cheap, disposable scouts. They can kill weak units or slow-firing things if they are left undefended, but are not powerful combat units. However, they are very cheap, build fast, and provide your enemies with one more target. Always have an Autofac or two building Wolves... their value as scouts and as "chaff" is very important, even if they have low combat power. Wolves can fly.

'''Archers''' kill Wolves, and move quickly enough to keep up with hordes. They are completely useless against all other units at this time. Mix them up in the queue at the Autofac with other units, like TriRooks and MegaSheep.

'''Knights''' are your hard-core rapid strike force. Armed with short-range flamethrowers and unbelievable healing powers, they are quite capable of taking apart a base in seconds if they aren't killed on the way in. While Knights are quite killable in this version, they are still very, very dangerous if used correctly.

'''Striders''' are both weak and powerful. They have been optimised for the current build of Spring's aiming code, but due to the low size of their weapon arc, they still require some micromanagement to really use effectively. Striders have rapid-fire burst chainguns that are quite capable of killing any unit in the game except for Wolves. They are fairly slow, but have a lot of hitpoints for a small unit, and take less damage from certain types of weapon. They are unbelievably deadly on flat terrain, but much less useful on rocky or broken places. Used correctly, Striders can smash open a defense very quickly. Used incorrectly, they are a waste of resoureces and unit-count.

'''TriRooks''' are the newest unit in NanoBlobs. They are very powerful attack units, but lack the armor to be all-out assault tanks. However, their weapon has good range, a rapid rate of fire... and due to its hovering nature, it can go over terrain that normal units can't see over... very, very handy. TriRooks require finesse to really use well, however, because they are a big economic drain. TriRooks are swimming units, and are effectively both ships and tanks.

'''SquareRooks''' are a general-purpose artillery unit. Lacking close-in defense, and vulnerable to Knights and Wolves, they are still worth using, because they have weapons that can kill Striders and other light unit types all day long. However, they fare poorly against Holders and SpireRooks.

'''Demons''' are the ultimate can-openers. They have a long-range popup missile that does decent damage to anything, but fires slowly. More importantly, however, they have an amazing DemonGun that can tear up massed units or defenses in a real hurry, and also has an effect over time, instead of being nearly instantaneous. Unlike other weapons it can keep killing units further back as they move through the deadly zone. Demons require protection from Knights, and aren't terribly fast, but they can also swim like TriRooks.

=Gameplay=

NanoBlobs is, basically, a new kind of game design. I started it out as a way to talk to the AI developers about making better AIs for Spring, but it's a lot more complicated than that at this point.

Basically, on anything but a small map, NanoBlobs is a completely strategic RTS. You're not going to want to micromanage your units, or worry about losing a few (thousand). Instead, you're going to block, scout, feint... and then attack, after finding the weak spots in your opponent's current streams of units.

NanoBlobs expects players to already know how to queue up multiple build orders, do things like the good ol' "bomber/guard" trick from OTA, and other Gnug skills. NanoBlobs is not terrifically noob-friendly, and requires that you actually pay attention to the massive battles... and plan well in advance. You can't win through just spamming one unit, and you can't win by playing defensively, and building up to Tech X, or slowly choking your enemy out of metal spots, or any of that boring crap. No. In NanoBlobs.. you win by killing the enemy... period. No tactic is "lame". Everything has a fairly obvious counter... plus a lot of subtleties. It's not "realistic", it's not an attempt to be anything but a pure battle experience.

Typical new players get stuck on three things:

1. They are like, "uh, where are the mines and tech levels". Uh... there aren't any. GET MOVING

2. They try to build defenses and hold until they have Demons. This is dumb, because then their opponant can steadily hopscotch new Autofacs nearer and nearer to them, and crush them with sheer firepower.

3. They think that .cheat .nocost is on, and spam in an unintelligent way. There ARE COSTS to most major units, and the gradual drain on your economy is a major part of gameplay, which future versions are going to emphasise more

The best thing to do, playing this game, is to decide where your first base will be... get it built before the enemy's first Wolves arrive, and then begin spamming out streams to scout and to hold as much of the map as possible. NanoBlobs is very much about map control- not so that you can get metal, but because that prevents the enemy from getting around your flanks.

After that, then what? Well, here are some classic options:

1. Rapid-build 50 Knights, then throw them at the weakest part of the enemy's lines. One Knight can destroy a base pretty easily. Really. Just give 'em a path, tell 'em to Roam, and then get on with something else... like sending all available Wolves ahead to distract their defenses

2. Spam out Wolves, MegaSheep, Knights and Archers in a mix, to keep the enemy engaged and pinned, then build up a force of SquareRooks and a couple of Demons. Use the Squares to punch a hole in the enemy streams, then use the Demons to kill their defenses. Just make sure to guard them against Knights.

3. Use your Lord to roam around, spiderwebbing Autofacs all over the map, anywhere the enemy doesn't contest you, and gradually spam them to death.

4. Use your Lord or a bunch of Sheep to build Holders to support your forces in a combat area, or to create a fall-back line that you can retreat to. Just because you can send thousands of robots to their death doesn't mean that the occasional retreat isn't a good idea.

5. Use the units that can swim to go around enemy land forces and crush them

... and lots and lots and lots of variants. NanoBlobs looks simple, but is not simple. Each unit has a lot of subtleties, from economic balance to what terrain it can handle to how fast it is. I've really tried to make sure that you never go, "hey, that's redundant", or "wow, that's useless" with the mod.

All of that said... this version's balance is still very rough, so please don't flame me when you find an obvious flaw (point it out though, I will keep it in mind). And I am contemplating some major changes for the future, to further reduce lag for low-end players... and when the new version of Spring is out, I will be making very heavy use of the new UnitIcons feature, so that you can direct your battles "from orbit".

{{Category:Mods}}
[[Category:Mods]]

Map development

2006-07-25T18:04:19Z

NOiZE:

=Map making SM3=

SM3 (Spring Mapformat 3) is getting allong nicely and maps using this format can be made. The following is documented so far.

*[[SM3_Map_Format|jcnossen's brief description on how this mapformat works.]]
*[[SM3_FAQ|The first FAQ for the new mapformat.]]

[[Image:sm3-minimap-thumb.jpg]]

=Map making, SM2=
Maps, are a complex mixture of heightmaps and textures.
Fortunately, 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]]

File:Sm3-minimap.jpg

2006-07-25T18:01:49Z

NOiZE: Showing Sm3

Showing Sm3

File:Sm3-minimap-thumb.jpg

2006-07-25T18:01:26Z

NOiZE: Showing the SM3

Showing the SM3

FAQ

2006-05-09T12:47:35Z

NOiZE: /* How do I create maps? */

==General information==

===What is Spring?===
Spring is a project to create the best RTS ever (no joke). There are three principle goals which we hope to achieve.

# Reach a stage where TA Spring can flawlessly execute most of Total Annihilation's original gameplay, with its original units in their original format.
# Add new features as we see fit, fix bugs, and release new versions when we feel it is appropriate to do so.
# Support the mod community as we see fit.
# Improving the already fine original TA Interface in a way that the Players will have more tatctical Options, more Control, more Comfort and still don`t get lost, as long as they are willing to learn.

The goals might need an update.. -- Tim Blokdijk

===Is Spring free?===
The core game is released under GPL License. However, some parts of the game are still under copyright by their owners. Therefore, today, you need to own the original TA game if you want to play. However the community is working hard in order to offer completely free alternatives.

===Why can I edit this page?===
This page, and several others, are located in the Spring [http://en.wikipedia.org/wiki/Wiki Wiki]. The link gives a full explanation of what it is, but in short it is a way of letting anyone who wants to contribute to the page content. This can of course be abused, but even while it is easy for someone to vandalise the page, it is just as easy for someone to restore it, since the wiki saves all previous versions of a page.

===Why can't I edit this page?===
You need to be [[Special:Userlogin|logged in]] to edit our wiki because people were vandalizing and/or being morons too much, so they had to lock it down.

===I want to help, what can I do?===
Please look at the Messageboard. There are lots of things you can do according to your skills. Particularly important is to create viable and pleasing free alternatives to copyrighted material, mainly sounds and units.

===I want to donate.===
People have made clear their desire to donate to the project, and so far, we have been fairly reluctant about accepting donations. Our main concern? While we certainly hope to have something on the level of a commercial release in the near future, there is no guarantee that it will ever happen. Unforeseen events arise, and it would be most unfortunate if everyone who donated felt swindled because the project did not turn out as they had hoped.

We do not plan to be more or less productive solely based upon the quantity and frequency of donations received. The Spring project is here only because we view this as an enjoyable hobby.

===I read all that and I still want to donate.===
Very well then! You can find the required details [http://taspring.clan-sy.com/donate.php here]. It will be much appreciated. :)

----

==Technical==

===What port numbers does Spring use?===
Game uses port 8452 UDP by default, which can be changed in the lobby. If you are behind a router, and are having problems hosting, try forwarding the correct port and also make sure the firewall is not blocking it.

===What APIs does Spring use?===
The Windows version of the program (Which is the Binary that can be downloaded from this site) uses: OpenGL for rendering, DirectSound for sound, and Winsock for networking.

The Linux port, see [[MultiplatformSpring]] with more info below, uses SDL/OpenGL for rendering, OpenAL for sound (which will connect to DirectSound on Windows and OSS or ALSA on Linux), BSD sockets for networking.

===What language is Spring written in?===
The spring game engine is written in C and C++. The Windows lobby client is written in Delphi, the lobby server is java. Another portable lobby is being made in Python.

===Is Spring open source?===
Yes, it is. Go to the [http://taspring.clan-sy.com/download.php downloads] section of the site to download the source code.

===Is there any documentation for the source code===
Yes, doxygen is used to automatically generate the [http://taspring.clan-sy.com/doxygen/ documentation]

==Requirements==

===What platforms will Spring run on?===
At the moment, it runs on Windows and Linux. However there is no working lobby for the Linux users at the moment, and Cross-Platform play does not work due to Sync errors.

===What sort of a system do I need to run Spring?===
You need a 3D graphics card to run Spring, which will probably require at least a a GeForce4 MX and the latest driver supported. Minimum CPU requirements are a little more complex. A more powerful CPU will have the capability to support larger maps and a greater maximum unit limit. A 1 GHz CPU should be able to support an estimated 500 units. The needed memory will also vary with unit count and map size, but 512 MB should be enough. However, 1024MB you should already have, so it'll run fine.

For further details and tested Systems check the [[Requirements]]-Page

===Spring says I need the GL_ARB_texture_env_combine extension, what can I do?===
If you encounter the error "Needed extension GL_ARB_texture_env_combine not found", this means that your video card driver does not support GL_ARB_texture_env_combine. You can try downloading a new video driver from the manufacturers website ([www.ati.com], [www.nvidia.com], ...). If they donÃ‚Â´t work, your last chance is to try "modded" drivers if you can find any. If this doesn't solve the problem either, then your video hardware is too old to support the extension. Buy a new video card.

EDIT: I am also having this problem with the geoforce 6800 ultra and I have the latest drivers.

REQUEST : please name some working and non-working 3D video cards. please give a value for minimum video memory : 32 Mo ? 64 Mo ?

ANSWER : its not REALLY a matter of video memory..though 32mb and 64mb are pretty small...i got myself a 128mb and its fine. But its more a question of the gfx cards clock speed. Even if the card had insane memory , lets say for example, 4000gb. If it isnt fast enough to utilise the memory, its fairly pointless. But i geuss, there must be a direct coralation between the memory and clock speed, otherwise the manufacturers need to rethink what theyre doing =D

List of video cards supposingly supporting GL_ARB_texture_env_combine :

http://www.delphi3d.net/hardware/extsupport.php?extension=GL_ARB_texture_env_combine

----

Spring works in full screen,but cncounters the error "Needed extension GL_ARB_texture_env_combine not found" when i try to run spring.exe in window

==Content==

===Do Spring maps need a "ground"?===
Spring maps do require a ground. We have had many requests to have space maps, however, a "true" (ala Homeworld) space setting is not likely. It would have to wait until a much later stage. This does not mean that TA's style of "space" maps won't be possible, (see the Final Frontier TC for examples of this).

===You stated that Spring uses the TA unit format.===
Spring does use the Total Annihilation unit format. However, we do plan to make Spring compatible with a custom unit format of our own design.

===How powerful will Spring's custom format be?===
Total Annihilation's unit format was extremely limited. Most of these limitations will either be expanded or non-existent in Spring's custom unit format. One of the most exciting improvements is the introduction of an entirely new method of scripting, with nearly complete control over every aspect of a unit's actions and behaviors.

===Does Spring have a limited number of weapons?===
No. Unlike Total Annihilation, Spring's weapon IDs will be unlimited. Meaning it will be possible to add as many third-party units as you want. However, the current model format limits 16 weapons to each unit.

===Does Spring have a limited number of unique units?===
No. Unit IDs, like weapon IDs, will be unlimited.

===Will units have a maximum of 3 unique weapons?===
Total Annihilation had a limitation that permitted a maximum of 3 unique weapons per unit. Spring currently has a way to have 16 weapons per unit. (Replace Primary, Secondary, Tertiary by 1 2 3 ...16). More can be made possible by modifying the source if there's a sufficient demand by mod makers.

===I'm curious as to the per-unit polygon limit.===
The engine itself does not have a polygon count limit. The limit is that of the processing power of today's computers. Since Spring requires a 3D card, the maximum polygon count per unit will be several times higher than Total Annihilation's. That means for your average mod, 300 polygons for common units and 700 for the more expensive ones is quite reasonable. (But don't waste polies unnecessarily!)

===Will units be able to perform basic terraforming?===
Total Annihilation units probably won't have any terrain editable functionality. Future units may be endowed with such functionality, but it's more of a gameplay issue and has not been decided upon yet. However construction units can restore ground, and certain weapons (especially explosive ones) can be used to deform the ground.

===Will tunnel building be possible?===
Subterranean areas of any sort is impossible. However, it is possible to heavily deform the ground with explosives.. Which is great fun!

===Will the ground's water retention be editable?===
No. Water will always collect when a piece of land has a height below sea level.

===Does Spring have a limit on the number of races?===
Spring has no limit on the total number of sides/races.

===What are the sizes of the biggest and smallest units?===
Static units (buildings, defenses, etc.) have no size limitations in the engine. Technically, neither do mobile units, but units with a footprint larger than 4x4 "squares" (an arbitrary size standard created by Cavedog) might have problems pathfinding.

===What is going to be the maximum possible sea depth?===
For all practical purposes, it will be unlimited. The depth values are stored as "float variables", so it is doubtful that maps would ever be made which even come close to approaching the limit.

===Will Spring support campaigns?===
Basic Map scripting has been implemented, using a Lua scripting engine. From that, it would be possible to make a basic campain, but for ease of use a better way of selecting scripts and an improved Single player menu is needed.

===How big are the Spring files?===
Spring will be as small as however much content is included with it. The "essential" files are only be several megabytes large. Content (such as maps and units) will add considerable size to the Spring download. Currently, the file size is roughly 30 MB.

===How will Spring render sound effects?===
Sound is rendered 3D, meaning that the volume and direction (assuming a multi-speaker setup) vary with the location of the camera from the sound "emitter". What this translates into gameplay terms means that the closer you are to a unit making a sound or motion, the louder the sound will be. Additionally, the sound will be heard differently depending on which way the camera is facing relative to units making sound.

===Will Spring have ambient sound?===
There is no ambient sound, and we haven't planned on adding it thus far.

===Will there be an AI or a "skirmish" mode?===
We have created an interface for AI's, and several are currently under development. In the meantime, the spawn script included in the latest version exists as a text file in the Spring folder, and can be modified by any text editor such as MS Notepad, for your particular play style, or mod.

===Will a "possess" or a FPS option be present?===
Yes, it is possible to fully control a unit from the first person view. It is more of a gimmick, but it still allows for a nice diversion once in a while. Instructions on it's use are in the [[Using_Spring#FPS_.22Mode.22_.28C.29|Using Spring]] article.

----

==Getting into a game==

===People talk about 'Single Player'. How do I start a single player game?===
Simply start a game in the lobby, and enter a password, so that nobody can join. Then click ready, and start and away you go !

===When I try to make a single player game, it gives me an error.===
Your graphics card probably can't support Spring. If you read the requirements it did say GeForce 3 or better. Go to the settings file in your Spring directory and lower some of the options. Sometimes that works.

===Does Spring support AI Players?===
Yes, see [[AI]] You can also use the [[random_enemies]] script, which spawns units out of thin air and sends them to attack you.

===When I try to connect to the lobby it gives me an error.===
There could be 3 problems. Either you don't have an account, the server is down, or you have not configured your router/firewall correctly. If you don't have an account, make one. If the server is down, you'll just have to wait (this doesn't happen often, though). If you have a router/firewall read below. Have a look at this website's News page and/or the Messageboard, it is likely that you will get some information there in the eventuality that the server is down.

Also make sure that you don't have any spaces in your username.

===I have a router and I don't seem to be able to get a game===

If you are using a router you may have other problems. Explanations of [http://www.portforward.com/routers.htm how to forward ports] has instructions for every router.

===Where can I download more maps?===
As for most Spring downloads [http://www.fileuniverse.com/?page=listing&ID=90 FileUniverse] is the place to be! A collection of maps can be downloaded [http://www.fileuniverse.com/?page=listing&ID=91 here].

===I used the small installer where can I get the missing maps?===
Unfortunately the maps included in the regular installer aren't available on File Universe. However, since many of the scripts included in the game rely on map4, this can be downloaded [http://taspring.clan-sy.com/dl/map4.7z here].

===How do I install downloaded maps?===
Most maps are released as .sdz or .sd7 files. These can be put directly into the "maps" folder inside the Spring folder. If they are compressed into another type of archive you will have to unpack them first. Just unzip them into your spring maps folder. Some map files use newer (smaller) file formats such as .rar or .7z, to unzip these newer formats, you'll need to download 7-Zip [http://www.7-zip.org/ http://www.7-zip.org/] or Zip-genius [http://downloads.zipgenius.it/ http://downloads.zipgenius.it/]. They both handle almost all formats and are totally free. There is also now a map browser in the TASClient lobby software, click the more maps button in a battle screen to access it.

===Sometimes when I try to join games it gives me an error.===
The host is behind a firewall that has not opened the correct ports for Spring.

===When a multiplayer game starts I never make it past the loading screen.===
This indicates a problem with your video card. Once again the best way to deal with this situation is to make sure your video card has the latest driver updates and that all Spring video features are on the lowest settings.

===When a multiplayer game starts, I make it past the loading screen, but when I get into the game it says, "Waiting for Host", and does a 10 second countdown. It always reaches zero and boots me out, what gives?===
This is a firewall issue. There are three things you can do to fix this. First, make sure your windows firewall is either off, or is not blocking the TA: Spring application. Secondly, if you are behind a router, you can forward the ports that the host is using (especially if you are the host), and it usually fixes the problem. To do this you must go to your router configuration page. You can see what port 'you' are using (as the host), by hosting a multiplayer game in the Spring Lobby. You must make this your trigger port, and make sure that it is open for both TCP and UDP. Thirdly, if none of the aforementioned worked. The easiest thing to do (assuming you are behind a router) is to set the DMZ (Demilitarized Zone). This means your computer will be completely exposed to the internet, which will make you vulnerable to any unknown or unpatched exploits in windows. All you have to do is find the personal IP if the computer you are using and add it to your router's DMZ list. Please only try this last option if you can't get the others to work.
Good Luck

===I got into the game, but some people didn't.===
The host may have reached the number of players it has set.
Or the players may be experiencing firewall or video card difficulty. That is not your fault. Please ask them too leave if they are still there when you get into the 'game lobby'. Some people have problem connecting to "hole punching" hosts.

===I got into a game but my name is red, nobody can hear me speak, and eventually I get disconnected===
This is to do with how long it takes the game to start up (the "load time"). If it takes too long you will see this problem. The load time can be reduced by changing the game graphics settings to lower quality. In particular try setting texture quality to lowest.

----

==Playing==

===What is with this weird right-click mode? I'm 'bout to break my keyboard.===
Sorry, you'll just have to get used to it. As of now it can't be changed.

===Why is somebody else also controlling my units?===
In the 'game lobby' there are two sets of teams. There are the 'Teams' and the 'Ally Teams'. If you are on the same 'Team', then you both get the same commander, and can control the same units. If you are on 'Ally Teams', then you both get different commanders and can't control each others units.

===Then why would I want to be on the same 'Team' as somebody?===
Because it's fun to just drive around units and not have to worry about commanding. (Assuming that one of the people on the team is commanding.)

===How do I talk to my allies only?===
You must type 'a:' before you speak. Here's an example: a: Now I am talking to my allies only. 
And most important, you can split tasks, as base building, troops managment.

===Help! After I'm finished driving a unit, the camera is all insane! This is nuts! How do I fix it?===
Whoa now. Calm down. Just press ctrl + mouse button 3 to change camera modes. If your unit is destroyed in FPS mode, you will stay in FPS mode until you change camera modes. Also, the camera will stay in "free look" when FPS mode is disengaged, press middle-mouse or J to switch to normal scrolling.

===After I'm finished driving a unit, where what used to be my mouse pointer is now a crosshair. Why?===
-This is a special 'view mode' that allows you to move around the screen much faster. It's good for viewing the battle or getting screenshots. Simply press on your third mouse button or 'delete' to revert back to your mouse pointer.

===But I don't have a third mouse button!===
The key 'J' works in the same way as the 'middle mouse button' does. So where you would use ctrl + middle mouse button to change camera modes, ctrl + j does the same thing. Pressing J once will also switch you from 'crosshair mode' to 'pointer mode' and vice versa.

===IÃ‚Â´ve managed to get stuck in this weird camera mode and my perspective is all messed up. How do I switch to the overhead (OTA style) camera?===
Shift+Backspace (or Shift+J or Shift+MiddleMouseClick) switches between the fps style, total war style and OTA style cameras. Use it to get your camera back to normal in this situation.

===People are cheating! How do I stop it?!===
Well currently, you can't.

Only the host can "activate" the cheat codes. After that, any player can do almost all cheats.

The best thing to do is just not play with the cheaters anymore. But with new spring version cheats are disabled in multiplayer, so that paragraph is hopefully now irrelevant.

===Well how do you cheat?===

<table border="3" cellpadding="2" cellspacing="0">

<tr><th>Cheat Command</th><th>Effect</th></tr>

<tr>
<td>'''.cheat'''</td><td>'''enable cheats - Cheats don't work in multiplayer until the host types this'''</td>
</tr>

<tr>
<td>.nocost</td><td>instabuild (doesn't work on things already under construction, only on new ones)</td>
</tr>

<tr>
<td>.setmaxspeed 50</td><td>Changes the maximum speed multiplier (default is 3.0)</td>
</tr>

<tr>
<td>.setminspeed 0</td><td>Changes the minimum speed multiplier (default is 0.3)</td>
</tr>

<tr>
<td>.spectator</td><td>Allows you to see the entire map... but you lose control of your units</td>
</tr>

<tr>
<td>.team 0, .team 1, etc.</td><td>Change player</td>
</tr>

<tr>
<td>.give ARMCOM, .give 10 CORKROG, etc.</td><td>Place 1 or specified number of specified unit. Valid units are the internal names of units as specified in the unit definition.</td>
</tr>

</table>

===In Game Commands===
The following ''non-cheating'' commands are also available in game:

<table border="3" cellpadding="2" cellspacing="0">

<tr>
<th>Command</th><th>Effect</th>
</tr>

<tr>
<td>.info</td><td>Shows you what colour each player is and their ping delay in the bottom left corner of the screen</td>
</tr>

<tr>
<td>.clock</td><td>Shows you the elapsed game time in minutes and seconds in the bottom left corner of the screen</td>
</tr>

<tr>
<td>.take</td><td>Pulls all allied units, that are owned by players who have lost connection to the server, to your team.</td>
</tr>

</table>

===How do I ally or unally in game?===
I'm pretty sure you can't. Yet.

===How do I give somebody units or metal or energy?===
Press the 'H' key. Then select the amount of metal and/or energy to share. Then select the receiving player and press OK.

When sharing units, you must first select the units to share, then press 'H' key. Tick share units checkbox and choose a receiving player.

===How do I continually give somebody metal and/or energy after a certain point (i.e. Original TA commands +setshare..., +shareall)?===
You'll notice that on your metal and energy bars (top of screen), there are two red bars. You have to put them wherever you want your metal and energy to be shared after.

===This game is different than TA, the units HP and damage are not the same===

There were several third party "balance" mods for the original TA game.

One of those mods were xTA, and was developed by the same clan (SY) that has brought life back to TA, making Spring.

This balance mod is what is bundled by default with the spring engine, and is the mod that was ready to play when spring was released.

Now are several mods available, install the mod of your choice.

[http://www.fileuniverse.com/?p=listing&ID=92 get mods here]

===XTA? OTA? AA? OMFGLAMO? What those all the abbreviations mean?===
zwzsg maintains a handy dandy FAQ about TA, and the abbreviations that relate to Spring too, of course.
[http://www.tauniverse.com/forum/showthread.php?t=27309 click here]. See also the Spring [[Glossary]], which contains brief explanations for all non-standard words and phrases.

===Why am I destroyed so easily by long range assaults?===
This is a realistic feature of Spring. Units will automatically attack 'radar blips' (units that they can not actually see, but that are indicated on radar). However, the accuracy is very bad while shooting at radar blips until:
* Your unit kills a lot of units and gets experience
* You get a targeting facility.

===Can I kick people from my 'game lobby' or my game?===
First of all, you have to be the host to kick. Use the good old ".kick playernamehere" command. Works in-game too, use it wisely.

===When I'm 'driving' my commander, why can't I use my laser?===
The TA: Spring team will most likely add a way for you to use your commander's laser soon.

===I hate driving around with the 'arrow keys'. Is there any way I can use the 'W-A-S-D' controls (the controls most First Person Shooters use) anymore?===
Go into your Spring directory and edit the uikeys file. Keep in mind that 'S' is originally a 'hot-key' that will stop your units and that 'D' is a 'hot-key' for your commander's D-Gun. You might want to change those too.

===I turned the shadows feature on; I still don't see shadows. What gives?===
Your graphics card can't handle shadows, so Spring automatically turns them off.

===I can't go backwards when I am 'driving' a unit. Why not?===
Because TA units were never intended to go backwards. Sorry, but you just cant.

===I'm in an Unreal Tournament kind of mood. How do I strafe?===
You can only strafe in 'brawler type' ships, such as the brawler, rapier, and light gunships.

===How can I record and watch demos/replays?===
From version 0.62 onwards recordings of all the games you play are easily available for replay via the Replays button in the TASclient.

You can use the Speed up/Slow down game keys while watching the replay, along with other in-game commands like .team

From version 0.60b1 onwards, demos are automatically recorded in the "demos" folder, underneath your Spring folder (default is C:\Program Files\TASpring\demos), named for the date and map they were played on. If you play multiple games in the same day on the same map, the games will also be numbered to prevent them from overwriting each other.

From version 0.62 onwards, to view a demo from the Windows file manager you can just double click the file name.

===Sometimes when I play get "not sync" "delayed synch" errors===

Thats caused because of lag. One of the players in the game is having some lag issues. Ask him/her to free up its bandwidth for the game to use.

Alternatively you can use the pause key and wait till the connection gets more stable.

Lag is the seccond number showed when you use the .info command ingame, numbers bigger than 40 are not usual in a normal game and are a signal of lag.

==Creating Content for Spring==
===How do I create maps?===
See the [[Map development]] page for all the map info.

===How do I create units/mods?===
See the [[Unit Development]] or the [[Mod Development]] page on creating units.

==Troubleshooting==

[[Category:Content]]

Spring Maps

2006-05-08T17:41:22Z

NOiZE:

== Maps ==
With version 0.6 Spring has a new map format.

=== Download maps ===
You can find a lot of new maps at [http://www.fileuniverse.com/?page=listing&ID=121 FileUniverse].

=== Map Information ===
*[[ Top 5 Maps]]: For information about the top 5 most played maps.
*[[Map reviews]]: Map reveiws galore
*[[Suggested maps for 1v1]]

Note: A lot of maps get released so this may not be up to date.

[[Category:Content]]

Map development

2006-05-08T17:29:35Z

NOiZE: /* Map making */

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

*[http://taspring.clan-sy.com/wiki/Create_maps| aGorm's map creating Guide]
*[http://taspring.clan-sy.com/wiki/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] 
*[http://taspring.clan-sy.com/wiki/Maps:Tutorial| Another tutorial from a designing point of view]
*[http://taspring.clan-sy.com/wiki/A_Complete_Map_Making_Tutorial| A Complete Map Making Tutorial (under construction)]
*[http://taspring.clan-sy.com/wiki/Runecrafter| Runecrafter's Map Tutorial]

== Specific Guides ==

*[http://taspring.clan-sy.com/wiki/Maps:SMD| Everything about .SMD]
*[http://taspring.clan-sy.com/wiki/Maps:Compiling| Everything about Compiling your map]
*[http://taspring.clan-sy.com/wiki/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...)

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

Map development

2006-05-08T17:24:57Z

NOiZE: /* Specific Guides */

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

*[http://taspring.clan-sy.com/wiki/Create_maps| aGorm's map creating Guide]
*[http://taspring.clan-sy.com/wiki/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] 
*[http://taspring.clan-sy.com/wiki/Maps:Tutorial| Another tutorial from a designing point of view]
*[http://taspring.clan-sy.com/wiki/A_Complete_Map_Making_Tutorial| A Complete Map Making Tutorial (under construction)]
*[http://taspring.clan-sy.com/wiki/Runecrafter| Runecrafter's Map Tutorial]

== Specific Guides ==

*[http://taspring.clan-sy.com/wiki/Maps:SMD| Everything about .SMD]
*[http://taspring.clan-sy.com/wiki/Maps:Compiling| Everything about Compiling your map]
*[http://taspring.clan-sy.com/wiki/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...)

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

Map development

2006-05-08T17:04:11Z

NOiZE: /* Full Guides For Map Making */

Map development

2006-05-08T17:03:42Z

NOiZE: /* Specific Guides */

Map development

2006-05-08T17:03:30Z

NOiZE: /* Specific Guides */

Map development

2006-05-08T17:03:07Z

NOiZE: /* Full Guides For Map Making */

Map development

2006-05-08T16:48:30Z

NOiZE: /* Map making */

Community news

2006-04-15T15:50:24Z

NOiZE:

On this page, you can post news items that will be seen in the top right section of the frontpage. You can use this to post if you have created or found something of interest to the Spring community, such as a new map, a useful tool or perhaps a new useful page in the wiki. Details on how to update this page can be found [[Community_news_editing | here]].

----
===2006-04-15 XTA Pimped Edition V5.5===
[http://tinyurl.com/p4mtc Read and Grab it here!]

===2006-04-10 AAI 0.60 released===
Experimental water support, linux support and a lot more... [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=4509 Look here]

===2006-04-05 FF v1.15===
New Version of Final Frontier [http://tinyurl.com/q3u3e Here]

===2006-03-30 OTAI v1.12===
With working command buffering [http://tinyurl.com/e8fuh Here]

===2006-03-27 XTA Pimped Edition V5===
[http://tinyurl.com/kr95f Grab it here].

===2006-03-26 NTai XE7.5 Skirmish AI===
[http://www.darkstars.co.uk/ Get it here]. - AF

===NanoBlobs 0.31(beta)===
Exponential game design. Updated. Smaller. Faster. Even cooler. Get it [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=4276 Here]

===2006-03-06 OTAI 1.10===
Now works in 0.70, fixed nanostall somewhat. Get it [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3412 Here]

===2006-02-25 AAI 0.55===
A rather small release mainly adding support for the modified ai interface [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3886 get it here].

===2006-02-25 NTAI XE6 for 0.70b1 Skirmish AI===
Universal mod support, statistical unit learning, freeform buildtrees [http://www.darkstars.co.uk/index.php Get them here]. - AF

===2006-02-19 AAI 0.52===
AAI 0.52 is only a small bugfix release [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3886 get it here].

===2006-02-13 Absolute Annihilation 1.44===
AA 1.44 completed and uploaded.[http://www.planetannihilation.com/aa AA Homepage].
.
[[SWTA]] [[Final_Frontier]] [[Absolute_Annihilation]]

===2006-2-19 AAI 0.52 Released===
AAI 0.52 is only a small bugfix release for AAI 0.5 - hopefully all crashes are gone now
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3886 click here].

===2006-2-15 NTAI XE 3 Released===
XE 3 has support map specific build data, 9 new keywords, StarWars/Gundam support, numerous fixes, and should run a lot faster ^^ [http://www.darkstars.co.uk/index.php here]. - AF

===2006-02-13 Absolute Annihilation 1.44 Released===
AA 1.44 completed and uploaded. Readme and changelog available at the [http://www.planetannihilation.com/aa AA Homepage].

===2006-2-06 OTAI 1.08 Released===
Now uses multithreading to reduce freezing!
[http://taspring.clan-sy.com/phpbb/viewtopic.php?p=55624#55624 Forum] [http://www.fileuniverse.com/?p=showitem&ID=2354 Download]

===2006-02-01 World Domination 5B62 Released===
This version fixes the crashes related to missing .cob-files.
Download [http://www.fileuniverse.com/?p=showitem&ID=2311 here].

===2006-1-31 Star Wars Spring Manual Released===
[http://spring.clan-sy.com/wiki/SWTA_Manual Read the SWS Manual right now!] It contains everything you would ever want to know about SWS, including: Installation Guide, In-Depth Unit Guide as well as a Strategy & Tactics section.

===2006-1-27 OTAI 1.07 Released===
Veylon released OTAI version 1.07. Now builds Dragon's Teeth and crashes less!
Download [http://www.geocities.com/veylon_ii/TASpring/ here].

===2006-11-19 UpSpring Tutorial Released===
Maestro R Setiawan released [http://tinyurl.com/cd25b a very comprehensive tutorial] to UpSpring, the application to import new models to Spring. Now you won't have any excuse to not use UV mapped S3O!

===2006-01-16 NTAI 0.29a Released===
NTAI 0.29a released, go get it here [http://taspring.clan-sy.com/phpbb/viewtopic.php?p=50716#50716 Download]

===2006-01-16 Absolute Annihilation 1.42 Released===
AA 1.42 completed and uploaded. Readme and changelog available at the [http://www.planetannihilation.com/aa AA Homepage].

[http://prdownloads.sourceforge.net/ta-aa/AASpring142.zip?download Download] (9 mb)

===2006-01-12 AAI 0.4 Released===
AAI 0.4 now supports air units as well as construction units assisting others.
Edit: Small Bugfix Version AAI 0.42 released
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3527 AAI v0.42].

===2006-1-07 Gundam Annihilation 0.98.sd7 Released===
This is a .sd7 for your spring lobby usage. I have corrected a few of the spring specific bugs in this release. Enjoy. [http://www.planetannihilation.com/gundam/ Gundam annihilation homepage]

[http://www.planetannihilation.com/gundam/shots/screen039.jpg http://www.planetannihilation.com/gundam/shots/screen039_thumb.gif] [http://www.planetannihilation.com/gundam/shots/screen012.jpg http://www.planetannihilation.com/gundam/shots/screen012_thumb.gif]

===2005-12-15 AAI 0.3 Released===
AAI 0.3 includes a lot of bug fixes and placement of defence buildings. [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3195 AAI v0.3].

===2005-12-14 Absolute Annihilation 1.35 Released===
AA 1.35 completed and uploaded. Readme and changelog available at the [http://www.planetannihilation.com/aa AA Homepage].

[http://prdownloads.sourceforge.net/ta-aa/AASpring135.zip?download Download] (16 mb)

===2005-12-13 OTAI 1.03b Released===
A fixed version of OTAI 1.03 now available.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3184 Forum Thread]
[http://www.geocities.com/veylon_ii/TASpring/OTAI_v103b.zip Download]

===2005-12-13 The Lost Legacy v1.04 Released===
The Lost Legacy Race, originally by M3G, ported to Spring by NOiZE.

This is the TA:Spring version of the masterpiece race created by the TA creation veterans M3G and Nik. Striving for perfection, they have completed an astoundishing number of 150 new units. This is by far the most expanded and carefully balanced race that has been created to this point. Explore the strategic values of the new submarine pens, defensive constructions and the many supersized monsters that let you toy with the opponent.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2860 Forum Thread]
[http://www.fileuniverse.com/?p=showitem&ID=1967 Download]

===2005-12-07 Star Wars: Spring 1.0 Released===
The well known Star Wars TC for TA has been ported to Spring.

One of the most complete TCs that existed for TA has now been fully ported to Spring - all of the bugs that plagued the quick and dirty earlier port have been fixed. Some balancing issues that came up in Spring has also been taken care of, along with a few other minor modifications, to ensure that this modification is made specifically for the Spring engine, so that you can enjoy it as such. Furthermore, many of the uglier low-polygon units for SWTA have been remodelled for Spring, so that you can now enjoy high-poly infantry units, as well as a few other vehecular changes.

Feel free to come join us on our own chat channel (itself a good 5 years old), where you can organise games, discuss balance, and report bugs:

Server: irc.gnug.org

Channel: #SWTA

An in-depth manual, with help regarding strategies and unit descriptions can be located [http://www.planetannihilation.com/swta/readme.asp here], however, bear in mind that while much of this will be very helpful, it was originally intended for the Original Total Annihilation release, and so is not 100% accurate or reliable with regards to the Spring release. A Spring-specific manual is in the works.

SWS features around 130 units ranging from all six movies and the expanded universe for the Galactic Empire and Rebel Alliance. Join this galaxy spanning war today, download SWS!

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=3166 Forum Thread]
[http://www.fileuniverse.com/?p=showitem&ID=1988 Download]
[http://www.planetannihilation.com/swta/ SWTA Homepage]

===2005-12-07 The Lost Legacy v1.03 Released===
The Lost Legacy Race, originally by M3G, ported to Spring by NOiZE.

This is the TA:Spring version of the masterpiece race created by the TA creation veterans M3G and Nik. Striving for perfection, they have completed an astoundishing number of 150 new units. This is by far the most expanded and carefully balanced race that has been created to this point. Explore the strategic values of the new submarine pens, defensive constructions and the many supersized monsters that let you toy with the opponent.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2860 Forum Thread]
[http://www.fileuniverse.com/?p=showitem&ID=1967 Download]

===2005-12-05 NTAI 0.28.10+ installer FIXED)===
Counter attacking, and numrous fixes, modifications. All who've downlaoded it redownload as I made a terrible mistake copying the wrong files over. - Alantai

[http://www.fileuniverse.com/?p=showitem&ID=1950 Download Installer]
[http://img479.imageshack.us/img479/8186/screen0121oq.jpg Screenshot]

===2005-12-01 NTAI 0.28Beta 7 Released===
Working Attack code, vastly improved building, Xect, Rhyoss, Mynn, TLL, XTA and AA support. - Alantai

[http://www.fileuniverse.com/?p=showitem&ID=1909 Download]
[http://img479.imageshack.us/img479/8186/screen0121oq.jpg Screenshot]

===2005-12-01 OTAI for 0.67 Released===
Veylons latest installment of OTAI, with a slew of improovements.
[http://www.geocities.com/veylon_ii/TASpring/OTAI_v102.zip Downlaod]

===2005-11-11 Cursor groupAI Released===
Show Allies what untis you have selected and where your mouse cursor is.

[http://www.fileuniverse.com/?p=showitem&ID=1873 Link]
[http://img479.imageshack.us/img479/8186/screen0121oq.jpg Screenshot]

(This is a new version from beta 6.5 released yesterday)

===2005-11-12 NTAI 028BETA 7.1 Released===
Full ARM + TLL support, and improved attacking.

[http://www.fileuniverse.com/?p=showitem&ID=1887 Linky]
[http://www.fileuniverse.com/?p=showimage&ID=1755 Screenshot]

(This is a new version from beta 6.5 released yesterday)

===2005-11-12 - NTAI 0.27 Released===
Water map support, krogoths, vehicles, aircraft, and more!
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2829 Details]
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2827 Screenshots]

===2005-10-29 - NTAI 0.25 Released===
The latest version of NTAI released today with many new abilities, such as a greatly improved attack system, and the ability to scout.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2687 Forum Thread]

===2005-10-20 - Absolute Annihilation: Spring Released===
The highly popular OTA mod, Absolute Annihilation, has now been fully converted for compatibility with Spring. Unlike the original Spring version released some months ago, the new version is fully compatible with the mod switching system. It also features many visual and strategic enhancements only possible in Spring, and uses the latest version of the AA dataset, 6.0.

Already a new version is available, 1.25, which corrects several major bugs.

[http://files.filefront.com/AASpring125zip/;4417183;;/fileinfo.html Direct Download (1.25)]

[http://prdownloads.sourceforge.net/ta-aa/AATrailer.zip?download Mod Trailer]

[http://www.planetannihilation.com/aa AA Homepage]

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2633 Forum Thread]

===2005-10-16 - KuroTA v0.45 Released===
This is the second public release of this fairly popular mod. It all started out as a bunch of custom units in a TA installation from years gone by, but thanks to dedication it's been turned into a playable and fairly balanced mod for everyone to play on Spring. For more info at [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2514 read this thread]. And it can be downloaded from [http://www.fileuniverse.com/?p=showitem&ID=1646 FileUniverse].

===2005-10-15 - UberHack, SpringVersion1.3 Released===
This port of the famous balance mod for TA, done by NOiZE, has been made as good as bug free now. This mod would not have been possible without help from: zwzsg, Gnome and Kuroneko. For more info at [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2540 read this thread]. And it can be downloaded from [http://www.fileuniverse.com/?p=showitem&ID=1633 FileUniverse].

===2005-10-12 - Maelstroms SMD Creator===
[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2420 Maelstroms SMD Creator] has been relesed, to help people create SMD Map files with an easy to use GUI.

===2005-10-11 - JCAI 0.20 Released===
[http://spring.clan-sy.com/phpbb/viewtopic.php?p=33275#33275 JCAI 0.20 skirmish AI] is released for Spring 0.64b1 with a modified spring exe, it is much more stable now. JCAI 0.20 is included in current release (0.65b1)

===2005-09-28 - UberHack, SpringVersion1.2 Released===
This port of the famous balance mod for TA, done by NOiZE, has been made as good as bug free now. This mod would not have been possible without help from: zwzsg, Gnome and Kuroneko. For more info at [http://spring.clan-sy.com/phpbb/viewtopic.php?t=2364 read this thread]. And it can be downloaded from [http://www.fileuniverse.com/?p=showitem&ID=1552 FileUniverse].

===2005-08-20 - wiki Button Added===
As you probably already have noticed, the SY's have added a wiki button (Made by aGorm) to the Navigation bar. Hopefully, this will make people more aware of the wiki, as some have never even heard of it! More info on [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=1917 this thread]. If you don't see the wiki button, empty the cache of your browser and refresh.

===2005-08-16 - JCAI Released===
Zaphod has released alpha 1 of his skirmish AI JCAI for spring,[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=1920 see forum post]
TAI code has been released but doesnt work. [http://www.fileuniverse.com/?p=showitem&ID=1322 Get it here]

===2005-08-03 - Mods and Maps===
zwzsg made a 3.6MB mod package with: OTA balance, Evolva models, UTASP Buildpics. Install and use easy thanks to the new mod switcher introduced in Spring 0.60b1.
 - [http://spring.clan-sy.com/phpbb/viewtopic.php?t=1843 More info and discussion]
 - [http://www.fileuniverse.com/?p=showitem&ID=1257 Download link]

[http://zwzsg.hosted.luckz.de/img/spring/Azure%20Rampart%20-%20evnbp%20-%20Bomber.png http://www.fileuniverse.com/images/Azure%20Rampart%20-%20evnbp%20-%20Bomber.jpg-thumb.png][http://www.fileuniverse.com/images/Ahspen%20-%20evnbp%20-%20Tanks%20Tracks.jpg http://www.fileuniverse.com/images/Ahspen%20-%20evnbp%20-%20Tanks%20Tracks.jpg-thumb.png][http://www.fileuniverse.com/images/RedHaven%20-%20evnbp%20-%20Core.jpg http://www.fileuniverse.com/images/RedHaven%20-%20evnbp%20-%20Core.jpg-thumb.png][http://www.fileuniverse.com/images/causticscreenshot.jpg http://www.fileuniverse.com/images/causticscreenshot.jpg-thumb.png]

Spring 0.60b1 made all previous maps obsolete, but as the pictures above show, there's a steadily increasing [http://www.fileuniverse.com/?p=listing&ID=121 choice of new maps], either old ones converted to the new format or brand new.

Tutorial:CreateMaps(Fnordia et al)

2006-02-20T12:39:14Z

NOiZE: /* Mothers MapConv */

'''Original by aGorm, with help from LathanStanley'''



==The Idea==
First of all you need an idea. There is no point (OK, there is some point for test purposes) in making a map just like another one that already exists. You need to think of certain things before you make your map.
# Is this map idea different, not just a copy of someone else's?
# Does my map idea give each player a fair share of the cover and high ground?
# Is my map idea possible to make?
# Is it possible with the amount of time I'm willing to spend?

If you answered yes to the above, then you are 25% of the way towards making your map!

You should probably doodle it on a piece of paper to act as a guide later.

==The Tools==
With your idea hopefully sketched out, it's time to get the tools to make the map! (You can skip this if you already have them.)

For all your map compiling needs you should first download the [http://fileuniverse.com/?p=showitem&ID=1234 newest MapConv program].

You will also need some image editing software. Favorites are Photoshop, the [http://www.gimp.org/ GIMP], And Paintshop Pro.
The GIMP, however, is the only one that's free!
(I'm going to have to assume you know how to use the program you choose. If you can't there are loads of tutorials on the net.)

You may also want to check out [http://www.planetside.co.uk/terragen/ Terragen] for generating terrain. But as you have to pay to render anything of a good size, I won't mention it other than here.

Another tool you might find useful is the freeware tool [http://www.delphigl.de/projects/terrtexgen/eng_index.html TerrTexGen]. It's useful for previewing your heightmap before compiling, but unless your texturemap is 4096 on both sides, you might find that the texturemaps that it creates are too small.

Finally, there is tool called [http://www.bundysoft.com/L3DT/ L3DT] which you might also find useful. It seems to be a program that is specificly designed for creating large height/texture maps. The free version is capable of rendering a heightmap as big as 4096x4096, and can generate a texturemap that is proportional to the heightmap. Of the mentioned packages, this seems the most useful and complete.

==Preparing your map==
This is the fun part! And also, often, the longest part.

For a map you will need several different things:
# a texture map
# a height map
# a metal map

And several optional things for added functionality:
# a tile map

They all have certain needs! Read this bit carfully!

===Texture Map===
All maps are based on a texture image. This image's width and height must be an exact multiple of 1024 pixels. So, for instance, you can have a "4096 by 8192" image, but not a "4096 by 4608" image, as 4608 does not divide by 1024. It, like all three maps, must be saved as a 24 bit BMP. A 1024x1024 Texture will produce a map shown as '2x2' in the launcher.

It may look like whatever you want! Find a texture (preferably, one that you can tile seamlessly) and fill your texture map with it. You could, for instance, fill the whole image with a sand texture. This would make your whole world look like sand. You could then decide to add a few patches of grass to it by finding a suitable grass texture and adding it on in patches. So you'd have a map that was mostly sand with a few patches of green.

Because of the way the map compiler work, it will '''greatly''' reduce your map filesize if you use 32x32 tiles on your texture map. So, whenever you have to fill a large area with a repeating pattern, make sure the small square you're repeating is 32x32 (or a multiple of it).

Hey, wtf, Tile Map and Texture Map are about the same stuff, someone merge those section!!

===Height Map===
Next is the height map. This must be exactly one eighth (1/8) of the size of the texture map '''+ 1 pixel!''' For instance, if the dimensions of your texture map are "4096 by 8192", divide 4096 and 8192 each by 8 and add one to the result of each. The result for this example would be "513 by 1025". The height map is a black and white BMP. Only use black and white, no colour! (well its better to work it as a greyscale image, and when saving to process, convert to rgb and save as bmp, that way you get a 24 bit bmp)

White areas are the tops of mountains; black areas are the sea floor or the bottom of valleys. The shades of grey between are the different heights between! When you draw your heightmap, make sure the white blends into the black with greys. I suggest you use the blur tool. If you have a white splodge in a patch of black you will have a very tall pillar that won't look natural at all!

===Metal Map===
Finally, you need a metal map. This is the same size as the height map, one eighth (1/8) of the size of the texture map '''+ 1 pixel.''' On this one you paint down red (in verying degrees) to represent metal. So a red spot that is RGB(50,0,0) will provide about a 5th of the metal patch of red RGB(255,0,0) will give.

On this map you can also place green pixels. Each green pixel will create 1 geothermal vent. If you put down a green splodge you will get a cluster of geo vents! Only place 1 pixel.

Ensure you have all three saved as 24 bit BMPs and you're ready to convert it all to a map!

===Tile Map===
Tiles are basically repeating images. They are exactly the same. The map compiler, by comparing peices to the texture to each other, sees which little square tiles in your texture are exactly alike. If they are the same, instead of wasting precious harddrive and bandwidth space, the compiler sets a reference from on tile to the next. If your map is made out of only one small tile, repeating for the whole texture, the map will compress extreemly well. Down to only a few kilobytes. But this would look very boring. So most map makers use a variety of tiles to make their map more interesting. A good map maker will find a balance between looks and size.

To make a tile:
Open up your image editing program.
Create a new image.
As the Spring engine uses a 32 pixel tile engine, you have to set your image size to 32 pixels, or a multiple of 32 pixels. Therefore, tile sizes should be one of the following:
32x32 pixels,
64x64 pixels,
96x96 pixels,
128x128 pixels
etc.
Tiles also do not have to be square, it is perfectly possible to make rectangular tiles. Tiles should also be seamless, so that when repeated do not seem to have an obvious edge.

Once you have created your tile, do a Fill operation with a texture. The texture of course is our tile that we have made in the previous step. If you do not know how to do this, ask around. Make sure to state which image editing software you use, so we can help you easier.

Now, once you have your basic tile down, add in different features on your map, such as mountains, rivers, seas, deserts, grasslands, or whatever your map has. Remeber, for smaler file sizes make these different features out of tiles as well. If you do all of this properly, you can get your file size down very small, and this will keep everyone happy.

== MapConv.exe ==

Instructions pulled from [http://fileuniverse.com/?p=showitem&ID=1234 the newest MapConv program]. If all goes well, the <code>MapConv.exe</code> should create four new files: <code>mini.bmp</code>, <code>mini.dds</code>, <code>yourmapname.smf</code>, and <code>yourmapname.smt</code>

<pre>
USAGE:

mapconv [-l] [-i] [-c <compression>] -x <max height> -n <min height> [-o
<Output file>] [-e <tile file>] [-y <Typemap file>] -m <Metalmap file> -a
<Heightmap file> -t <Texture file> [--] [-v] [-h]

Where:

-l, --lowpass
Lowpass filters the heightmap

-i, --invert
Inverts the height map vertically (not the height values but the height map
(uhm someone rewrite this))

-c <compression>, --compress <compression>
(value required) How much we should try to compress the texture file.
Default value 0.8 . (lower=higher quality, larger file)

-x <max height>, --maxheight <max height>
(required) (value required) What altitude in spring the max(0xffff) level
of the height map should represent

-n <min height>, --minheight <min height>
(required) (value required) What altitude in spring the min(0) level of
the height map should represent

-o <Output file>, --outfile <Output file>
(value required) The name of the created map

-e <tile file>, --externaltilefile <tile file>
(value required) External tile file that will be used for finding tiles,
tiles not found in this will be added in a new tile file

-y <Typemap file>, --typemap <Typemap file>
(value required) Type map to use, uses the red channel to decide type,
types are defined in the .smd, if this argument is skipped the map will be
all type 0

-m <Metalmap file>, --metalmap <Metalmap file>
(required) (value required) Metal map to use, red channel is amount of
metal, green=255 is where to place geos (one pixel=one geo). Is resized to
fit the mapsize

-a <Heightmap file>, --heightmap <Heightmap file>
(required) (value required) Input heightmap to use for the map, this
should be in 16 bit raw format (.raw extension) or an image file. Must be
xsize*128+1 x ysize*128+1 in size.

-t <Texture file>, --intex <Texture file>
(required) (value required) Input bitmap to use for the map. Must be
xsize*1024 x ysize*1024 in size. (xsize,ysize integers determined from this
file)

--, --ignore_rest
Ignores the rest of the labeled arguments following this flag.

-v, --version
Displays version information and exits.

-h, --help
Displays usage information and exits.

Convers a series of bmp/raw files to a spring map. This just creates the .smf
file, you will also have to create a .smd file using a text editor
</pre>

==Mothers MapConv==
The usage is the same as above, with the following exceptions:
All features (including GeoVent/Tree/Grass) are now on their own FeatureMap. This is a 24bit bmp specified with the -f <featuremapname.bmp> flag.
''It should be 1/8th the resolution of your map.'' (i.e. 1 pixel smaller in each direction then your heightmap)

Tree's and GeoVents are placed on the green layer.
*255 Places a GeoVent
*200-215 Places tree types 1-16

MapConv will try to place these features in the exact spot you place them, it will then go into crackhead mode if it cannot.

Grass is the blue layer. The blue value maps to a 'pseudo-density' of the grass. The 'grass' map in the engine is very very low resolution, so be aware that you will not get nice linear results. 255=full grass, 0=no grass.

The red layer places 'Arbitrary Features,' aka wreckages. One pixel of red equals one feature. Red '255' gives you a feature of the first arbitrary type, 254 the second, 253 the third, and so on.

===But what are these 'Arbitrary Features,' Im so confused!===
They are 'features' found in the /features/All Worlds or /features/corpses filesystems. Which feature is 'type 1' is defined on a map-by-map basis via a new file called 'fs.txt'. This file should contain <cr> delimited feature names. The first line is the feature placed when a red=255 dot is found, etc.

=== Ok, Now what do I do? ===
If you are using any custom features, and/or you want to mod-proof your map, you should include them in the sd7 that you package the map in. The tree structure should look something like:

<pre>
<mapname.sd7>
-maps/
-mapname.smf
-mapname.smt
-mapname.smd
-Objects3d/
-<featurename[s]>.3do(specified in the tdf)
-features/
-All Worlds/
(and/or)
-Corpses/
-<featurename[s]>.tdf
-textures/
-tatex/
-<texname[s]>00.bmp or .tga
</pre>
Without getting into modding/unit making I will say that the <code>.tdf</code> tells you the name of the <code>.3do</code> ("<code>Object=</code>"), and the name of the 'feature' is in the top brackets. The <code>.3do</code> specifies the texture names. The engine looks for those texture names + 00 in either bmp or tga format in tatex.

Examples of a built-in XTA wreckage name would be <code>armckfus_dead</code> which would be looking for a tdf (likely <code>armckfus_dead.tdf</code>) that has a <code>[armckfus_dead]</code> section which then specified something like:
<pre>Object=armckfus_dead</pre>
<code>armckfus_dead.3do</code> would then specify some texture like <code>wreck01b</code> which would go looking for either a <code>wreck01b00.bmp<c/ode> or <code>wreck01b00.tga</code> file.

[http://fileuniverse.com/?p=showitem&ID=1421 Start with this version of MapConv]
or
[http://www.fileuniverse.com/?p=showitem&ID=1507 This one]
[I will clean this up and add more later --Mother]

==Making your map work==
This is the final push. Once Sharp map has finshed it will spit out a .sm2 file. This needs to be copyed to the MAPS folder in Spring. But you still need one more thing: an .smd file. Basically, this file tells the game things like the maximum metal, the light colours, the clouds, etc. (All the bits you were thinking that you hadn't done yet!)

I would suggest you copy the .smd of another map and fiddle with the settings until you get what you want. smd's can be opened in notepade or similar. Look at all the .smd's so you can get a jist of what each option does. Make sure both the .sm2 and .smd have the same file name then start up Spring (not the client!) in [http://taspring.clan-sy.com/wiki/FAQ#People_talk_about_.27Single_Player.27._How_do_I_start_a_single_player_game.3F single-player mode] and run the commanders script. Choose your map and away you go!

==SMD Rundown==
What follows is all that we (aGorm and LathanStanley) have figured out in the SMD's. Its by no means the be all and end all, but it's the next best thing.

* Goto [[Maps:SMD]] for a more detailed listing

===General Map Information===
* Description is just a short description of your map. Keep it simple.
* TidalStrength determines how much energy tidal generators will produce. A normal figure is around 20.
* Gravity, as you would expect, affects ballisitcs and how far units fly after an explosion.
* MaxMetal is the maximum amount of metal you will gain from one game square in 1 second from an area of metal that had a red value of 255 in your metal map. If making an old style metal deposit map, then this will be quite high: maybe 2 or 3. If you are making a new style metal-all-over-the-place-map, then it will be low: perhaps 0.2. Also for old style maps, you'll have to fiddle with the...
* ExtractorRadius, which is the area that is harvested by 1 metal extractor. For old style maps make this very small, so as they only take from one deposit.

=== Atmosphere, Water Colours ===
Each value (it would appear this bit is by no means gospel) is a representation of the [[RGB]] values for that parameter. It would appear to be relative, i.e. you can put in what ever numbers you like and the game will work out what you want.

The best way to go about it is to look at it as percentages.
The numbers 1, 0.5, 0.2 refer to 100% red, 50% green and 20% blue. But 2, 1, 0.4, will get the same result. Using numbers below one for all the numbers will result in the colour being less bright.

This is all a bit confusing so an example will be given:

<pre>SkyColor=0.2 0.1 0.5;</pre>

In this example the sky is coloured with 20% red, 10% green, and 50% blue, approximatly RGB(51,25,127), resulting in a very deep night-time blue. Other colours are added to the initial sky colour. If you set your sun as being a pale yellow and it came out rather green, this is why.

One helpful tip is ''negative'' colour. That's right: you can type in a negative number for a colour and it will remove it from the base sky colour. Just be careful not to go below the original values or you may get a surprise.

===The Sun System/Shadow System===
The Sun System/Shadow System is quite a useful tool as well in making your maps look ''well done''.
Within the <code>.smd</code> file there is a line:

: <code>SunDir=-1 1 -.5; //direction of sun</code> (The part after the "//" is a comment)

The numbers "-1", "1", ".5" determine the angle and elevation of the sunlight system.

The first number is the X angle (East/West) (from -1 to 1) where any negative number means the sun is on the West (and therefore shadows will be cast east), and any positive number means the sun is on the East (and therefore shadows will be cast west), and if the number is 0 there are no east or west shadows, the sun is directly above you.

The second is its elevation, (0 to 1), this number is how far from the horizion the sun is, ignoring it's angle. Thus, 1 puts the sun directly overhead (while still casting angular shadows) and 0 putting it directly on the horizion.

The final number is the Z angle (North/South). (I know, I know, they wrote the engine with Y as elevation and Z as vertical. Don't blame me.) It is just like the East West positioning, where negative numbers put them on the North, and positive numbers put them on the South.

'''Example Usage:''' If you want the shadows ''in'' one of the boxes (your shadow casting surface is in the middle), use the numbers provided, or start from them and tweak the angle and sun height as seen fit.

[[Image:ShadowDirection.gif]]

'''Note:''' on the current build, it ''will'' cast the shadows in the proper direction, etc. Negative direction numbers tend to make some maps unstable and cause crashes. The best solution would be to rotate or flip your map to where the shadows point up or right (North or West). I do believe these bugs are being worked on and will be fixed soon.

We can only hope this has been helpful! Any questions, or things you think we have missed, please ask us in the maps section.

==Other Articles==

[[Maps:Compiling]] is about properly compile and compress your map to a sd7 file.

[[Category:Maps]]
[[Category:Development]]

Tutorial:CreateMaps(Fnordia et al)

2006-02-09T13:52:26Z

NOiZE: /* Other Articles */

'''Original by aGorm, with help from LathanStanley'''



==The Idea==
First of all you need an idea. There is no point (OK, there is some point for test purposes) in making a map just like another one that already exists. You need to think of certain things before you make your map.
# Is this map idea different, not just a copy of someone else's?
# Does my map idea give each player a fair share of the cover and high ground?
# Is my map idea possible to make?
# Is it possible with the amount of time I'm willing to spend?

If you answered yes to the above, then you are 25% of the way towards making your map!

You should probably doodle it on a piece of paper to act as a guide later.

==The Tools==
With your idea hopefully sketched out, it's time to get the tools to make the map! (You can skip this if you already have them.)

For all your map compiling needs you should first download the [http://fileuniverse.com/?p=showitem&ID=1234 newest MapConv program].

You will also need some image editing software. Favorites are Photoshop, the [http://www.gimp.org/ GIMP], And Paintshop Pro.
The GIMP, however, is the only one that's free!
(I'm going to have to assume you know how to use the program you choose. If you can't there are loads of tutorials on the net.)

You may also want to check out [http://www.planetside.co.uk/terragen/ Terragen] for generating terrain. But as you have to pay to render anything of a good size, I won't mention it other than here.

Another tool you might find useful is the freeware tool [http://www.delphigl.de/projects/terrtexgen/eng_index.html TerrTexGen]. It's useful for previewing your heightmap before compiling, but unless your texturemap is 4096 on both sides, you might find that the texturemaps that it creates are too small.

Finally, there is tool called [http://www.bundysoft.com/L3DT/ L3DT] which you might also find useful. It seems to be a program that is specificly designed for creating large height/texture maps. The free version is capable of rendering a heightmap as big as 4096x4096, and can generate a texturemap that is proportional to the heightmap. Of the mentioned packages, this seems the most useful and complete.

==Preparing your map==
This is the fun part! And also, often, the longest part.

For a map you will need several different things:
# a texture map
# a height map
# a metal map

And several optional things for added functionality:
# a tile map

They all have certain needs! Read this bit carfully!

===Texture Map===
All maps are based on a texture image. This image's width and height must be an exact multiple of 1024 pixels. So, for instance, you can have a "4096 by 8192" image, but not a "4096 by 4608" image, as 4608 does not divide by 1024. It, like all three maps, must be saved as a 24 bit BMP. A 1024x1024 Texture will produce a map shown as '2x2' in the launcher.

It may look like whatever you want! Find a texture (preferably, one that you can tile seamlessly) and fill your texture map with it. You could, for instance, fill the whole image with a sand texture. This would make your whole world look like sand. You could then decide to add a few patches of grass to it by finding a suitable grass texture and adding it on in patches. So you'd have a map that was mostly sand with a few patches of green.

Because of the way the map compiler work, it will '''greatly''' reduce your map filesize if you use 32x32 tiles on your texture map. So, whenever you have to fill a large area with a repeating pattern, make sure the small square you're repeating is 32x32 (or a multiple of it).

Hey, wtf, Tile Map and Texture Map are about the same stuff, someone merge those section!!

===Height Map===
Next is the height map. This must be exactly one eighth (1/8) of the size of the texture map '''+ 1 pixel!''' For instance, if the dimensions of your texture map are "4096 by 8192", divide 4096 and 8192 each by 8 and add one to the result of each. The result for this example would be "513 by 1025". The height map is a black and white BMP. Only use black and white, no colour! (well its better to work it as a greyscale image, and when saving to process, convert to rgb and save as bmp, that way you get a 24 bit bmp)

White areas are the tops of mountains; black areas are the sea floor or the bottom of valleys. The shades of grey between are the different heights between! When you draw your heightmap, make sure the white blends into the black with greys. I suggest you use the blur tool. If you have a white splodge in a patch of black you will have a very tall pillar that won't look natural at all!

===Metal Map===
Finally, you need a metal map. This is the same size as the height map, one eighth (1/8) of the size of the texture map '''+ 1 pixel.''' On this one you paint down red (in verying degrees) to represent metal. So a red spot that is RGB(50,0,0) will provide about a 5th of the metal patch of red RGB(255,0,0) will give.

On this map you can also place green pixels. Each green pixel will create 1 geothermal vent. If you put down a green splodge you will get a cluster of geo vents! Only place 1 pixel.

Ensure you have all three saved as 24 bit BMPs and you're ready to convert it all to a map!

===Tile Map===
Tiles are basically repeating images. They are exactly the same. The map compiler, by comparing peices to the texture to each other, sees which little square tiles in your texture are exactly alike. If they are the same, instead of wasting precious harddrive and bandwidth space, the compiler sets a reference from on tile to the next. If your map is made out of only one small tile, repeating for the whole texture, the map will compress extreemly well. Down to only a few kilobytes. But this would look very boring. So most map makers use a variety of tiles to make their map more interesting. A good map maker will find a balance between looks and size.

To make a tile:
Open up your image editing program.
Create a new image.
As the Spring engine uses a 32 pixel tile engine, you have to set your image size to 32 pixels, or a multiple of 32 pixels. Therefore, tile sizes should be one of the following:
32x32 pixels,
64x64 pixels,
96x96 pixels,
128x128 pixels
etc.
Tiles also do not have to be square, it is perfectly possible to make rectangular tiles. Tiles should also be seamless, so that when repeated do not seem to have an obvious edge.

Once you have created your tile, do a Fill operation with a texture. The texture of course is our tile that we have made in the previous step. If you do not know how to do this, ask around. Make sure to state which image editing software you use, so we can help you easier.

Now, once you have your basic tile down, add in different features on your map, such as mountains, rivers, seas, deserts, grasslands, or whatever your map has. Remeber, for smaler file sizes make these different features out of tiles as well. If you do all of this properly, you can get your file size down very small, and this will keep everyone happy.

== MapConv.exe ==

Instructions pulled from [http://fileuniverse.com/?p=showitem&ID=1234 the newest MapConv program]. If all goes well, the <code>MapConv.exe</code> should create four new files: <code>mini.bmp</code>, <code>mini.dds</code>, <code>yourmapname.smf</code>, and <code>yourmapname.smt</code>

<pre>
USAGE:

mapconv [-l] [-i] [-c <compression>] -x <max height> -n <min height> [-o
<Output file>] [-e <tile file>] [-y <Typemap file>] -m <Metalmap file> -a
<Heightmap file> -t <Texture file> [--] [-v] [-h]

Where:

-l, --lowpass
Lowpass filters the heightmap

-i, --invert
Inverts the height map vertically (not the height values but the height map
(uhm someone rewrite this))

-c <compression>, --compress <compression>
(value required) How much we should try to compress the texture file.
Default value 0.8 . (lower=higher quality, larger file)

-x <max height>, --maxheight <max height>
(required) (value required) What altitude in spring the max(0xffff) level
of the height map should represent

-n <min height>, --minheight <min height>
(required) (value required) What altitude in spring the min(0) level of
the height map should represent

-o <Output file>, --outfile <Output file>
(value required) The name of the created map

-e <tile file>, --externaltilefile <tile file>
(value required) External tile file that will be used for finding tiles,
tiles not found in this will be added in a new tile file

-y <Typemap file>, --typemap <Typemap file>
(value required) Type map to use, uses the red channel to decide type,
types are defined in the .smd, if this argument is skipped the map will be
all type 0

-m <Metalmap file>, --metalmap <Metalmap file>
(required) (value required) Metal map to use, red channel is amount of
metal, green=255 is where to place geos (one pixel=one geo). Is resized to
fit the mapsize

-a <Heightmap file>, --heightmap <Heightmap file>
(required) (value required) Input heightmap to use for the map, this
should be in 16 bit raw format (.raw extension) or an image file. Must be
xsize*128+1 x ysize*128+1 in size.

-t <Texture file>, --intex <Texture file>
(required) (value required) Input bitmap to use for the map. Must be
xsize*1024 x ysize*1024 in size. (xsize,ysize integers determined from this
file)

--, --ignore_rest
Ignores the rest of the labeled arguments following this flag.

-v, --version
Displays version information and exits.

-h, --help
Displays usage information and exits.

Convers a series of bmp/raw files to a spring map. This just creates the .smf
file, you will also have to create a .smd file using a text editor
</pre>

==Mothers MapConv==
The usage is the same as above, with the following exceptions:
All features (including GeoVent/Tree/Grass) are now on their own FeatureMap. This is a 24bit bmp specified with the -f <featuremapname.bmp> flag.
''It should be 1/8th the resolution of your map.'' (i.e. 1 pixel smaller in each direction then your heightmap)

Tree's and GeoVents are placed on the green layer.
*255 Places a GeoVent
*200-215 Places tree types 1-16

MapConv will try to place these features in the exact spot you place them, it will then go into crackhead mode if it cannot.

Grass is the blue layer. The blue value maps to a 'pseudo-density' of the grass. The 'grass' map in the engine is very very low resolution, so be aware that you will not get nice linear results. 255=full grass, 0=no grass.

The red layer places 'Arbitrary Features,' aka wreckages. One pixel of red equals one feature. Red '1' gives you a feature of the first arbitrary type, 2 the second, 3 the third, and so on.

===But what are these 'Arbitrary Features,' Im so confused!===
They are 'features' found in the /features/All Worlds or /features/corpses filesystems. Which feature is 'type 1' is defined on a map-by-map basis via a new file called 'fs.txt'. This file should contain <cr> delimited feature names. The first line is the feature placed when a red=255 dot is found, etc.

=== Ok, Now what do I do? ===
If you are using any custom features, and/or you want to mod-proof your map, you should include them in the sd7 that you package the map in. The tree structure should look something like:

<pre>
<mapname.sd7>
-maps/
-mapname.smf
-mapname.smt
-mapname.smd
-Objects3d/
-<featurename[s]>.3do(specified in the tdf)
-features/
-All Worlds/
(and/or)
-Corpses/
-<featurename[s]>.tdf
-textures/
-tatex/
-<texname[s]>00.bmp or .tga
</pre>
Without getting into modding/unit making I will say that the <code>.tdf</code> tells you the name of the <code>.3do</code> ("<code>Object=</code>"), and the name of the 'feature' is in the top brackets. The <code>.3do</code> specifies the texture names. The engine looks for those texture names + 00 in either bmp or tga format in tatex.

Examples of a built-in XTA wreckage name would be <code>armckfus_dead</code> which would be looking for a tdf (likely <code>armckfus_dead.tdf</code>) that has a <code>[armckfus_dead]</code> section which then specified something like:
<pre>Object=armckfus_dead</pre>
<code>armckfus_dead.3do</code> would then specify some texture like <code>wreck01b</code> which would go looking for either a <code>wreck01b00.bmp<c/ode> or <code>wreck01b00.tga</code> file.

[http://fileuniverse.com/?p=showitem&ID=1421 Start with this version of MapConv]
or
[http://www.fileuniverse.com/?p=showitem&ID=1507 This one]
[I will clean this up and add more later --Mother]

==Making your map work==
This is the final push. Once Sharp map has finshed it will spit out a .sm2 file. This needs to be copyed to the MAPS folder in Spring. But you still need one more thing: an .smd file. Basically, this file tells the game things like the maximum metal, the light colours, the clouds, etc. (All the bits you were thinking that you hadn't done yet!)

I would suggest you copy the .smd of another map and fiddle with the settings until you get what you want. smd's can be opened in notepade or similar. Look at all the .smd's so you can get a jist of what each option does. Make sure both the .sm2 and .smd have the same file name then start up Spring (not the client!) in [http://taspring.clan-sy.com/wiki/FAQ#People_talk_about_.27Single_Player.27._How_do_I_start_a_single_player_game.3F single-player mode] and run the commanders script. Choose your map and away you go!

==SMD Rundown==
What follows is all that we (aGorm and LathanStanley) have figured out in the SMD's. Its by no means the be all and end all, but it's the next best thing.

* Goto [[Maps:SMD]] for a more detailed listing

===General Map Information===
* Description is just a short description of your map. Keep it simple.
* TidalStrength determines how much energy tidal generators will produce. A normal figure is around 20.
* Gravity, as you would expect, affects ballisitcs and how far units fly after an explosion.
* MaxMetal is the maximum amount of metal you will gain from one game square in 1 second from an area of metal that had a red value of 255 in your metal map. If making an old style metal deposit map, then this will be quite high: maybe 2 or 3. If you are making a new style metal-all-over-the-place-map, then it will be low: perhaps 0.2. Also for old style maps, you'll have to fiddle with the...
* ExtractorRadius, which is the area that is harvested by 1 metal extractor. For old style maps make this very small, so as they only take from one deposit.

=== Atmosphere, Water Colours ===
Each value (it would appear this bit is by no means gospel) is a representation of the [[RGB]] values for that parameter. It would appear to be relative, i.e. you can put in what ever numbers you like and the game will work out what you want.

The best way to go about it is to look at it as percentages.
The numbers 1, 0.5, 0.2 refer to 100% red, 50% green and 20% blue. But 2, 1, 0.4, will get the same result. Using numbers below one for all the numbers will result in the colour being less bright.

This is all a bit confusing so an example will be given:

<pre>SkyColor=0.2 0.1 0.5;</pre>

In this example the sky is coloured with 20% red, 10% green, and 50% blue, approximatly RGB(51,25,127), resulting in a very deep night-time blue. Other colours are added to the initial sky colour. If you set your sun as being a pale yellow and it came out rather green, this is why.

One helpful tip is ''negative'' colour. That's right: you can type in a negative number for a colour and it will remove it from the base sky colour. Just be careful not to go below the original values or you may get a surprise.

===The Sun System/Shadow System===
The Sun System/Shadow System is quite a useful tool as well in making your maps look ''well done''.
Within the <code>.smd</code> file there is a line:

: <code>SunDir=-1 1 -.5; //direction of sun</code> (The part after the "//" is a comment)

The numbers "-1", "1", ".5" determine the angle and elevation of the sunlight system.

The first number is the X angle (East/West) (from -1 to 1) where any negative number means the sun is on the West (and therefore shadows will be cast east), and any positive number means the sun is on the East (and therefore shadows will be cast west), and if the number is 0 there are no east or west shadows, the sun is directly above you.

The second is its elevation, (0 to 1), this number is how far from the horizion the sun is, ignoring it's angle. Thus, 1 puts the sun directly overhead (while still casting angular shadows) and 0 putting it directly on the horizion.

The final number is the Z angle (North/South). (I know, I know, they wrote the engine with Y as elevation and Z as vertical. Don't blame me.) It is just like the East West positioning, where negative numbers put them on the North, and positive numbers put them on the South.

'''Example Usage:''' If you want the shadows ''in'' one of the boxes (your shadow casting surface is in the middle), use the numbers provided, or start from them and tweak the angle and sun height as seen fit.

[[Image:ShadowDirection.gif]]

'''Note:''' on the current build, it ''will'' cast the shadows in the proper direction, etc. Negative direction numbers tend to make some maps unstable and cause crashes. The best solution would be to rotate or flip your map to where the shadows point up or right (North or West). I do believe these bugs are being worked on and will be fixed soon.

We can only hope this has been helpful! Any questions, or things you think we have missed, please ask us in the maps section.

==Other Articles==

[[Maps:Compiling]] is about properly compile and compress your map to a sd7 file.

[[Category:Maps]]
[[Category:Development]]

Tutorial:CreateMaps(Fnordia et al)

2006-02-09T13:51:37Z

NOiZE:

'''Original by aGorm, with help from LathanStanley'''



==The Idea==
First of all you need an idea. There is no point (OK, there is some point for test purposes) in making a map just like another one that already exists. You need to think of certain things before you make your map.
# Is this map idea different, not just a copy of someone else's?
# Does my map idea give each player a fair share of the cover and high ground?
# Is my map idea possible to make?
# Is it possible with the amount of time I'm willing to spend?

If you answered yes to the above, then you are 25% of the way towards making your map!

You should probably doodle it on a piece of paper to act as a guide later.

==The Tools==
With your idea hopefully sketched out, it's time to get the tools to make the map! (You can skip this if you already have them.)

For all your map compiling needs you should first download the [http://fileuniverse.com/?p=showitem&ID=1234 newest MapConv program].

You will also need some image editing software. Favorites are Photoshop, the [http://www.gimp.org/ GIMP], And Paintshop Pro.
The GIMP, however, is the only one that's free!
(I'm going to have to assume you know how to use the program you choose. If you can't there are loads of tutorials on the net.)

You may also want to check out [http://www.planetside.co.uk/terragen/ Terragen] for generating terrain. But as you have to pay to render anything of a good size, I won't mention it other than here.

Another tool you might find useful is the freeware tool [http://www.delphigl.de/projects/terrtexgen/eng_index.html TerrTexGen]. It's useful for previewing your heightmap before compiling, but unless your texturemap is 4096 on both sides, you might find that the texturemaps that it creates are too small.

Finally, there is tool called [http://www.bundysoft.com/L3DT/ L3DT] which you might also find useful. It seems to be a program that is specificly designed for creating large height/texture maps. The free version is capable of rendering a heightmap as big as 4096x4096, and can generate a texturemap that is proportional to the heightmap. Of the mentioned packages, this seems the most useful and complete.

==Preparing your map==
This is the fun part! And also, often, the longest part.

For a map you will need several different things:
# a texture map
# a height map
# a metal map

And several optional things for added functionality:
# a tile map

They all have certain needs! Read this bit carfully!

===Texture Map===
All maps are based on a texture image. This image's width and height must be an exact multiple of 1024 pixels. So, for instance, you can have a "4096 by 8192" image, but not a "4096 by 4608" image, as 4608 does not divide by 1024. It, like all three maps, must be saved as a 24 bit BMP. A 1024x1024 Texture will produce a map shown as '2x2' in the launcher.

It may look like whatever you want! Find a texture (preferably, one that you can tile seamlessly) and fill your texture map with it. You could, for instance, fill the whole image with a sand texture. This would make your whole world look like sand. You could then decide to add a few patches of grass to it by finding a suitable grass texture and adding it on in patches. So you'd have a map that was mostly sand with a few patches of green.

Because of the way the map compiler work, it will '''greatly''' reduce your map filesize if you use 32x32 tiles on your texture map. So, whenever you have to fill a large area with a repeating pattern, make sure the small square you're repeating is 32x32 (or a multiple of it).

Hey, wtf, Tile Map and Texture Map are about the same stuff, someone merge those section!!

===Height Map===
Next is the height map. This must be exactly one eighth (1/8) of the size of the texture map '''+ 1 pixel!''' For instance, if the dimensions of your texture map are "4096 by 8192", divide 4096 and 8192 each by 8 and add one to the result of each. The result for this example would be "513 by 1025". The height map is a black and white BMP. Only use black and white, no colour! (well its better to work it as a greyscale image, and when saving to process, convert to rgb and save as bmp, that way you get a 24 bit bmp)

White areas are the tops of mountains; black areas are the sea floor or the bottom of valleys. The shades of grey between are the different heights between! When you draw your heightmap, make sure the white blends into the black with greys. I suggest you use the blur tool. If you have a white splodge in a patch of black you will have a very tall pillar that won't look natural at all!

===Metal Map===
Finally, you need a metal map. This is the same size as the height map, one eighth (1/8) of the size of the texture map '''+ 1 pixel.''' On this one you paint down red (in verying degrees) to represent metal. So a red spot that is RGB(50,0,0) will provide about a 5th of the metal patch of red RGB(255,0,0) will give.

On this map you can also place green pixels. Each green pixel will create 1 geothermal vent. If you put down a green splodge you will get a cluster of geo vents! Only place 1 pixel.

Ensure you have all three saved as 24 bit BMPs and you're ready to convert it all to a map!

===Tile Map===
Tiles are basically repeating images. They are exactly the same. The map compiler, by comparing peices to the texture to each other, sees which little square tiles in your texture are exactly alike. If they are the same, instead of wasting precious harddrive and bandwidth space, the compiler sets a reference from on tile to the next. If your map is made out of only one small tile, repeating for the whole texture, the map will compress extreemly well. Down to only a few kilobytes. But this would look very boring. So most map makers use a variety of tiles to make their map more interesting. A good map maker will find a balance between looks and size.

To make a tile:
Open up your image editing program.
Create a new image.
As the Spring engine uses a 32 pixel tile engine, you have to set your image size to 32 pixels, or a multiple of 32 pixels. Therefore, tile sizes should be one of the following:
32x32 pixels,
64x64 pixels,
96x96 pixels,
128x128 pixels
etc.
Tiles also do not have to be square, it is perfectly possible to make rectangular tiles. Tiles should also be seamless, so that when repeated do not seem to have an obvious edge.

Once you have created your tile, do a Fill operation with a texture. The texture of course is our tile that we have made in the previous step. If you do not know how to do this, ask around. Make sure to state which image editing software you use, so we can help you easier.

Now, once you have your basic tile down, add in different features on your map, such as mountains, rivers, seas, deserts, grasslands, or whatever your map has. Remeber, for smaler file sizes make these different features out of tiles as well. If you do all of this properly, you can get your file size down very small, and this will keep everyone happy.

== MapConv.exe ==

Instructions pulled from [http://fileuniverse.com/?p=showitem&ID=1234 the newest MapConv program]. If all goes well, the <code>MapConv.exe</code> should create four new files: <code>mini.bmp</code>, <code>mini.dds</code>, <code>yourmapname.smf</code>, and <code>yourmapname.smt</code>

<pre>
USAGE:

mapconv [-l] [-i] [-c <compression>] -x <max height> -n <min height> [-o
<Output file>] [-e <tile file>] [-y <Typemap file>] -m <Metalmap file> -a
<Heightmap file> -t <Texture file> [--] [-v] [-h]

Where:

-l, --lowpass
Lowpass filters the heightmap

-i, --invert
Inverts the height map vertically (not the height values but the height map
(uhm someone rewrite this))

-c <compression>, --compress <compression>
(value required) How much we should try to compress the texture file.
Default value 0.8 . (lower=higher quality, larger file)

-x <max height>, --maxheight <max height>
(required) (value required) What altitude in spring the max(0xffff) level
of the height map should represent

-n <min height>, --minheight <min height>
(required) (value required) What altitude in spring the min(0) level of
the height map should represent

-o <Output file>, --outfile <Output file>
(value required) The name of the created map

-e <tile file>, --externaltilefile <tile file>
(value required) External tile file that will be used for finding tiles,
tiles not found in this will be added in a new tile file

-y <Typemap file>, --typemap <Typemap file>
(value required) Type map to use, uses the red channel to decide type,
types are defined in the .smd, if this argument is skipped the map will be
all type 0

-m <Metalmap file>, --metalmap <Metalmap file>
(required) (value required) Metal map to use, red channel is amount of
metal, green=255 is where to place geos (one pixel=one geo). Is resized to
fit the mapsize

-a <Heightmap file>, --heightmap <Heightmap file>
(required) (value required) Input heightmap to use for the map, this
should be in 16 bit raw format (.raw extension) or an image file. Must be
xsize*128+1 x ysize*128+1 in size.

-t <Texture file>, --intex <Texture file>
(required) (value required) Input bitmap to use for the map. Must be
xsize*1024 x ysize*1024 in size. (xsize,ysize integers determined from this
file)

--, --ignore_rest
Ignores the rest of the labeled arguments following this flag.

-v, --version
Displays version information and exits.

-h, --help
Displays usage information and exits.

Convers a series of bmp/raw files to a spring map. This just creates the .smf
file, you will also have to create a .smd file using a text editor
</pre>

==Mothers MapConv==
The usage is the same as above, with the following exceptions:
All features (including GeoVent/Tree/Grass) are now on their own FeatureMap. This is a 24bit bmp specified with the -f <featuremapname.bmp> flag.
''It should be 1/8th the resolution of your map.'' (i.e. 1 pixel smaller in each direction then your heightmap)

Tree's and GeoVents are placed on the green layer.
*255 Places a GeoVent
*200-215 Places tree types 1-16

MapConv will try to place these features in the exact spot you place them, it will then go into crackhead mode if it cannot.

Grass is the blue layer. The blue value maps to a 'pseudo-density' of the grass. The 'grass' map in the engine is very very low resolution, so be aware that you will not get nice linear results. 255=full grass, 0=no grass.

The red layer places 'Arbitrary Features,' aka wreckages. One pixel of red equals one feature. Red '1' gives you a feature of the first arbitrary type, 2 the second, 3 the third, and so on.

===But what are these 'Arbitrary Features,' Im so confused!===
They are 'features' found in the /features/All Worlds or /features/corpses filesystems. Which feature is 'type 1' is defined on a map-by-map basis via a new file called 'fs.txt'. This file should contain <cr> delimited feature names. The first line is the feature placed when a red=255 dot is found, etc.

=== Ok, Now what do I do? ===
If you are using any custom features, and/or you want to mod-proof your map, you should include them in the sd7 that you package the map in. The tree structure should look something like:

<pre>
<mapname.sd7>
-maps/
-mapname.smf
-mapname.smt
-mapname.smd
-Objects3d/
-<featurename[s]>.3do(specified in the tdf)
-features/
-All Worlds/
(and/or)
-Corpses/
-<featurename[s]>.tdf
-textures/
-tatex/
-<texname[s]>00.bmp or .tga
</pre>
Without getting into modding/unit making I will say that the <code>.tdf</code> tells you the name of the <code>.3do</code> ("<code>Object=</code>"), and the name of the 'feature' is in the top brackets. The <code>.3do</code> specifies the texture names. The engine looks for those texture names + 00 in either bmp or tga format in tatex.

Examples of a built-in XTA wreckage name would be <code>armckfus_dead</code> which would be looking for a tdf (likely <code>armckfus_dead.tdf</code>) that has a <code>[armckfus_dead]</code> section which then specified something like:
<pre>Object=armckfus_dead</pre>
<code>armckfus_dead.3do</code> would then specify some texture like <code>wreck01b</code> which would go looking for either a <code>wreck01b00.bmp<c/ode> or <code>wreck01b00.tga</code> file.

[http://fileuniverse.com/?p=showitem&ID=1421 Start with this version of MapConv]
or
[http://www.fileuniverse.com/?p=showitem&ID=1507 This one]
[I will clean this up and add more later --Mother]

==Making your map work==
This is the final push. Once Sharp map has finshed it will spit out a .sm2 file. This needs to be copyed to the MAPS folder in Spring. But you still need one more thing: an .smd file. Basically, this file tells the game things like the maximum metal, the light colours, the clouds, etc. (All the bits you were thinking that you hadn't done yet!)

I would suggest you copy the .smd of another map and fiddle with the settings until you get what you want. smd's can be opened in notepade or similar. Look at all the .smd's so you can get a jist of what each option does. Make sure both the .sm2 and .smd have the same file name then start up Spring (not the client!) in [http://taspring.clan-sy.com/wiki/FAQ#People_talk_about_.27Single_Player.27._How_do_I_start_a_single_player_game.3F single-player mode] and run the commanders script. Choose your map and away you go!

==SMD Rundown==
What follows is all that we (aGorm and LathanStanley) have figured out in the SMD's. Its by no means the be all and end all, but it's the next best thing.

* Goto [[Maps:SMD]] for a more detailed listing

===General Map Information===
* Description is just a short description of your map. Keep it simple.
* TidalStrength determines how much energy tidal generators will produce. A normal figure is around 20.
* Gravity, as you would expect, affects ballisitcs and how far units fly after an explosion.
* MaxMetal is the maximum amount of metal you will gain from one game square in 1 second from an area of metal that had a red value of 255 in your metal map. If making an old style metal deposit map, then this will be quite high: maybe 2 or 3. If you are making a new style metal-all-over-the-place-map, then it will be low: perhaps 0.2. Also for old style maps, you'll have to fiddle with the...
* ExtractorRadius, which is the area that is harvested by 1 metal extractor. For old style maps make this very small, so as they only take from one deposit.

=== Atmosphere, Water Colours ===
Each value (it would appear this bit is by no means gospel) is a representation of the [[RGB]] values for that parameter. It would appear to be relative, i.e. you can put in what ever numbers you like and the game will work out what you want.

The best way to go about it is to look at it as percentages.
The numbers 1, 0.5, 0.2 refer to 100% red, 50% green and 20% blue. But 2, 1, 0.4, will get the same result. Using numbers below one for all the numbers will result in the colour being less bright.

This is all a bit confusing so an example will be given:

<pre>SkyColor=0.2 0.1 0.5;</pre>

In this example the sky is coloured with 20% red, 10% green, and 50% blue, approximatly RGB(51,25,127), resulting in a very deep night-time blue. Other colours are added to the initial sky colour. If you set your sun as being a pale yellow and it came out rather green, this is why.

One helpful tip is ''negative'' colour. That's right: you can type in a negative number for a colour and it will remove it from the base sky colour. Just be careful not to go below the original values or you may get a surprise.

===The Sun System/Shadow System===
The Sun System/Shadow System is quite a useful tool as well in making your maps look ''well done''.
Within the <code>.smd</code> file there is a line:

: <code>SunDir=-1 1 -.5; //direction of sun</code> (The part after the "//" is a comment)

The numbers "-1", "1", ".5" determine the angle and elevation of the sunlight system.

The first number is the X angle (East/West) (from -1 to 1) where any negative number means the sun is on the West (and therefore shadows will be cast east), and any positive number means the sun is on the East (and therefore shadows will be cast west), and if the number is 0 there are no east or west shadows, the sun is directly above you.

The second is its elevation, (0 to 1), this number is how far from the horizion the sun is, ignoring it's angle. Thus, 1 puts the sun directly overhead (while still casting angular shadows) and 0 putting it directly on the horizion.

The final number is the Z angle (North/South). (I know, I know, they wrote the engine with Y as elevation and Z as vertical. Don't blame me.) It is just like the East West positioning, where negative numbers put them on the North, and positive numbers put them on the South.

'''Example Usage:''' If you want the shadows ''in'' one of the boxes (your shadow casting surface is in the middle), use the numbers provided, or start from them and tweak the angle and sun height as seen fit.

[[Image:ShadowDirection.gif]]

'''Note:''' on the current build, it ''will'' cast the shadows in the proper direction, etc. Negative direction numbers tend to make some maps unstable and cause crashes. The best solution would be to rotate or flip your map to where the shadows point up or right (North or West). I do believe these bugs are being worked on and will be fixed soon.

We can only hope this has been helpful! Any questions, or things you think we have missed, please ask us in the maps section.

==Other Articles==

[[Maps:Compiling]]

[[Category:Maps]]
[[Category:Development]]

Maps:Compiling

2006-02-09T13:46:20Z

NOiZE: /* Compressing your map */

== Compiling Spring Maps ==

This is often the bit that scares alot of people off, but it is really not that dificult. There are two different ways to compile a map, so you can choose which option suits you best. You can:

*Compile through a DOS prompt, or
*Create and batch file.

=== Before you start ===

First off, download a map converter. These can be found on [www.FileUniverse.com FileUniverse.com]. There are two compiliers that most people use:
* [http://www.fileuniverse.com/?p=showitem&ID=1421 mother's MapConv with 'optimisation'] This version does not work for some people. If you are one of these people, try:
* [http://www.fileuniverse.com/?p=showitem&ID=1507 mother's mapconc, without optimisation] Use this if the other one does not work.

Place the compiler in to a directory on your computer somewhere. Because of a bug in the program, the path to the map converter can NOT contain ANY Spaces. A Path of '''C:\Maps\MapConv\''' is good, but a path of '''C:\Maps\Map Conv\''' is BAD.

A good practise is to save all your source Pictures into seperate folders when making a map. However, this gets very tedious when compiling. So it is a good idea to make a copy of your source BMP files and place these in the same folder as the map converter. This just makes things alot easier later on. You should have the following files in your MapConv folder:

* Texture.bmp
* Height.bmp
* Metal.bmp
* Feature.bmp

You should also put, if you are using them, your type map (Type.bmp) and your tile
map (Tile.bmp). Most maps do not use these, so you do not usually need to worry about them.

You need the 7-zip compression program to compress your map into a .sd7 map file.
* [http://www.7-zip.org 7-zip homepage]
* [http://prdownloads.sourceforge.net/sevenzip/7z431.exe?download Download Link]

A .smd file. These can be made with [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2420 Maelstroms SMD creator].
It is recommended to actually try to learn how the different SMD values works though by looking at other maps .smd files. The SMD creator is also not completly bugfree, so you should preferably look it through once with a text editor anyway.

You also need to know:

*The minimum and maximum heights of your map.
*The name of your map.
*How much you want to compress your map.

=== Command Line Options ===

As the compiler runs off information entered into it as '''Command Line Parameters''' , you need to know a bit about them first. Command Line Parameters are really not difficult to understand. They look a bit like this:

ProgramName -Setting1 Value -Setting2 Value

The first bit is how we launch the program. Windows will launch whatever program is specified by '''ProgramName'''. '''-Setting1 Value''' is also very simple. Windows basically says to the program "Setting1 is Value". A better example would be -height 10, which basicly means "Height is 10". These can be combined with as many settings as you want, as we can see with the '''Setting2 Value''' bit. In this way we can pass as much information to the compiler as we want. To compile a map, we need the following Command Line Parameters:

'''Map Compression'''
This takes the form of '''-c Compression''', where Compression is a value. Typing '''-c 0.5''' will give a compression of 0.5

'''Max Height'''
This specifies the maximum height of the map. This option looks like '''-x Height''', where Height is the maximum height of the map. Typing '''-x 300''' will give your map a maximum height of 300 map units.

'''Minimum Height'''
This specifies the minimum height of the map. This option looks like '''-n Height''', where Height is the minimum height of the map. Typing '''-x -50''' will give your map a minimum height of -50 map units.

'''Texture'''
This specifies the location of your texture picture. This option looks like '''-t Location''', where Location is the location of your texture image. Typing '''-t texture.bmp''' will make the compiler look in the same directory it is in for '''texture.bmp'''. Typing '''-t C:\Maps\HillMap\texture.bmp''' will make the compiler look in the '''C:\Maps\HillMap\''' for texture.bmp. This name cannot contain spaces.

'''Other Picture files'''
These work in basically the same way as the texture option works, with just a changed Setting name.
*'''-m metal.bmp''': Specifies the location of the metal map.
*'''-a height.bmp''': Specifies the location of the height map.
*'''-f feature.bmp''': Specifies the location of the feature map.
*'''-y typemap.bmp''': Specifies the location of the terain type map.
Please note that these names cannot contaion spaces.

'''Map Name'''
The Map Converter needs to know where to save your map, and what to call it. We use the '''-o Mapname.smf''' setting to do this. Of course, you replace Mapname with the name of your map, but you NEED to have the '.smf' bit on the end of it, otherwise the compiling wont work. An example would be '''-o HillMap.smf'''. This name cannot contain spaces.

'''Other Tags'''
Some of these tags are helpfull, some are annoying and some are just a mystery. This is basicly the mics tags settings.
*'''Low Pass''': If you map has very steep slopes or rough areas that look ugly, this will smooth them a bit. Is activated just by typing '''-l'''.
*'''Invert Height map''': As the logical way to make a height map is the same way up as all the other maps, but the way the map is actually used is the inverted version of this. To make things easier, they included this option to invert the height map. Is activated just by typing '-i'. Most maps will use this.

=== Compiling through a batch file ===

This is perhaps the easiest option. You just have to create a simple text file, rename it, and run.

First, open up Notepad. Notepad can be found in Start > Program Files > Accessories > Notepad. In notepad, type or copy the following:

'''mapconv -c 0.5 -x 500 -n 50 -o MapName.smf -t texture.bmp -m metal.bmp -a height.bmp -f feature.bmp -i '''

Replace the relevant values with the values you need, as the settings here will not work for all the maps. Then, in Notepad click File > Save As. In the file name box, type '''"Compile.bat"''', with the quotes. If you do not have the quotes, it will not work. Save the file in the same directory as your compiler.

Go to the MapConv folder on your hard drive, and you should see a new file. This file will be called Compile.bat. Double click this file, and a black Dos window should pop up. After a few minutes the window should close. There will now be 2 extra files in that directory. '''MapName.smt''' and '''MapName.smf'''.

=== Compiling through DOS ===

Use this option if you want to read the information that the MapConv outputs. If you are not familiar with how DOS works, then this way is not for you.

All you need to do is navigate your way through DOS to the location of your map converter program. Then, type in the following:

'''mapconv -c 0.5 -x 500 -n 50 -o MapName.smf -t texture.bmp -m metal.bmp -a height.bmp -f feature.bmp -i '''

Replace the relevant values with the values you need, as the settings here will not work for all the maps.

Once compiled, there will be 2 extra files in that directory. '''MapName.smt''' and '''MapName.smf'''.

=== Compressing your map ===

Your SMD file needs to have the same name as the .smt and .smf files. If your smt file is calles '''HillMap.smt''', your .smd file needs to be called '''HillMap.smd'''.

Place the '''MapName.smd''', '''MapName.smt''' and '''MapName.smf''' files into an empty folder called maps\. Eg: '''C:\maps\'''. Right click this folder, and a right click menu should appear. In that menu, there will be a 7-Zip'''>''' submenu. Open this menu, and click '''Add to Archive...'''. A 7-zip window will appear. Make sure the settings are identical to the following picture:
[[Image:7-zip_options.jpg]]

Change the '''Archive''' box at the top to the name of your map, with .sd7 on the end. Eg: '''HillMap.sd7'''. Click the '''OK''' button. After the compression has completed, there will be a file called '''HillMap.sd7''' in the same directory as the folder was. In this example, the '''HillMap.sd7''' would be straight on the C:\ drive. Copy '''HillMap.sd7''' to your TASpring\Maps\ directory.

NOiZE: The compresion can be set at ultra. but make sure you don't make it a solid archive!

If all of this was done correctly, the map should now appear your maps list in the lobby, and you can go play it.

Community news

2005-12-13T18:48:01Z

NOiZE:

Community news

2005-12-07T17:38:15Z

NOiZE:

Tutorial:CreateMaps(Fnordia et al)

2005-12-02T14:35:24Z

NOiZE: /* But what are these 'Arbitrary Features,' Im so confused! */

'''Original by aGorm, with help from LathanStanley'''



==The Idea==
First of all you need an idea. There is no point (OK, there is some point for test purposes) in making a map just like another one that already exists. You need to think of certain things before you make your map.
# Is this map idea different, not just a copy of someone else's?
# Does my map idea give each player a fair share of the cover and high ground?
# Is my map idea possible to make?
# Is it possible with the amount of time I'm willing to spend?

If you answered yes to the above, then you are 25% of the way towards making your map!

You should probably doodle it on a piece of paper to act as a guide later.

==The Tools==
With your idea hopefully sketched out, it's time to get the tools to make the map! (You can skip this if you already have them.)

For all your map compiling needs you should first download the [http://fileuniverse.com/?p=showitem&ID=1234 newest MapConv program].

You will also need some image editing software. Favorites are Photoshop, the [http://www.gimp.org/ GIMP], And Paintshop Pro.
The GIMP, however, is the only one that's free!
(I'm going to have to assume you know how to use the program you choose. If you can't there are loads of tutorials on the net.)

You may also want to check out [http://www.planetside.co.uk/terragen/ Terragen] for generating terrain. But as you have to pay to render anything of a good size, I won't mention it other than here. Another tool for generating terrain is the freeware tool [http://www.delphigl.de/projects/terrtexgen/eng_index.html TerrTexGen]. "It generates a terraintexture on the base of a grayscale heightmap und uses five surfacetextures that are distributed over the heightmap."

==Preparing your map==
This is the fun part! And also, often, the longest part.

For a map you will need several different things:
# a texture map
# a height map
# a metal map

And several optional things for added functionality:
# a tile map

They all have certain needs! Read this bit carfully!

===Texture Map===
All maps are based on a texture image. This image's width and height must be an exact multiple of 1024 pixels. So, for instance, you can have a "4096 by 8192" image, but not a "4096 by 4608" image, as 4608 does not divide by 1024. It, like all three maps, must be saved as a 24 bit BMP. A 1024x1024 Texture will produce a map shown as '2x2' in the launcher.

It may look like whatever you want! Find a texture (preferably, one that you can tile seamlessly) and fill your texture map with it. You could, for instance, fill the whole image with a sand texture. This would make your whole world look like sand. You could then decide to add a few patches of grass to it by finding a suitable grass texture and adding it on in patches. So you'd have a map that was mostly sand with a few patches of green.

Because of the way the map compiler work, it will '''greatly''' reduce your map filesize if you use 32x32 tiles on your texture map. So, whenever you have to fill a large area with a repeating pattern, make sure the small square you're repeating is 32x32 (or a multiple of it).

Hey, wtf, Tile Map and Texture Map are about the same stuff, someone merge those section!!

===Height Map===
Next is the height map. This must be exactly one eighth (1/8) of the size of the texture map '''+ 1 pixel!''' For instance, if the dimensions of your texture map are "4096 by 8192", divide 4096 and 8192 each by 8 and add one to the result of each. The result for this example would be "513 by 1025". The height map is a black and white BMP. Only use black and white, no colour! (well its better to work it as a greyscale image, and when saving to process, convert to rgb and save as bmp, that way you get a 24 bit bmp)

White areas are the tops of mountains; black areas are the sea floor or the bottom of valleys. The shades of grey between are the different heights between! When you draw your heightmap, make sure the white blends into the black with greys. I suggest you use the blur tool. If you have a white splodge in a patch of black you will have a very tall pillar that won't look natural at all!

===Metal Map===
Finally, you need a metal map. This is the same size as the height map, one eighth (1/8) of the size of the texture map '''+ 1 pixel.''' On this one you paint down red (in verying degrees) to represent metal. So a red spot that is RGB(50,0,0) will provide about a 5th of the metal patch of red RGB(255,0,0) will give.

On this map you can also place green pixels. Each green pixel will create 1 geothermal vent. If you put down a green splodge you will get a cluster of geo vents! Only place 1 pixel.

Ensure you have all three saved as 24 bit BMPs and you're ready to convert it all to a map!

===Tile Map===
Tiles are basically repeating images. They are exactly the same. The map compiler, by comparing peices to the texture to each other, sees which little square tiles in your texture are exactly alike. If they are the same, instead of wasting precious harddrive and bandwidth space, the compiler sets a reference from on tile to the next. If your map is made out of only one small tile, repeating for the whole texture, the map will compress extreemly well. Down to only a few kilobytes. But this would look very boring. So most map makers use a variety of tiles to make their map more interesting. A good map maker will find a balance between looks and size.

To make a tile:
Open up your image editing program.
Create a new image.
As the Spring engine uses a 32 pixel tile engine, you have to set your image size to 32 pixels, or a multiple of 32 pixels. Therefore, tile sizes should be one of the following:
32x32 pixels,
64x64 pixels,
96x96 pixels,
128x128 pixels
etc.
Tiles also do not have to be square, it is perfectly possible to make rectangular tiles. Tiles should also be seamless, so that when repeated do not seem to have an obvious edge.

Once you have created your tile, do a Fill operation with a texture. The texture of course is our tile that we have made in the previous step. If you do not know how to do this, ask around. Make sure to state which image editing software you use, so we can help you easier.

Now, once you have your basic tile down, add in different features on your map, such as mountains, rivers, seas, deserts, grasslands, or whatever your map has. Remeber, for smaler file sizes make these different features out of tiles as well. If you do all of this properly, you can get your file size down very small, and this will keep everyone happy.

==MapConv.exe==

Instuctions pulled from [http://fileuniverse.com/?p=showitem&ID=1234 the newest MapConv program]. If all goes well, the MapConv.exe should create four new files: mini.bmp, mini.dds, yourmapname.smf, and yourmapname.smt.

<code>USAGE:

mapconv [-l] [-i] [-c <compression>] -x <max height> -n <min height> [-o
<Output file>] [-e <tile file>] [-y <Typemap file>] -m <Metalmap file> -a
<Heightmap file> -t <Texture file> [--] [-v] [-h]

Where:

-l, --lowpass
Lowpass filters the heightmap

-i, --invert
Inverts the height map vertically (not the height values but the height map
(uhm someone rewrite this))

-c <compression>, --compress <compression>
(value required) How much we should try to compress the texture file.
Default value 0.8 . (lower=higher quality, larger file)

-x <max height>, --maxheight <max height>
(required) (value required) What altitude in spring the max(0xffff) level
of the height map should represent

-n <min height>, --minheight <min height>
(required) (value required) What altitude in spring the min(0) level of
the height map should represent

-o <Output file>, --outfile <Output file>
(value required) The name of the created map

-e <tile file>, --externaltilefile <tile file>
(value required) External tile file that will be used for finding tiles,
tiles not found in this will be added in a new tile file

-y <Typemap file>, --typemap <Typemap file>
(value required) Type map to use, uses the red channel to decide type,
types are defined in the .smd, if this argument is skipped the map will be
all type 0

-m <Metalmap file>, --metalmap <Metalmap file>
(required) (value required) Metal map to use, red channel is amount of
metal, green=255 is where to place geos (one pixel=one geo). Is resized to
fit the mapsize

-a <Heightmap file>, --heightmap <Heightmap file>
(required) (value required) Input heightmap to use for the map, this
should be in 16 bit raw format (.raw extension) or an image file. Must be
xsize*128+1 x ysize*128+1 in size.

-t <Texture file>, --intex <Texture file>
(required) (value required) Input bitmap to use for the map. Must be
xsize*1024 x ysize*1024 in size. (xsize,ysize integers determined from this
file)

--, --ignore_rest
Ignores the rest of the labeled arguments following this flag.

-v, --version
Displays version information and exits.

-h, --help
Displays usage information and exits.

Convers a series of bmp/raw files to a spring map. This just creates the .smf
file, you will also have to create a .smd file using a text editor
</code>
==Mothers MapConv==
The usage is the same as above, with the following exceptions:
All features (including GeoVent/Tree/Grass) are now on their own FeatureMap. This is a 24bit bmp specified with the -f <featuremapname.bmp> flag.
''It should be 1/8th the resolution of your map.'' (i.e. 1 pixel smaller in each direction then your heightmap)

Tree's and GeoVents are placed on the green layer.
*255 Places a GeoVent
*200-215 Places tree types 1-16

MapConv will try to place these features in the exact spot you place them, it will then go into crackhead mode if it cannot.

Grass is the blue layer. The blue value maps to a 'pseudo-density' of the grass. The 'grass' map in the engine is very very low resolution, so be aware that you will not get nice linear results. 255=full grass, 0=no grass.

The red layer places 'Arbitrary Features,' aka wreckages. One pixel of red equals one feature. Red '1' gives you a feature of the first arbitrary type, 2 the second, 3 the third, and so on.

===But what are these 'Arbitrary Features,' Im so confused!===
They are 'features' found in the /features/All Worlds or /features/corpses filesystems. Which feature is 'type 1' is defined on a map-by-map basis via a new file called 'fs.txt'. This file should contain <cr> delimited feature names. The first line is the feature placed when a red=255 dot is found, etc.

===Ok, Now what do I do?===
If you are using any custom features, and/or you want to mod-proof your map, you should include them in the sd7 that you package the map in. The tree structure should look something like:

<code>
<mapname.sd7>
-maps/
-mapname.smf
-mapname.smt
-mapname.smd
-Objects3d/
-<featurename[s]>.3do(specified in the tdf)
-features/
-All Worlds/
(and/or)
-Corpses/
-<featurename[s]>.tdf
-textures/
-tatex/
-<texname[s]>00.bmp or .tga
</code>
Without getting into modding/unit making I will say that the .tdf tells you the name of the .3do ("Object="), and the name of the 'feature' is in the top brackets. The .3do specifies the texture names. The engine looks for those texture names + 00 in either bmp or tga format in tatex.

Examples of a built-in XTA wreckage name would be <code>armckfus_dead</code> which would be looking for a tdf (likely armckfus_dead.tdf) that has a [armckfus_dead] section which then specified something like <code>Object=armckfus_dead</code>.

armckfus_dead.3do Would then specify some texture like <code>wreck01b</code> which would go looking for either a wreck01b00.bmp or wreck01b00.tga file.

[http://fileuniverse.com/?p=showitem&ID=1421 Start with this version of MapConv]
or
[http://www.fileuniverse.com/?p=showitem&ID=1507 This one]
[I will clean this up and add more later --Mother]

==Making your map work==
This is the final push. Once Sharp map has finshed it will spit out a .sm2 file. This needs to be copyed to the MAPS folder in Spring. But you still need one more thing: an .smd file. Basically, this file tells the game things like the maximum metal, the light colours, the clouds, etc. (All the bits you were thinking that you hadn't done yet!)

I would suggest you copy the .smd of another map and fiddle with the settings until you get what you want. smd's can be opened in notepade or similar. Look at all the .smd's so you can get a jist of what each option does. Make sure both the .sm2 and .smd have the same file name then start up Spring (not the client!) in [http://taspring.clan-sy.com/wiki/FAQ#People_talk_about_.27Single_Player.27._How_do_I_start_a_single_player_game.3F single-player mode] and run the commanders script. Choose your map and away you go!

==SMD Rundown==
What follows is all that we (aGorm and LathanStanley) have figured out in the SMD's. Its by no means the be all and end all, but it's the next best thing.

* Goto [[Maps:SMD]] for a more detailed listing

===General Map Information===
* Description is just a short description of your map. Keep it simple.
* TidalStrength determines how much energy tidal generators will produce. A normal figure is around 20.
* Gravity, as you would expect, affects ballisitcs and how far units fly after an explosion.
* MaxMetal is the maximum amount of metal you will gain from one game square in 1 second from an area of metal that had a red value of 255 in your metal map. If making an old style metal deposit map, then this will be quite high: maybe 2 or 3. If you are making a new style metal-all-over-the-place-map, then it will be low: perhaps 0.2. Also for old style maps, you'll have to fiddle with the...
* ExtractorRadius, which is the area that is harvested by 1 metal extractor. For old style maps make this very small, so as they only take from one deposit.

===Atmosphere, Water Colours===
Each value (it would appear this bit is by no means gospel) is a representation of the RGB values for that parameter. It would appear to be relative, i.e. you can put in what ever numbers you like and the game will work out what you want. The best way to go about it is to look at it as percentages.
The numbers 1, 0.5, 0.2 refer to 100% red, 50% green and 20% blue. But 2, 1, 0.4, will get the same result. Using numbers below one for all the numbers will result in the colour being less bright.

This is all a bit confusing so an example will be given:

SkyColor=0.2 0.1 0.5;

In this example the sky is coloured with 20% red, 10% green, and 50% blue, approximatly RGB(51,25,127), resulting in a very deep night-time blue. Other colours are added to the initial sky colour. If you set your sun as being a pale yellow and it came out rather green, this is why.

One helpful tip is ''negative'' colour. That's right: you can type in a negative number for a colour and it will remove it from the base sky colour. Just be careful not to go below the original values or you may get a surprise.

===The Sun System/Shadow System===
The Sun System/Shadow System is quite a useful tool as well in making your maps look ''well done''.
Within the .smd file there is a line:

"SunDir=-1 1 -.5; //direction of sun" (The part of the "//" is a comment.)

The numbers "-1", "1", ".5" determine the angle and elevation of the sunlight system.

The first number is the X angle (East/West) (from -1 to 1) where any negative number means the sun is on the West (and therefore shadows will be cast east), and any positive number means the sun is on the East (and therefore shadows will be cast west), and if the number is 0 there are no east or west shadows, the sun is directly above you.

The second is its elevation, (0 to 1), this number is how far from the horizion the sun is, ignoring it's angle. Thus, 1 puts the sun directly overhead (while still casting angular shadows) and 0 putting it directly on the horizion.

The final number is the Z angle (North/South). (I know, I know, they wrote the engine with Y as elevation and Z as vertical. Don't blame me.) It is just like the East West positioning, where negative numbers put them on the North, and positive numbers put them on the South.

'''Example Usage:''' If you want the shadows ''in'' one of the boxes (your shadow casting surface is in the middle), use the numbers provided, or start from them and tweak the angle and sun height as seen fit.

[[Image:ShadowDirection.gif]]

'''Note:''' on the current build, it ''will'' cast the shadows in the proper direction, etc. Negative direction numbers tend to make some maps unstable and cause crashes. The best solution would be to rotate or flip your map to where the shadows point up or right (North or West). I do believe these bugs are being worked on and will be fixed soon.

We can only hope this has been helpful! Any questions, or things you think we have missed, please ask us in the maps section.

[[Category:Maps]]
[[Category:Development]]