UFOpaedia - User contributions [en]

User talk:Danial

2014-10-11T22:03:31Z

WurmD: /* User Commentary */

This is a place for me to explain each of my theories on the conversion of UFO:EU, a 2D isometric game, into the 3D realm. Each of the ideas explained here have been discussed in forums previously, but no conclusions were ever resolved, so I'll use this page for my own opinions. Discussion is welcome...
=Sizes=
==Height==
One of the more commonly disputed ideas is how tall X-COM units would be in real-life. As a start, I'll list the in-game heights:
'''Silacoid''' 10
'''Celatid''' 12
'''Cyberdisc''' 15
'''Sectoid''' 16
'''Snakeman''' 18
'''Zombie''' 18
'''Ethereal''' 20
'''Floater''' 21
'''Muton''' 21
'''Chryssalid''' 21
'''Reaper''' 23
'''Sectopod''' 23
'''Ceiling''' 24

<i>Note that some floating units are [[Height|effectively taller]].</i>

Now, the basis for my theory on unit heights is a standard house ceiling. The normal* height of a ceiling is 8ft, which in metric** is about 2.40m. Staight away you can see the similarity of 2.4 to 24 - a simple divider of 10. If you then use this to work out the height of, say, a Zombie, it would make it 1.8m, or 6ft. To me, this makes sense seeing as the Zombies are made of poisoned men, and an ''average'' man height is generally stated as 6ft.

The observant of you might have noticed that I left X-COM and civilians out of that list. I did this for a good reason. Here are their listed heights:
'''Tank''' 12
'''Civilian''' 21
'''Soldier''' 22
As you can see, if a ceiling is 2.4m high, this would make an X-COM soldier 2.2m tall! At first I couldn't understand these numbers, until one day it dawned on me that Aliens can't kneel in the game. This means that they can't gain the FA +15% kneeling modifier. So, it's my belief that to compensate the Aliens for this lack of ability, the makers simply made the humans taller, making them bigger targets, and hence, easier to hit. If you scale them down to 18, it makes the civilians 1.72cm tall and the tanks 98cm tall. Both of these results seem acceptable to me.

So in summary, if you want to convert the in-game heights to real-life:
'''Metric Meters''' = (Unit Height)/10
'''Imperial Feet''' = (Unit Height)/3

For Humans, divide again by 1.22 (22/18).

''<nowiki>*</nowiki>Obviously ceilings can be any height the builder wants to make them, but 8ft is the standard.''

''<nowiki>**</nowiki>The makers were British.''

==Tile Size==
It is generally assumed that 1 tile in-game is equal to 1m. I believe this is way too small. The only known ''fact'' is that in actual geometric terms, a tile, with a hypotenuse of 32px, can be derived to be 22.6px wide. In a thread on XCTC (now StrategyCore) several concepts were discussed:
*'''1m:''' The assumed 1m tile would lead to a wall height of 1.22m, or 4ft, which is simply rediculous.
*'''1.4m:''' Roughly derived from the animation walk-cycle, I don't believe this is a suitable reference.
*'''1.6m:''' Based off Line of Fire Templates.
*'''2.26m:''' Based off my div/10 formula above.
I believe that 2.26m is the best alternative, but I suppose it's all up to personal opinion as to which you adopt.

===User Commentary===
<i>2.26m seems way, way too high a value for me. 2.4m sounds about right for the height of a tile, but with this sort of width doors would be nearly squares. Great big ones at that.

Each tile is made up of 12, 16x16 [[LOFTEMPS.DAT|Line of Fire Templates]], stacked one on top of the other. Assuming they're double stacked to create a 16x16x24 object (which makes sense given the maximum unit height of 23), the div/10 formula suggests that a tile is 1.6 meters square.

On the other hand, that result can easily be skewed up or down by assuming that one "height" value is not of the same real-world-measurement as one "width" value. The two don't have to be equal. The programmers likely stuck to multiples of eight for processing ease as opposed to realism, so mathematics applied to known game values probably won't always produce realistic measurements.

My personal hunch is that a tile is a meter wide and the isometric view just makes things look shorter then they really are. - [[User:Bomb Bloke|Bomb Bloke]] 02:04, 5 November 2007 (PST)

I've always assumed a meter/yard squares. 8ft/2m40 sounds about right for height. Julian Gollop, the lead creator, is British, and our ceilings are indeed usually 8ft. Doors are 30 inches, 36 inches (3ft/1 yard) if you include the surround. [[User:Last Hussar|Last Hussar]] 00:18 9 March 2011 (GMT)</i>

=Speed=
As everyone knows (or should know), TUs equate to speed. This lead to to calculate the walking speeds of each unit in the game. I based my calculations off averages. An average X-COM Soldier has 65 TUs and the average human walking speed is 5 km/h, so if you multiply TUs by 5/65 (or 1/13), you get:
'''Unit TUs Speed'''
'''---- --- -----'''
Chryssalid 110-124 8-10 km/h
Celatid 70-82 5-6 km/h
X-COM 50-80 4-6 km/h
Ethereal 68-79 5-6 km/h
Cyberdisc 62-72 5-6 km/h
Reaper 62-72 5-6 km/h
Sectopod 62-72 5-6 km/h
Floater Commander 60-70 5-5 km/h
Muton 56-65 4-5 km/h
Floater Leader 55-64 4-5 km/h
Sectoid 54-63 4-5 km/h
Snakeman Commander 45-63 3-5 km/h
Floater 50-58 4-4 km/h
Silacoid 40-47 3-4 km/h
Snakeman 40-47 3-4 km/h
Zombie 40-47 3-4 km/h

If you want running and sprinting speeds, just multiply by 3/13 or 5/13 respectively.

For those who like formulas:
'''Walking Speed''' = (Base TUs)/13
'''Running Speed''' = (Base TUs)*3/13
'''Sprinting Speed''' = (Base TUs)*5/13

=Turn Length=
This is probably the most controversial aspect of the game. To work out how long a turn actually is, two important things need to be known - Tile Size and Speed!

I'll use a Soldier with 80 TUs for my example, and a hypothetical 2m tile size.

We know that 80 TUs will allow the Soldier to cover 20 tiles per turn, which makes 40m in this case.

Based on my calculations above a Soldier of 80 TUs can move at 6km/h, or more precisely, 1.71m/s.

So, 40m at 1.71m/s = '''23.4s'''

Results with varying tile sizes:
1.0m = '''11.7s'''
1.4m = '''16.4s'''
2.0m = '''23.4s'''
2.3m = '''26.5s'''

===User Commentary===

''This assumes that X-Com soldiers walk around the battlefield (which it looks like from their animations.) However seeing as how they tend to run out of breath (energy) after 3-4 turns of continuous moving (and we have established that to be at most 2 minutes), it is much more likely they move in sprints. This gives us 8.5 m/s for a 80TU soldier, and 4.7 seconds per turn (let's make that 5 seconds, since this is all ballpark measurements). This is also explains why they can only fire 2-3 short bursts on any given turn. --[[User:A1s|A1s]] 21:13, 18 January 2011 (EST)''

<i>If, as I suspect, a square is a Yard (call it a meter for ease) that makes your example soldier speed 20m/5 sec. This is a speed of 14.4kmh- just shy of 9mph. This isn't a bad speed for a soldier; while olympic sprinters could make 50m in 5 seconds our men are not olympic sprinters, plus they have all their kit. If you've ever run in webbing you know the feeling of it bouncing around you, while your boots slow you down anyway. Additionally soldiers don't have the luxury of a 'tunnel vision' sprint, and have to be aware of surroundins. 5 seconds seems right, and you've done a lot of good work here, but I think you've over estimated the horizontal. I think we can explain away the speed of shooting with an assumption that single shots represent a number of single shots or bursts, where as auto is the flipping the selector to 'Full', and what we see is a representation of a number of bullets per 'streak'.[[User:Last Hussar|Last Hussar]] 00:18 9 March 2011 (GMT)</i>

----

You've done your homework here.

I think, in the end, there's one thing that will make or break any 3D version of X-com: a <i>really bitchin'</i> Heavy Plasma model.--[[User:Papa Legba|Papa Legba]] 20:26, 19 December 2005 (PST)

Made :) [[User:WurmD|WurmD]] ([[User talk:WurmD|talk]]) 18:03, 11 October 2014 (EDT)

[[Category: data tables]]

Avenger

2014-10-11T20:32:21Z

WurmD: /* Vital Statistics */ added construction requirements

[[Image:UP001.gif|right|Avenger - Ultimate Craft]]
The '''Avenger''' is the ultimate replication of Alien technology. It is both the best troop transporter and best interceptor available in the game.

This craft appears in ''[[X-COM|UFO: Enemy Unknown]]''. For the ''[[TFTD|Terror from the Deep]]'' equivalent, refer to the [[Leviathan]].

==How to use it==

The Avenger is the fastest craft available to [[X-COM]], capable of reaching any point on earth within three hours and intercepting any UFO. With enough fuel for ten hours of flight, it can still patrol a bit and/or follow UFOs around. It has a very large damage capacity. When armed with dual [[Plasma Beam]]s, the Avenger is the only craft available to X-COM that can reliably intercept an alien battleship single-handedly without risk of complete destruction - if necessary, though is not recommended as will become apparent shortly.

It has sufficient room to carry 26 [[soldiers]] (or a mix of soldiers and up to four [[Heavy Weapons Platforms]]). Due to the 80 item limit, 26 soldiers will cause difficulties in inventory juggling. To get around this, bring some HWPs , don't fill the Avenger to full capacity, or get your unarmed troops to pick up weapons off fallen enemies.

The Avenger is unfortunately expensive and takes a long time to build. Many players find it easier to employ cheaper or more readily available ships and have only a few Avengers to supplement them in times of great need.

There is a common misconception that an Avenger will be in the repairshop for longer than other craft. This is mostly untrue. An Avenger that received 400 damage will take exactly the same time to repair as a Firestorm that takes 400 damage. Admittedly, if you Firestorm is destroyed, you do not have to repair it at all, but losing a ship and letting the battleship complete its mission seems silly, it would have been better not to engage it at all in that case.

The Avenger's high hit points frequently trick inexperienced commanders into making an Avenger solo a Battleship. A Plasma Beam armed Avenger will always beat a Battleship, since it has many more Health than a Firestorm. However, even though the damage might look small, it actually took the same amount of damage as a Firestorm would have, the only difference being the Firestorm might have been destroyed, but the Avenger always survives, albeit with several hundred damage received. Since damage is repaired at the same rate as other aircraft at 1 hitpoint per hour, a very badly damaged Avenger could be in repair for over a month.

Therefore, when engaging a [[Battleship]], it is more or less imperative to send in multiple Avengers at once. The best is to ALWAYS send in four Avengers at once. Firstly,this will bring it down quicker. The faster it is shot down, the less return fire will be received. Every additional Avenger, or any other ship armed with plasma beams, that join the dogfight will potentially reduce the length of battle to one half, one third or one quarter of the length of a normal air skirmish respectively. Secondly, it has been unconfirmed that enemy UFOs have a fixed firing rate, which is distributed among all intercept craft. However, be warned that the UFOs will attempt to concentrate fire on your intercept craft one by one!!! To be precise, when clicking the Aggresive Attack button in order of Top Left, Top Right, Bottom Left, Bottom Right, the Battleship was observed to fire almost exclusively at the Top Left ship, once that was destroyed, the Top Right, then Bottom Left, then Bottom Right.

To summarise, damage received seem to indicate an average result of:
1 Avenger, solo, receives 740 damage (1 free shot from Battleship as you close in + 7 more shots)
4 Avengers, simultaneous, receive damage distribution of 150, 60, 50, 0 based on which ship attacks first.
Where 1 point of damage = 1 hour being repaired.

Note that intercepting with 4 avengers at once uses up 4 times as much Elerium as intercepting with 1 avenger.
Also note that, if you have a very large workshop base, it is faster to just send in 1 Avenger to solo, then decommission it upon return. Just replace the Plasma Beams with Stingray Launchers and sell your Avenger. Manufacture a new Avenger to replace it... this will take only 6.5 days using 250 engineers working in 6 workshops. Expensive (3.5 million per Avenger), but time saving.

Due to its acceleration and speed, the Avenger is the most fuel efficient Hybrid craft. Despite its size, the Avenger uses Elerium fuel at the same 1 per 10 minute rate as the Firestorm and Lightning, however it will reach its destinations much faster and return faster, thus it uses less fuel overall. This acceleration and top speed also make it the best craft to hunt down and engage UFOs.
However, as with any elerium fueled aircraft, an Avenger has very limited fuel capacity, and shares the same [[Known Bugs#Elerium-fueled Craft Bug|design flaw]] as the [[Firestorm]] and the [[Lightning]] that forces it to return to base after depleting half of its fuel, cutting its air time even further. This makes it unsuitable (and the fact that it uses Elerium as fuel makes it very costly) for general patrol or for hunting potential alien base locations. The Interceptor or Skyranger are better suited to this task.

==Battlescape Graphics==
<gallery widths="175">
Image:AVENGER-L0.PNG|Avenger Level 0
Image:AVENGER-L1.PNG|Avenger Level 1
Image:AVENGER-L2.PNG|Avenger Level 2
</gallery>

== Special Requirements ==
The "Avenger" craft is fueled by [[Elerium-115]]. Before [[manufacturing]] this craft, ensure that you have sufficient stocks of Elerium in your [[General_Stores|general stores]].

While airborne, the Avenger consumes 1 fuel unit (1/5th unit of [[Elerium-115]], 1.66% total fuel) every ten minutes, regardless of the speed of the craft. The Avenger has a maximum (radial) range of 27,000 nautical miles, while being airborne for 5 hours. Its maximum (distance) range is 54,000 nautical miles for a total fly time of 10 hours. Patrolling has no effect on fuel consumption.

One Avenger requires 12 units of Elerium for refueling. When refueling, the Avenger receives 8.33% more fuel (one unit of Elerium) every half hour, on the half hour. So it can take up to six hours to refuel, and will be finished fueling precisely on the turn of a half hour.

If Plasma Beams have been fired, it will take 3 hours to re-arm, regardless of how many PB shots were used. At the turn of the first hour after refueling (measured by hour on the clock, straight up), your left Plasma Beam goes to 100 ammo. Turn of second hour, right one goes to 100. Turn of third hour: Craft drops out of REARMING status and is ready to fly. Even if your craft has not fired (ammo=100), it will still wait until the next hour (straight up) going through that last REARM phase after refueling.

Avengers are repaired at the rate of 2% damage per day. Thus it can take e.g. THIRTY DAYS to fix a 60% damaged Avenger. A Firestorm would recover from 60% in just over 12 days (4.8%%/day). However, what's really happening here is that they both repair exactly the same ''Damage Capacity'' (i.e., "hit points") per day... 2% of 1200 equals 24/day for Avenger, and 4.8% of 500 equals 24/day for Firestorm. In fact, 60% damage to an Avenger is 720 damage, which would have utterly destroyed a Firestorm, leaving nothing to repair. 60% damage for a Firestorm is only 300. So, comparing damage % between an Avenger and Firestorm is just being silly... UFOs do damage in damage capacity points, not in percentage terms. The correct analysis is to compare a Firestorm which receives 300 damage to an Avenger which receives 300 damage... and the result is that they both spend the exact same time in the workshop. The only difference is when a Battleship manages to inflict over 499 points of damage in which case the Avenger spends a long time being repaired, and in the Firestorm's case, you would have to manufacture a new Firestorm and 2 Plasma Beams.

Service is done in this order: [[Repairs]], [[refueling]], [[rearming]]. If you transfer an Avenger between bases, it will still need refueling and rearming when it arrives even though 12+ hours have passed (if it needed them before it left).

== Vital Statistics ==
<table>
<tr><td>Maximum Speed:</td><td>5,400</td></tr>
<tr><td>Acceleration:</td><td>10</td></tr>
<tr><td>Fuel Capacity:</td><td>60</td></tr>
<tr><td>Weapon Pods:</td><td>2</td></tr>
<tr><td>Damage Capacity:</td><td>1,200</td></tr>
<tr><td>Cargo Space:</td><td>26</td></tr>
<tr><td>[[:Category:Heavy Weapons Platforms|HWP]] Capacity:</td><td>4</td></tr>
<tr><td>'''Construction Requirements'''</td><td></td></tr>
<tr><td>Work Space Required:</td><td>36</td></tr>
<tr><td>Man hours:</td><td>34000</td></tr>
<tr><td>Alien Alloys:</td><td>120</td></tr>
<tr><td>UFO Power Source:</td><td>1</td></tr>
<tr><td>UFO Navigation:</td><td>2</td></tr>
</table>

== See Also ==
{{Craft Navbar}}

[[Category: Research (EU)]][[Category:X-COM Craft (EU)]]
[[Category:Enemy Unknown/UFO Defense]]

Personal Armour

2014-09-21T13:18:27Z

WurmD: /* Statistics */ added sell value, cost to produce, man hours, needs some estetic adjustments

Once you've researched [[Alien Alloys]], you will be able to research '''Personal Armour''', which is a vast improvement to the standard coveralls.

While serving as a vital upgrade to the pitiful defenses offered by an unarmored X-Com soldier, personal armour is only mildly effective against weapons like the [[Heavy Plasma]] you'll end up facing in later missions, though it can often withstand a single frontal hit if you're lucky. Personal armour is also inexpensive and fast to produce, and since you often end up with huge stockpiles of alien alloys, you will seldom run out of materials to build the armor with.

This armor should see heavy use until you can build the [[Power Suit]], which dramatically outperforms the personal armour.

This armor is used in ''[[X-COM|UFO: Enemy Unknown]]''. In ''[[TFTD|Terror from the Deep]]'', the [[Plastic Aqua Armor]] is the equivalent.

== Statistics ==
<center>
<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>Facing</th>
<th>Protection</th></tr>
<tr><td>Front</td><td>50</td></tr>
<tr><td>Right</td><td>40</td></tr>
<tr><td>Left</td><td>40</td></tr>
<tr><td>Rear</td><td>30</td></tr>
<tr><td>Under</td><td>30</td></tr>
</table>
</center>
Due to a bug when units are spawned, soldiers wearing Personal Armour are treated as though they are wearing Power Armor when damage modifiers are applied -- but a [[Power Suit]] or better is needed against [[stun]] damage from smoke.

Cost to Produce: 22'000

Man hours necessary: 800

Sell Value: 54000

==Images==
[[Image:PersonalArmour.gif|Personal Armour]]

==See also==
*[[Coveralls]]
*[[Power Suit]]
*[[Flying Suit]]

{{Equipment (UFO Defense) Navbar}}
[[Category:Armour]]
[[Category:Research (EU)]]
[[Category:Enemy Unknown/UFO Defense]]

Avalanche

2014-09-15T08:17:32Z

WurmD: /* Vital Statistics */ added price

[[Image:avalanche.png|thumb|right|200px|Avalanche Missile]]
The '''Avalanche''' missile is the most powerful craft weapon available to X-COM until the [[Plasma Beam]] can be [[research]]ed.

With a far superior range and power than the [[Cannon]] and [[Stingray]] missile, it is capable of bringing down most UFOs, although with medium and large UFOs it may be beneficial to intercept with multiple craft to minimise damage and missed shots. The Avalanche is overall a great starting weapon, although it will often destroy smaller Scout-class crafts, which should be shot down with smaller weapons or attacked while landed.

This weapon is used in 1994 ''[[X-COM|UFO: Enemy Unknown]]''. For the ''[[TFTD|Terror from the Deep]]'' equivalent, refer to the [[D.U.P. Head]]. For the 2012 [[Enemy Unknown (EU2012)|X-COM: Enemy Unknown]] version, see [[Avalanche Missiles (EU2012)]].

<br clear="all">
== Vital Statistics ==
<table>
<tr><td>Damage:</td><td>100</td></tr>
<tr><td>Range:</td><td>60 km</td></tr>
<tr><td>Accuracy:</td><td>80%</td></tr>
<tr><td>Reload Time:<br>(Agg/Std/Cau)</td><td>24/36/48 game seconds (gs) nominal/minimum<br>36/54/72gs average<br>48/72/96gs maximum</td></tr>
<tr><td>Shots:</td><td>3</td></tr>
<tr><td>Ammunition Used:</td><td>Avalanche Missile</td></tr>
<tr><td>Price of Missile:</td><td>$7200</td></tr>
</table>

Note that the Accuracy given in the in-game UFOPaedia is incorrect; two independent code digs have confirmed these are the correct accuracies for the craft weaponry. Similarly the UFOPaedia reload times are incorrect; the values stated here are based on empirical tests.

==See Also==
{{Craft Navbar}}

[[Category:Craft Armaments (EU)]]
[[Category:Enemy Unknown/UFO Defense]]

Stingray

2014-09-15T08:16:31Z

WurmD: Added price

[[Image:stingray.png|thumb|right|200px|Stingray Missile]]
The '''Stingray''' is an adequate weapon, capable of taking down Small and Medium-sized UFOs. It has a longer range (30 km) than the armaments of [[Small Scout]]s, [[Medium Scout]]s, [[Abductor]]s, and [[Harvester]]s, and an [[Interceptor]] armed with dual Stingrays can usually down even the Medium-sized crafts.

[[Large Scout]]s have a weapon range of 34 km; against them, your Interceptors will sustain some damage if armed solely with Stingrays or other short-range weapons.

The Stingray is not suitable against Large and Very Large UFOs.

This weapon is used in ''[[X-COM|UFO: Enemy Unknown]]''. For the ''[[TFTD|Terror from the Deep]]'' equivalent, refer to the [[AJAX]].

<br clear="all">
== Vital Statistics ==
<table>
<tr><td>Damage:</td><td>70</td></tr>
<tr><td>Range:</td><td>30 km</td></tr>
<tr><td>Accuracy:</td><td>70%</td></tr>
<tr><td>Reload Time:<br>(Agg/Std/Cau)</td><td>16/24/32gs nominal/minimum<br>24/36/48gs average<br>32/48/64gs maximum </td></tr>
<tr><td>Shots:</td><td>6</td></tr>
<tr><td>Ammunition Used:</td><td>Stingray Missile</td></tr>
<tr><td>Price of Missile:</td><td>$2400</td></tr>
</table>

The reload time given in the in-game UFOpaedia is incorrect; the value stated here is based on empirical tests. The Stingray's accuracy of 70% is the ONLY craft weapon accuracy to be correctly stated in the in-game UFOpaedia; all the others are incorrect due to a [[Known_Bugs#UFOPaedia_Craft_Weapon_Hit_Probability_Bug|bug]]. The Stingray coincidentally having the same firepower and accuracy may have been responsible for this bug being missed during development.

==See Also==
{{Craft Navbar}}

[[Category:Craft Armaments (EU)]]
[[Category:Enemy Unknown/UFO Defense]]

Talk:Statstrings

2014-09-13T08:29:46Z

WurmD: XcomUtil.cfg substituted by XcomUtil_Statstrings.rul in OpenXCOM1.0 ? with different sintax?

==Edit for clarity==

The "default configuration" example was literally the default configuration, copied verbatim from the xcomutil.conf file as it comes in the archive. Are you sure that this is valid syntax? Even if the pluses work just as well, I don't think we should present a "default conf" that has already been tampered with... --[[User:Schnobs|Schnobs]] 12:13, 22 October 2007 (PDT)

:I didn't realize that was taken verbatim right out of the code file. If you're looking to have machine-readable examples, or examples right out of the file, feel free to revert it; my apologies. [[User:Arrow Quivershaft|Arrow Quivershaft]] 13:16, 22 October 2007 (PDT)

I tried to come up with an explanation of the syntax, but... Maybe someone whose english is better than mine should try his hand at this.

An entry consists of two parts:
*first, the statstring that will be added to a soldiers' name. It can be anything you like, but should better be short.
*second, the condition to trigger that string (like k:30-59), which itself is made up of two parts: a one-letter handle for the stat (like r for reactions or b for bravery), and the experience range.

Note that these are ''ranges'': lower boundary, dash, upper boundary. Either one can be omitted if the range should be open-end. So 30-50 means "from thirty to fifty", -25 means "anything below 26" (and is equal to 0-25) and 60- means "sixty or higher" (equal to 60-255). 42, unsurprisingly, would mean "a value of exactly 42".

I'm not quite sure how some strings override others.--[[User:Schnobs|Schnobs]]

:I can help with that, it's actually very simple. Single character strings accumulate. But any string with more than one character will end the search right there and no further strings will be added to the name. The strings are parsed in the order they are written in XcomUtil.cfg--[[User:Mannon|Mannon]] 15:42, 1 August 2008 (PDT)

::Here's a related tip. If you really want multi character string that will not end statstrings you can still do it, it's just counterintuitive. You have to split each character of your string. For example if you wanted "Sct" for anybody that had high TU's. You just do each letter individually with the same criteria and keep the lines together in your strings so they won't get other stats between them. I did this with an older version of my StatStrings, but ditched it for character space. (I don't like having to chop down long last names to use my strings.) Example below.--[[User:Mannon|Mannon]] 15:55, 1 August 2008 (PDT)
// Will produce "Sct" for any soldier with 80 or more TU's and will continue to accumulate strings after.
S d:80-
c d:80-
t d:80-

== Useful ==

Very useful article, thanks guys. [[User:Spike|Spike]] 13:35, 1 February 2009 (CST)

== Example ==

I've added another example. Please feel free to alter it if you can improve on the language. [[User:Off the Rails|Off the Rails]] 04:01, 11 October 2012 (EDT)

== XcomUtil.cfg substituted by XcomUtil_Statstrings.rul in OpenXCOM1.0 ? with different sintax? ==
Below are the current contents of XcomUtil_Statstrings.rul

Should we add into this wiki page examples with this sintax as well? (or substitute all exemples to this sintax altogether

# Based on XcomUtil by Scott Jones and BladeFireLight
# See http://ufopaedia.org/index.php?title=Statstrings
# These are the default statStrings from XcomUtil.
statStrings:
- string: "x"
psiStrength: [~, 30]
- string: "P"
psiStrength: [80, ~]
- string: "p"
psiStrength: [60, 79]
- string: "K"
psiSkill: [60, ~]
- string: "k"
psiSkill: [30, 59]
- string: "b"
bravery: [60, ~]
- string: "c"
bravery: [~, 10]
- string: "w"
strength: [~, 25]
- string: "Snpr"
firing: [60, ~]
reactions: [60, ~]
- string: "M"
firing: [70, ~]
- string: "m"
firing: [60, 69]
- string: "Sct"
reactions: [50, ~]
tu: [60, ~]
- string: "R"
reactions: [60, ~]
- string: "r"
reactions: [50, 59]
[[User:WurmD|WurmD]] ([[User talk:WurmD|talk]]) 04:29, 13 September 2014 (EDT)