Cabal BR how we made this?

[ynry]

how we made this? whith MHS

[OmegaArma]

LoL, +31.....
You have changed everything on that orb -,- its probally topaz orb or forcium -,-

[zenyth12]

its real ??

[cobr_h]

yes, this is real. until now I had seen just a three-slotted daikatana which had 50% critical damage with three critical damage slots (that should result in 60%) -plus- 20% crit dam in craft. Thought it was a bug if the item had more than 60% in critical damage, some bits were overflew and the +31 happened. It seems it really was made on MHS.. dunno how.

EDIT: about the picture's comments, it is about the screen font the user is using. it is normal, see the last picture, the last lines are all overflowing the box. I saw by myself a -link- to a titanium daikatana as well.

[Obilee]

#moved

[Pupix]

Just client side shet,you can do this with CE too >_> BUT it's just graphic effect,nothing real

[Mikawa]

thats pherystin right?

[.Law.]

Whats so special about that ;o ?
I'll post some screens soon xD

[cobr_h]

well whoever they are they did it and spread the link among the server so everyone could see and copy the link and turn GMs mad

unfortunately it seems wiseco's x-trap since today, has now found a way to block MHS. It kind of scans memory. Only after logging, only and only if you attach MHS to cabalmain.exe, it takes 2-60 seconds to detect a fault and close cabal, although it can't say which 'tool' is accessing the game data.

funny fact: in the morning they apparently blocked xtrap itself. The game was, for about 4 hours, closing upon logging, after a x-trap update. In the beginning of the day, another x-trap update came, and now it closes only when a cheat engine attaches to cabal.exe. tried some different ACC values with no luck.