SW_COVER_INCREASE, any successful use?

[mutonizer]

Can't get it to work for now and eyes bleeding again with all these numbers. I've tried isolating whatever decides the random class selection and there are some odd class selection features in there but couldn't really edit anything relevant and can't seem to make the cover changes work proper.

 

Will check again later on after some tea and biscuits.

[Caiman]

The functions, eh? Lets test that then.

 

The rockets werent just a display error: I wasnt able to shoot a second one(clicked on the empty icon).

[DaGawdfadda]

@Daemonjax

So is the only reason to unpack the upk is to be able to open the files within to find the "references" to w/e we are changing? Once we find the references they are the same within the packed upk? I though I read something like that in another thread.

[Mashadar]

But, if you're used to editing the upk directly, then you're not missing out on anything by doing it that way.

 

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?

[tbkiah]

Unless you understand the bytecode it's difficult... this might help in identifying some thing.. but it's basically trial and error:

 

http://dl.dropbox.com/u/32777109/Games/XCOM%202012/output.txt