Search results

Such is the fate of a forum with 0 active staff.

Those bats are dependent of the parent entity and will crash if they haven't got a parent. That being said, it may be possible to have them be child to something other than orangebell.. You mean normal old flags? There's a function for that. 0040E930 - Check Flag (Returns 1 or 0) The param is...

The hitbox is as such 0xA00,0x1000,0xA00,0x1000 Left, up, Right, Down those are game-units.

Dear sir/madame: Please make sure that before you make a new thread that the exact same thing isn't on the exact same page Kind regards, Noxid

I use Paint.NET with antialiasing disabled and overwrite blending, 0% tolerance, mainly sticking to a size 2 pen or using the replace tool. When it's nearly finished, I take the pencil and smooth out all the rough lines or add certain details. Sometimes I use a layer, but usually not...

Figure it out for yourself.

Perhaps that could be taken as evidence to the contrary though.. :0? Because it's hard to hack if you don't feel like it.

I believe I've tested this before and if memory serves, calling a TSC event while in the context of another event does work. Basically, it'd be like jamming an <EVEXXXX into the TSC right at the moment you died.

Alright, let's see what we have here.. 0x419055 - Change that to an 0xEB (basically a JE to JMP) and that *should* allow collisions during TSC events always. In order to have it say, able to be toggled would require a more creative solution (Maybe change the address to refer to a particular...

That's an interesting theory. I wouldn't be able to test this due to compulsive napping at 3PM, but if you ever get the chance be sure to document your results. How'd you break your context menu D: That's not a good sign...

Fun fact: lunarsoul can't ban people, I do that. Also, there are circumstances when a double post is appropriate since I had no idea you did all that stuff or whatever on account of not reading threads that I've already read before.

It's possible >_>; Although there is a good reason for it to be the way it is which I forget I haven't got time to look for it right now though.

3AM is a magical time when I don't care anymore.

I couldn't sleep... It's nothing special.

Will it cost money..?

No.

If you make sure that the value at 414B24 is never more than uh... 0x7F, let's say, when you release then you should be safe at least on this front. Although if memory serves there are other things that might need to be changed for exceptionally large numbers of maps.. Lace would know better...

The size of the memory buffer allocated is 0x80 so 0-127 theoretically should be the safe 'zone' of maps. I don't know exactly how CE calculates it though. Anyway, there's also the option of just assembler/hex editing the value push'd since nobody uses <MPJ anyway.

I have figured out at least Ollie's problem. Compare these two sets of code: CPU Disasm Address Hex dump Command Comments 00414B20 /$ 55 push ebp ; Dokutsu_Clean.00414B20(guessed void) 00414B21 |. 8BEC...

I'm not familiar with this glitch.

It should, assuming you calculate it correctly. Remember that the first map is zero.

Ah, let's see... you should be able to calculate it. 4BF000 + (Map Number * 0xC8) + 0x40

That should fix it, yes.

oh, sorry, I meant to say 4BF9A0. Make sure that says 02 00 00 00, because it didn't in the .exe you gave Lace.

If it doesn't trigger, that means the value of the Map Scroll Type was greater than 7, which usually indicates bad data.