ExclamationDanZ ROTMG Fullscreen Hacks Pack

Posts 114 of 14 · Page 1 of 1
DanZ ROTMG Fullscreen Hacks Pack
DanZ's Multiple Fullscreen Hacks Pack

Instructions:

Download the Hack Pack

Choose your Hack

Open it with your Internet Browser (Google Chrome, etc.)


Features:

AimBot ( Press i )

AutoNexus at 30% Health (Some Have and Some Don't)

Connection Messages

No Debuffs

Video: (Same as Video, but with Fullscreen and Some Have Autonexus and Some Don't for the people who don't like Autonexus)


Virus Scans:
Jotti's Scan
Virus Total
Jotti's Scan 1920x1080
Virus Total 1920x1080

DOWNLOAD AND THANKS!!!

Added 1920x1080

Credits to: Nilly
DGS ROTMG Hacks Fullscreen Versions v123.5.1_mpgh.net.rar8.3 MB · 158 downloads Scanning…
DGS ROTMG Hack Fullscreen 1920x1080_mpgh.net.rar2.1 MB · 68 downloads Scanning…
Approved
1600x900 is totally wrong, I posted the right numbers, in the fullscreen post of Nilly, maybe you only stole the first page ^^

if you want to adjust "your" fullscreen hack for 1600*900 here the right values:

Side Bar
Code:
findproperty        QName(PackageNamespace(""), "scaleX")
pushdouble          1.29
initproperty        QName(PackageNamespace(""), "scaleX")

findproperty        QName(PackageNamespace(""), "scaleY")
pushdouble          1.29
initproperty        QName(PackageNamespace(""), "scaleY")

findproperty        QName(PackageNamespace(""), "x")
pushint             943
initproperty        QName(PackageNamespace(""), "x")

findproperty        QName(PackageNamespace(""), "y")
pushint             -86
initproperty        QName(PackageNamespace(""), "y")
text box
Code:
findproperty        QName(PackageNamespace(""), "scaleX")
pushdouble          1.2
initproperty        QName(PackageNamespace(""), "scaleX")

findproperty        QName(PackageNamespace(""), "scaleY")
pushdouble          1.2
initproperty        QName(PackageNamespace(""), "scaleY")

findproperty        QName(PackageNamespace(""), "x")
pushint             -395
initproperty        QName(PackageNamespace(""), "x")

findproperty        QName(PackageNamespace(""), "y")
pushint             -50
initproperty        QName(PackageNamespace(""), "y")
Code:
findproperty QName(PackageNamespace(""), "width")
pushint 1600
initproperty QName(PackageNamespace(""), "width")
		
findproperty QName(PackageNamespace(""), "height")
pushint 900
initproperty QName(PackageNamespace(""), "height")	

findproperty QName(PackageNamespace(""), "x")
pushint -560
initproperty QName(PackageNamespace(""), "x")
		
findproperty QName(PackageNamespace(""), "y")
pushint -240
initproperty QName(PackageNamespace(""), "y")
Sometime you could say "thanks to someone for posting code i use for hack", I rabcdasm your and it's nilly code... still don't understand leechers.
Quote Originally Posted by raikoug View Post
1600x900 is totally wrong, I posted the right numbers, in the fullscreen post of Nilly, maybe you only stole the first page ^^

if you want to adjust "your" fullscreen hack for 1600*900 here the right values:

Side Bar
Code:
findproperty        QName(PackageNamespace(""), "scaleX")
pushdouble          1.29
initproperty        QName(PackageNamespace(""), "scaleX")

findproperty        QName(PackageNamespace(""), "scaleY")
pushdouble          1.29
initproperty        QName(PackageNamespace(""), "scaleY")

findproperty        QName(PackageNamespace(""), "x")
pushint             943
initproperty        QName(PackageNamespace(""), "x")

findproperty        QName(PackageNamespace(""), "y")
pushint             -86
initproperty        QName(PackageNamespace(""), "y")
text box
Code:
findproperty        QName(PackageNamespace(""), "scaleX")
pushdouble          1.2
initproperty        QName(PackageNamespace(""), "scaleX")

findproperty        QName(PackageNamespace(""), "scaleY")
pushdouble          1.2
initproperty        QName(PackageNamespace(""), "scaleY")

findproperty        QName(PackageNamespace(""), "x")
pushint             -395
initproperty        QName(PackageNamespace(""), "x")

findproperty        QName(PackageNamespace(""), "y")
pushint             -50
initproperty        QName(PackageNamespace(""), "y")
Code:
findproperty QName(PackageNamespace(""), "width")
pushint 1600
initproperty QName(PackageNamespace(""), "width")
		
findproperty QName(PackageNamespace(""), "height")
pushint 900
initproperty QName(PackageNamespace(""), "height")	

findproperty QName(PackageNamespace(""), "x")
pushint -560
initproperty QName(PackageNamespace(""), "x")
		
findproperty QName(PackageNamespace(""), "y")
pushint -240
initproperty QName(PackageNamespace(""), "y")
Sometime you could say "thanks to someone for posting code i use for hack", I rabcdasm your and it's nilly code... still don't understand leechers.
will fix, ty
Quote Originally Posted by raikoug View Post
1600x900 is totally wrong, I posted the right numbers, in the fullscreen post of Nilly, maybe you only stole the first page ^^

if you want to adjust "your" fullscreen hack for 1600*900 here the right values:

Side Bar
Code:
findproperty        QName(PackageNamespace(""), "scaleX")
pushdouble          1.29
initproperty        QName(PackageNamespace(""), "scaleX")

findproperty        QName(PackageNamespace(""), "scaleY")
pushdouble          1.29
initproperty        QName(PackageNamespace(""), "scaleY")

findproperty        QName(PackageNamespace(""), "x")
pushint             943
initproperty        QName(PackageNamespace(""), "x")

findproperty        QName(PackageNamespace(""), "y")
pushint             -86
initproperty        QName(PackageNamespace(""), "y")
text box
Code:
findproperty        QName(PackageNamespace(""), "scaleX")
pushdouble          1.2
initproperty        QName(PackageNamespace(""), "scaleX")

findproperty        QName(PackageNamespace(""), "scaleY")
pushdouble          1.2
initproperty        QName(PackageNamespace(""), "scaleY")

findproperty        QName(PackageNamespace(""), "x")
pushint             -395
initproperty        QName(PackageNamespace(""), "x")

findproperty        QName(PackageNamespace(""), "y")
pushint             -50
initproperty        QName(PackageNamespace(""), "y")
Code:
findproperty QName(PackageNamespace(""), "width")
pushint 1600
initproperty QName(PackageNamespace(""), "width")
		
findproperty QName(PackageNamespace(""), "height")
pushint 900
initproperty QName(PackageNamespace(""), "height")	

findproperty QName(PackageNamespace(""), "x")
pushint -560
initproperty QName(PackageNamespace(""), "x")
		
findproperty QName(PackageNamespace(""), "y")
pushint -240
initproperty QName(PackageNamespace(""), "y")
Sometime you could say "thanks to someone for posting code i use for hack", I rabcdasm your and it's nilly code... still don't understand leechers.
Hmm, I would disagree (with the code).

1.29 scale for 1600x900 will not reach from top to bottom.

The original res is 800x600, we use the height to determine the scale to avoid a gap either above or below the sidebar.

The scale for 1920x1080 would be found by dividing 1080 by 600, which gives 1.8 (which matches the value Nilly gave).

Now apply the same to any other resolution....

1600x900 -> 900/600 = 1.5
1366x768 -> 768/600 = 1.28

A scale of 1.29 should be for a resolution of X by 774 not 1600 by 900.

EDIT: What I just said is invalid if you don't run in fullscreen (true fullscreen) and instead have toolbars e.t.c cutting off bits.
But who does that...


Text box/guild/fame/rank scales is preference I guess.


That last piece of code is for the loading screen, which most people disable.
Quote Originally Posted by Strudul View Post
Hmm, I would disagree (with the code).

1.29 scale for 1600x900 will not reach from top to bottom.

The original res is 800x600, we use the height to determine the scale to avoid a gap either above or below the sidebar.

The scale for 1920x1080 would be found by dividing 1080 by 600, which gives 1.8 (which matches the value Nilly gave).

Now apply the same to any other resolution....

1600x900 -> 900/600 = 1.5
1366x768 -> 768/600 = 1.28

A scale of 1.29 should be for a resolution of X by 774 not 1600 by 900.

EDIT: What I just said is invalid if you don't run in fullscreen (true fullscreen) and instead have toolbars e.t.c cutting off bits.
But who does that...


Text box/guild/fame/rank scales is preference I guess.


That last piece of code is for the loading screen, which most people disable.
so youre saying the one i uploaded is good?
Quote Originally Posted by Strudul View Post
Hmm, I would disagree (with the code).

1.29 scale for 1600x900 will not reach from top to bottom.

The original res is 800x600, we use the height to determine the scale to avoid a gap either above or below the sidebar.

The scale for 1920x1080 would be found by dividing 1080 by 600, which gives 1.8 (which matches the value Nilly gave).

Now apply the same to any other resolution....

1600x900 -> 900/600 = 1.5
1366x768 -> 768/600 = 1.28

A scale of 1.29 should be for a resolution of X by 774 not 1600 by 900.

EDIT: What I just said is invalid if you don't run in fullscreen (true fullscreen) and instead have toolbars e.t.c cutting off bits.
But who does that...


Text box/guild/fame/rank scales is preference I guess.


That last piece of code is for the loading screen, which most people disable.

Hum, I could say "ok" but, that's false, becouse I tried this values with my pc, it is 1600*900. Danz client is cutted even in full screen (total full screen), mine values are perfect for a normal screen, without deleting the bars, and in a full screen works nicely with little margins.
Quote Originally Posted by raikoug View Post
Hum, I could say "ok" but, that's false, becouse I tried this values with my pc, it is 1600*900. Danz client is cutted even in full screen (total full screen), mine values are perfect for a normal screen, without deleting the bars, and in a full screen works nicely with little margins.
idk which one to go with ;/, dont have a 1600 by 900 so cant test :/
Quote Originally Posted by MrDanZ View Post
idk which one to go with ;/, dont have a 1600 by 900 so cant test :/
Well I have a 1600x900 and I can screenie it for ya. (Pro tip - get a virtual machine to test other resolutions)

My values are for if you play in fullscreen. Also my method uses maths, don't argue with maths.

Raikoug's values are for if you haven't found out about flash projector yet and are still playing in a browser.

Flash Projector improves performance.

The way Raikoug does it, he is compensating for the cut off, so he also has to use a higher pushbyte, therefore unnecessarily lowering performance.

EDIT: My 1600x900
Quote Originally Posted by Strudul View Post
Well I have a 1600x900 and I can screenie it for ya. (Pro tip - get a virtual machine to test other resolutions)

My values are for if you play in fullscreen. Also my method uses maths, don't argue with maths.

Raikoug's values are for if you haven't found out about flash projector yet and are still playing in a browser.

Flash Projector improves performance.

The way Raikoug does it, he is compensating for the cut off, so he also has to use a higher pushbyte, therefore unnecessarily lowering performance.

EDIT: My 1600x900
ty, staying with the one i put
no problem, I'm fixing the main menu buttons (account play etc.) but there is still something wrong, when moving them they aren't clickable anymore..
Quote Originally Posted by raikoug View Post
no problem, I'm fixing the main menu buttons (account play etc.) but there is still something wrong, when moving them they aren't clickable anymore..
maybe you moved the buttons, but the click coords or something are incorrect, that happened one time when i was making my own program XD, i really dont know lol

btw, you sure those are right codes of 1600x900?, ive seen many other codes with the same ones as the one i have

cant test cuz i dont have that type of screen XD
I was just thinking the same thing CalciumFire.

Also boom, head shot with maths argument Strudul.

MrDanZ strikes me as one of these people who care about the "thanks" counter. MrDanZ makes me smile, to put it pleasantly.
Posts 114 of 14 · Page 1 of 1
This thread is closed for replies.

Similar Threads

Tags for this Thread

None

Need help?