Jump to content

Recommended Posts

Posted

I wish to make a compile of Classic Interlude Client - generally it is modified client of Grand Crusade with protocol 110. I am able to compile a new Interface based on Grand Crusade Client Compiler archive and even it works, but... I found that UE Explorer 1.4.5  able to decompile just Interface.u package. For Instance Core.u and Engine.u I can't decompile with. it thrwong message that "This package has unknown signature".:
image.png.69fee092655fc8b12f0bf95a9b35df2b.png

I also installed UT Package Tool v2.0 beta 5 - and I able to decompile package.... but the source code that it produce Compile can't  recognize:
 

Compiler_Interface-Grand_Crusade\Core\Classes\Object.uc(25) : Error, Unrecognized type 'Vector'
Compile aborted due to errors.
Failure - 1 error(s), 0 warning(s)

 

More over, I found that UE Explorer source code that produce UT Package Tool are sligtly different, for instanse :
 

function openDialogNumpad (INT64 Adena)
{
  Class'UICommonAPI'.DialogSetID(200001);
  Class'UICommonAPI'.DialogSetEditType("number");
  Class'UICommonAPI'.DialogSetParamInt64(Adena);
  Class'UICommonAPI'.DialogSetDefaultOK();
  Class'UICommonAPI'.DialogShow(1,6,GetSystemString(3138),string(self));
}

function HandleDialogCancel ()
{
}

function HandleDialogOK ()
{
  local INT64 inputNum;
  local int Id;

  if (  !Class'UICommonAPI'.DialogIsOwnedBy(string(self)) )
  {
    return;
  }
  Id = Class'UICommonAPI'.DialogGetID();
  if ( Id == 200001 )
  {
}

 

UE Explorer:

 

function openDialogNumpad(INT64 Adena)
{
    Class'UICommonAPI'.static.DialogSetID(200001);
    Class'UICommonAPI'.static.DialogSetEditType("number");
    Class'UICommonAPI'.static.DialogSetParamInt64(Adena);
    Class'UICommonAPI'.static.DialogSetDefaultOK();
    Class'UICommonAPI'.static.DialogShow(1, 6, GetSystemString(3138), string(self));
    return;
}

function HandleDialogCancel()
{
    return;
}

function HandleDialogOK()
{
    local INT64 inputNum;
    local int Id;

    // End:0x19
    if(!Class'UICommonAPI'.static.DialogIsOwnedBy(string(self)))
    {
        return;
    }
    Id = Class'UICommonAPI'.static.DialogGetID();
    // End:0x87
    if(Id == 200001)
    {
        inputNum = (Class'UICommonAPI'.static.DialogGetString());
        CallGFxFunction("AdenaDistributionWnd", "HandleDialogOK", (inputNum));
    }
    return;
}

 

 

It seems like compiler requires to have return, cause otherwise it throws:
 

Compiler_Interface-Grand_Crusade\Interface\Classes\AdenaDistributionWnd.uc(96) : Error, Unexpected end of file at end of Class
Compile aborted due to errors.
Failure - 1 error(s), 0 warning(s)

 

After considering compilers and content of UE Explorer and UT Package Tooll I found that it seems like they noth rely on UCC . I also found documentation how to use it :

UCC-wiki

 

BatchExport

  • Package: Editor
  • Syntax: batchexport package.ext classname export_ext [path]
  • Availability: Unreal v226* onwards, UT v436 onwards, Unreal II, UT2003, UT2004.

Exports resources from Unreal packages in bulk.

  • package.ext: Package whose objects you wish to export. Extension and directory are optional: (e.g. Botpack.u, ..\Maps\CTF-Face.unr or just CTF-Face)
  • classname: The type of objects to export from the package. It can be one of class, texture, sound, music, level, model, polys or textbuffer.
  • export_ext: Extension used for the exported files. The accepted file extensions per class are as follows:
  • class: uc, h.
  • texture: bmp, pcx.
  • sound: wav.
  • music: s3m, xm, it or any other tracker format.
  • level, model and polys: t3d. level exports the complete map with all actors and brushes; model exports all the brushes used in a map (with the red builder being Brush.t3d while the other brushes being Model##.t3d); and polys exports polygons (?) to files named Polys#.t3d.
  • textbuffer: txt. Exports all kinds of text sources in the package. Script code is exported as ScriptCode.txt for each class, so the files will instantly overwrite each other. Maps have an additional text buffer with camera settings for UnrealEd.
  • path: Path to export files to, like C:\MyPath.

 

but when I tried to execute it:

 

\Compiler_Interface-Grand_Crusade\System>UCC.exe batchexport Interface.u class uc Classes\
=======================================
ucc.exe: UnrealOS execution environment
Copyright 2001 Epic Games Inc
=======================================

Commandlet batchexport not found

 

 

So, please help me to found proper decompiler. Many thanks!

 

Posted

You can't extract that with UE Explorer because you haven't decompressed the files. 

https://prnt.sc/VwM8ISeUppuP

 

However, you won't get 'clean' source files with utpt nor ue explorer, you can maybe make some sort of frankenstein on your current compiler's engine.u by using the scripts extracted from ue explorer as reference, manually adding missing scripts/parts of the .uc scripts that don't exist in your current compiler, etc.

The reason why you get an error when using batchexport, is because your compiler is probably missing some file.
usually your .ini should look sorta like this:

EditPackages=Core
EditPackages=Engine
EditPackages=Editor
EditPackages=Fire

and batchexport should work fine. However, this will probably also not give you the result that you expect.

 

Whichever way you use to decompile those files, you'll have to do some manual work, shouldn't take more than a couple of hours, or maybe a few minutes depending on what you're trying to do.

Posted
13 hours ago, 911reg said:

You can't extract that with UE Explorer because you haven't decompressed the files. 

https://prnt.sc/VwM8ISeUppuP

 

However, you won't get 'clean' source files with utpt nor ue explorer, you can maybe make some sort of frankenstein on your current compiler's engine.u by using the scripts extracted from ue explorer as reference, manually adding missing scripts/parts of the .uc scripts that don't exist in your current compiler, etc.

The reason why you get an error when using batchexport, is because your compiler is probably missing some file.
usually your .ini should look sorta like this:

EditPackages=Core
EditPackages=Engine
EditPackages=Editor
EditPackages=Fire

and batchexport should work fine. However, this will probably also not give you the result that you expect.

 

Whichever way you use to decompile those files, you'll have to do some manual work, shouldn't take more than a couple of hours, or maybe a few minutes depending on what you're trying to do.

 

I wish to decompile all package to create not only interface, but other packages compiler. I have found for instance that my version of Core.u contains additional class named HelloWorldCommandlet , that original Grand Crusade provided but Client Compiler, so I wish to revise existing package and able to modify them if needed.

 

16 hours ago, 911reg said:

You can't extract that with UE Explorer because you haven't decompressed the files. 

https://prnt.sc/VwM8ISeUppuP

 

However, you won't get 'clean' source files with utpt nor ue explorer, you can maybe make some sort of frankenstein on your current compiler's engine.u by using the scripts extracted from ue explorer as reference, manually adding missing scripts/parts of the .uc scripts that don't exist in your current compiler, etc.

The reason why you get an error when using batchexport, is because your compiler is probably missing some file.
usually your .ini should look sorta like this:

EditPackages=Core
EditPackages=Engine
EditPackages=Editor
EditPackages=Fire

and batchexport should work fine. However, this will probably also not give you the result that you expect.

 

Whichever way you use to decompile those files, you'll have to do some manual work, shouldn't take more than a couple of hours, or maybe a few minutes depending on what you're trying to do.

 

 

My l2.ini :
 

[Engine.Engine]
EditorEngine=Editor.EditorEngine

[Core.System]
Paths=../System/*.u

[Editor.EditorEngine]
CacheSizeMegs=32

EditPackages=Core
EditPackages=Engine
EditPackages=Fire
EditPackages=Editor
EditPackages=NWindow
EditPackages=Interface

 

I have unpacked Core.u, Engine.u and now can properly vuew them throw the UE Explorer, but batchexport are still printing:
 

\Compiler_Interface-Grand_Crusade\System> ./UCC.exe batchexport Editor.u class ./Classes

=======================================
ucc.exe: UnrealOS execution environment
Copyright 2001 Epic Games Inc
=======================================

Commandlet batchexport not found

 

 

Maybe some wrong syntax on windows pc?

 

16 hours ago, 911reg said:

You can't extract that with UE Explorer because you haven't decompressed the files. 

https://prnt.sc/VwM8ISeUppuP

 

However, you won't get 'clean' source files with utpt nor ue explorer, you can maybe make some sort of frankenstein on your current compiler's engine.u by using the scripts extracted from ue explorer as reference, manually adding missing scripts/parts of the .uc scripts that don't exist in your current compiler, etc.

The reason why you get an error when using batchexport, is because your compiler is probably missing some file.
usually your .ini should look sorta like this:

EditPackages=Core
EditPackages=Engine
EditPackages=Editor
EditPackages=Fire

and batchexport should work fine. However, this will probably also not give you the result that you expect.

 

Whichever way you use to decompile those files, you'll have to do some manual work, shouldn't take more than a couple of hours, or maybe a few minutes depending on what you're trying to do.

 

 

My l2.ini :
 

[Engine.Engine]
EditorEngine=Editor.EditorEngine

[Core.System]
Paths=../System/*.u

[Editor.EditorEngine]
CacheSizeMegs=32

EditPackages=Core
EditPackages=Engine
EditPackages=Fire
EditPackages=Editor
EditPackages=NWindow
EditPackages=Interface

 

I have unpacked Core.u, Engine.u and now can properly vuew them throw the UE Explorer, but batchexport are still printing:
 

\Compiler_Interface-Grand_Crusade\System> ./UCC.exe batchexport Editor.u class ./Classes

=======================================
ucc.exe: UnrealOS execution environment
Copyright 2001 Epic Games Inc
=======================================

Commandlet batchexport not found

 

The help command of UCC:

Compiler_Interface-Grand_Crusade\System> ./UCC help
=======================================
ucc.exe: UnrealOS execution environment
Copyright 2001 Epic Games Inc
=======================================

Usage:
   ucc <command> <parameters>

Commands for "ucc":
   ucc help <command>        Get help on a command
   ucc mastermd5 [*.ext {*.ext ...} ] Generate the master MD5 table
   ucc server                Network game server

 

Maybe some wrong syntax on windows pc?

 

Posted

Could also be the case that you're missing editor.int in your compiler's folder.
 

[Public]
Object=(Name=Editor.BatchExportCommandlet,Class=Class,MetaClass=Core.Commandlet)
Object=(Name=Editor.BatchDecompileCommandlet,Class=Class,MetaClass=Core.Commandlet)

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • I fixed it now my friends can join too, with what do you want help with? Also can you upload the interlude client of gx-ext for c4? just to have it because i deleted the rar i just have the folder
    • me ayudas a montar ese pack por que no entiendo tanto es para tener de prueba
    • GX-C4 pack, its ok...just used it.
    • This post originally appeared on MmoGah. Arena Breakout: Infinite is a hardcore tactical extraction shooter that demands precision, patience, and strategy. This guide will walk you through everything a beginner needs to know—from gear and combat to survival and extraction.     What Is Arena Breakout: Infinite? Arena Breakout: Infinite (ABI) is a free-to-play online extraction shooter developed by MoreFun Studios and released on Steam in September 2025. Unlike traditional battle royales, ABI focuses on risk vs. reward rather than being the last one standing. Players enter instanced maps called "raids," where they must scavenge loot, survive enemy encounters, and extract safely.   Core Gameplay Mechanics 1. Raids and Extraction Each raid features 4–6 teams (solo or squad) dropped into a map. The goal is to loot valuable items and extract through designated points. Extraction is not exclusive—multiple teams can leave the map alive. 2. PvPvE Combat You'll face both human players and AI enemies. AI can be unpredictable and deadly, especially in high-tier zones. 3. No Hand-Holding ABI offers no tutorials or guidance. You learn by dying—and surviving.   Gear and Loadouts 1. Choose Wisely Your gear determines your survivability. Armor, helmets, and medical supplies are essential. Weapons vary in recoil, damage, and handling. Start with low-cost rifles like the AKS-74U or MP5. 2. Insurance System You can insure gear to recover it if you die and it isn't looted. Use insurance for expensive items, but don't rely on it blindly. 3. Backpacks and Storage Larger backpacks allow more loot but make you a bigger target. Organize your inventory to quickly access meds and ammo during combat.   Tactical Tips for Beginners 1. Know What to Loot Prioritize high-value items like weapon parts, medical kits, and rare electronics. Learn loot hotspots on each map—warehouses, bunkers, and military zones often yield better gear. 2. Sound Is Everything Footsteps, gunfire, and reloads are loud. Use headphones and move cautiously. Crouch-walking and slow peeking reduce noise and improve stealth. 3. Map Knowledge Study maps offline or in low-risk raids. Learn extraction points, choke zones, and sniper nests. 4. Stamina Management Sprinting drains stamina, which affects aim and movement. Rest in safe zones and avoid overexertion during firefights.   Combat and Survival 1. Engage Smartly Don't chase kills—survival and extraction are the real goals. Use cover, lean mechanics, and suppressive fire to control fights. 2. Healing and Damage ABI features a detailed health system: limbs can be fractured, bleeding, or disabled. Carry splints, bandages, and painkillers. Know how to treat each condition. 3. Death Is a Lesson You will die—a lot. Use each death to learn positioning, gear value, and enemy behavior.   Progression and Economy 1. Free-to-Play Friendly ABI is generous with starter gear and daily rewards. You can earn the currency Arena Breakout: Infinite Koens through successful raids and selling loot. 2. Marketplace Trade gear with other players or sell to vendors. Prices fluctuate—learn market trends to maximize profit. 3. No Skill Trees Unlike similar games, ABI doesn't use operator skills. Progression is gear-based and tactical, not RPG-style.   Settings and Optimization 1. Graphics and Performance Lower shadows and post-processing for better visibility. Use high FPS settings for smoother combat. 2. Keybinds Customize controls for quick access to healing, leaning, and inventory. Practice muscle memory in offline raids. 3. Audio Settings Maximize footstep and gunfire volume. Reduce ambient noise to focus on threats.   Beginner Loadout Recommendation Slot Item Notes Primary Gun AKS-74U or MP5 Low recoil, easy to handle Secondary Pistol (optional) Backup for emergencies Armor Basic Vest Better than nothing Helmet Light Helmet Protects against headshots Backpack Medium Balance between space and size Meds Bandages, Splints Treat bleeding and fractures Ammo 2–3 extra mags Always reload before fights         Final Advice for New Players Start slow: Don't rush into high-tier zones. Learn the basics in low-risk areas. Play with friends: Squad play improves survival and makes learning easier. Watch and learn: Study streamers and guides to understand advanced tactics. Don't hoard: Use your gear. Hoarding leads to stagnation and fear of loss. Extract often: Surviving and extracting builds confidence and resources. Arena Breakout: Infinite is brutal, but deeply rewarding. With patience and practice, you'll evolve from a terrified scavenger to a confident operator. Every raid is a story—make yours one of survival and triumph.
  • Topics

×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock