News A server update was released on July 20. Server patch notes and downloads are here. Additionally, a client update was released on the same day. Client patch notes are here.
Injecting commands

EK.IceFlake

  • Hero Member
  • "We are the champions my fellahs" - Sufyan/VK.SuFy
  • Posts: 1,728
Re: Injecting commands
« Reply #30,  »
Quote from . on June 14th, 07:38 PM
Well, in that case we're indeed talking about bots. So we really do need to get into ethics because... cheating. Regardless of how you look at it, that information leads straight to cheating. Definitely not you, I mean, you probably won't get any further than copying that example. Let alone compiling it, injecting it and maintaining it (updating offsets and adjusting for changes after each update).

At which point this topic does (or will) represent an "issue" to the developers. No matter how nice and OK they seem to be with it now. We're going to reach that point where they'll need deal with it in a less than friendly manner.
While the developers do the exact same thing all day long (<<< exaggerated), right?

Zeyad Ahmed

  • Sr. Member
  • CEO of Pyramux Software
  • Posts: 291
Re: Injecting commands
« Reply #31,  »Last edited
ok there is small script to set  the health value into 100
Code: [Select]
[ENABLE]
//code from here to '[DISABLE]' will be used to enable the cheat
alloc(newmem,2048)
label(returnhere)
label(originalcode)
label(exit)

newmem: //this is allocated memory, you have read,write,execute access
//place your code here
mov [edx],#100
originalcode:
//mov [edx],ax
mov eax,[esi+0000111C]

exit:
jmp returnhere

"duke_base.dll"+793A3:
jmp newmem
nop
nop
nop
nop
returnhere:


 
 
[DISABLE]
//code from here till the end of the code will be used to disable the cheat
dealloc(newmem)
"duke_base.dll"+793A3:
mov [edx],ax
mov eax,[esi+0000111C]
//Alt: db 66 89 02 8B 86 1C 11 00 00
Where is the offsets and addresses? are the offsets is 793A3?
Re: Injecting commands
« Reply #32,  »
sorry for double post it a server timeout problem

EK.IceFlake

  • Hero Member
  • "We are the champions my fellahs" - Sufyan/VK.SuFy
  • Posts: 1,728
Re: Injecting commands
« Reply #33,  »
Quote from Zeyad Ahmed on June 16th, 06:58 AM
ok there is small script to set  the health value into 100
Code: [Select]
[ENABLE]
//code from here to '[DISABLE]' will be used to enable the cheat
alloc(newmem,2048)
label(returnhere)
label(originalcode)
label(exit)

newmem: //this is allocated memory, you have read,write,execute access
//place your code here
mov [edx],#100
originalcode:
//mov [edx],ax
mov eax,[esi+0000111C]

exit:
jmp returnhere

"duke_base.dll"+793A3:
jmp newmem
nop
nop
nop
nop
returnhere:


 
 
[DISABLE]
//code from here till the end of the code will be used to disable the cheat
dealloc(newmem)
"duke_base.dll"+793A3:
mov [edx],ax
mov eax,[esi+0000111C]
//Alt: db 66 89 02 8B 86 1C 11 00 00
Where is the offsets and addresses? are the offsets is 793A3?
Quote from . on June 14th, 07:38 PM
Definitely not you, I mean, you probably won't get any further than copying that example. Let alone compiling it, injecting it and maintaining it (updating offsets and adjusting for changes after each update).

Zeyad Ahmed

  • Sr. Member
  • CEO of Pyramux Software
  • Posts: 291
Re: Injecting commands
« Reply #34,  »
Quote from EK.IceFlake on June 16th, 08:41 AM
Quote from Zeyad Ahmed on June 16th, 06:58 AM
ok there is small script to set  the health value into 100
Code: [Select]
[ENABLE]
//code from here to '[DISABLE]' will be used to enable the cheat
alloc(newmem,2048)
label(returnhere)
label(originalcode)
label(exit)

newmem: //this is allocated memory, you have read,write,execute access
//place your code here
mov [edx],#100
originalcode:
//mov [edx],ax
mov eax,[esi+0000111C]

exit:
jmp returnhere

"duke_base.dll"+793A3:
jmp newmem
nop
nop
nop
nop
returnhere:


 
 
[DISABLE]
//code from here till the end of the code will be used to disable the cheat
dealloc(newmem)
"duke_base.dll"+793A3:
mov [edx],ax
mov eax,[esi+0000111C]
//Alt: db 66 89 02 8B 86 1C 11 00 00
Where is the offsets and addresses? are the offsets is 793A3?
Quote from . on June 14th, 07:38 PM
Definitely not you, I mean, you probably won't get any further than copying that example. Let alone compiling it, injecting it and maintaining it (updating offsets and adjusting for changes after each update).
i didnt understand?! what SLC means?

EK.IceFlake

  • Hero Member
  • "We are the champions my fellahs" - Sufyan/VK.SuFy
  • Posts: 1,728
Re: Injecting commands
« Reply #35,  »
Quote from Zeyad Ahmed on June 16th, 08:52 AM
Quote from EK.IceFlake on June 16th, 08:41 AM
Quote from Zeyad Ahmed on June 16th, 06:58 AM
ok there is small script to set  the health value into 100
Code: [Select]
[ENABLE]
//code from here to '[DISABLE]' will be used to enable the cheat
alloc(newmem,2048)
label(returnhere)
label(originalcode)
label(exit)

newmem: //this is allocated memory, you have read,write,execute access
//place your code here
mov [edx],#100
originalcode:
//mov [edx],ax
mov eax,[esi+0000111C]

exit:
jmp returnhere

"duke_base.dll"+793A3:
jmp newmem
nop
nop
nop
nop
returnhere:


 
 
[DISABLE]
//code from here till the end of the code will be used to disable the cheat
dealloc(newmem)
"duke_base.dll"+793A3:
mov [edx],ax
mov eax,[esi+0000111C]
//Alt: db 66 89 02 8B 86 1C 11 00 00
Where is the offsets and addresses? are the offsets is 793A3?
Quote from . on June 14th, 07:38 PM
Definitely not you, I mean, you probably won't get any further than copying that example. Let alone compiling it, injecting it and maintaining it (updating offsets and adjusting for changes after each update).
i didnt understand?! what SLC means?
The potential hacker thing doesn't apply to you because all you can do is copy it. You will not be able to progress any further.

Zeyad Ahmed

  • Sr. Member
  • CEO of Pyramux Software
  • Posts: 291
Re: Injecting commands
« Reply #36,  »
Quote from EK.IceFlake on June 16th, 12:00 PM
Quote from Zeyad Ahmed on June 16th, 08:52 AM
Quote from EK.IceFlake on June 16th, 08:41 AM
Quote from Zeyad Ahmed on June 16th, 06:58 AM
ok there is small script to set  the health value into 100
Code: [Select]
[ENABLE]
//code from here to '[DISABLE]' will be used to enable the cheat
alloc(newmem,2048)
label(returnhere)
label(originalcode)
label(exit)

newmem: //this is allocated memory, you have read,write,execute access
//place your code here
mov [edx],#100
originalcode:
//mov [edx],ax
mov eax,[esi+0000111C]

exit:
jmp returnhere

"duke_base.dll"+793A3:
jmp newmem
nop
nop
nop
nop
returnhere:


 
 
[DISABLE]
//code from here till the end of the code will be used to disable the cheat
dealloc(newmem)
"duke_base.dll"+793A3:
mov [edx],ax
mov eax,[esi+0000111C]
//Alt: db 66 89 02 8B 86 1C 11 00 00
Where is the offsets and addresses? are the offsets is 793A3?
Quote from . on June 14th, 07:38 PM
Definitely not you, I mean, you probably won't get any further than copying that example. Let alone compiling it, injecting it and maintaining it (updating offsets and adjusting for changes after each update).
i didnt understand?! what SLC means?
The potential hacker thing doesn't apply to you because all you can do is copy it. You will not be able to progress any further.
he means that i will not understand? maybe i can improve the example?
i came her for an answer!