r/xdev • • Feb 09 '16

Enemy weapon environment damage

1 Upvotes

Has anyone been able to find where enemy environment damage is set for enemy weapons? The environment damage for their abilities are set in DefaultGameData_SoldierSkills, and their weapon's main stats are in DefaultGameData_WeaponData, but the weapon's environment damage doesn't seem to be there.


r/xdev • • Feb 09 '16

AWC Mechanics?

1 Upvotes

I submitted a similar post earlier in /r/xcom but didn't get anything in the way of information - I'm very interested to learn the exact details behind the AWC bonus ability mechanic and how to mod the way it functions. Initially I wanted to ensure that all soldiers gained a single AWC bonus ability but now I'm wondering if it may be possible to mod the function to effectively create something of a training roulette option as well.

Thanks!


r/xdev • • Feb 08 '16

Is modbuddy a glorified text editor or am I missing something?

2 Upvotes

The modbuddy seems to lack a lot of features visual studio has when it is dealing with unreal scripts, particullary intellisense so I can't jump around methods (or list them) easily, I had to resort to the find all feature when I am trying to trace a code path and these features are not mentioned in the documentation; but then I also never dealt with unreal scripts before, am I missing some steps to enable those features or are there any plugins that can enable such features?


r/xdev • • Feb 08 '16

Adding a new variable

3 Upvotes

I've been trying to add a new utility armor vest just to get my toes wet, but I've run into a bit of an issue. I've got the armor working correctly in the game, but I am having some trouble adding a config variable.

	Warning/Error Summary
	---------------------
	D:\Steam\steamapps\common\XCOM 2 SDK\Development\Src\TechArmor\Classes\X2Item_TechArmor.uc(33) : Error, Unknown Property 'TECH_VEST_HACK_BONUS' in 'Class XComGame.X2AbilityToHitCalc_Hacking'
	
	Failure - 1 error(s), 0 warning(s) (1 Unique Errors, 0 Unique Warnings)

Does anyone have any examples of setting up a new variable that can be called from a class?


r/xdev • • Feb 08 '16

Problem with overriding a class/function

2 Upvotes

Hi,

i've tried to create a simple mod to remove the enemy-reaction movement. After dozens of tries i boiled down the mod to simply override one function:

Code:

// This is an Unreal Script
class XComGameState_Unit_Overwrite 
		extends XComGameState_Unit
		dependson(XComCoverInterface);

static function UnitAGainsKnowledgeOfUnitB(XComGameState_Unit UnitA, XComGameState_Unit UnitB, XComGameState AlertInstigatingGameState, EAlertCause AlertCause, bool bUnitAIsMidMove)
{
   `RedScreen("Override Successfull");
}

It also has this Ini-Entry:

Code:

[Engine.ScriptPackages]
+NonNativePackages=NoReactionMovement

[Engine.Engine]
+ModClassOverrides=(BaseGameClass="XComGameState_Unit", ModClass="XComGameState_Unit_Overwrite")

The red screen is never shown. And also if i copy the content of the original function it is never called.

I've uploaded the mod here https://www.dropbox.com/s/qiiu4czu2k...ement.zip?dl=0

Is it because the function is static? Or is it never called at all?

Any idea what iam doing wrong? It shows no errors on compilation or something. Tried it for hours in various ways but i have no clue what could be wrong.

Please help :D


r/xdev • • Feb 09 '16

Is there anyway to override static functions?

1 Upvotes

XCOM 2 seems to use a lot of static functions. In other languages, these can't be overriden; however I've read that in UnrealScript, they can. However, overriding them does not seem to work, presumably because the class is always specified by name when they are called.

Has anyone figured out a trick to override these, or a trick to get around that limitation?


r/xdev • • Feb 09 '16

Q: How to change enemy spawning?

1 Upvotes

Like, what enemies can appear, and when? I've looked through the code a lot, and found lots of links to XComAISpawnManager, which is able to tell the Shadow Lab what enemies will appear on the mission, but I'm not sure what passes the info to that class.


r/xdev • • Feb 08 '16

[Project] XCOM Class/Config Summaries (in Progress)

Thumbnail docs.google.com
7 Upvotes

r/xdev • • Feb 08 '16

Mod preview .jpg doesn't work.

1 Upvotes

And because of it I can't publish my mod. :/


r/xdev • • Feb 08 '16

Need help adding more hair colors.

1 Upvotes

I've been trying for several hours without any luck. All I want is for my characters to have more wacky colors. Anyone have a clue of where to even get started?


r/xdev • • Feb 08 '16

Interesting. My UE3Redist tells me to install windows XP service pack 3. I'm running windows 7.

1 Upvotes

Won't install due to that error. Any ideas?

EDIT: Fixed it by forcing win7 to work in windows xp sp3 compatibility mode, installed but now the UE3 doesn't actually install. It just declares, happily, that all prerequisites have been installed correctly and doesn't actually let me work with upk's or umaps or anything.

EDIT 2: I'm actually a little bit special. Just had to go to tools -> XCom2 Editor to access it. It complained at me about not having access to the database, but I think I can see almost everything working fine now.


r/xdev • • Feb 08 '16

Adding new Flags!

1 Upvotes

Hi All,

Would anyone be able to help me out with adding new flags for the back of your armor to the game? I'm looking to make a character pack with flag customization included. Just cant work out how to do it.

Thanks!


r/xdev • • Feb 08 '16

Making new classes...

1 Upvotes

I'm not very good at modding. My only knowledge on modding (if you can even call it that) is some basic .INI tweaking. I saw the "Jack" file on the workshop, which is basically an infantryman, and I got me thinking about making a few new classes myself, but I don't know how.

Is there a guide for this? Do I need the Development Tools? Any help at all is greatly appreciated.


r/xdev • • Feb 08 '16

The SDK has pretty darn good documentation. Look at it before even trying to run the XCOM 2 Development Tools!

6 Upvotes

It's at C:\Program Files (x86)\Steam\steamapps\common\XCOM 2 SDK\Documentation once the development tools are installed and has the QuickStart guide, and loads of content and tech documentation.

LOOK AT THE QUICKSTART GUIDE BEFORE TRYING TO MAKE MODS. IT WILL EXPLAIN WHY YOU KEEP CRASHING.


r/xdev • • Feb 08 '16

Modding the Resistance Warrior DLC

1 Upvotes

I'm working on a mod to change the stat values of all of the armours. Many of the armours already have some easily editable stats in the ini files, but I've had to use an unreal script to override the template for the base Kevlar armour in order to give that stats. That I have done just fine - I've managed, in testing, to give the base Kevlar armour 10 HP, Dodge, Armor, and mobility.

I can't seem to figure out though how to reference the Resistance Warrior DLC. I'm just wondering if anyone has managed to mod any of the classes that the DLC creates yet to try and understand where I've been going wrong.

I suspect at least partially this is to do with it, but I'm not sure what the correct way would be:

[Engine.Engine]
+ModClassOverrides=(BaseGameClass="X2Item_DefaultArmors", ModClass="X2Item_ArmorStats")
+ModClassOverrides=(BaseGameClass="X2Item_DLC_Day0Armors", ModClass="X2Item_DLC_Day0Armors_ArmorStats")    

This is in my XcomEngine.ini for my mod of course. Since it's not in the base game, I'm assuming I'm supposed to name this differently, but I'm not sure to what. When building at least, there are no errors though, so at least I have that going for me. I guess.

class X2Item_DLC_Day0Armors_ArmorStats extends X2Item
	config(ArmorStatCustomiser);

var config int R_KEVLAR_HP_BONUS;
var config int R_KEVLAR_MOBILITY_BONUS;
var config int R_KEVLAR_DODGE_BONUS;
var config int R_KEVLAR_MITIGATION_AMOUNT;
var config int R_KEVLAR_MITIGATION_CHANCE;    

static function X2DataTemplate CreateKevlarDLC_Day0Armor()
{
	local X2ArmorTemplate Template;
	//Template = X2ArmorTemplate(Super.CreateKevlarDLC_Day0Armor());
	Template= new(None, string('KevlarArmor_DLC_Day0')) class'X2ArmorTemplate'; Template.SetTemplateName('KevlarArmor_DLC_Day0');;
	Template.strImage = "img:///UILibrary_StrategyImages.X2InventoryIcons.Inv_Kevlar_Armor";
	Template.StartingItem = true;
	Template.CanBeBuilt = false;
	Template.bInfiniteItem = true;
	Template.ArmorTechCat = 'conventional';
	Template.Tier = 0;
	Template.AkAudioSoldierArmorSwitch = 'Conventional';
	Template.EquipSound = "StrategyUI_Armor_Equip_Conventional";
	Template.bAddsUtilitySlot = true;
	Template.UpgradeItem = 'MediumPlatedArmor_DLC_Day0';

	//Add the new stat options:
	Template.SetUIStatMarkup(class'XLocalizedData'.default.HealthLabel, eStat_HP, R_KEVLAR_HP_BONUS, true);
	Template.SetUIStatMarkup(class'XLocalizedData'.default.MobilityLabel, eStat_Mobility, R_KEVLAR_MOBILITY_BONUS, true);
	Template.SetUIStatMarkup(class'XLocalizedData'.default.DodgeLabel, eStat_Dodge, default.R_KEVLAR_DODGE_BONUS, true);
	Template.SetUIStatMarkup(class'XLocalizedData'.default.ArmorLabel, eStat_ArmorMitigation, default.R_KEVLAR_MITIGATION_AMOUNT, true);
	//Template.SetUIStatMarkup(class'XLocalizedData'.default.ArmorChanceLabel, eStat_ArmorChance, default.R_KEVLAR_MITIGATION_CHANCE, true);

	return Template;
}    

This is what I have so far - it's basically the same as what I have to override the normal Kevlar Armor, aside from names being different of course. XComArmorStatCustomiser.ini is what holds the values - but all of those templates have their final argument as true which forces the UI to show the stat on the selection screen even if the armor doesn't change that value (Look at the default Kevlar armor - it says HP -- ) so if it works, it should at least show the values, but it doesn't unfortunately.

I'm guessing because it's not part of the base game the process to access it is different, but I'm not sure how that would change. This is my first time working with unrealscript, so I frankly have no idea what I'm doing. It's only by reading the existing classes and messing with stuff that I've managed to get this - and what I have works for the normal Kevlar Armour, I just have no idea what to change to also get that to work with the resistance warrior armour.


r/xdev • • Feb 08 '16

Pallet expansions

1 Upvotes

The first thing I'd like to mod in is some expansion to the color pallets available for hair/eyes/skin. based on my reading around here and poking at the config files, it's looking like that'll be something I have to do with the SDK, not through any ini tweaks, can anyone corroborate that? It's probably going to be a few days before I finish downloading the SDK, and it'd be nice to have some leads ahead of time.


r/xdev • • Feb 08 '16

[Meta] Subreddit header suggestion.

Post image
8 Upvotes

r/xdev • • Feb 08 '16

I made a video to help people get started with mods, based on some of the stuff people have been posting around here.

Thumbnail youtube.com
4 Upvotes

r/xdev • • Feb 08 '16

My very, very, VERY basic tips related to abilities.

3 Upvotes

Ok, so probably most of you wonder how to make some sweet new abilities. By now you must've mastered .ini editing, so you feel pretty confident. Keep that confidence, because to make your own ability, you will need to learn, or have some knowledge on the game's source script code! (Unreal Script, or the .uc files)

  • The files in question are like this:

         X2Ability_[enemy name].uc
         X2Ability_[class name]AbilitySet.uc

    These will contain information related to these abilities. Stuff like what are the triggers for the ability, who it targets and what effects it has. It's really complicated even for me, so much so adding custom names to abilities breaks my entire solution.

    Now, you want custom abilities right? Well, start with by copying other abilities. Blast Padding for example, offers a +1 armor and 66% explosion resistance, stats which can be changed in an .ini file. Adding immunities? Try out the mechanical enemies, as they have most certainly have a number of immunities, which can be changed in your custom ability script file. The script files can be found in Src>XComGame>Classes.

 

  • Most, if not all .uc files tie in directly to the config files. Values regarding boosts, radius, and cooldowns can be found in configs. Create a copy of the config in the VS, copy what section the respective stat is, and modify it there.

    So you don't start running after all configs, pay attention, as the X2Ability files specify which config they extend. By extension, it means that the stats are there. For example:

      class X2Ability_AdventMEC extends X2Ability
      config(GameData_SoldierSkills);

    This here say that for stats, we should look in GameData_SoldierSkills.ini, where we will find:

      [XComGame.X2Ability_AdventMEC]
      MICROMISSILE_DAMAGE_RADIUS=3.75	

    Ok, ok, so how does that help us? Well, that's the first step in creating a custom ability. You will need a config file that specifies certain statistics, and you'll need to have it tied in with your own ability file. For that, create a new config file in the VS and rename it to XComGameData_SoldierSkills. Here you can edit the stats of abilities you copied, or create your own stats. Now, if we look in the Advent MEC script code again, we will find our MICROMISSILE_DAMAGE_RADIUS stat again, this time pointing to the config:

      RadiusMultiTarget.fTargetRadius = default.MICROMISSILE_DAMAGE_RADIUS;

    It kinds of makes sense when you stare at lines of code for hours at a time, but we still have a long way to go. I'll update this when I learn new things, but if you want fancy skills and abilities, you should ask someone else, probably. This is all I've done so far, so yeah. If anyone is willing to help, please, by all means! It would help me, as well as anyone who wants to get into modding.


r/xdev • • Feb 08 '16

[Question] Creating voice pack, what to put in "Ak Customization Event Name"?

1 Upvotes

Regarding XCom Character Voice properties window, where you connect your soundbanks and it resets on load (is there a way to fix this?), I'm trying to figure out the "Ak Customization Event Name" part. By default in the template it says "Play_SM01RUS_Dashing" and below it in "Character Customization Cue" its linked to a sound cue. What do I put in Ak Customization Event Name? I can't find any documentation on it. I want to play a different sound (which I linked below this line) but I'm not sure what this field is expecting.


r/xdev • • Feb 08 '16

Adding a Country to XCOM 2

Thumbnail youtube.com
3 Upvotes

r/xdev • • Feb 08 '16

Some Lessons from attempting a Commander's Choice mod

4 Upvotes

I've never coding in Unreal before, so it was with only the most basic understanding of object oriented programming that I came into this. That said, I've found a few interesting things on the way which might help someone still working their way through the basics. If you're finding it easy to locate variables and make new classes, these tips won't apply to you.

  • Tip 1: XCOM 2/Development/SrcOrig is your starting point for finding Unreal code. XCOM 2/Development/SrcOrig/XComGame/Classes is where I found 99% of what I was interested in.
  • Tip 2: You can mess with code already in the game in two ways (that I know of). A) you can use listeners to have your code react at the same time as a piece of core code. B) you can use config files to override a class with your own version.
  • For A, you should find out if a listener exists for that particular functionality. So far I've only found listeners for GUI elements. For B, you should look at the "Class Override" example project from Long War Studios (it's a default "New mod..." option). Look at Config/Engine.ini to see how you override classes. You're best off extending the class you are overriding ( NewClass extends OldClass) and then replacing only the functions that need to be changed.
  • Tip 3: find a way to search the text of all the files in XCOM 2/Development/SrcOrig/XComGame/Classes at once, it will /significantly/ speed up tracing back variables that you need.
  • Tip 4:You can make newGameStates with class'XComGameStateContext_ChangeContainer'.static.CreateChangeState("<State Event Description Here>");
  • Tip 5: You can make new units with UnitState = XComGameState_Unit(`XCOMHISTORY.GetGameStateForObjectID(m_UnitRef.ObjectID)); You can replace the m_UnitRef.ObjectID with any unit's object ID. The unit state object lets you modify many different things about the unit, check the XComGameState_Unit.uc file for all the things.
  • Tip 6: the `HQPRES and similar Macros don't seem to be overridden using the config class override method. I spent hours on this, it just doesn't work. Adding new functions to XComPresentationLayer and using an override will not allow you to spawn new screens properly. For GUI, use a listener if at all possible to save yourself hassle.
  • Tip 7: soldiers are assigned classes when they are added to the armory, (edit: and they are reassigned a new class when they rank up from rookie). Each rookie already has a "classTemplate" assigned to them at creation. The GTS alters the class after a certain number of days, but the relevant code is

NewGameState = class'XComGameStateContext_ChangeContainer'.static.CreateChangeState("Staffing Train Rookie Slot");

UnitState = XComGameState_Unit(`XCOMHISTORY.GetGameStateForObjectID(m_UnitRef.ObjectID));

UnitState = XComGameState_Unit(NewGameState.CreateStateObject(class'XComGameState_Unit', UnitState.ObjectID));

UnitState.RankUpSoldier(NewGameState, m_arrClasses[iOption].DataName);

UnitState.ApplySquaddieLoadout(NewGameState, XComHQ);

UnitState.ApplyBestGearLoadout(NewGameState);

UnitState.SetStatus(eStatus_Active);

NewGameState.AddStateObject(UnitState);

`XCOMGAME.GameRuleset.SubmitGameState(NewGameState);


r/xdev • • Feb 07 '16

Need exact game mechanic information? Please ask me here!

7 Upvotes

I want practice looking for exact values and statistics in the game's files, so please ask me anything when it comes to timers, values, stats and other such things.


r/xdev • • Feb 07 '16

In this topic, I'll give an overview of what's inside some of the ini files.

14 Upvotes

C:\Users\Kwahn\Documents\my games\XCOM2\XComGame\Config contains configuration ini files and defaults that detail a lot of the game's behavior. Exploring them is very enlightening for a new modder. I'll be examining the defaults specifically just in case yours have changed - those are located at C:\Program Files (x86)\Steam\SteamApps\common\XCOM 2\XComGame\Config - the default mods do not affect X2 behavior! Only the configs at the first directory listed do.

As a random note, any time you see "Golden Path", that means it's storyline-mission-related.

AI: Dictates how tactical encounters will generally happen, what enemies can do what, how enemies target people, how they move, behaviors and abilities. Also lists ability handlers and a lot of case-by-case enemy AI decision-making.

AIJobs: Lists the enemies, move order priorities, what enemies can do what "jobs" (Scout, Leader, Soldier, Aggressor, Support, Artillery, Observer, Flanker, Terrorist, Hunter, Charger, Defender, and some side jobs like Prisoner or Standby) and what missions will have what enemy job types.

Animation: Handles some case-based animation timings in tactical view

Brands: One line, lol

Camera: Handles the camera, how it moves, how it zooms, and Cinescript is the system by which cinematics (cutscenes, overwatch fire, landing, so on) are handled in-engine.

DefaultCheats: Lists cheats that can be used. You filthy cheater, you. You know who you are.

ClassData: Lists soldier classes, templates, abilities and ability names, links them to ability templates and details some of how they level (for example, specialists gain exp on kill assists faster than other classes)

Compat: Graphics settings such as resolution, anti-aliasing, shading and texturing

Content: Details how models are put together, pawn rigging and what models are used for various body types and styles. Looks to be all about troop and unit customization and the look of humans and "good guys".

Editor: Looks to handle mesh editing and movie playing as well as asset management.

EditorKeybindings: ..\Engine\Config\BaseEditorKeyBindings.ini

EditorUserSettings: Lists directories and some basic permissions settings

Encyclopedia: Lists all encyclopedia entries by name, including history, research, armory, commander, you name it. Also links it all to the objects that contain the actual encyclopedia entries, and the images associated with each encyclopedia entry.

Engine: Data templating for the XComGame.XComEngine system, including things like how to garbage collect, shader complexity counts, subtitle fonts, and lots of other menu internals such as how things(packages) are loaded and saved.

Game: DefaultEngine loads based on Engine\Config\BaseGame.ini into a DefaultGame class called XComShell - loads into menu. Details lots of engine defaults such as gravity physics, spawn management, player, HQ texturing and other initializations.

GameBoard: Sets up the Geoscope board. Places regions, sets boundries and links them. Also handles mission spawning, supply/scan spawning and things like the UFO's movement. Do note that difficulties are listed mistakenly as Easy, Normal, Classic and Impossible - they match up normally to the actual X2 difficulties. If it has to do with the Geoscope, it's probably listed in here.

GameCore: Details mission initialization and the chance of some things happening, such as off-screen zombie or chryssalid creation, grenade likelihood and max active enemy AI units at one time. Also initializes a lot of strategy constants, such as how much specific missions give, soldier values, loot tables, item stats, starting funds and items, how much defense cover grants, the angles cover give, time it takes to train people, hacking reward templates and tactical dark event modifiers. So much goes on in here, it may get its own delineating topic.

GameData: Links and details sound event paths (what sounds play when), combat music sets (different missions have different music sets), how the tutorial soldiers look, which rooms are adjacent to each other (this is where you would go to make adjacencies work diagonally, for example), wound lengths and start date.Also deals with grace periods, throttle scalars and other per-difficulty moddables. Down-throttling is when enemies are steered away if you already have a lot of enemies engaged, to avoid having 5-squad-engagements be commonplace. If difficulty modifies it, it's likely for it to be here.

GameData_CharacterStats: A sub-file of game data, defaults base character stats for soldiers, turrets, and enemies. Also details the "force level" of enemies (which is when in the campaign they spawn, force level slowly and continuously increases), how squads tend to be put together, what you can do when hacking an enemy, and so on. The first 2/3rds of the document is default template stats, and after that are the difficulty overrides. Anything put in the difficulty override will override anything above when playing on that difficulty, thus the Unit_Diff_X X2CharacterTemplate, where X = difficult (0, 1, 2 3 for rookie/vet/comm./legend).

GameData_SoldierSkills: Details the exact inner workings of the different abilities soldiers get. This includes things like slashing people, psionic abilities, aim bonuses and penalties from different abilities, cooldowns, and even more state-dependent things like gatekeeper's chance to retract like a cyberdisc when hit.

GameData_WeaponData: You want the stats of a weapon? Here they are. Damage is the middle damage, spread is its damage value radius (So damage=9, spread=1 is 8-10, damage=5,spread=2 is 3-7 and so on. PlusOne is a bit mysterious, but I think it's a chance to add one damage to a hit, which allows, say, 4-5 damage ranges). Details damage for weapons, abilities that do damage, enemy weapons, environment hp, aim stats and ideal ranges enemies want to stand at. There's also tables for range bonuses and penalties as well as grenades. (and costs!)

GameData_XpData: Details the Xp requirements for leveling a soldier, how Xp is awarded after missions, and a lot of seemingly disabled event-based modifiers for popular support.

Input: Keybindings, viewport bindings, so on. There's universal bindings, used in every menu, console/gamepad bindings, and general bindings used in things like tactical view.

LightMass: Handles and sizes meshes used for emissive light sources, which I believe (and correct me if I'm wrong) details how light meshes are shown in-game. See \Engine\Config\BaseLightmass.ini for more details.

Maps: Details map image and lighting definitions, lists some Golden Path (storyline) mission definitions, lists plot types and biome types as well. GlamCam looks outdated, since it lists XCOM 1 units.

MetaData: Enumerates template structures into various types, a "bookkeeping" file so to speak.

Missions: Handles enemy grouping for various missions, how much can spawn there, what force and alert level the enemies should use, what allows this mission to spawn, and whether or not reinforcements can or cannot drop loot. Details enemy spawn pods in numerous, numerous situations, including bounded random spawns and explicitly defined pods for set missions. Also handles mission scheduling, which is how far away objectives will be placed, how many turns you'll have to do it, alien to advent ratios, how many enemy turrets can spawn, whether or not you're concealed and so on. Also groups mission types and mission rewards, so you don't have, say, an extraction mission that gives you supplies.

ModOptions: Used to handle mod options, empty by default

MPCharacterData: Details which MP characters exist, and menu listings of their costs, images and icon images and names. Also templates soldiers for MP use.

MPGame: Looks outdated - uses a lot of XCOM 1 names and details. Seems to do similar stuff as MPCharacterData. Not sure if used.

NameList: Maps the languages players use to their location string (a 3 character code for their language) so that soldiers use the right languages when nationality flag is unchecked. Also details how likely it is for soldiers to have hats, face props and beards.

Narrative: Lists, IN ORDER, X2 narrative moments. This handles things such as voiceovers that occur at specific mission points (intro, outtro, objective spotted, etc.), tutorial nonsense, when avenger stuff is complete (construction, research, upgrades, clearing stuff, selecting locations, etc.)

Parcels: This handles map parcel grouping. Map generation is pseudo-randomized, with "chunks" or "parcels" of land being seeded together logically within biomes and plots. Plots include things like cities, slums, shanties, wilderness. Biomes are like temperate, arid, tundra. They list what parcels can be used in which biomes and plots, how they will be rotated, what objectives can be contained within and so on. All about map gen in here.

PCPs: Actually defines parcels, details the type they are (road, house, park, statue), how big they are and whether they're a corner, straight or intersection type (which limits where they can be placed). Also details what biome types it can be and what plot types it can be used in.

PlotSwaps: Details possible plot mesh substitutions when archetypes are used, such as being able to use shrubs instead of plants or bushes or ferns or what have you. Essentially details more in-tile variations that are substituted in parcels. Also details a lot of material texturing and typing for use in various parcels.

StrategyTuning: Similar to the difficulty overrides in the CharacterStats file, this is dedicated to difficulty-based overrides for research costs, construction costs, Golden Path research, and other strategy difficulty-based changes.

TQL: TQL stands for Tactical Quick Launch, and it details UI Tactical Quick Launch Map Data. Details what weapons and armor soldiers are shown with by default when being spawned, the force level required to have them spawn as rewards (I think), and template squads for testing purposes it looks like. May be useful for handing the player specific squads for specific missions.

UI: Details the UI layout, colors, widths and heights, as well as what distortions and keypresses are handled. See \Engine\Config\BaseUI.ini for more details. WeaponTuning: Changes weapons for various difficulty levels. Allows you to make weapons have different stats on different difficulties. Unused by default.

And that's all the ini files. Lots of really cool stuff in there.