Username:
Password:

Details for " Trials.Fusion.STATEMENT.READNFO-CODEX"

Notice Trials.Fusion.STATEMENT.READNFO-CODEX
Uploaded2014-04-28 20:46:09
Real NFOShow the real NFO
Web NFO
Show/Hide
CODEX PRESENTS:
Trials Fusion STATEMENT
Release Date : 4/2014 Protection : Brains
Discs : 1 Genre : Action RPG
CODEX is rather new to the scene, so it was to be expected
that one of the old established groups would sooner or later
start picking at us. Now Skid Row took a poor attempt to
actually score again in a scene that has overtaken them ...
If you are throwing accusations of stolen code around , atleast
make sure your information is correct.
We did not copy your code , nor do we have any interest in copying it.
After investigating your emu, we find that your code is hilarious
and lacking , but we do not hold this against you and we encourage
everybody who is able to verify that the two emulators are different
in numerous ways that disproves any claims of copying. More about
the difference further at the bottom.
The reasons given for a PROPER release of Trials Fusion are
so far fetched, that we decided to clear a few things up. So
heres an extract of Skid Rows accusations with our statements:
SKIDROW: 99 procent of all their API calls in the
code is identical with ours.
CODEX: Of course thats the case because we are trying
to emulate uplay, and thats how uplay works.
So if you take a look at ANY other UBI emu
available - you will definetly find a lot
of code loking alike.
Like the simplest of all; return 0/1.
This is in fact the most used way of returning
a function that has no real value in the game.
SKIDROW: We did of course plant several stealth API calls,
that identify and tag our work. Yet those API calls
are inside the CODEX emulation dlls.
CODEX: Which API calls are you referring to then?
Maybe they are too stealth that they cant be found
anymore ...
SKIDROW: Link above show one, out of many proofs of stolen
code. It shows the original function written by
the coder, using a global variable for another
function. Basicially the way the coder wrote
the API, to set the flag is unique, and simply
copy and paste of our code by CODEX.
CODEX: The unique flag you supposedly set, is actually in
OUR code a DWORD array which holds a simple value
for telling the function that is called - to define
if the Overlap Operation has been completed or not.
Now how unique is that approach ? ...
SKIDROW: To finalize their CODEX stupidity - they set the
wrong parameter for CreateFile API when it comes
to folders. We do use GENERIC_READ, cause of
an important point, Windows simply dont
allow GENERIC_ALL without admin rights.
CODEX: Didnt you accuse us that we copy/pasted your
entire emu ? So why are there differences now ?
Maybe because we coded everything ourselves ..
Thanks for pointing that out.
As a result to this pathetic attempt to make everyone believe
we are copycats, we had to spend some time looking into their
crappy code and found some interesting and obvious differences:
- CODEX emu is written in c++ , SR emu is written in ASM - how
can you blindly copy/paste there ?
- CODEX emu uses 76 Imports, SR emu uses 27 Imports
- CODEX emu has 75 Exports, SR emu has 70 Exports
- CODEX doesnt use file padding, SR does
- CODEX uses heaprealloc and heapsize, SR doesnt
- CODEX emu doesnt need a patched .exe in Trials Fusion
to work, SR emu does need it ...
- CODEX uses 6 vars for their read function, SR uses 7 vars
- .....
We could go on showing you a lot more differences, but we dont
think its worth the effort since nothing is stolen.
Concerning your nice little picture where you busted us,
heres our 2 cents to this awesome finding :
Our original c++ code :
UPLAY_R1_LOADER int UPLAY_HasOverlappedOperationCompleted
(TwoDwords * OverlappedOperationCompleted)
if (OverlappedOperationCompleted-a2)
Ovrlaped[0] DWORD(OverlappedOperationCompleted-a1);
return 0;
else return 1;
... in a debugger it looks like this:
0FFD1A92 / 55 PUSH EBP
0FFD1A93 . 8BEC MOV EBP,ESP
0FFD1A95 . 8B45 08 MOV EAX,DWORD PTR SS:[EBP+8]
0FFD1A98 . 8378 04 00 CMP DWORD PTR DS:[EAX+4],0
0FFD1A9C . 74 09 JE SHORT 0FFD1AA7
0FFD1A9E . A3 A0D8FE0F MOV DWORD PTR DS:[FFED8A0],EAX
0FFD1AA3 . 33C0 XOR EAX,EAX
0FFD1AA5 . 5D POP EBP
0FFD1AA6 . C3 RETN
0FFD1AA7 33C0 XOR EAX,EAX
0FFD1AA9 . 40 INC EAX
0FFD1AAA . 5D POP EBP
0FFD1AAB \. C3 RETN
CODEX is open for a head to head discussion about this issue. You guys
know where to find us! We will no further have this silly discussion
in public anymore .. We have nothing to hide and wont participate in
your lets beat the new guy before he gets too strong mission.
CODEX is currently looking for:
nothing but competition!
are you ready?
LNKCPS 02/2014
Download nfo Trials.Fusion.STATEMENT.READNFO-CODEX.nfo



Comments for " Trials.Fusion.STATEMENT.READNFO-CODEX"

No comments yet.



You must login to post a comment!