Just for you to know, if you want to modify the bytecode of an already compiled class, it can be done using ReJava. Much more simple than decompile/recompile.
I've been trying to tweak kc.class this way, because there is a 7190000 constant in there, which is used to start the countdown (a little obsfurcated with a + rand(10000) -97).
Still no luck though...
There is no 'need' to speak English. It's pure courtesy. Let me illustrate this for you:
Donc, j'ai bien repris la méthode no dans laquelle on retrouve le compteur. J'ai réussi à passer outre l'affichage de la limite de temps, et je pense donc que même si cela donne l'impression de réussite, ça ne marche pas. Vous pouvez essayer et me faire vos retours!
There is no 'need' to speak English. It's pure courtesy. Let me illustrate this for you:
Donc, j'ai bien repris la méthode no dans laquelle on retrouve le compteur. J'ai réussi à passer outre l'affichage de la limite de temps, et je pense donc que même si cela donne l'impression de réussite, ça ne marche pas. Vous pouvez essayer et me faire vos retours!
xsires, I'm dead certain it's not working
I just shunt the 'no' class, which is taking into account the display...
If you waht something workable, here it is:
For those who want to sleep soundly, and protected... It's still a bit ugly, with a counter, but it's not getting down.
Keep me posted if there is a problem with it. I'll try to make it nicer, with a hidden counter.
Good night!
xsires, I'm dead certain it's not working
I just shunt the 'no' class, which is taking into account the display...
If you waht something workable, here it is:
For those who want to sleep soundly, and protected... It's still a bit ugly, with a counter, but it's not getting down.
Keep me posted if there is a problem with it. I'll try to make it nicer, with a hidden counter.
Good night!
Thank you ,good night )) i will testing it ) you can tell in detail what you did?
hmmm...
This morning, the automizer was down, and it kind of self-destructed
I modified the void a(long) class within the kc class --> this is the function that is updating the counter. In the end, it seems that I managed to get it past the 2h limit, but 2h10min after the start, it crashes in a systematic way, and modifies the .jar to a size of 4k. I'll have a look at what's inside on the next crash.
hmmm...
This morning, the automizer was down, and it kind of self-destructed
I modified the void a(long) class within the kc class --> this is the function that is updating the counter. In the end, it seems that I managed to get it past the 2h limit, but 2h10min after the start, it crashes in a systematic way, and modifies the .jar to a size of 4k. I'll have a look at what's inside on the next crash.
Same problem here, i used it for 2 hours then it stopped and replaced itself by a 3kb jar.
Same problem here, i used it for 2 hours then it stopped and replaced itself by a 3kb jar.
Yes.. when i start oa bot, the program crash and not work if i restrat it.... after 3/4 hour the oa crash and replace the .jar... is a new protection for crack???
I just arrived back home.
Anyway there is a part of the script that checks i guess the hash of the jar.
If its incorrect it will rewrite the file .
Making it read only might fix it.
Or look for the script its included in the class list i gave to try to locate it .
Hey Maoukami,
Glad you're home.
I spent some time to understand what happens to the mP class. I've seen using a debugger that even if the bytecode is representing what I changed, something else is executed (original bytecode). It's the first time I've seen something like this... I tried to modify this class by recompiling it, and by editing the bytecode, and it gives for both cases the same result...
Quote:
Making it read only might fix it.
This is true, it's fixing the rewrite of the jar, but it's still crashing.
Any clue what the error is for the crash ?
You might wanna run the .jar using a .bat file or .sh file for linux.
And the console should log the error message at least i'm hoping .
Also it might help by just setting the value of 2 hours to like 100+ hours.
Not sure where this is stored but it might make things a bit more easy.
And less chance it crashes.
Also it might help by just setting the value of 2 hours to like 100+ hours.
Not sure where this is stored but it might make things a bit more easy.
This value is set in kc.class, in the kc public function via this.jdField_s_of_type_Long. After the initialization, the value is accessed by the no.class using function a(Long) for writing purpose:
Quote:
long l = System.currentTimeMillis() - this.jdField_a_of_type_SKc.jdField_f_of_type_Long;
if ((l > 0L) && (l < 120000L))
this.jdField_a_of_type_SKc.a(this.jdField_a_of_typ e_SKc.a() - l);
else
this.jdField_a_of_type_SKc.a(this.jdField_a_of_typ e_SKc.a() - bE.jdField_a_of_type_JavaUtilRandom.nextInt(60000) );
this.jdField_a_of_type_SKc.jdField_f_of_type_Long = System.currentTimeMillis();
}
I did modify function a(Long) in kc to render it ineffective, and set to 42 hours the initial counter, but as said before, there must be a hidden counter somewhere else, which is making the code crash. I'll try to have a look at the error in a few hours (it's not crashing fast enough )
.
