Author Topic: Is it possible to stop the hacking? (Read 21134 times)

Pass · August 11, 2013, 12:48:21 PM

Quote from: Scriode on August 10, 2013, 05:49:29 PM

Wrong. If badspot changed the whole locations code, the creator of the dll would have to also change the dll to work with it. You can keep remaking it though

the .dll is injected directly into blockland.exe. the location of the .dll compared to the blockland folder has no relations at all. please know what you're talking about before you post it.

Ad Bot · Advertisement

Blockzillahead · August 11, 2013, 12:49:35 PM

Quote from: Pass on August 11, 2013, 12:48:21 PM

the .dll is injected directly into blockland.exe. the location of the .dll compared to the blockland folder has no relations at all. please know what you're talking about before you post it.

Doesn't the .dll file change memory addresses in the game?

.::Taboo::. · August 11, 2013, 12:51:13 PM

Quote from: Blockzillahead on August 11, 2013, 12:49:35 PM

Doesn't the .dll file change memory addresses in the game?

yeah, and?

Blockzillahead · August 11, 2013, 12:53:56 PM

Quote from: .::Taboo::. on August 11, 2013, 12:51:13 PM

yeah, and?

If Badspot changes those certain memory addresses, wouldn't that require the creator of the .dll to re-edit the .dll file so it changes the new memory addresses once they are found?

.::Taboo::. · August 11, 2013, 01:00:14 PM

oh, we thought you meant the actual game directory
yeah, that's pretty much as far as most anti-hack updates in games can really go, and it's also why it's such a pointless and endless battle because it typically takes so little work on both sides

Zeblote · August 11, 2013, 01:14:20 PM

Quote from: Blockzillahead on August 11, 2013, 12:53:56 PM

If Badspot changes those certain memory addresses, wouldn't that require the creator of the .dll to re-edit the .dll file so it changes the new memory addresses once they are found?

no
the dll is still going to work

Operator� · August 11, 2013, 01:19:14 PM

inb4 terms of use is updated to include memory editing

$trinick · August 11, 2013, 03:26:31 PM

Quote from: Operator� on August 11, 2013, 01:19:14 PM

inb4 terms of use is updated to include memory editing

It already doesn't allow it.

.::Taboo::. · August 11, 2013, 03:27:44 PM

Not to mention it's kind of a given.

Blockzillahead · August 11, 2013, 03:29:35 PM

Well at least the hacks are client-sided and not server-sided.

.::Taboo::. · August 11, 2013, 03:30:14 PM

how would that even make sense
if anything that'd be a good thing because then only idiot hosts would be able to activate it on their servers, leaving others unaffected

Mura · August 11, 2013, 03:33:52 PM

Server sided hacks would be cool. They would pretty much just be .dll add-ons

Blockzillahead · August 11, 2013, 03:34:25 PM

Quote from: .::Taboo::. on August 11, 2013, 03:30:14 PM

how would that even make sense
if anything that'd be a good thing because then only idiot hosts would be able to activate it on their servers, leaving others unaffected

?? Client-sided only affects the client who has it. Server-sided affects everyone. I'm saying client-sided is better because it only affects the guy who uses it and not the whole server which can make it worse.

Blockzillahead · August 11, 2013, 03:35:43 PM

Quote from: Blockzillahead on August 11, 2013, 03:34:25 PM

?? Client-sided only affects the client who has it. Server-sided affects everyone. I'm saying client-sided is better because it only affects the guy who uses it and not the whole server which can make it worse.

I mean if it's possible. I don't know, maybe a backdoor or a way to insert the .dll and make it server-sided. Doesn't necessarily have to be activated by the host.

.::Taboo::. · August 11, 2013, 03:38:57 PM

i think it's time you stopped posting