ZenHAX

You see, you spotted a bug I introduced in the beta that it would have been hard for me to find.
The problem was caused by setting a pointer to NULL and then using it (output->sub_var->*)
Fixed in the local beta that I will upload in the week-end.

I really tought 4096 commands was an extremely big number but apparently I was wrong.
My longest script is probably next_car_game.bms which has 1500 commands.
I'm now checking if I can remove that limit by making the number of commands unlimited.

Making the number of commands dynamic is a mess.
The only thing I can do is increasing the limit like 8k instead of the current 4k.

Ah, the new beta is out in case you want to test the fixes.

thank you sir aluigi
everything works great, i think it can be release
but there is a minor problem (minor? don't know what's going on in code, so forgive me if i don't have good notion)
using filter request overwrite

That's Windows console that makes a mess.
Use {} instead of * and it will work: -f "{}.png"

two problem

1) commenting

get MY_VAR_1 long 0#comment 1
get MY_VAR_2 long#comment 2

Error: invalid datatype long#comment at line 2

Last script line before the error or that produced the error:
2 get MY_VAR_2 long#comment 2

adding # next to the syntax will cause this problem, but not in file number
not a problem and can solve it just with one space before #, but i reported it anyway...

2) using -f (filter)
i think filter option not working as well in newer betas, for example, i can use -f "*file_00_*" in older verions, but in last beta, it's not working (maybe in current betas too)
and i used {} too... but didn't worked

please check batch files in my attached file
all of batch files works fine in older versions (for example: 0.9.1)

1)
yeah not really a problem

2)
I don't why it may have worked in older versions but on Windows I have never seen asterisks working in arguments due to how they get interpreted by the console, no matter if they are enclosed in quotes (that's the crazy thing indeed).
As already suggested, use ever {} instead of *.

P.S.: beta no longer exists now, please refer to version 0.11 for any report

Keep getting a error when trying to extract a pak file in unreal tournament 4.

error in src\extra\xalloc.c line 618: xdbg_malloc()

It says Error: memory allocation problem Not enough memory resources are available to process this command.
Using latest versions of both. Should have plenty of memory running it off a mobile workstation.

@Theboy
It means the script is not compatible with your file.
The topic for any question/request/issue about UE4 is viewtopic.php?f=9&t=1005