Mashadar

Very intersted in this effect...if you dont mind walking a noob through it.. I am using "Warspace" and have tweaked it a bit to my tastes, so im hoping its something i can edit in the exe Thanks. Snapshots are pretty easy. Just open up the DefaultGameCore file and look up the Characters list from line 16 to 33. Soldiers are for XCOM troops, tank means SHIV (all types), the rest are self explanatory. Each one has a reaction value of 0 by default. That's percentage chance of reaction fire. The settings I used were: Sectoid (and Commander): 20 Floater (and heavy): 30 Muton (and soldier): 40 Elite Muton, Thin Men: 50 Cyberdisk, Drone: 70 SHIV, Sectopod: 100 After that, scroll down to the weapons list and look for the variable iReactionRange. They should all be -1. Change that to the same value as their respective iRange. e.g. if something has an iRange of 27, iReactionRange should be changed from -1 to 27 and so on. If you want to add the option of suppressive fire to that, just replace any of the eAbility_NONE tags with eAbility_ShotSuppress to the respective weapon types.

I've made some experiments into giving the aliens varying levels of reaction fire to go with XCOMs, and holy hell does it change a lot of things. With high reactions across the board, combat is pretty much a tense affair of smoke bombs and suppressive fire just for any one side to make a push without getting a face full of plasma. Firefights are absolutely brutal with this running.

Danger zone still has effect, but Mayhem didn't seem to do anything.

Can you please elaborate on step 2? I'm not sure exactly what you mean here.

Currently researching a method to tie in the reaction modifier to the leveling system, though from the looks of it, it'll take more than just slapping iReaction=10 to the SoldierStatProgression setting.

I need some help with that though. What I've been doing so far is comparing extracted files and then going back to the upk to make alterations to them. This works for const files which have very small sizes and so are easy to decipher, but not so much for things like the function files, which are larger. What methods do you use for navigating the upk file for larger scale hex editting? For example, this case in the XGAbility tree. { // End:0x2b5 Loop:False if(!kAbility.m_kUnit.m_bInfiniteGrenades) { kAbility.m_kUnit.SetFragGrenades(kAbility.m_kUnit.GetFragGrenades() - 1); } } How would you navigate to it in the upk with a hex editor?

I'd like to know how you managed to edit the ability tree in human readable format. I'm stuck with clunky hex edits.

I tried it on a loaded game. Didn't do anything. Do I have to start a fresh game for it to take effect?

Wait, there's a packer? I've been hex editing the the upk directly.

Can you clarify on the second? The only character array with a reaction value is the same one that lists civilians along with the rest of the alien troops. Did you mean that one? And if so, which one is the one for XCOM troops? Soldier?

No, just the base install folder.

What have you got so far that works Daemonjax? I'm still experimenting with it, but nothing simple to change with immediately apparent effects has popped up on my search.

Well damn. I've tried editing the number of grenades and rockets available in xcomgame.upk, but none of the changes seem to be taking. Looks like the XGTacticalGameCoreNativeBase sub field may be a red herring.

Running two concurrent mods. One with changes to the .ini files which hasn't had any severe problems (random crashes, but not too frequent), and the other which was the base_num_rockets.const I figured it could have been a constant that only loads in a new game, so I tried starting a fresh game, which caused all the errors to pop up. Might not be related to the modifications I made, but the timing is pretty damning. Right now, I'm having Steam do a verification to clean up all the files, and starting from scratch again.

Damnit. I think I broke something somewhere. Loading an existing game is fine, but if I try to start a new one, it crashes on me. I'll have to start from scratch again.