About sfall FileSystem.cpp 107 lines

[gvx]

About sfall FileSystem.cpp 107 lines

static const DWORD ptr_xfprintf=0x4DF11C;

Are there problems??

4DF11C-> 4DF1AC

or problems 496 lines??

HookCall(0x4C5F04, &asm_xfprintf);

4C5F04 call 004DF1AC

4C5F04-> 4C5F1B

4C5F1B call 004DF11C

 

[Timeslip]

4DF11C-> 4DF1AC

Yes, I think you're right. The confusion was that db_fprintf calls xvfprintf and db_vfprintf calls xfprintf, instead of the other way around.

I didn't hook db_vfprintf because nothing ever calls it, and then mistakingly linked db_fprintf to xfprintf instead of xvfprintf. Will correct in svn. (Edit: Done)

What're you doing using the file system functions anyway? I added them for my random map generator, and wasn't expecting anyone else to be playing around with them.

 

[NovaRain]

He's porting sfall to Chinese version exe. It seems it's mostly done.

 

[.Pixote.]

What're you doing using the file system functions anyway? I added them for my random map generator, and wasn't expecting anyone else to be playing around with them.

Care to elaborate...

 

[Timeslip]

Care to elaborate...

There's not much else to say. I never came close to finishing it. I was just playing around with methods of having a different map each playthrough.

A few of the more random bits of sfall were to support other little mods of mine. eg. the hs_hexmoveblocking hookscript was for a tower defense conversion, both because my 'towers' were still moving around one hex at a time if I just raised their movement ap cost to 100, and to coral the spawns onto the correct path.