Spring - User contributions [en]

AI:HughAI

2025-04-17T11:28:49Z

Hughperkins: /* To install */ added link to github repo

== What is HughAI ==

HughAI is a an AI written in Java. Works quite well at fast rush attacks.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

sorry, no up to date link. github repo here: https://github.com/hughperkins/HughAI

2. Remove any old AI/Skirmish/HughAI directory

3. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

4. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

Works with BA mod, with the AI running as ARM.

== Play-style ==

It's a non-cheating AI by day ... but if you go to the 'Config' tab on the gui and tick the box next to 'maphack' and then click 'apply' or 'save' ... it will become a cheating maphack AI!

Otherwise, its playstyle is essentially to rush. If it doesn't beat you within a few minutes, it's basically not going to do very much else just yet ;-) Maybe in the future though ;-)

== Cheating / maphack ==

In the gui, in the 'config' tab, click 'maphack' then 'apply' or 'save' to enable maphack.

Unclick it, and then 'apply' or 'save' to disable it.

== To disable gui ==

Either:

- run spring in windowed mode, in the gui, in the config tab, unclick 'guiactivated' and then click 'save', or
- in the config file BA_2.xml, change guiactivated from 'yes' to 'no'.

== Can it beat other AIs? ==

Yes ;-) it beats E323 v2.12.0 sometimes.

== Configuration ==

There is a gui with a tab 'Config' that can be used to configure many things.

A few extra things are configurable in the config file 'BA_<side>.xml' , in the AI's directory, where side is core or arm.

There are also a number of workflow xml files in the BA_<side>workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Survive the initial rush, and it will probably not do too much else.

== Console ==

For techies, there's a console, where you can directly write Java code.

== Soure-code ==

The sources are available from the following git repository:

https://github.com/spring/HughAI

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources, which I try to keep somewhat up-to-date, but really, if you have any questions, just ask me ;-)
[[Category:AI]]

AI:Development:Lang:CSharp

2015-08-09T10:41:26Z

Hughperkins: Created page with "A really old C# AI is at https://springrts.com/wiki/AI:CSAI It probably needs some tweaking, since it was written in 2006 :-P The code is at https://github.com/hughperkins/S..."

A really old C# AI is at https://springrts.com/wiki/AI:CSAI It probably needs some tweaking, since it was written in 2006 :-P The code is at https://github.com/hughperkins/SpringRTS-CSharpAI

GlobalAI Mono Bindings

2015-08-09T10:34:58Z

Hughperkins: direct manageddreams.com with hughperkins.com

= Introduction =

Writing AIs in C# massively facilitates development, because C# runs just as fast as C++ and avoids those annoying stack/heap corruption errors.

We have bindings for .Net Framework 1.1 and 2.0 for Windows. It would be useful to create a set of bindings for Mono so that this could run also on any Mono-supported platform.

Such bindings would make it possible to write portable AIs in C#, Boo (Python.Net), and any .Net language capable of being compiled into a portable ILSM class library.

Here's some thoughts on writing such bindings.

These thoughts are taken from a fuller thread at [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=7634&postdays=0&postorder=asc http://taspring.clan-sy.com/phpbb/viewtopic.php?t=7634&postdays=0&postorder=asc]

= High-level overview =

To create bindings for Mono, we almost certainly need a generator. The hardest part of writing a generator is parsing the input files. In the case of the Mono bindings, we can use Reflection on the existing CSAIInterfaces.dll. This could save a lot of time.

= Download =

Code written so far:
*prototyping code and generator: modified MonoEmbeddedTest at [http://hughperkins.com/csai/MonoEmbeddedTest.zip http://hughperkins.com/csai/MonoEmbeddedTest.zip]
*C# AI "Hello World" for Mono: [http://hughperkins.com/csai/CSharpAIMono.zip http://hughperkins.com/csai/CSharpAIMono.zip] Note that you will need to ensure that Mono-1.1.18/bin is in Spring.exe's path.

A generator has been started in the file "GenerateCode.cs" in the MonoEmbeddedTest.zip zipfile. You can build it by doing:

<pre>
csc /debug GenerateCode.cs /reference:CSAIInterfaces.dll
</pre>

Using mono, you'd do:

<pre>
mcs -debug -reference:CSAIInterfaces.dll GenerateCode.cs
</pre>

= Architecture =

There are three types of classes we need to deal with:
*data classes, pass-by-value. This includes: Command, Float3
*proxied method calls from C++ to C#. This includes: IGlobalAI
*proxied method calls from C# to C++. This includes: IUnitDef, IAICallback

== Pass-by-value ==

We create a class in C++ for each pass-by-value class, with static methods "Marshall_MyType_to_MonoObject" and "Marshall_MonoObject_to_MyType"

The generator does this already, although it needs tweaking to cope with the double array in Command.

Two files are created for each type: MyTypeMarshaller.cpp and MyTypeMarshaller.h

We include the include file for the original Spring native type from MyTypeMarshaller.h, eg Float3Marshaller.h includes Float3.h.

== Proxied method calls from C++ to C# ==

There is only one class that this applies to, IGlobalAI.

We create a C# class GlobalAIProxyLoader, which contains delegate definitions for each method in IGlobalAI, and which calls SetUnitCreatedHandler etc on the C++ proxy class

We create a C++ class GlobalAIProxyCppToCs , which contains a function to receive each delegate from the C# ProxyLoader. It implements each function in IGlobalAI, redirecting to a user-provided GlobalAI C# class.

We strip the leading "I" from the interface name to get the underlying type name.

== Proxied method calls from C# to C++ ==

This applies to: IUnitDef, and IAICallback.

The native instances of these classes are always created by Spring itself, then passed back to the AI. We need to provide a C# proxy to wrap calls to a C++ proxy, which forwards the calls to the native instance.

Two classes called MyTypeCallbackProxyCsToCpp are created, one in C# one in C++.

The MyTypeCallbackProxyCsToCpp class in C# contains instance methods, such as SendTextMsg, which redirect to static methods, such as _SendTextMsg. The static methods are extern'd internal calls to methods with the same name in the MyTypeCallbackProxyCsToCpp class in C++.

In the general case, there can be many instances of each of these proxied classes, so we create a map of reference number to instance in the C++ proxy. The reference number is an arbitrary number starting from 1.

Each time a function on the Spring side returns a class that needs to be proxied into C#, we create a new reference number and add it to the map. The reference number is returned into the C#-side proxy, and will be used as a handle for method calls in the future.

The C#-side proxy that called the spring function that returned the new proxied class will receive the new handle from the C++-side proxy, and create a new instance of the appropriate proxy class, passing in the new handle in the constructor. It can then pass the new proxy class instance onto the C# AI.

The method calls from C# into C++ contain an additional first parameter, which is the reference number , which allows the C++-side proxy to select the appropriate native object and forward the call, eg to a UnitDef object. The instance methods in the C#-side proxy class will add the additional handle parameter when they call the corresponding static method.

The method calls in the C++ proxy are static, so they can be internal-called from C#, and in a class, to avoid namespace collisions.

= Generator main block =

The generator main block can add each of the types to be generated into an arraylist TypesByVal, ProxiesCppToCs or ProxiesCsToCpp, as appropriate. Then when we call generate:
*it goes through each arraylist and generates the appropriate classes
*when a class undergoing generation uses one of the other classes, the generator can handle this accordingly by checking which arraylist the other classes are in

= Use of attributes =

It's possible to add custom attributes to parameters and methods in the interface classes in CSAIInterfaces.dll . These can be read by the generator and used to tweak the generation.

For example, we could have [MarshallAsCNullTerminatedString] vs [MarshallAsCppStdString].

An attribute is just an empty class that derives from Attribute, eg:

<pre>
[AttributeUsage(AttributeTargets.Parameter, Inherited = false, AllowMultiple = true)]
public class MarshallAsCNullTerminatedString: Attribute
{
// nothing needed here, empty class
}
</pre>

Use of attributes should probably be kept to a minimum, to avoid modifying CSAIInterfaces.dll, but the possibility exists where necessary.

= Hand-Tweaked Code =

It will almost certainly be necessary to add hand-tweaked code to the proxies. For example, GetMetalMap() cannot be easily guessed, because there is no info on the size of the array, and it's not constant either.

Hand-tweaked code could be added by creating a derived class, in C++, from the proxy class one wishes to tweak. This keeps generated code separate from human-written code, so it is easy to regenerate the files as the interfaces change.

The generator will need to know the name of any derived classes so that it can use this in any "new" statements it generates for that proxy.

= Overall =

A plan exists that should probably work. Some code has been written. The devil is in the details.

Writing the Mono bindings will need someone with a good knowledge of the Mono API, the Spring GlobalAI API, C, C++ and C#.
[[Category: AI Dev]]

AI:CSAI

2015-08-09T10:31:30Z

Hughperkins: redirect manageddreams.com to hughperkins.com, and add github repo link

== CSAI ==

CSAI works ok as ARM on land maps, using the AA2.23 or XTA7 mod.

CSAI is written in C#, by Hugh Perkins

== Supported Mods ==

*AA2.23
*XTA7

== Supported Platforms ==

*Windows

== Supported Maps ==

CSAI works best with maps with one large contiguous land segment.

The following maps have been tested and work ok:
*SmallDivide
*CometCatcher Remake v02
*SpeedMetal
*Small Supreme Battlefield

== Screenshots ==

CSAI scout sets off, SSB, XTA7:

[[File:csaivsaai_xta7_ssb_4zippysetsoffsmall.JPG]]

CSAI tanks leave trail of destruction through AAI base, SSB, XTA7:

[[File:csaivsaai_xta7_ssb_23trailofdestructionthroughaaibasesmall.JPG]]

CSAI tanks kill AAI commander on SSB, XTA7:

[[File:csaivsaai_xta7_ssb_25byebyeaaicommandersmall.JPG]]

CSAI (in red) approaches TSI base, SpeedMetal, AA2.23. That plasma beam could cause some pain.

[[File:csaivstsispeedmetal_arriveatbase.JPG]]

Plasma beam down, CSAI overruns TSI base, SpeedMetal, AA2.23.

[[File:csaivstsispeedmetal_2plasmagoneoverrun.JPG]]

CSAI (in red) attacks AAI, SpeedMetal, AA2.23

[[File:speedmetalzergsmall.JPG]]

CSAI units approach TSI base, SmallDivide, AA2.23

[[File:vstsismalldivide_1_attackgroupapproachingbase.JPG]]

CSAI units kill TSI commander, SmallDivide, AA2.23

[[File:vstsismalldivide_6tsicommanderdies.JPG]]

== Replays ==

Here are some replays to give you an impression of how CSAI fights.

CSAI vs AAI 0.75, XTA7:

Small Supreme Battlefield

*[http://hughperkins.com/csai/061026-SmallSupremeBattlefield-0.73b1-0-csai-vs-aai-xta7.sdf http://hughperkins.com/csai/061026-SmallSupremeBattlefield-0.73b1-0-csai-vs-aai-xta7.sdf]

CSAI vs AAI 0.75, AA2.23:

*[http://hughperkins.com/csai/061023-SmallDivide-0.73b1-20.sdf http://hughperkins.com/csai/061023-SmallDivide-0.73b1-20.sdf]
*[http://hughperkins.com/csai/061023-CometCatcherRemake-v02-0.73b1-0.sdf http://hughperkins.com/csai/061023-CometCatcherRemake-v02-0.73b1-0.sdf]
*[http://hughperkins.com/csai/061025-SpeedMetal-0.73b1-2.sdf http://hughperkins.com/csai/061025-SpeedMetal-0.73b1-2.sdf]

CSAI vs TSI 0.12, AA2.23:

*[http://hughperkins.com/csai/061025-CometCatcherRemake-v02-0.73b1-3.sdf http://hughperkins.com/csai/061025-CometCatcherRemake-v02-0.73b1-3.sdf]
*[http://hughperkins.com/csai/061025-SpeedMetal-0.73b1-0-csai-vs-tsi-aa223.sdf http://hughperkins.com/csai/061025-SpeedMetal-0.73b1-0-csai-vs-tsi-aa223.sdf]
*[http://hughperkins.com/csai/061025-SmallDivide-0.73b1-0-csai-vs-tsi-aa223.sdf http://hughperkins.com/csai/061025-SmallDivide-0.73b1-0-csai-vs-tsi-aa223.sdf]

== Downloads ==

Latest release:
*[http://hughperkins.com/csai/CSharpAI-20061028.zip http://hughperkins.com/csai/CSharpAI-20061028.zip]

Previous releases:
*[http://hughperkins.com/csai/CSharpAI_20061026b.zip http://hughperkins.com/csai/CSharpAI_20061026b.zip]
*[http://hughperkins.com/csai/CSharpAI_20061026.zip http://hughperkins.com/csai/CSharpAI_20061026.zip]
*[http://hughperkins.com/csai/CSharpAI_20061025.zip http://hughperkins.com/csai/CSharpAI_20061025.zip]
*[http://hughperkins.com/csai/CSharpAI_20061024.zip http://hughperkins.com/csai/CSharpAI_20061024.zip]

== To Install ==

*Ensure that you have the Microsoft Framework .Net 1.1 runtime installed. You can download this from Microsoft, for free.
*Ensure that you have the latest version of Spring installed, 0.73b.
*Download the latest CSharpAI zipfile from the Downloads section and unzip it.
*Run setup.exe
*Confirm the Spring installation directory
*The CSAI dlls should be automatically installed into the Spring directory

== To use ==

To run the bot:
*create a multiplayer game, using Absolute Annihilation 2.23
*specify start positions as "random" or "fixed"
*click "add bot"
*specify the ai as "csailoader.dll"
*Important: ensure bot plays as ARM

You can find a logfile in the Spring/AI/CSAI directory, called csharpai_team0.log , where 0 is the name of the team

== Commands available ==

You can talk to your AI whilst it plays.

Commands to the ai always start with ".csai ", then the command.

Type ".csai help" for a list of available commands. Here are some of them:

*.csai commanderbuildpower Commander builds a solar cell near him
*.csai commanderbuildextractor Commander builds a metal extractor on nearest available metal spot
*.csai commandermove 0 1000 1500 Move team 0 commander to position (1000,1500)
*.csai commandergetpos Ask for commander's current position
*.csai commanderbuild armvp Ask commander to build a vehicle plant next to him. Use any valid unit name here (see logfile for list) (must be buildable by arm commander)

*.csai killallfriendly Kills all units belonging to AI, except for commander This is sometimes useful during AI testing
*.csai unitcount (countunits?) Shows number of units currently

*.csai showmetalspots Show detected optimal metal extractor positions. Also shows metalspots that have been marked used

*.csai tankscount Find out how many tanks are available
*.csai tanksmoveto 0 500 1000 Move all team 0 tanks to position 500, 1000

*.csai autoshowenemieson Shows detected mobile enemies (samson icon) and static enemies (antinuke icon)

== How to beat CSAI ==

Here are some strategies that will kill the current release of CSAI.

Massive concentration of defense near AI's base:

http://hughperkins.com/csai/screenshots/silpkillcsai-3.JPG

Replay:
[http://hughperkins.com/csai/silp3-061031-Core_Faf-0.73b1-2.sdf http://hughperkins.com/csai/silp3-061031-Core_Faf-0.73b1-2.sdf]

== Known issues ==

*All current released versions: on computers where the regional settings specifies the decimal separator as something other than ".", the metal cache will fail to load correctly. This means the commander will put extractors along the top of the screen and lose. This affects computers in France and Germany.

== Release notes ==

=== Release 28 October ===

C /C# Interface

*corrected critical bug in AICallbackProxy::GetMetalMap()
*augmented number of allowed units to 10000 in AICallbackProxy

CSAI

*(experimental) created setup.exe to facilitate installation

=== Release 26 October 2006 b ===

C /C# Interface
*No changes

CSAI
*created PackCoordinator architecture
*fixed bug that caused infantry factories to shutdown occasionally when playing XTA
*spreadsearch initiated more aggressively

=== Release 26 October 2006 ===

C /C# Interface
*No changes

CSAI
*supports XTA 7
*modified Metal algo to prefer spots which are over actual metal, rather than offset to one side
*(experimental) clearance around metal extractors reduced to improve location precision. NOTE: this may increase unit blocking, to be verified
*you can turn debug on by creating an empty file called "debug.flg" in the ai/csai directory
*(experimental) added search algo for tanks if they havent seen an enemy for about a minute and there's at least 100 of them
*improved radar deployment

=== Release 25 October 2006 ===

C /C# Interface
*No changes

CSAI
*added support for metal maps
*fixed bug with metalspots being marked used even if not
*added constructor controller, to ensure always at least one constructor
*added anti-sticking patch for constructors
*added memory for buildings to enemycontroller (since buildings cant move)
*corrected bugs in enemy selection algorithm
*trimmed cpu resource drain for stuck constructors
*removed default drawing of detected enemies; you can say ".csai autoshowenemieson" to reactivate this
*removed default drawing of planned construction site; you can say ".csai constructorshownextbuildsiteon" to reactivate this
*experimenting with kbot factory
*experimenting with replacing samsons by jethros
*factories no longer announce their creation
*added AttackPackCoordinator to improve pack grouping

=== Release 24 October 2006 ===

C /C# Interface
*CSAI.dll moved to AI/CSAI (only CSAIInterfaces.dll remains in Spring root)
*<csailoaderfilename>.xml config file added, to configure which C# AI dll to load
*batchfile building no longer supported (please use nant)
*added IMoveData
*added IUnitDef.movedata
*added all command constants, eg MOVE, SELFD, to Command.cs
*added operators to Float3
*added UnitIsBusy to AICallback (checks GetCurrentUnitCommands returns empty deque)
*documentation moved to wiki at http://springrts.com/wiki/AI:CSAIInterface

CSAI
*added commands to move commander, and get commander to build things
*logfiles moved to AI/CSAI , in line with AI standards
*batchfile building no longer supported (please use nant)
*UnitController added, to register player-owned units
*FactoryController added, to register player-owned factories
*added port of AF's UnitDefHelp
*added architecture for strategies
*event architecture added to CSAI for unitcreated, unitfinished, unitdamaged, etc
*added PowerController to control energy
*added MetalController to control metal
*added TankController to manage tanks (bootstrapping class only)
*added EnemyController to monitor enemies
*added RadarController to manage radars
*added simple heuristic to prevent commander blocking himself in or factories
*added ScoutController
*added Request system to factories, to decide what to build
*documentation moved to wiki at http://springrts.com/wiki/AI:CSAI

== Developer resources ==

You may wish to extend or modify CSAI. If so, the following pages may be useful:

* github repo: https://github.com/hughperkins/SpringRTS-CSharpAI
*[[CSAI Build Instructions]] How to build CSAI
*[[AI:CSAIInterface]] Information on the C /C# interface
[[Category:AI]]

Maps:Map Designer

2012-02-28T02:06:39Z

Hughperkins:

[[Engine_Development|Development]] < [[Map_development|Map Development]] < {{FULLPAGENAME}}

== MapDesigner, by Hugh Perkins ==

[http://hughperkins.com/csai/MapDesigner.zip Download]

*Supports multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

Source-code repository, in git:

git://github.com/hughperkins/SpringMapDesigner.git

Source-code browser:

http://github.com/hughperkins/SpringMapDesigner/tree/master

Written in C#, using either mono or .net, both work, over gtk.net.

== User interface ==

[image:http://hughperkins.com/csai/mapdesigner3small.JPG]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[Media:http://hughperkins.com/csai/multitextureview1.JPG]

[Media:http://hughperkins.com/csai/multitextureview2.JPG]

[Media:http://hughperkins.com/csai/multitextureview3.JPG]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture. That's because it's the base texture for the map, on top of which the other textures are painted.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[Media:http://hughperkins.com/csai/mapdesignblendediting.JPG]

== Water ==

Areas below zero height will be underwater:

[Media:http://hughperkins.com/csai/mapdesignwater.JPG]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[Media:http://hughperkins.com/csai/slopemap2.JPG]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration
[[Category:Map_making]]

Maps:Map Designer

2012-02-28T02:05:40Z

Hughperkins: /* Concepts */

[[Engine_Development|Development]] < [[Map_development|Map Development]] < {{FULLPAGENAME}}

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Supports multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

Source-code repository, in git:

git://github.com/hughperkins/SpringMapDesigner.git

Source-code browser:

http://github.com/hughperkins/SpringMapDesigner/tree/master

Written in C#, using either mono or .net, both work, over gtk.net.

== User interface ==

[image:http://manageddreams.com/csai/mapdesigner3small.JPG]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[Media:http://hughperkins.com/csai/multitextureview1.JPG]

[Media:http://hughperkins.com/csai/multitextureview2.JPG]

[Media:http://hughperkins.com/csai/multitextureview3.JPG]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture. That's because it's the base texture for the map, on top of which the other textures are painted.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]

== Water ==

Areas below zero height will be underwater:

[Media:http://manageddreams.com/csai/mapdesignwater.JPG]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[Media:http://manageddreams.com/csai/slopemap2.JPG]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration
[[Category:Map_making]]

File:Vstsismalldivide 6tsicommanderdies.JPG

2011-01-12T08:32:45Z

Hughperkins:

File:Vstsismalldivide 1 attackgroupapproachingbase.JPG

2011-01-12T08:32:35Z

Hughperkins:

File:Speedmetalzergsmall.JPG

2011-01-12T08:32:26Z

Hughperkins:

File:Csaivstsispeedmetal 2plasmagoneoverrun.JPG

2011-01-12T08:32:10Z

Hughperkins:

File:Csaivstsispeedmetal arriveatbase.JPG

2011-01-12T08:31:55Z

Hughperkins:

File:Csaivsaai xta7 ssb 25byebyeaaicommandersmall.JPG

2011-01-12T08:31:25Z

Hughperkins: uploaded a new version of "File:Csaivsaai xta7 ssb 25byebyeaaicommandersmall.JPG"

File:Csaivsaai xta7 ssb 23trailofdestructionthroughaaibasesmall.JPG

2011-01-12T08:30:49Z

Hughperkins: uploaded a new version of "File:Csaivsaai xta7 ssb 23trailofdestructionthroughaaibasesmall.JPG"

File:Csaivsaai xta7 ssb 23trailofdestructionthroughaaibasesmall.JPG

2011-01-12T08:29:18Z

Hughperkins:

AI:CSAI

2011-01-12T08:28:58Z

Hughperkins: /* Screenshots */

== CSAI ==

CSAI works ok as ARM on land maps, using the AA2.23 or XTA7 mod.

CSAI is written in C#, by Hugh Perkins

== Supported Mods ==

*AA2.23
*XTA7

== Supported Platforms ==

*Windows

== Supported Maps ==

CSAI works best with maps with one large contiguous land segment.

The following maps have been tested and work ok:
*SmallDivide
*CometCatcher Remake v02
*SpeedMetal
*Small Supreme Battlefield

== Screenshots ==

CSAI scout sets off, SSB, XTA7:

[[File:csaivsaai_xta7_ssb_4zippysetsoffsmall.JPG]]

CSAI tanks leave trail of destruction through AAI base, SSB, XTA7:

[[File:csaivsaai_xta7_ssb_23trailofdestructionthroughaaibasesmall.JPG]]

CSAI tanks kill AAI commander on SSB, XTA7:

[[File:csaivsaai_xta7_ssb_25byebyeaaicommandersmall.JPG]]

CSAI (in red) approaches TSI base, SpeedMetal, AA2.23. That plasma beam could cause some pain.

[[File:csaivstsispeedmetal_arriveatbase.JPG]]

Plasma beam down, CSAI overruns TSI base, SpeedMetal, AA2.23.

[[File:csaivstsispeedmetal_2plasmagoneoverrun.JPG]]

CSAI (in red) attacks AAI, SpeedMetal, AA2.23

[[File:speedmetalzergsmall.JPG]]

CSAI units approach TSI base, SmallDivide, AA2.23

[[File:vstsismalldivide_1_attackgroupapproachingbase.JPG]]

CSAI units kill TSI commander, SmallDivide, AA2.23

[[File:vstsismalldivide_6tsicommanderdies.JPG]]

== Replays ==

Here are some replays to give you an impression of how CSAI fights.

CSAI vs AAI 0.75, XTA7:

Small Supreme Battlefield

*[http://manageddreams.com/csai/061026-SmallSupremeBattlefield-0.73b1-0-csai-vs-aai-xta7.sdf http://manageddreams.com/csai/061026-SmallSupremeBattlefield-0.73b1-0-csai-vs-aai-xta7.sdf]

CSAI vs AAI 0.75, AA2.23:

*[http://manageddreams.com/csai/061023-SmallDivide-0.73b1-20.sdf http://manageddreams.com/csai/061023-SmallDivide-0.73b1-20.sdf]
*[http://manageddreams.com/csai/061023-CometCatcherRemake-v02-0.73b1-0.sdf http://manageddreams.com/csai/061023-CometCatcherRemake-v02-0.73b1-0.sdf]
*[http://manageddreams.com/csai/061025-SpeedMetal-0.73b1-2.sdf http://manageddreams.com/csai/061025-SpeedMetal-0.73b1-2.sdf]

CSAI vs TSI 0.12, AA2.23:

*[http://manageddreams.com/csai/061025-CometCatcherRemake-v02-0.73b1-3.sdf http://manageddreams.com/csai/061025-CometCatcherRemake-v02-0.73b1-3.sdf]
*[http://manageddreams.com/csai/061025-SpeedMetal-0.73b1-0-csai-vs-tsi-aa223.sdf http://manageddreams.com/csai/061025-SpeedMetal-0.73b1-0-csai-vs-tsi-aa223.sdf]
*[http://manageddreams.com/csai/061025-SmallDivide-0.73b1-0-csai-vs-tsi-aa223.sdf http://manageddreams.com/csai/061025-SmallDivide-0.73b1-0-csai-vs-tsi-aa223.sdf]

== Downloads ==

Latest release:
*[http://manageddreams.com/csai/CSharpAI-20061028.zip http://manageddreams.com/csai/CSharpAI-20061028.zip]

Previous releases:
*[http://manageddreams.com/csai/CSharpAI_20061026b.zip http://manageddreams.com/csai/CSharpAI_20061026b.zip]
*[http://manageddreams.com/csai/CSharpAI_20061026.zip http://manageddreams.com/csai/CSharpAI_20061026.zip]
*[http://manageddreams.com/csai/CSharpAI_20061025.zip http://manageddreams.com/csai/CSharpAI_20061025.zip]
*[http://manageddreams.com/csai/CSharpAI_20061024.zip http://manageddreams.com/csai/CSharpAI_20061024.zip]

== To Install ==

*Ensure that you have the Microsoft Framework .Net 1.1 runtime installed. You can download this from Microsoft, for free.
*Ensure that you have the latest version of Spring installed, 0.73b.
*Download the latest CSharpAI zipfile from the Downloads section and unzip it.
*Run setup.exe
*Confirm the Spring installation directory
*The CSAI dlls should be automatically installed into the Spring directory

== To use ==

To run the bot:
*create a multiplayer game, using Absolute Annihilation 2.23
*specify start positions as "random" or "fixed"
*click "add bot"
*specify the ai as "csailoader.dll"
*Important: ensure bot plays as ARM

You can find a logfile in the TASpring/AI/CSAI directory, called csharpai_team0.log , where 0 is the name of the team

== Commands available ==

You can talk to your AI whilst it plays.

Commands to the ai always start with ".csai ", then the command.

Type ".csai help" for a list of available commands. Here are some of them:

*.csai commanderbuildpower Commander builds a solar cell near him
*.csai commanderbuildextractor Commander builds a metal extractor on nearest available metal spot
*.csai commandermove 0 1000 1500 Move team 0 commander to position (1000,1500)
*.csai commandergetpos Ask for commander's current position
*.csai commanderbuild armvp Ask commander to build a vehicle plant next to him. Use any valid unit name here (see logfile for list) (must be buildable by arm commander)

*.csai killallfriendly Kills all units belonging to AI, except for commander This is sometimes useful during AI testing
*.csai unitcount (countunits?) Shows number of units currently

*.csai showmetalspots Show detected optimal metal extractor positions. Also shows metalspots that have been marked used

*.csai tankscount Find out how many tanks are available
*.csai tanksmoveto 0 500 1000 Move all team 0 tanks to position 500, 1000

*.csai autoshowenemieson Shows detected mobile enemies (samson icon) and static enemies (antinuke icon)

== How to beat CSAI ==

Here are some strategies that will kill the current release of CSAI.

Massive concentration of defense near AI's base:

[[Media:http://manageddreams.com/csai/screenshots/silpkillcsai-3.JPG]]

Replay:
[http://manageddreams.com/csai/silp3-061031-Core_Faf-0.73b1-2.sdf http://manageddreams.com/csai/silp3-061031-Core_Faf-0.73b1-2.sdf]

== Known issues ==

*All current released versions: on computers where the regional settings specifies the decimal separator as something other than ".", the metal cache will fail to load correctly. This means the commander will put extractors along the top of the screen and lose. This affects computers in France and Germany.

== Release notes ==

=== Release 28 October ===

C /C# Interface

*corrected critical bug in AICallbackProxy::GetMetalMap()
*augmented number of allowed units to 10000 in AICallbackProxy

CSAI

*(experimental) created setup.exe to facilitate installation

=== Release 26 October 2006 b ===

C /C# Interface
*No changes

CSAI
*created PackCoordinator architecture
*fixed bug that caused infantry factories to shutdown occasionally when playing XTA
*spreadsearch initiated more aggressively

=== Release 26 October 2006 ===

C /C# Interface
*No changes

CSAI
*supports XTA 7
*modified Metal algo to prefer spots which are over actual metal, rather than offset to one side
*(experimental) clearance around metal extractors reduced to improve location precision. NOTE: this may increase unit blocking, to be verified
*you can turn debug on by creating an empty file called "debug.flg" in the ai/csai directory
*(experimental) added search algo for tanks if they havent seen an enemy for about a minute and there's at least 100 of them
*improved radar deployment

=== Release 25 October 2006 ===

C /C# Interface
*No changes

CSAI
*added support for metal maps
*fixed bug with metalspots being marked used even if not
*added constructor controller, to ensure always at least one constructor
*added anti-sticking patch for constructors
*added memory for buildings to enemycontroller (since buildings cant move)
*corrected bugs in enemy selection algorithm
*trimmed cpu resource drain for stuck constructors
*removed default drawing of detected enemies; you can say ".csai autoshowenemieson" to reactivate this
*removed default drawing of planned construction site; you can say ".csai constructorshownextbuildsiteon" to reactivate this
*experimenting with kbot factory
*experimenting with replacing samsons by jethros
*factories no longer announce their creation
*added AttackPackCoordinator to improve pack grouping

=== Release 24 October 2006 ===

C /C# Interface
*CSAI.dll moved to AI/CSAI (only CSAIInterfaces.dll remains in Spring root)
*<csailoaderfilename>.xml config file added, to configure which C# AI dll to load
*batchfile building no longer supported (please use nant)
*added IMoveData
*added IUnitDef.movedata
*added all command constants, eg MOVE, SELFD, to Command.cs
*added operators to Float3
*added UnitIsBusy to AICallback (checks GetCurrentUnitCommands returns empty deque)
*documentation moved to wiki at http://taspring.clan-sy.com/wiki/AI:CSAIInterface

CSAI
*added commands to move commander, and get commander to build things
*logfiles moved to AI/CSAI , in line with AI standards
*batchfile building no longer supported (please use nant)
*UnitController added, to register player-owned units
*FactoryController added, to register player-owned factories
*added port of AF's UnitDefHelp
*added architecture for strategies
*event architecture added to CSAI for unitcreated, unitfinished, unitdamaged, etc
*added PowerController to control energy
*added MetalController to control metal
*added TankController to manage tanks (bootstrapping class only)
*added EnemyController to monitor enemies
*added RadarController to manage radars
*added simple heuristic to prevent commander blocking himself in or factories
*added ScoutController
*added Request system to factories, to decide what to build
*documentation moved to wiki at http://taspring.clan-sy.com/wiki/AI:CSAI

== Developer resources ==

You may wish to extend or modify CSAI. If so, the following pages may be useful:

*[[CSAI Build Instructions]] How to build CSAI
*[[AI:CSAIInterface]] Information on the C /C# interface
[[Category:AI]]

File:Csaivsaai xta7 ssb 4zippysetsoffsmall.JPG

2011-01-12T08:28:00Z

Hughperkins:

File:Csaivsaai xta7 ssb 25byebyeaaicommandersmall.JPG

2011-01-12T08:26:39Z

Hughperkins:

AI:HughAI

2009-09-21T06:05:47Z

Hughperkins: /* To install */

== What is HughAI ==

HughAI is a an AI written in Java. Works quite well at fast rush attacks.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI20090921b.tar.bz2

2. Remove any old AI/Skirmish/HughAI directory

3. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

4. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

Works with BA mod, with the AI running as ARM.

== Play-style ==

It's a non-cheating AI by day ... but if you go to the 'Config' tab on the gui and tick the box next to 'maphack' and then click 'apply' or 'save' ... it will become a cheating maphack AI!

Otherwise, its playstyle is essentially to rush. If it doesn't beat you within a few minutes, it's basically not going to do very much else just yet ;-) Maybe in the future though ;-)

== Cheating / maphack ==

In the gui, in the 'config' tab, click 'maphack' then 'apply' or 'save' to enable maphack.

Unclick it, and then 'apply' or 'save' to disable it.

== To disable gui ==

Either:

- run spring in windowed mode, in the gui, in the config tab, unclick 'guiactivated' and then click 'save', or
- in the config file BA_2.xml, change guiactivated from 'yes' to 'no'.

== Can it beat other AIs? ==

Yes ;-) Replays against E323:

1. against E323 from mid-August:

http://manageddreams.com/hughaireplays/HughAIbeatsE323.tar.bz2

2. against E323 v2.12.0:

http://manageddreams.com/hughaireplays/hughaivse323_sep14.tar.bz2

== Configuration ==

There is a gui with a tab 'Config' that can be used to configure many things.

A few extra things are configurable in the config file 'BA_<side>.xml' , in the AI's directory, where side is core or arm.

There are also a number of workflow xml files in the BA_<side>workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Survive the initial rush, and it will probably not do too much else.

== Console ==

For techies, there's a console, where you can directly write Java code:

[Media:http://manageddreams.com/hughai/ConsoleInAction2.png]

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources, which I try to keep somewhat up-to-date, but really, if you have any questions, just ask me ;-)

AI:HughAI

2009-09-21T05:19:53Z

Hughperkins: /* Configuration */

== What is HughAI ==

HughAI is a an AI written in Java. Works quite well at fast rush attacks.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI20090921.tar.bz2

2. Remove any old AI/Skirmish/HughAI directory

3. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

4. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

Works with BA mod, with the AI running as ARM.

== Play-style ==

It's a non-cheating AI by day ... but if you go to the 'Config' tab on the gui and tick the box next to 'maphack' and then click 'apply' or 'save' ... it will become a cheating maphack AI!

Otherwise, its playstyle is essentially to rush. If it doesn't beat you within a few minutes, it's basically not going to do very much else just yet ;-) Maybe in the future though ;-)

== Cheating / maphack ==

In the gui, in the 'config' tab, click 'maphack' then 'apply' or 'save' to enable maphack.

Unclick it, and then 'apply' or 'save' to disable it.

== To disable gui ==

Either:

- run spring in windowed mode, in the gui, in the config tab, unclick 'guiactivated' and then click 'save', or
- in the config file BA_2.xml, change guiactivated from 'yes' to 'no'.

== Can it beat other AIs? ==

Yes ;-) Replays against E323:

1. against E323 from mid-August:

http://manageddreams.com/hughaireplays/HughAIbeatsE323.tar.bz2

2. against E323 v2.12.0:

http://manageddreams.com/hughaireplays/hughaivse323_sep14.tar.bz2

== Configuration ==

There is a gui with a tab 'Config' that can be used to configure many things.

A few extra things are configurable in the config file 'BA_<side>.xml' , in the AI's directory, where side is core or arm.

There are also a number of workflow xml files in the BA_<side>workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Survive the initial rush, and it will probably not do too much else.

== Console ==

For techies, there's a console, where you can directly write Java code:

[Media:http://manageddreams.com/hughai/ConsoleInAction2.png]

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources, which I try to keep somewhat up-to-date, but really, if you have any questions, just ask me ;-)

AI:HughAI

2009-09-21T05:19:10Z

Hughperkins: /* To install */

== What is HughAI ==

HughAI is a an AI written in Java. Works quite well at fast rush attacks.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI20090921.tar.bz2

2. Remove any old AI/Skirmish/HughAI directory

3. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

4. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

Works with BA mod, with the AI running as ARM.

== Play-style ==

It's a non-cheating AI by day ... but if you go to the 'Config' tab on the gui and tick the box next to 'maphack' and then click 'apply' or 'save' ... it will become a cheating maphack AI!

Otherwise, its playstyle is essentially to rush. If it doesn't beat you within a few minutes, it's basically not going to do very much else just yet ;-) Maybe in the future though ;-)

== Cheating / maphack ==

In the gui, in the 'config' tab, click 'maphack' then 'apply' or 'save' to enable maphack.

Unclick it, and then 'apply' or 'save' to disable it.

== To disable gui ==

Either:

- run spring in windowed mode, in the gui, in the config tab, unclick 'guiactivated' and then click 'save', or
- in the config file BA_2.xml, change guiactivated from 'yes' to 'no'.

== Can it beat other AIs? ==

Yes ;-) Replays against E323:

1. against E323 from mid-August:

http://manageddreams.com/hughaireplays/HughAIbeatsE323.tar.bz2

2. against E323 v2.12.0:

http://manageddreams.com/hughaireplays/hughaivse323_sep14.tar.bz2

== Configuration ==

There is a gui with a tab 'Config' that can be used to configure many things.

A few extra things are configurable in the config file 'BA_2.xml' , in the AI's directory.

There are also a number of workflow xml files in the BA_workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Survive the initial rush, and it will probably not do too much else.

== Console ==

For techies, there's a console, where you can directly write Java code:

[Media:http://manageddreams.com/hughai/ConsoleInAction2.png]

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources, which I try to keep somewhat up-to-date, but really, if you have any questions, just ask me ;-)

AI:HughAI

2009-09-14T05:20:44Z

Hughperkins:

== What is HughAI ==

HughAI is a an AI written in Java. Works quite well at fast rush attacks.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI_20090914.tar.bz2

2. Remove any old AI/Skirmish/HughAI directory

3. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

4. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

Works with BA mod, with the AI running as ARM.

== Play-style ==

It's a non-cheating AI by day ... but if you go to the 'Config' tab on the gui and tick the box next to 'maphack' and then click 'apply' or 'save' ... it will become a cheating maphack AI!

Otherwise, its playstyle is essentially to rush. If it doesn't beat you within a few minutes, it's basically not going to do very much else just yet ;-) Maybe in the future though ;-)

== Cheating / maphack ==

In the gui, in the 'config' tab, click 'maphack' then 'apply' or 'save' to enable maphack.

Unclick it, and then 'apply' or 'save' to disable it.

== To disable gui ==

Either:

- run spring in windowed mode, in the gui, in the config tab, unclick 'guiactivated' and then click 'save', or
- in the config file BA_2.xml, change guiactivated from 'yes' to 'no'.

== Can it beat other AIs? ==

Yes ;-) Replays against E323:

1. against E323 from mid-August:

http://manageddreams.com/hughaireplays/HughAIbeatsE323.tar.bz2

2. against E323 v2.12.0:

http://manageddreams.com/hughaireplays/hughaivse323_sep14.tar.bz2

== Configuration ==

There is a gui with a tab 'Config' that can be used to configure many things.

A few extra things are configurable in the config file 'BA_2.xml' , in the AI's directory.

There are also a number of workflow xml files in the BA_workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Survive the initial rush, and it will probably not do too much else.

== Console ==

For techies, there's a console, where you can directly write Java code:

[Media:http://manageddreams.com/hughai/ConsoleInAction2.png]

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources, which I try to keep somewhat up-to-date, but really, if you have any questions, just ask me ;-)

AI:HughAI

2009-09-14T05:17:05Z

Hughperkins:

== What is HughAI ==

HughAI is a an AI written in Java. Works quite well at fast rush attacks.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI_20090914.tar.bz2

2. Remove any old AI/Skirmish/HughAI directory

3. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

4. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

Works with BA mod, with the AI running as ARM.

== Play-style ==

It's a non-cheating AI by day ... but if you go to the 'Config' tab on the gui and tick the box next to 'maphack' and then click 'apply' or 'save' ... it will become a cheating maphack AI!

Otherwise, its playstyle is essentially to rush. If it doesn't beat you within a few minutes, it's basically not going to do very much else just yet ;-) Maybe in the future though ;-)

== Can it beat other AIs? ==

Yes ;-) Replays against E323:

1. against E323 from mid-August:

http://manageddreams.com/hughaireplays/HughAIbeatsE323.tar.bz2

2. against E323 v2.12.0:

http://manageddreams.com/hughaireplays/hughaivse323_sep14.tar.bz2

== Configuration ==

There is a gui with a tab 'Config' that can be used to configure many things.

A few extra things are configurable in the config file 'BA_2.xml' , in the AI's directory.

There are also a number of workflow xml files in the BA_workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Survive the initial rush, and it will probably not do too much else.

== Console ==

For techies, there's a console, where you can directly write Java code:

[Media:http://manageddreams.com/hughai/ConsoleInAction2.png]

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources, which I try to keep somewhat up-to-date, but really, if you have any questions, just ask me ;-)

AI:HughAI

2009-09-09T10:08:25Z

Hughperkins: minor formatting

== What is HughAI ==

HughAI is a Java port of CSAI2, which was a partially refactored version of [[AI:CSAI]], a fast rush AI, written in C#, by Hugh Perkins.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI.2009sep09.tar.bz2

2. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

3. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

It only really works with Balanced Annihilation, unless you start to tweak the config files.

== Play-style ==

It's a non-cheating AI by day ... but if you go to the 'Config' tab on the gui and tick the box next to 'maphack' and then click 'apply' or 'save' ... it will become a cheating maphack AI!

Otherwise, its playstyle is essentially to rush. If it doesn't beat you within a few minutes, it's basically not going to do very much else just yet ;-) Maybe in the future though ;-)

== Can it beat other AIs? ==

Yes ;-) Replay against E323:

http://manageddreams.com/hughaireplays/HughAIbeatsE323.tar.bz2

Of course, it's all a bit fragile, and there's a lot of luck involved, so I'm sure it's pretty easy to make a replay of E323 being the winning AI :-D

== Configuration ==

There is a gui with a tab 'Config' that can be used to configure many things.

A few extra things are configurable in the config file 'BA_2.xml' , in the AI's directory.

There are also a number of workflow xml files in the BA_workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Survive the initial rush, and it will probably not do too much else.

== Console ==

For techies, there's a console, where you can directly write Java code:

[Media:http://manageddreams.com/hughai/ConsoleInAction2.png]

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources, which I tree to keep somewhat up-to-date, but really, if you have any questions, just ask me ;-)

AI:HughAI

2009-09-09T10:07:56Z

Hughperkins: Updated with today's changes, and a replay vs E323 ;-)

== What is HughAI ==

HughAI is a Java port of CSAI2, which was a partially refactored version of [[AI:CSAI]], a fast rush AI, written in C#, by Hugh Perkins.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI.2009sep09.tar.bz2

2. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

3. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

It only really works with Balanced Annihilation, unless you start to tweak the config files.

== Play-style ==

It's a non-cheating AI by day ... but if you go to the 'Config' tab on the gui and tick the box next to 'maphack' and then click 'apply' or 'save' ... it will become a cheating maphack AI!

Otherwise, its playstyle is essentially to rush. If it doesn't beat you within a few minutes, it's basically not going to do very much else just yet ;-) Maybe in the future though ;-)

Can it beat other AIs?
======================

Yes ;-) Replay against E323:

http://manageddreams.com/hughaireplays/HughAIbeatsE323.tar.bz2

Of course, it's all a bit fragile, and there's a lot of luck involved, so I'm sure it's pretty easy to make a replay of E323 being the winning AI :-D

== Configuration ==

There is a gui with a tab 'Config' that can be used to configure many things.

A few extra things are configurable in the config file 'BA_2.xml' , in the AI's directory.

There are also a number of workflow xml files in the BA_workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Survive the initial rush, and it will probably not do too much else.

== Console ==

For techies, there's a console, where you can directly write Java code:

[Media:http://manageddreams.com/hughai/ConsoleInAction2.png]

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources, which I tree to keep somewhat up-to-date, but really, if you have any questions, just ask me ;-)

AI:HughAI

2009-09-07T12:33:41Z

Hughperkins: minor forrmatting

== What is HughAI ==

HughAI is a Java port of CSAI2, which was a partially refactored version of [[AI:CSAI]], a fast rush AI, written in C#, by Hugh Perkins.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI.tar.bz2

2. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

3. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

It only really works with Balanced Annihilation, unless you start to tweak the config files.

== Play-style ==

It's a non-cheating AI. It sends out scouts to locate the enemy. It attacks with a pack of units, and withdraws them if too many die. That's it for now ;-) It did ok in its C# form. It's currently undergoing quite a lot of mutation, and it's becoming quite configurable, so it's early days yet.

== Configuration ==

There is a per-mod configuration file in the AI directory, with a version postfix, currently _2, ie:

BA_2.xml

This can be used to tweak the names of certain default and basic units.

There are also a number of workflow xml files in the BA_workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Currently, no threatmap, so just dump some really powerful defense in its way, and it'll obsessively throw itself against it.

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources:

http://github.com/hughperkins/HughAI/blob/f23bf8cb4353d5577599f0c531474d36342fba11/src-ai/architecture.txt

AI:HughAI

2009-09-07T10:59:22Z

Hughperkins: Wrote it more from the poitn of view of a user than a developer

== What is HughAI ==

HughAI is a Java port of CSAI2, which was a partially refactored version of [[AI:CSAI]], a fast rush AI, written in C#, by Hugh Perkins.

== To install ==

To install

Make sure you have hoijui's Java Interface v0.1 installed. I believe this is installed automatically if you have Windows. Other platforms may have varying mileage.

Once you have Java Interface 0.1 installed ok:

1. Download HughAI from:

http://manageddreams.com/hughai/HughAI.tar.bz2

2. untar (using Winzip or your favorite zip utility) into AI/Skirmish, so you should have the following directory structure:

AI/
Skirmish/
HughAI/
0.1/
SkirmishAI.jar
... other files ...

3. Run springlobby, create a single-player game, and do "add-bot"

Note that the AI needs to be playing as Arm, and on Balanced Annihilation. On anything else, it will probably just sit there and do nothing :-D

It's fairly early days yet, so don't expect too much just yet ;-) I'll update this message as it gets better.

== Mods and maps ==

It only really works with Balanced Annihilation, unless you start to tweak the config files.

== Play-style ==

It's a non-cheating AI. It sends out scouts to locate the enemy. It attacks with a pack of units, and withdraws them if too many die. That's it for now ;-) It did ok in its C# form. It's currently undergoing quite a lot of mutation, and it's becoming quite configurable, so it's early days yet.

== Configuration ==

There is a per-mod configuration file in the AI directory, with a version postfix, currently _2, ie:

BA_2.xml

This can be used to tweak the names of certain default and basic units.

There are also a number of workflow xml files in the BA_workflows subdirectory. Currently, only one of the workflows are used, so there's no point in adding more than one for now ;-) In the future, it might simply randomly select from one, at random, so a human enemy doesn't know if the AI will tech or rush or whatever. Sounds reasonable?

The workflow config files define what will get built essentially, with a priority, a unitname, and a quantity.

The higher the priority, the earlier the units will be built.

You can add in the same unit on multiple lines, with different priorities, so you can say: ok, first build a couple of stumpies, then a jeffy, then some more stumpies, or whatever.

== Limitations /ways to beat it ==

Currently, no threatmap, so just dump some really powerful defense in its way, and it'll obsessively throw itself against it.

== Soure-code ==

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git
http://github.com/hughperkins/HughAI/tree/master

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources:

http://github.com/hughperkins/HughAI/blob/f23bf8cb4353d5577599f0c531474d36342fba11/src-ai/architecture.txt

AI:HughAI

2009-09-06T14:45:38Z

Hughperkins: added link to

HughAI is a Java port of CSAI2, which was a partially refactored version of [[AI:CSAI]], a fast rush AI, written in C#, by Hugh Perkins.

It is not quite ready for use as a fun interesting opponent in a real game, but it could be fun to play with by developers. It includes a bunch of classes for deriving maps, such as slope maps, movement area maps, and los maps, from the data made available to the AI.

It contains a GUI written in Swing, to which classes can subscribe, registering the name of a button, and a handler method to be called.

Similarly, chat commands can be registered by the AI classes.

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources:

http://github.com/hughperkins/HughAI/blob/f23bf8cb4353d5577599f0c531474d36342fba11/src-ai/architecture.txt

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git

Web browser page:

http://github.com/hughperkins/HughAI/tree/master

The AI uses hoijui's Java Interface v0.1.

Maps:Map Designer

2009-09-06T14:42:02Z

Hughperkins: corrected links

[[Engine_Development|Development]] < [[Map_development|Map Development]] < {{FULLPAGENAME}}

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Supports multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

Source-code repository, in git:

git://github.com/hughperkins/SpringMapDesigner.git

Source-code browser:

http://github.com/hughperkins/SpringMapDesigner/tree/master

Written in C#, using either mono or .net, both work, over gtk.net.

== User interface ==

[image:http://manageddreams.com/csai/mapdesigner3small.JPG]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[Media:http://manageddreams.com/csai/multitextureview1.JPG]

[Media:http://manageddreams.com/csai/multitextureview2.JPG]

[Media:http://manageddreams.com/csai/multitextureview3.JPG]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture. That's because it's the base texture for the map, on top of which the other textures are painted.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]

== Water ==

Areas below zero height will be underwater:

[Media:http://manageddreams.com/csai/mapdesignwater.JPG]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[Media:http://manageddreams.com/csai/slopemap2.JPG]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

Maps:Map Designer

2009-09-06T14:39:46Z

Hughperkins: /* Concepts */ corrected links

[[Engine_Development|Development]] < [[Map_development|Map Development]] < {{FULLPAGENAME}}

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Supports multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

Source-code repository, in git:

git://github.com/hughperkins/SpringMapDesigner.git

Source-code browser:

http://github.com/hughperkins/SpringMapDesigner/tree/master

Written in C#, using either mono or .net, both work, over gtk.net.

== User interface ==

[image:http://manageddreams.com/csai/mapdesigner3small.JPG]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[Media:http://manageddreams.com/csai/multitextureview1.JPG]

[Media:http://manageddreams.com/csai/multitextureview2.JPG]

[Media:http://manageddreams.com/csai/multitextureview3.JPG]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture. That's because it's the base texture for the map, on top of which the other textures are painted.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]]

== Water ==

Areas below zero height will be underwater:

[[Media:http://manageddreams.com/csai/mapdesignwater.JPG]]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[[Media:http://manageddreams.com/csai/slopemap2.JPG]]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

Maps:Map Designer

2009-09-06T14:39:15Z

Hughperkins: /* MapDesigner, by Hugh Perkins */ added new repository

[[Engine_Development|Development]] < [[Map_development|Map Development]] < {{FULLPAGENAME}}

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Supports multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

Source-code repository, in git:

git://github.com/hughperkins/SpringMapDesigner.git

Source-code browser:

http://github.com/hughperkins/SpringMapDesigner/tree/master

Written in C#, using either mono or .net, both work, over gtk.net.

== User interface ==

[image:http://manageddreams.com/csai/mapdesigner3small.JPG]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[[Media:http://manageddreams.com/csai/multitextureview1.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview2.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview3.JPG]]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture. That's because it's the base texture for the map, on top of which the other textures are painted.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]]

== Water ==

Areas below zero height will be underwater:

[[Media:http://manageddreams.com/csai/mapdesignwater.JPG]]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[[Media:http://manageddreams.com/csai/slopemap2.JPG]]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

Maps:Map Designer

2009-09-06T14:36:57Z

Hughperkins: /* User interface */ corrected link

[[Engine_Development|Development]] < [[Map_development|Map Development]] < {{FULLPAGENAME}}

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Supports multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

== User interface ==

[image:http://manageddreams.com/csai/mapdesigner3small.JPG]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[[Media:http://manageddreams.com/csai/multitextureview1.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview2.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview3.JPG]]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture. That's because it's the base texture for the map, on top of which the other textures are painted.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]]

== Water ==

Areas below zero height will be underwater:

[[Media:http://manageddreams.com/csai/mapdesignwater.JPG]]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[[Media:http://manageddreams.com/csai/slopemap2.JPG]]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

AI:HughAI

2009-09-06T14:21:00Z

Hughperkins: added link to architecture.txt

HughAI is a Java port of CSAI2, which was a partially refactored version of CSAI, a fast rush AI, written in C#, by Hugh Perkins.

It is not quite ready for use as a fun interesting opponent in a real game, but it could be fun to play with by developers. It includes a bunch of classes for deriving maps, such as slope maps, movement area maps, and los maps, from the data made available to the AI.

It contains a GUI written in Swing, to which classes can subscribe, registering the name of a button, and a handler method to be called.

Similarly, chat commands can be registered by the AI classes.

More details on the architecture can be found in the file src-ai/architecture.txt, in the sources:

http://github.com/hughperkins/HughAI/blob/f23bf8cb4353d5577599f0c531474d36342fba11/src-ai/architecture.txt

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git

Web browser page:

http://github.com/hughperkins/HughAI/tree/master

The AI uses hoijui's Java Interface v0.1.

AI:HughAI

2009-09-06T14:11:16Z

Hughperkins: Created new page for HughAI

HughAI is a Java port of CSAI2, which was a partially refactored version of CSAI, a fast rush AI, written in C#, by Hugh Perkins.

It is not quite ready for use as a fun interesting opponent in a real game, but it could be fun to play with by developers. It includes a bunch of classes for deriving maps, such as slope maps, movement area maps, and los maps, from the data made available to the AI.

It contains a GUI written in Swing, to which classes can subscribe, registering the name of a button, and a handler method to be called.

Similarly, chat commands can be registered by the AI classes.

More details on the architecture can be found in the file Architecture.txt, in the sources.

The sources are available from the following git repository:

git://github.com/hughperkins/HughAI.git

Web browser page:

http://github.com/hughperkins/HughAI/tree/master

The AI uses hoijui's Java Interface v0.1.

AI:Skirmish:List

2009-09-06T14:06:31Z

Hughperkins: /* Under Active Development */ added HughAI

[[Main_Page|Main Page]] < AIs

Basics about [[AI:Skirmish|Skirmish AIs]] in Spring.

==== Under Active Development ====
Listed in alphabetical order.

; '''[[AI:AAI|AAI]]''' : config-based, by [[User:Submarine|Submarine]] 
; '''[[AI:BKPAI|BKPAI]]''' : config-less, Kernel Panic only, by Baczek 
; '''[[AI:HughAI|HughAI]]''' : config-based, Java port of CSAI, by Hugh Perkins 
; '''[[AI:KAIK|KAIK]]''' : config-less, most competitive AI for BA, based on [[AI:KAI|KAI]] by Krogothe, now developed by Kloot 
; '''[[AI:NTAI|NTai]]''' : config-based, the longest running AI, currently non-functional, by [[User:AF|AF]] 
; '''[[AI:RAI|RAI]]''' : config-less, supports more mods then KAIK, by Reth 
; '''[[AI:C.R.A.I.G.|C.R.A.I.G.]]''' : config-based, currently [http://spring1944.net/ Spring 1944] and [http://www.imperialwinter.com/ SWIW] only, by Tobi 

==== Special ====

; '''[[AI:NullAI|NullAI]]''' : C Test AI, does nothing 
; '''[[AI:NullLegacyCppAI|NullLegacyCppAI]]''' : Legacy C++ Test AI, does nothing 
; '''[[AI:NullJavaAI|NullJavaAI]]''' : basic Java Test AI, does nothing 
; '''[[AI:NullOOJavaAI|NullOOJavaAI]]''' : Java Test AI using the OO wrapper, does nothing 
; '''[[Random enemies]]''' : Generates random enemies at enemy starting positions who then seek you out. This is not really a Skirmish AI, but rather what was in place before Skirmish AIs for spring existed. 

==== No Longer Under Development ====
None of these AIs will work with the current spring release version.
They are listed here, in case someone wants to take up development again,
and for code reference.

; '''[[AI:CSAI|CSAI]]''' : C# AI, by Hugh Perkins 
; '''[[AI:JAI|JAI]]''' : first try at writing an AI in Java, by [[User:hoijui|hoijui]] 
; '''[[AI:JCAI|JCAI]]''' : by Zaphod 
; '''[[AI:KAI|KAI]]''' : by Krogothe 
; '''[[AI:MyAI|MyAI]]''' : An earlier AI, by Berion 
; '''[[AI:OTAI|OTAI]]''' : V1.13, An AI aimed at emulating the AI in OTA, by Veylon 
; '''[[AI:QAI|QAI]]''' : V2.42, A half finished AI, by Qman 
; '''[[AI:SAI|SAI]]''' : V0.15, by Spectre 
; '''[[AI:TSI|TSI]]''' : A Polish project, originally based on [[AI:SAI|SAI]] 
; '''[[AI:TAI|TAI]]''' : replaced by [[AI:NTAI|NTai]], by [[User:AF|AF]] 
; '''[[AI:ZcAIn|ZcAIn]]''' : by Cain 

==== Planned For Development ====
; '''[[AI:Epic|Epic]]''' : Next Gen AI, planned by [[User:AF|AF]] 
; '''[[AI:GAI|GAI]]''' : Groovy AI, planned by Agon & [[User:hoijui|hoijui]] 

[[Category: AI]]

Building Spring on Linux

2009-09-06T14:05:18Z

Hughperkins: /* Full list */ added name of 7zip ubuntu package 'p7zip-full'

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Build From Source on Linux =
If prefer to use your distributions package system, refer to the Linux [[SetupGuide]].

If there is no package tailored for your distribution, you have to install from sources manually. Doing this for distributions where packages are available is not recommended.

'''Warning: Be carefull when building from source. You might encounter sync errors in online play if you are using special compilers (all GCC from the 4.x series should be safe) or unstandard compiler settings (be carefull about -march)!'''
 

==Obtaining the Source ==
{{Obtaining_The_Source_Code}}

= Get Dependencies =

You will need to install some development packages Spring depends on. These vary from distro to distro and may also depend on your specific configuration.

If your distributions is not listed below, you should be able to figure out the correct package names from this. The scons configure will whine if you forget something, but it does not check if you remembered to install zip, even though you still need it.

== Full list ==
* Programs necessary to build
** cmake (or scons)
** 7zip (aka p7zip (package 'p7zip-full' on Ubuntu))
** The usual build toolchain
*** gcc
*** make
* Libraries
** SDL
** boost (version 1.35 or later)
*** threads
*** regex
*** signals
*** system
** DeviL (IL, ILU)
** OpenAL (openal-soft, older openal-0.0.8 does not work)
** OpenGL headers (mesa, glew, etc.)
** zlib
** freetype
** ogg,vorbis and vorbisfile
* Optional, for bindings and Ais
** Python (2.5)
** Java-SDK

== Debian ==

For Etch (debian 4.0 stable) and Sid (debian unstable), I've confirmed the
following to be the minimal set that is necessary to get. This works with Ubuntu 8.10, too.
The version of spring from git repository depends on boost at least version 1.35.* (if your distro is behind you can try [https://launchpad.net/~pgquiles/+archive/ppa some unofficial backports]) and won't work on lower versions.

Also, on 64-bit be sure to build against devIl 1.6.8-rc2 or higher, 1.6.7 has a bug in the PNG loading code that causes issues.

<code><pre>
sudo aptitude install build-essential zlib1g-dev libfreetype6-dev
sudo aptitude install libsdl1.2-dev libopenal-dev libglew-dev libboost-dev
sudo aptitude install libboost-thread-dev libboost-regex-dev libdevil-dev
sudo aptitude install libboost-serialization-dev zip
sudo aptitude install libboost-program-options-dev
sudo aptitude install libvorbis-dev libxcursor-dev
</pre></code>
and either scons and python2.5-dev or cmake, depending on what you use for building (I advise to use cmake). On debian 5.0 (lenny), libglew1.5-dev is required as well.

== Gentoo ==
This has been tested to work with a clean install of gentoo 2008.0:

<code><pre>
emerge cmake \>=media-libs/freetype-2.0.0 \>=media-libs/libsdl-1.2.0
emerge media-libs/openal media-libs/glew dev-libs/boost
emerge app-arch/zip media-libs/libogg
USE="png jpg tiff opengl" emerge media-libs/devil
</pre></code>

== Fedora ==

On Fedora 8, these dependencies should be sufficient:

<code><pre>
yum install cmake boost-devel openal-devel SDL-devel \
DevIL-devel glew-devel libvorbis-devel
</pre></code>

= Build And Install =

== Using CMake (2.6 or newer) ==
Configure and build:

<code><pre>
cmake .
make
</pre></code>

Install:

<code><pre>
make install
</pre></code>

Your paths are: Spring executable in <code>/usr/local/games/spring</code> and
read-only data in <code>/usr/local/share/games/spring</code>.

== Using Scons ==
Configure and build:

<code><pre>
scons configure
scons
</pre></code>

Install:

<code><pre>
scons install
</pre></code>

 
{{Finalizing_linux_install}}

 
{{Troubleshooting_linux}}

[[Category:Compiling]]

Lua:Main

2008-11-07T06:11:25Z

Hughperkins:

'''Lua FAQ''' 
[[Lua_Beginners_FAQ]] 
[[:Category:Lua]] (shows which interfaces are loaded by LuaUI,LuaRules,etc.) 
[http://spring.clan-sy.com/phpbb/viewtopic.php?f=23&t=15596 Forum topic with some basic information about gadgets] 
[http://spring.clan-sy.com/phpbb/viewtopic.php?f=23&t=16223 Forum topic with a manual on Spring lua scripting] 

'''Interfaces''' (last update: 76b1) 
{{LuaInterfaces}}
 
'''Other useful tables''' 
[[LuaCallinReturn]] 
[[WeaponDefNames]] 
[[UnitDefNames]]

'''Official Lua documentation''' 
[http://www.lua.org/pil/ 'Programming in Lua' book online] 
[http://www.lua.org/manual/5.1/ Lua 5.1 Reference manual] 
[http://lua-users.org/wiki/TutorialDirectory Lua tutorials]

'''old Wikis''' (outdated) 
[[Lua_SyncedInterface]] 
[[Units:LuaCOB]] 
[[Lua_Startscripts]]

SpringEngineTODO

2008-11-07T05:55:40Z

Hughperkins:

'''This page is badly out of date. Some of these items have been done, abandoned or replaced with better ideas.'''

Here is a TODO list for anyone interested in developing the spring code. If you are not involved in the development, please contact one of the developers first before you add things here.

* Implement saving/loading. There are a lot of direct LoadSave() functions in the game code, but the easier way would probably to finish the serialization in the class registration type interfaces (rts/System/creg), so everything can be serialized automatically.

* [[Syncing System|Implement re-sync]]. After a sync problem is detected, and a re-sync of the random seed does not fix it the game would pause and use the rsync to adjust game state (current plan if for float3 data) to resync, as suggested by Jesse Schoch in [http://lolut.utbm.info/pipermail/taspring-linux/2006-February/000810.html]. After using rsync on it should be able to continue normally until the next sync error is detected.

* Abstract and improve unit rendering:
** 3DO/S3O support is not abstracted, many parts of unit rendering are spread throughout spring and assume 3DO, and the rendering is a messy mixture of 3DO and S3O stuff. Abstracting the model rendering with a sort of IModel and IModelInstance interfaces would allow adding other model formats as well (Such as a skeletal animation format).

* Implement a general sensor system replacing the radars, as described in http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6105

* Add a dynamic-lighting system: Allow units to have dynamic lights on them that affect lighting of other units and landscape, with sort of "approximating lights" for cases where a lot of units get close together. This is a big thing, but it would improve spring graphics a lot if done well. Or Deferred Lighting/Shading?

* Fix the left-click/right-click thing, preferably make it possible to configure mouse / keyboard settings.

* Get a mac version working. Contact the developers on the forums for this, as there are people looking into this already.

Even though this isn't really about the Spring engine:

* SpringLobby is a cross-platform lobby client, implemented in C++ and wxWidgets. We encourage you to look into our todo list on http://springlobby.info and see what you could do for it.

Lua:

* Create a Mission Development Kit: ie, do whatever it takes to make it easy to create campaign missions, eg create a gui tool that makes it easy to place units on the map, create triggers, and so on.

[[Category:Source development]]

SpringEngineTODO

2008-11-07T05:54:43Z

Hughperkins:

SpringEngineTODO

2008-11-07T05:54:16Z

Hughperkins:

SpringEngineTODO

2008-11-07T05:53:10Z

Hughperkins:

Building spring

2008-11-07T05:51:02Z

Hughperkins: /* Development Suggestions */ Replaced "list of example projects" link with "SpringEngineTODO" link, which is way more comprehensive and up to date

'''NOTE: Outlined below is information on assisting with the development of the Spring source itself. For information about developing a mod (units, widgets, maps, etc.) see the [[Mod_and_Unit_development]] page.'''

'''Even if you are developing a mod, it is highly recommended that you get the engine source. Engine source + full text search: DO IT.'''

Below you can find information on how to work with the Spring source in the current mainline (Windows platform) if you like to work on another platform (Linux & Mac) please look at the bottem of this page under "Multiplatform development"

==Starting Development==
To start development, you will need
#To read the [[Coding_Standards]]
#The latest version of the source
#A good code manipulation program
#Compiling your modified source

== Keep track what others do ==
If you develop with others, you need to know what they do. We have [http://spring.clan-sy.com/fisheye/ fisheye], a very handy SVN helper, and [http://spring.clan-sy.com/websvn/ WebSVN] running on the server.

===Source Code Documentation===
A good place to start is [http://buildbot.no-ip.org/~buildbot/spring/doxygen the source code documentation].

An explanation on how the code is executed in game can be found in the [[Spring Engine Code]]
page.

==Obtaining the Source==
The latest SVN is at: [https://spring.clan-sy.com/svn/spring https://spring.clan-sy.com/svn/spring] 
A hourly updated read-only mirror is available at: svn://caspring.org:3691/

Another option is to manually [http://spring.clan-sy.com/download.php download] it along with the latest released version of the game. However, for serious developers, a better way would be to download the source straight from the subversion (SVN) repository. This will also allow you to make a patch out of the changes you make to the code, and send it to one of the developers with SVN access.

Windows SVN clients : [http://subversion.tigris.org Subversion] (Win32-Console),
[http://www.syntevo.com/smartsvn/index.jsp SmartSVN] (Java) and [http://tortoisesvn.tigris.org TortoiseSVN] (MSI).

Assuming that you are using the Subversion svn client you can download the latest SVN source with one of the following commands:

<code>svn.exe checkout https://spring.clan-sy.com/svn/spring/trunk 
svn.exe checkout svn://caspring.org:3691/trunk</code>

It will create a trunk subdirectory in the directory from where you ran it, which will contain the source code root directory which will be later referred to as /spring

If you're using Git rather than SVN, you need to initialize local repository and fetch using:

<code>git-svn clone https://spring.clan-sy.com/svn/spring
</code>

(this may take a while)

To update your local repository, use:

<code>git-svn fetch https://spring.clan-sy.com/svn/spring
</code>

==Learning C++==
You will need to know C++ to modify or understand Spring's source code. If you are interested in learning C++, see [[Learning_CPP]]

However please note that badly designed code (code created by a C++ novice for example), even if working will likely not be included in the spring code. Spring is a large project, and therefore it is necessary to stay away from hack jobs and create general solutions to problems.

==Setting up your development environment==
You have either to use the SCons build system that is multi platform, or use Microsoft Visual Studio for building spring. See also [[Development_IDEs]] for some more background information about the IDE to choose.

===Visual Studio 8 (2005)===
(possibly the free Express Edition)

* Install the [http://spring.clan-sy.com/dl/spring-vc8libs.exe vclibs library package]. You need to install this in the /spring directory from the SVN checkout or the zipped source. If done right, it will look like:
**/spring/
**/spring/installer
**/spring/rts
**/spring/... other dirs
**/spring/vclibs
* Install the [http://msdn.microsoft.com/directx/sdk/ DirectX SDK]
* Install the PlatformSDK. I got away with unchecking the parts of the PlatformSDK that were obviously not related (IIS, web stuff). Makes for a smaller download. Make '''sure''' the Platform SDK and DirectX SDK are in the VS search/include directories:
* After installing them, open Visual C++. Click Tools >> Options >> Projects and Solutions >> VC++ Directories. Add these entries to the corresponding sections (paths just a reference, yours may be different):
**Include files:
***$(ProgramFiles)\Microsoft DirectX SDK (August 2007)\Include
***$(ProgramFiles)\Microsoft Platform SDK\include
**Library files:
***$(ProgramFiles)\Microsoft DirectX SDK (August 2007)\Lib\x86 (Might need \x64 on a 64-bit platform, I don't know.)
***$(ProgramFiles)\Microsoft Platform SDK\lib
* Open the solution. /spring/rts/build/vstudio8/rts.sln
* Start building (usually you want to select the release/no debug build, debug is really too slow and is used only when you really know what you want to test)
* Select the working directory in the project properties, otherwise spring will not work correctly

===Visual Studio 9 (2008)===
(possibly the free Express Edition)

Not yet fully working as far as I know; you need at least this hotfix from Microsoft though:

http://support.microsoft.com/kb/946040

For the rest the Visual Studio 8 instructions should apply, mostly.

===SCONS/MinGW===
Code::Blocks and Dev C++ use MinGW too, so if you are using one of these IDEs, you'll want to follow these instructions too.

'''Getting the compiler'''

You can compile spring either with MinGW version 3 or 4. MinGW 4.2.1 is used for spring release builds (cross compiled on Linux). Therefore, version 4 is recommended.

''MinGW 3''

If you do not have MinGW installed yet, the easiest way to get it, is to install it together with one of the two IDEs [http://downloads.sourceforge.net/dev-cpp/devcpp-4.9.9.2_setup.exe Dev-C++] or [http://downloads.sourceforge.net/codeblocks/codeblocks-8.02mingw-setup.exe Code::Blocks]. They both come with MinGW 3.4, which still compiles spring correctly (June 2008). Use [http://spring.clan-sy.com/dl/spring-mingwlibs-v10.exe v10 of the MinGW library package] if you have MinGW 3.

''MinGW 4 (recommended)''

If you don't yet have it, go to [http://sf.net/project/showfiles.php?group_id=2435 the MinGW download page], and get at least the following packages (MinGW 4.3.0):
* mingw-runtime
* core
* c++
* java (if MinGW 4.3.1 is out yet, you dont need this)
* binutils
* win32api
Use [http://spring.jobjol.nl/show_file.php?id=1102 v11 of the MinGW library package] if you have MinGW 4.

'''Compiling spring'''

Make sure you install the MinGW library package in the checkout directory, so the path is: /spring/mingwlibs. If done right, it will look like:
**/spring/
**/spring/installer
**/spring/rts
**/spring/... other dirs
**/spring/mingwlibs

These programs are a must have if you want to compile Spring with MinGW, so install them now, if you don't have them already.

*[http://www.python.org/ftp/python/2.5.1/python-2.5.1.msi Python 2.5 installer]
*[http://downloads.sourceforge.net/pywin32/pywin32-210.win32-py2.5.exe Python 2.5 win32 extensions installer]
*[http://prdownloads.sourceforge.net/scons/scons-0.96.96.win32.exe Scons 0.96 installer]
*[http://www.cmake.org/files/v2.6/cmake-2.6.0-win32-x86.exe CMake 2.6 installer]

Oh, and quick instructions:

* Grab and install the above programs.
* Make sure C:\Python25, C:\Python25\Scripts and C:\Dev-Cpp\bin are in your PATH environment variable. Set environment variables by: Start -> Settings -> Control Panel -> System -> Advanced -> Environment variables (for Windows XP).
* Make sure a MINGDIR environment variable with value C:\Dev-Cpp exists. (change paths where appropriate.)
* Checkout the Spring SVN repository, following the instructions above in obtaining source. (TODO:link)
* Open a console (Start -> Run -> cmd.exe -> Run), cd \where you checked it out in the previous step, if you checked it out on a different drive make sure to change drives with DriveLetter:<enter> first.
* Type scons configure<enter>. Refer to scons --help for options which can be passed to scons configure. Gotchas:
** If you get an error message starting with "EOFError: : env = Environement...", try deleting the file build/scons_signatures.dblite
** If you get an error message stating "ImportError: No module named win32file:", you have probably not installed the python-win32-extensions.
** If all proceeds as intended you will see a message similar to: "Everything seems OK. Run `scons' now to build."
* Type scons<enter> to start the compilation.
** If you have Delphi installed and get an error message that the commandline params "--no-print-directory" & "-C" aren't supported, then you should remove the Delphi dirs from your PATH variable, because scons tried to run the delphi's make.exe instead of using mingw32-make. (this will cause that streflop can't be build!)
* Wait for the compilation to finish, this may take a while.
* Copy datafiles and stuff from official Spring installation to the /spring/game directory (where spring.exe is located, after the compilation finished.)
* Copy missing DLLs from mingwlibs/dll.
* Start developing.

If you are using Linux, refer to the [[SetupGuide]] to build Spring and get it running.

=== CMake/GCC ===
Currently the CMake scripts are not capable of generating Visual Studio project files, so CMake can only be used for gcc compiling.

* Install CMake (must be at least version 2.6.0) from either www.cmake.org or through your distributions package manager
* get the source code (from svn, tarballs...)
==== The GUI method ====
CMake offers a nice Qt4 gui to ease the following steps (to use the gui explained here, cmake must be at least version 2.6.1). Doing so should be straightforward:
* select source directory
* select (and/or create) build directory where temporary files are stored
* hit configure button
* choose your build type:
** Unix makefile if you are using linux and want to compile linux executables
** mingw makefiles if you are working on windows
** Unix makefile with cross compiler setup to cross-compile mingw32 executables, you have to select the toolchain file you want to use (see below)
* configure variables to your need (move the mouse over the options and read the tooltip for further informations on them and or see Section "Options")
* push generate button
* open commandline and do "make" and "make install"

==== The commandline method ====
Only works with the linux version of cmake, and is easiely scriptable.
* cd to (and/or create) build directory where temporary files are stored
* "cmake <path to source tree> <options>" where:
** <path to source tree> is the path to the spring source directory
** <options> are defined like "-D<option name>=<value>
* depending on your settings you may need to run "cmake ..." twice
* run "make" and "make install"
* PACKAGE MAINTAINERS:
** doing "make install DESTDIR=/some/path" will install spring in the specified place, putting files in subdirectories like configured. This may be helpfull when making packages so spring don'T get installed on your system for real (see also CMake FAQ [[http://www.vtk.org/Wiki/CMake_FAQ#Does_CMake.27s_.22make_install.22_support_DESTDIR.3F]]).
** You need to update the mime database (update-mime-database) and the kde database (kbuildsycoca) after installing to make the system aware of the newly installed mime types and desktop shortcuts.

==== Some Options Explained ====
* MINGWLIBS: directory where the [http://spring.jobjol.nl/show_file.php?id=1102 v11 of the MinGW library package is] (only needed when compiling with mingw)
* CMAKE_BUILD_TYPE: either RELEASE, DEBUG, DEBUG2, DEBUG3 which compiler options to use
* CMAKE_INSTALL_PREFIX: installation prefix (defaults to /usr/local) defines the base directory for installing
* DATADIR, LIBDIR, BINDIR: where to install data, libraries or binaries (relative paths are based on CMAKE_INSTALL_PREFIX, absolute paths are absolute (DESTDIR is still respected))
* APPLICATIONS_DIR, MIME_DIR, PIXMAPS_DIR: where to install freedesktop-files (icons, mime-types and application-description)

==== The toolchain file ====
An example should be self-explainatory:
<code>
# the name of the target operating system
SET(CMAKE_SYSTEM_NAME Windows)

# which compilers to use for C and C++
SET(CMAKE_C_COMPILER i686-mingw32-gcc)
SET(CMAKE_CXX_COMPILER i686-mingw32-g++)

# here is the target environment located
SET(CMAKE_FIND_ROOT_PATH /usr/i686-mingw32)

SET(MINGWLIBS /home/karl/spring/mingwlibs_v11)</code>
Pass this with "-DCMAKE_TOOLCHAIN_FILE=/your/toolchain/file" to cmake or select it in the gui to make a cross-compilation.

==== Further reference ====
* CMake FAQ [[http://www.vtk.org/Wiki/CMake_FAQ]]
* man CMake
* the CMake documentation (long!) [[http://www.cmake.org/HTML/cmake-2.6.html]]

==Development Suggestions==
Before starting to make modifications to the source, take a look at the [[development guidelines]] which outlines some important things to think about. To find something interesting to work on, look at [[SpringEngineTODO]]. You can also check the list of [[whois doing what]] to see what others are doing. If you do edit the code, please add [[Doxygen style comments]] to the code, which will then enhance the source code documentation.

==How to get your code included==
If you create something that you think should be included in the official source tree, you can report a "bug" in [http://spring.clan-sy.com/mantis/ mantis, our BTS]. Add your patch as attachment, and put "[patch]" in front of the subject, so it is easy for us to separate patches from bugs.

It's also considered standard practice to post one's modifications in the [http://spring.clan-sy.com/phpbb/viewforum.php?f=12 development forum] and get feedback.

==Spring Engine TODO list==
There is a TODO list for developers who want to contribute to the engine itself:
[[SpringEngineTODO]]. There is also a [http://spring.clan-sy.com/phpbb/viewforum.php?f=21 feature request forum], which may give you some ideas. Don't be overwhelmed by the sheer number of (silly) requests though!

==Development links==
* [http://planetspring.free.fr/spring/ Automatic installer builds (crosscompiled, mingw)]
* [http://spring.jobjol.nl/show_file.php?id=860 Spring base content files]
* [http://developer.berlios.de/projects/taspring-linux BerliOS project page (OLD)]
* [http://spring.clan-sy.com/mantis Bug Tracking System]
* [http://buildbot.no-ip.org:8010/ Buildbot]
* [https://lists.berlios.de/mailman/listinfo/taspring-linux-commit Commit mailing list]
* [http://spring.clan-sy.com/dl/spring-vc8libs.exe Development libraries for Visual Studio 2005]
* [http://www.unknown-files.net/spring/3839/mingwlibsv10/ Development libraries for MinGW]
* [http://lolut.utbm.info/cgi-bin/mailman/listinfo/taspring-linux Developers mailing list (practically dead, use this forum instead) (DOWN)]
* [http://buildbot.no-ip.org/~buildbot/spring/doxygen Doxygen pages of the latest source (regenerated nightly)]
* [http://spring.clan-sy.com/fisheye Fisheye interface to SVN]
* [http://sourceforge.net/projects/springrts SourceForge project page (OLD)]
* [http://buildbot.no-ip.org/~buildbot/spring/stacktraceTranslator.php StackTrace Translator]
* [https://spring.clan-sy.com/svn/spring/trunk/ Subversion repository]
* [http://spring.clan-sy.com/websvn/listing.php?repname=spring&path=%2F&sc=0 WebSVN]
* [http://spring.clan-sy.com/websvn/log.php?repname=spring&path=%2F&rev=0&sc=0&isdir=1 WebSVN link to "development log"]
* [http://spring.clan-sy.com/websvn/filedetails.php?repname=spring&path=%2Ftrunk%2FDocumentation%2Fchangelog.txt&rev=0&sc=0 WebSVN link to the most recent changelog.txt]

[[Category:Development]] [[Category:Source development]]

SpringEngineTODO

2008-11-01T10:15:05Z

Hughperkins:

'''This page is badly out of date. Some of these items have been done, abandoned or replaced with better ideas.'''

Here is a TODO list for anyone interested in developing the spring code. If you are not involved in the development, please contact one of the developers first before you add things here.

* Implement saving/loading. There are a lot of direct LoadSave() functions in the game code, but the easier way would probably to finish the serialization in the class registration type interfaces (rts/System/creg), so everything can be serialized automatically.

* [[Syncing System|Implement re-sync]]. After a sync problem is detected, and a re-sync of the random seed does not fix it the game would pause and use the rsync to adjust game state (current plan if for float3 data) to resync, as suggested by Jesse Schoch in [http://lolut.utbm.info/pipermail/taspring-linux/2006-February/000810.html]. After using rsync on it should be able to continue normally until the next sync error is detected.

* Abstract and improve unit rendering:
** Improve the S3O rendering: It doesn't generate nice explosion particles like the 3DO system, and it has other issues with drawing as well (refer to the s3o related threads on the forum for this, or test it and see for yourself).
** 3DO/S3O support is not abstracted, many parts of unit rendering are spread throughout spring and assume 3DO, and the rendering is a messy mixture of 3DO and S3O stuff. Abstracting the model rendering with a sort of IModel and IModelInstance interfaces would allow adding other model formats as well (Such as a skeletal animation format).

* Improve weapon collision detection with more complex shapes for the bigger units. Giving every model a set of convex collision meshes, saved in the S3O file, could be a solution. This will need a change in the s3o format and upspring editor, so you will need some cooperate with me on that part(jcnossen).

* Make more elements of spring data-driven. Explosion bitmaps, trees, etc... A lot of graphics are hardcoded and should be changeable with scripts or config files (FBI/TDF).

* Implement a general sensor system replacing the radars, as described in http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6105

* Add a dynamic-lighting system: Allow units to have dynamic lights on them that affect lighting of other units and landscape, with sort of "approximating lights" for cases where a lot of units get close together. This is a big thing, but it would improve spring graphics a lot if done well.

* Get a mac version working. Contact the developers on the forums for this, as there are people looking into this already.

* Add context-sensitive music. Most generic way could be to allow lua to be used to play tracks included within a "sound" directory of the current mod.

* Create a Mission Development Kit: ie, do whatever it takes to make it easy to create campaign missions, eg create a gui tool that makes it easy to place units on the map, create triggers, and so on.

* Make nano particles unsynced, ie. make them respect the MaxParticles setting.

Even though this isn't really about the Spring engine:

* SpringLobby is a cross-platform lobby client, implemented in C++ and wxWidgets. We encourage you to look into our todo list on http://springlobby.info and see what you could do for it.

[[Category:Source development]]

Maps:Map Designer

2006-12-01T10:04:08Z

Hughperkins: /* MapDesigner, by Hugh Perkins */

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Supports multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

== User interface ==

[[Media:http://manageddreams.com/csai/mapdesigner3small.JPG]]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[[Media:http://manageddreams.com/csai/multitextureview1.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview2.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview3.JPG]]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture. That's because it's the base texture for the map, on top of which the other textures are painted.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]]

== Water ==

Areas below zero height will be underwater:

[[Media:http://manageddreams.com/csai/mapdesignwater.JPG]]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[[Media:http://manageddreams.com/csai/slopemap2.JPG]]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

Maps:Map Designer

2006-12-01T10:02:34Z

Hughperkins: /* Texture stages */

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Support multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

== User interface ==

[[Media:http://manageddreams.com/csai/mapdesigner3small.JPG]]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[[Media:http://manageddreams.com/csai/multitextureview1.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview2.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview3.JPG]]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture. That's because it's the base texture for the map, on top of which the other textures are painted.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]]

== Water ==

Areas below zero height will be underwater:

[[Media:http://manageddreams.com/csai/mapdesignwater.JPG]]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[[Media:http://manageddreams.com/csai/slopemap2.JPG]]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

Maps:Map Designer

2006-12-01T09:59:09Z

Hughperkins: /* Concepts */

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Support multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

== User interface ==

[[Media:http://manageddreams.com/csai/mapdesigner3small.JPG]]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[[Media:http://manageddreams.com/csai/multitextureview1.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview2.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview3.JPG]]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]]

== Water ==

Areas below zero height will be underwater:

[[Media:http://manageddreams.com/csai/mapdesignwater.JPG]]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[[Media:http://manageddreams.com/csai/slopemap2.JPG]]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

Maps:Map Designer

2006-12-01T09:58:04Z

Hughperkins: Added texture stage section

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Support multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

== User interface ==

[[Media:http://manageddreams.com/csai/mapdesigner3small.JPG]]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize section
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[[Media:http://manageddreams.com/csai/multitextureview1.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview2.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview3.JPG]]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Texture stages ==

Multiple texture stages can be configured. We use one texture stage for each splatted texture and set its operation to "Blend".

The first texture stage - texstage1 - should be set to "Replace", and has no blend texture.

Advanced:
*It's possible to set other operations on the texture stages.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]]

== Water ==

Areas below zero height will be underwater:

[[Media:http://manageddreams.com/csai/mapdesignwater.JPG]]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[[Media:http://manageddreams.com/csai/slopemap2.JPG]]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

Maps:Map Designer

2006-12-01T09:55:44Z

Hughperkins: Added concepts section

== MapDesigner, by Hugh Perkins ==

[http://manageddreams.com/csai/MapDesigner.zip Download]

*Support multipass texture splatting. SM3 loader.
*Heightmap editor. Left click to raise land, right click to lower
*Paint splatted texture. Left click to paint texture, right click to erase
*Export heightmap, slopemap and blend maps
*Exported slopemap color-coded by movement area, eg infantry, vehicle and extreme (configurable)

== User interface ==

[[Media:http://manageddreams.com/csai/mapdesigner3small.JPG]]

== Concepts ==

MapDesigner is optimized for creating SM3 maps, which use texture splatting to provide high detail maps.

For each texture, we need:
*the texture, which will be tiled according to the tilesize section
*a blend map, which controls where the texture will be visible

The blend map is essentially an alpha map. The areas which are white will be splatted with our texture, and the other areas will be transparent.

The textures are rendered in layers, one by one. The later layers cover the earlier layers, according to each one's blend map texture. Here's some pictures that illustrate how this works. We are rendering each layer with a vertical offset so you can see each layer on its own.

[[Media:http://manageddreams.com/csai/multitextureview1.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview2.JPG]]

[[Media:http://manageddreams.com/csai/multitextureview3.JPG]]

In reality, these layers are all rendered together, with no vertical offset, so they look like they are all part of the same single terrain.

You can use any DevIL-compatible texture as your splat texture. Select a texture stage and click "Load texture..." to load the texture into that texture stage. You can change the tilesize to control how it is splatted in the visible areas.

The blend texture works like an alpha texture, but the data is actually stored in the RGB channels, as a grey-level. MapDesigner lets you paint or remove to and from the blend texture, which has the effect of painting splat texture on the map, or removing it.

== Paint splatted texture ==

*select "Paint texture"
*select a texture stage
*set texture stage operation to "Blend" and load a texture if necessary
*Left click map to paint texture, right click to erase
*You can click "Save blend texture" to export the blend texture map

Note that texture stages are applied in order, first 1 then 2 then 3 etc. The later layers cover the earlier ones.

If you click the map and nothing happens, your changes may be being masked by later layers. You can edit the later layers to uncover your changes, or click "move down" to move your edited layer later in the queue.

[[Media:http://manageddreams.com/csai/mapdesignblendediting.JPG]]

== Water ==

Areas below zero height will be underwater:

[[Media:http://manageddreams.com/csai/mapdesignwater.JPG]]

== Exported Slopemap ==

You can use File | Export slopemap... to export a slopemap for your map.

Black means zero slope, green is vehicles, blue is infantry, red is extreme:

[[Media:http://manageddreams.com/csai/slopemap2.JPG]]

== Configuration ==

Configuration is stored in config.xml ,which can be opened in notepad
*You can change height and width in the display section to change the window size on next startup
*You can configure key mappings, and mouse move configuration

Maps:Map Designer

2006-12-01T09:34:11Z

Hughperkins:

Maps:Map Designer

2006-12-01T09:33:24Z

Hughperkins: Updated for 0.3

Map development

2006-12-01T04:47:31Z

Hughperkins: /* Tools */

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

*[[Quanto_OTAMAP_Guide|Quanto's Guide to OTA Porting and Small Maps]]
*[[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] 

== Tools ==

*[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2420 Maelstrom's SMD Generator]
*[http://www.fileuniverse.com/?p=showitem&ID=1507 Mother's Mapconv]
*[http://user.supradigital.org/jcnossen/FeaturePlacer.zip Jnossen's SM3 feature placer]
*[[Maps:Map Designer]] Hugh's 3D map designer. Splatting, heightmap editing, splat painting, SM3

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