<![CDATA[Eliot's Forum - Unreal File Format]]>

<![CDATA[Eliot's Forum - Unreal File Format]]> https://eliotvu.com/forum/ Mon, 04 May 2026 13:44:18 +0000 MyBB <![CDATA[Hi is it possible to get better names for obfuscated packages?]]> https://eliotvu.com/forum/showthread.php?tid=565 Tue, 18 Mar 2025 17:38:38 +0000 rubening87]]> https://eliotvu.com/forum/showthread.php?tid=565
but in that case will it handle this situation :

Some obfuscated classes are tricky, because some variables of different type, are called the same way, so replacing words in a text editor is not a good idea (not even talking about local variables in different functions..) i talk about global vars .. for example a string being the same name as an int. and so on.. it can happen and it doesnt make it easier...

i was wonder is there a way to differ those names in the data table or something making them read differently when i see the files as text?]]>
but in that case will it handle this situation :

Some obfuscated classes are tricky, because some variables of different type, are called the same way, so replacing words in a text editor is not a good idea (not even talking about local variables in different functions..) i talk about global vars .. for example a string being the same name as an int. and so on.. it can happen and it doesnt make it easier...

i was wonder is there a way to differ those names in the data table or something making them read differently when i see the files as text?]]> <![CDATA[Arrays Data Structure]]> https://eliotvu.com/forum/showthread.php?tid=525 Sun, 04 Dec 2022 22:34:01 +0000 RadiantBastard]]> https://eliotvu.com/forum/showthread.php?tid=525 Hey Eliot, do you have any information on the structure of arrays?

I'm working on a project and need to modify an array to change the flight characteristics for an aircraft in this game. I used UE Explorer to view the actor class in the .u file, and pull the array from the default properties.

Array=(Points=/* Array type was not detected. */,InVal=0,OutVal=0,ArriveTangent=0,LeaveTangent=0,InterpMode=0)

I used UE Explorer's Default Properties table buffer and Hex Workshop to extract the raw binary for the array.

(Formatted in 32 bit chunks so it's readable. Almost certainly NOT the correct formatting.)

4F 3A 00 00 00 00 00 00 ED 40 00 00 00 00 00 00
D7 01 00 00 00 00 00 00 E9 23 00 00 00 00 00 00
01 37 00 00 00 00 00 00 23 02 00 00 00 00 00 00
B7 01 00 00 00 00 00 00 03 00 00 00 F6 23 00 00
00 00 00 00 94 17 00 00 00 00 00 00 04 00 00 00
00 00 00 00 00 00 00 00 FC 34 00 00 00 00 00 00
94 17 00 00 00 00 00 00 04 00 00 00 00 00 00 00
00 00 00 00 24 02 00 00 00 00 00 00 94 17 00 00
00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00
BD 25 00 00 00 00 00 00 94 17 00 00 00 00 00 00
04 00 00 00 00 00 00 00 00 00 00 00 EB 23 00 00
00 00 00 00 C0 07 00 00 00 00 00 00 01 00 00 00
00 00 00 00 00 BC 32 00 00 00 00 00 00 F6 23 00
00 00 00 00 00 94 17 00 00 00 00 00 00 04 00 00
00 00 00 00 00 00 00 7A 44 FC 34 00 00 00 00 00
00 94 17 00 00 00 00 00 00 04 00 00 00 00 00 00
00 00 00 80 3E 24 02 00 00 00 00 00 00 94 17 00
00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00
00 BD 25 00 00 00 00 00 00 94 17 00 00 00 00 00
00 04 00 00 00 00 00 00 00 00 00 00 00 EB 23 00
00 00 00 00 00 C0 07 00 00 00 00 00 00 01 00 00
00 00 00 00 00 00 BC 32 00 00 00 00 00 00 F6 23
00 00 00 00 00 00 94 17 00 00 00 00 00 00 04 00
00 00 00 00 00 00 00 A0 8C 45 FC 34 00 00 00 00
00 00 94 17 00 00 00 00 00 00 04 00 00 00 00 00
00 00 00 00 80 3F 24 02 00 00 00 00 00 00 94 17
00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00
00 00 BD 25 00 00 00 00 00 00 94 17 00 00 00 00
00 00 04 00 00 00 00 00 00 00 00 00 00 00 EB 23
00 00 00 00 00 00 C0 07 00 00 00 00 00 00 01 00
00 00 00 00 00 00 00 BC 32 00 00 00 00 00 00 BC
32 00 00 00 00 00 00

My next step is just brute force it by searching for known values, and trying to put the pieces together. I figured I'd ask if you had any information on the structure of the compiled arrays to make the process of bashing my head into my keyboard a little bit less headachey. Big Grin

Any and all info on the matter is greatly appreciated. ]]> Hey Eliot, do you have any information on the structure of arrays?

I'm working on a project and need to modify an array to change the flight characteristics for an aircraft in this game. I used UE Explorer to view the actor class in the .u file, and pull the array from the default properties.

Array=(Points=/* Array type was not detected. */,InVal=0,OutVal=0,ArriveTangent=0,LeaveTangent=0,InterpMode=0)

I used UE Explorer's Default Properties table buffer and Hex Workshop to extract the raw binary for the array.

(Formatted in 32 bit chunks so it's readable. Almost certainly NOT the correct formatting.)

4F 3A 00 00 00 00 00 00 ED 40 00 00 00 00 00 00
D7 01 00 00 00 00 00 00 E9 23 00 00 00 00 00 00
01 37 00 00 00 00 00 00 23 02 00 00 00 00 00 00
B7 01 00 00 00 00 00 00 03 00 00 00 F6 23 00 00
00 00 00 00 94 17 00 00 00 00 00 00 04 00 00 00
00 00 00 00 00 00 00 00 FC 34 00 00 00 00 00 00
94 17 00 00 00 00 00 00 04 00 00 00 00 00 00 00
00 00 00 00 24 02 00 00 00 00 00 00 94 17 00 00
00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00
BD 25 00 00 00 00 00 00 94 17 00 00 00 00 00 00
04 00 00 00 00 00 00 00 00 00 00 00 EB 23 00 00
00 00 00 00 C0 07 00 00 00 00 00 00 01 00 00 00
00 00 00 00 00 BC 32 00 00 00 00 00 00 F6 23 00
00 00 00 00 00 94 17 00 00 00 00 00 00 04 00 00
00 00 00 00 00 00 00 7A 44 FC 34 00 00 00 00 00
00 94 17 00 00 00 00 00 00 04 00 00 00 00 00 00
00 00 00 80 3E 24 02 00 00 00 00 00 00 94 17 00
00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00
00 BD 25 00 00 00 00 00 00 94 17 00 00 00 00 00
00 04 00 00 00 00 00 00 00 00 00 00 00 EB 23 00
00 00 00 00 00 C0 07 00 00 00 00 00 00 01 00 00
00 00 00 00 00 00 BC 32 00 00 00 00 00 00 F6 23
00 00 00 00 00 00 94 17 00 00 00 00 00 00 04 00
00 00 00 00 00 00 00 A0 8C 45 FC 34 00 00 00 00
00 00 94 17 00 00 00 00 00 00 04 00 00 00 00 00
00 00 00 00 80 3F 24 02 00 00 00 00 00 00 94 17
00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00
00 00 BD 25 00 00 00 00 00 00 94 17 00 00 00 00
00 00 04 00 00 00 00 00 00 00 00 00 00 00 EB 23
00 00 00 00 00 00 C0 07 00 00 00 00 00 00 01 00
00 00 00 00 00 00 00 BC 32 00 00 00 00 00 00 BC
32 00 00 00 00 00 00

My next step is just brute force it by searching for known values, and trying to put the pieces together. I figured I'd ask if you had any information on the structure of the compiled arrays to make the process of bashing my head into my keyboard a little bit less headachey. Big Grin

Any and all info on the matter is greatly appreciated. ]]> <![CDATA[Decompiling Switch statments]]> https://eliotvu.com/forum/showthread.php?tid=107 Sat, 21 Mar 2015 15:46:22 +0000 ELiZ]]> https://eliotvu.com/forum/showthread.php?tid=107
I'm trying to decompiling some switchstatments, and are hitting a brick wall, most of them are decompiled correctly, but some don't.

I'm using UTPT and UE Explorer to check my results.
I also has an almost complete original source of the game as well.

The original Code:

Code:
static event string GetDescriptionText(string PropName)

{

    switch (PropName)

    {

        case "ServerName":    

            return default.GRIPropDescText[0];

        case "AdminName":    

            return default.GRIPropDescText[1];

        case "AdminEmail":    

            return default.GRIPropDescText[2];

        case "MessageOfTheDay":    

            return default.GRIPropDescText[3];

    }

    return Super.GetDescriptionText(PropName);

}

UE Explorer

Code:
static event string GetDescriptionText(string PropName)

{

    switch(PropName)

    {

        case "ServerName":

            return default.GRIPropDescText[0];

        case "AdminName":

            return default.GRIPropDescText[1];

        case "AdminEmail":

            return default.GRIPropDescText[2];

        case "MessageOfTheDay":

            return default.GRIPropDescText[3];

        default:

            return super(Info).GetDescriptionText(PropName);

    }

    //return;    

}

UTPT

Code:
function string GetDescriptionText(string PropName)

{

    switch (PropName)

    {

        case "ServerName":

        return Default.GRIPropDescText[0];

        case "AdminName":

        return Default.GRIPropDescText[1];

        case "AdminEmail":

        return Default.GRIPropDescText[2];

        case "MessageOfTheDay":

        return Default.GRIPropDescText[3];

        default:

    }

    return Super.GetDescriptionText(PropName);

    return;

}

The problem is "return Super.GetDescriptionText(PropName);" witch in the original code is after the switch code, UTPT places it correctly, but UE explorer places it in default:
My code is even worse, and that is why I was looking into why.

Here is the raw hex:
[Image: j60vhs.png]

I suspect that the problem occurs because the default: is empty in the switch

This is from Unreal Tournament Package File Format(v1.6).pdf by Antonio Cordero.

Quote:Size is the size of the Condition

expression. The end of the switch
is unknown except maybe for
some hints inside it.

It might also be just this game that has the issue(America's Army 2.5), but I hope that you have an idea how to detect the end of the switch in this cases.]]>
I'm trying to decompiling some switchstatments, and are hitting a brick wall, most of them are decompiled correctly, but some don't.

I'm using UTPT and UE Explorer to check my results.
I also has an almost complete original source of the game as well.

The original Code:

Code:
static event string GetDescriptionText(string PropName)

{

    switch (PropName)

    {

        case "ServerName":    

            return default.GRIPropDescText[0];

        case "AdminName":    

            return default.GRIPropDescText[1];

        case "AdminEmail":    

            return default.GRIPropDescText[2];

        case "MessageOfTheDay":    

            return default.GRIPropDescText[3];

    }

    return Super.GetDescriptionText(PropName);

}

UE Explorer

Code:
static event string GetDescriptionText(string PropName)

{

    switch(PropName)

    {

        case "ServerName":

            return default.GRIPropDescText[0];

        case "AdminName":

            return default.GRIPropDescText[1];

        case "AdminEmail":

            return default.GRIPropDescText[2];

        case "MessageOfTheDay":

            return default.GRIPropDescText[3];

        default:

            return super(Info).GetDescriptionText(PropName);

    }

    //return;    

}

UTPT

Code:
function string GetDescriptionText(string PropName)

{

    switch (PropName)

    {

        case "ServerName":

        return Default.GRIPropDescText[0];

        case "AdminName":

        return Default.GRIPropDescText[1];

        case "AdminEmail":

        return Default.GRIPropDescText[2];

        case "MessageOfTheDay":

        return Default.GRIPropDescText[3];

        default:

    }

    return Super.GetDescriptionText(PropName);

    return;

}

I suspect that the problem occurs because the default: is empty in the switch

This is from Unreal Tournament Package File Format(v1.6).pdf by Antonio Cordero.

Quote:Size is the size of the Condition

expression. The end of the switch
is unknown except maybe for
some hints inside it.

It might also be just this game that has the issue(America's Army 2.5), but I hope that you have an idea how to detect the end of the switch in this cases.]]> <![CDATA[[INFO] Structures]]> https://eliotvu.com/forum/showthread.php?tid=85 Sat, 31 Aug 2013 06:51:29 +0000 sh!ft]]> https://eliotvu.com/forum/showthread.php?tid=85
This is just something to get you started. I personally wrote mine in C.. Cause I really find C++ becomes far too extravagant for absolutely no reason except programmer preference half the time.

Code:
#pragma pack(push, 1)

/**

 * If you really wanna bother going around and writing your own stream processor like Eliot just to ensure your endianness is correct, do it.

 * Otherwise, let's use this compiler/preprocessor trick to so we can literally cast a block of memory to our structure and not have to write parsing code ourselves.

 */

#ifdef __INTEL__

#undef __INTEL__

#endif 

#define __INTEL__ 1

#define __INTEL_BYTE_ORDER__ 1

typedef void* VPTR;

typedef unsigned __int32 DWORD, NAME_INDEX;

typedef signed __int32 INT, UBOOL;

typedef unsigned __int8 TCHAR;

struct FPair

{

  VPTR Key;

  VPTR Value;

};

struct FMap

{

  FPair *Data;

  DWORD ArrayNum;

  DWORD ArrayMax;

  DWORD *Hashes;

  DWORD HashCount;

};

struct FArray

{

  void *Data;

  DWORD ArrayNum;

  DWORD ArrayMax;

};

struct FGuid

{

  DWORD A;

  DWORD B;

  DWORD C;

  DWORD D;

};

struct FString

{

  TCHAR *Data;

  INT Length;

  INT Limit;

};

struct FName

{

  NAME_INDEX Index;

  WORD Number;

  WORD Size;

};

struct FPackageFileSummary

{

  INT Tag;

  INT FileVersion;

  DWORD PackageFlags;

  INT NameCount;

  INT NameOffset;

  INT ExportCount;

  INT ExportOffset;

  INT ImportCount;

  INT ImportOffset;

  FGuid Guid;

  FArray Generations;

};

struct FArchiveItem

{

  FString _Filename_;

  DWORD Offset;

  DWORD Size;

  DWORD Flags;

};

struct FArchiveHeader

{

  INT Magic;

  INT TableOffset;

  INT FileSize;

  INT Ver;

  INT CRC;

  FArray _Items_;

};

struct FArchive

{

  INT ArVer;

  INT ArNetVer;

  INT ArLicenseeVer;

  UBOOL ArIsLoading;

  UBOOL ArIsSaving;

  UBOOL ArIsTrans;

  UBOOL ArIsPersistent;

  UBOOL ArForEdit;

  UBOOL ArForClient;

  UBOOL ArForServer;

  UBOOL ArIsError;

  UBOOL ArIsCriticalError;

  UBOOL ArContainsCode;

  INT ArMaxSerializeSize;

  INT Stopper;

};

#pragma pop

]]>
This is just something to get you started. I personally wrote mine in C.. Cause I really find C++ becomes far too extravagant for absolutely no reason except programmer preference half the time.

Code:
#pragma pack(push, 1)

/**

 * If you really wanna bother going around and writing your own stream processor like Eliot just to ensure your endianness is correct, do it.

 * Otherwise, let's use this compiler/preprocessor trick to so we can literally cast a block of memory to our structure and not have to write parsing code ourselves.

 */

#ifdef __INTEL__

#undef __INTEL__

#endif 

#define __INTEL__ 1

#define __INTEL_BYTE_ORDER__ 1

typedef void* VPTR;

typedef unsigned __int32 DWORD, NAME_INDEX;

typedef signed __int32 INT, UBOOL;

typedef unsigned __int8 TCHAR;

struct FPair

{

  VPTR Key;

  VPTR Value;

};

struct FMap

{

  FPair *Data;

  DWORD ArrayNum;

  DWORD ArrayMax;

  DWORD *Hashes;

  DWORD HashCount;

};

struct FArray

{

  void *Data;

  DWORD ArrayNum;

  DWORD ArrayMax;

};

struct FGuid

{

  DWORD A;

  DWORD B;

  DWORD C;

  DWORD D;

};

struct FString

{

  TCHAR *Data;

  INT Length;

  INT Limit;

};

struct FName

{

  NAME_INDEX Index;

  WORD Number;

  WORD Size;

};

struct FPackageFileSummary

{

  INT Tag;

  INT FileVersion;

  DWORD PackageFlags;

  INT NameCount;

  INT NameOffset;

  INT ExportCount;

  INT ExportOffset;

  INT ImportCount;

  INT ImportOffset;

  FGuid Guid;

  FArray Generations;

};

struct FArchiveItem

{

  FString _Filename_;

  DWORD Offset;

  DWORD Size;

  DWORD Flags;

};

struct FArchiveHeader

{

  INT Magic;

  INT TableOffset;

  INT FileSize;

  INT Ver;

  INT CRC;

  FArray _Items_;

};

struct FArchive

{

  INT ArVer;

  INT ArNetVer;

  INT ArLicenseeVer;

  UBOOL ArIsLoading;

  UBOOL ArIsSaving;

  UBOOL ArIsTrans;

  UBOOL ArIsPersistent;

  UBOOL ArForEdit;

  UBOOL ArForClient;

  UBOOL ArForServer;

  UBOOL ArIsError;

  UBOOL ArIsCriticalError;

  UBOOL ArContainsCode;

  INT ArMaxSerializeSize;

  INT Stopper;

};

#pragma pop

]]> <![CDATA[Function Object Precedence]]> https://eliotvu.com/forum/showthread.php?tid=77 Sat, 15 Jun 2013 09:02:32 +0000 ELiZ]]> https://eliotvu.com/forum/showthread.php?tid=77
I'm writing a decompiler for an old game called America's Army 2.8.5
I'm coming along well, but have gotten a bit stuck on operator Precedence.

I see in the release notes for 1.2.2.1 that you have solved this

Quote:Function precedences are now decompiled for example prior update “(4 + 5) * 4” was decompiled as “4 + 5 * 4”

What information do I need?

I have precedence on the native operators defenitions in Core.Object.

native(173) static final operator(18) Float % (float A, float B);
native(174) static final operator(20) Float + (float A, float B);
native(175) static final operator(20) Float - (float A, float B);
native(176) static final operator(24) Bool < (float A, float B);

There is also a property in the function definitions, witch is called OperatorPrecedence(After iNative)

Have I missed any input needed?

The lower the Precedence, the higher the importance of keeping it together?

As I understand it the compiler moves around the operators in a statement so the "rules" will produce a correct output

Can you provide any information on this subject(OperatorPrecedence)?]]>
I'm writing a decompiler for an old game called America's Army 2.8.5
I'm coming along well, but have gotten a bit stuck on operator Precedence.

I see in the release notes for 1.2.2.1 that you have solved this

Quote:Function precedences are now decompiled for example prior update “(4 + 5) * 4” was decompiled as “4 + 5 * 4”

What information do I need?

I have precedence on the native operators defenitions in Core.Object.

native(173) static final operator(18) Float % (float A, float B);
native(174) static final operator(20) Float + (float A, float B);
native(175) static final operator(20) Float - (float A, float B);
native(176) static final operator(24) Bool < (float A, float B);

There is also a property in the function definitions, witch is called OperatorPrecedence(After iNative)

Have I missed any input needed?

The lower the Precedence, the higher the importance of keeping it together?

As I understand it the compiler moves around the operators in a statement so the "rules" will produce a correct output

Can you provide any information on this subject(OperatorPrecedence)?]]> <![CDATA[Hex Editing UPK Files]]> https://eliotvu.com/forum/showthread.php?tid=73 Thu, 02 May 2013 15:33:41 +0000 eliot]]> https://eliotvu.com/forum/showthread.php?tid=73
Link: Hex Editing UPK Files]]>
Link: Hex Editing UPK Files]]> <![CDATA[Function Headers]]> https://eliotvu.com/forum/showthread.php?tid=53 Sat, 22 Dec 2012 05:07:13 +0000 twinj]]> https://eliotvu.com/forum/showthread.php?tid=53
Now I understand that the last 16 bytes in the 48 byte header have size and position information.

Code:
DWORD LineNumber 'in class'. In UE Explorer this can be confirmed lines however do not match perfectly.. 

DWORD unknown

DWORD TextPos ??? I am assuming 'text' to be data loaded in memory. In my short analysis this always seems to be higher than EndOffset and the cave size (endoffset - TextPos) seems to always be a multiple of 4. So I am thinking this has something to do with scripts virtual size. I believe that if you rewrite a script and change the amount of index reads that you must recalculate this..

DWORD EndOffset This is the 'size' of the script from the end of the header to the start of the End of Script token 0x53. Note this size does not include actual load size. Some tokens get expanded to 8 bytes rather than 4. 

BYTEs Script Script Code

BYTES 0x53 plus 15 more. There seems to be some flags in this part. I do not understand the bytes at the end of a function

Code:
DWORD LineNumber 'in class'. In UE Explorer this can be confirmed lines however do not match perfectly.. 

DWORD unknown

DWORD TextPos ??? I am assuming 'text' to be data loaded in memory. In my short analysis this always seems to be higher than EndOffset and the cave size (endoffset - TextPos) seems to always be a multiple of 4. So I am thinking this has something to do with scripts virtual size. I believe that if you rewrite a script and change the amount of index reads that you must recalculate this..

DWORD EndOffset This is the 'size' of the script from the end of the header to the start of the End of Script token 0x53. Note this size does not include actual load size. Some tokens get expanded to 8 bytes rather than 4. 

BYTEs Script Script Code

BYTES 0x53 plus 15 more. There seems to be some flags in this part. I do not understand the bytes at the end of a function

The reason I am asking is because I have re written bytes to do a while loop instead of adding an item manually one by one so I can edit the amount added to a dynamic array rather than get stuck with the hardcoded size.

I am still getting a little stuck on which INDEX objects get 8 bytes and when to add e.g: in jump code.

Anyway, so what is this header and footer information and do I need to adjust anything when Index reads change?[/code][/quote]]]> <![CDATA[Deserializing Unreal Packages - Tables]]> https://eliotvu.com/forum/showthread.php?tid=44 Tue, 06 Nov 2012 11:05:43 +0000 eliot]]> https://eliotvu.com/forum/showthread.php?tid=44 http://eliotvu.com/news/view/35/deserial...ges-tables

Any feedback is welcome!]]> http://eliotvu.com/news/view/35/deserial...ges-tables

Any feedback is welcome!]]> <![CDATA[Deserializing Unreal Packages - Data Structures]]> https://eliotvu.com/forum/showthread.php?tid=43 Sat, 03 Nov 2012 19:00:03 +0000 eliot]]> https://eliotvu.com/forum/showthread.php?tid=43
Here's the link =)
http://eliotvu.com/news/view/34/deserial...structures]]>
Here's the link =)
http://eliotvu.com/news/view/34/deserial...structures]]> <![CDATA[Any chance of publishing your findings?]]> https://eliotvu.com/forum/showthread.php?tid=42 Fri, 02 Nov 2012 15:37:57 +0000 ahnold11]]> https://eliotvu.com/forum/showthread.php?tid=42
Have you ever given any thought into collecting all that info into a document or forum post or whatnot? For those interested in games modding it could be some incredibly useful information.

Or is this information that is proprietary and can not be shared, or maybe it just took a lot of hard work to figure out and learn and you'd rather not share it? (or take too long to write all down Wink

).

Personally myself, I have a very minor modification I'd like to do to an Unreal Engine game. Specifically there is a single UE Script I'd like to change, however no mod tools have been released, so changing a Script would require changing the bytecode, which requires rather intimate knowledge of the bytecode structure itself and the upk organization. Something that for such a small mod is probably not worth spending all the time to learn the whole thing. (Quite literally it's modifying a single line: duplicating a function call, an addition, and division).

Having some form of documentation I could study to learn what I needed to accomplish the task, would actually make the small change a viable thing to try.

No worries if there is any thing preventing you from doing it, I was just curious myself if this was something you might do (or have already done, and I've just missed it).

Either way, thanks for all the work making such a useful and interesting tool.]]> <![CDATA[Feel free to ask any questions regarding .upk files etc]]> https://eliotvu.com/forum/showthread.php?tid=37 Fri, 26 Oct 2012 19:01:10 +0000 eliot]]> https://eliotvu.com/forum/showthread.php?tid=37 I'm surprised to not see any questions here regarding the structure of .NTL, .u, and .upk files.

So yeah feel free to make a new thread asking anything related to bytecodes, structures of files, and whatever else there might be.]]> I'm surprised to not see any questions here regarding the structure of .NTL, .u, and .upk files.

So yeah feel free to make a new thread asking anything related to bytecodes, structures of files, and whatever else there might be.]]> <![CDATA[Help modifying a packge code]]> https://eliotvu.com/forum/showthread.php?tid=33 Fri, 17 Aug 2012 23:16:59 +0000 sskillz]]> https://eliotvu.com/forum/showthread.php?tid=33 I've decompressed a Unreal Engine 3 package using this tool from gildor.org (Unreal Package Decompressor). And I found the address of the variable I wanted to to modify using your great UE Explorer. I than changed it using a
hex editor (Was just a single byte). But now I need to compress the package back so the game won't notice it changed, right now
as uncompressed the game crushes.
Do you know how I go about recompressing it?

Thanks ahead.]]> I've decompressed a Unreal Engine 3 package using this tool from gildor.org (Unreal Package Decompressor). And I found the address of the variable I wanted to to modify using your great UE Explorer. I than changed it using a
hex editor (Was just a single byte). But now I need to compress the package back so the game won't notice it changed, right now
as uncompressed the game crushes.
Do you know how I go about recompressing it?

Thanks ahead.]]>