Quote:
Originally Posted by BlankPerson
*nods* I've noticed in other hacking threads that the general difficulty is that if you kill one of the three, one of the others WILL notice unless it's done carefully.
Although, that Aegis CAN be disabled is a big step in the right direction towards freeing s4 from this retardedly dysfunctional antihack combination, I think.
|
No, it is not. Killing Aegis is not a big deal and it is the smallest step into the direction, there are far bigger ones.
Quote:
|
Speaking of which, I'm actually really surprised that nobody's tossed together some sort of emulator for X-Trap.
|
there are already some xtrap bypasses, they are just not public.
you just have to disable xtrap, aegis and hgwc and emulate the heartbeat packets of xtrap.
Quote:
This might be a dumb question, but...are you sure it's not the reverse?
I mean, xtrap monitors the memory that the game is using, right? Normally, a player will equip one set of equipment and stick with it.
So under normal circumstances, the memory holding inventory information doesn't change often. But you're suggesting that players should change it whenever their IM-stored equipment isn't needed; I would think all this switching around would make xtrap errors MORE common, not less.
Am I making any sense here? D:
|
No, i think you understood me wrong.
XTrap checks if the inventory is the same as it should be.
For example if you take off all your clothes, xtrap notices that and saves the datas.
Now, if you just write the item IDs into the inventory again, without really using the Equip function of S4, xtrap will notice the difference and disconnect you.
So you have to make sure, that the saved datas of xtrap and the real inventory datas differ for an as short time as possible!
Thats why you have to restore before clicking start actually.
Quote:
|
As far as computer differences go, it looks like my setup is similar to yours; the only difference being that I use Windows Firewall. It's doubtful that that's the problem though, as I have it set to be transparent to s4...
|
the windows xp firewall is crap afaik!
you can allow incomming connections but no outcomming ones.
maybe this is the problem, the connection might be blocked.
a few months ago exactly this was my problem, but on win7. the win7 firewall is not as fail as the win xp firewall, so i could allow s4's connections completely and it worked again, but on xp it might be different.
just try to disable the FW.