CipSoft RealEngine 7.4 [Development Thread] – BETA Phase Incoming

[Codinablack]

Its as you said. Its translated code

I figured as much, but I had to ask to be sure.. Thanks

PS. Sorry for mucking up the thread.
PSS @Ezzz I apologize if I offended , I do not mean to be so abrasive sometimes

 

[Ascendia]

I figured as much, but I had to ask to be sure.. Thanks

Anytime buddy. But to add to what you said cipsoft binary doesnt just present the entire code. You have to reconstruct it and not everything is just handen to you. Its a fuck ton of work basically.

 

[Codinablack]

Anytime buddy. But to add to what you said cipsoft binary doesnt just present the entire code. You have to reconstruct it and read the bytes and tell what some functions are supposed to do and what their translations actually accurately are. If that is not reverse engineering then so be it.

reconstruct is still translate in a variation.. but if you have to figure out how to read bytes without knowing the answer to how the data is structured, then yeah, that's for sure reverse engineering, and if you had to do that, then I double apologize to @Ezzz for saying it's not reverse engineering... I didn't know that you guys were having to do those things, although I am curious as to why you would need to do those things when all the information is already available for that client protocol and file formats.


Anyways, I don't want to spam your thread anymore.

 

[Ascendia]

reconstruct is still translate in a variation.. but if you have to figure out how to read bytes without knowing the answer to how the data is structured, then yeah, that's for sure reverse engineering, and if you had to do that, then I double apologize to @Ezzz for saying it's not reverse engineering... I didn't know that you guys were having to do those things, although I am curious as to why you would need to do those things when all the information is already available for that client protocol and file formats.


Anyways, I don't want to spam your thread anymore.

Not quiet what I meant. Not everything is presented to you as clear text. Some code is presented fucked up. Some attempts wont even produce the full logic of a function. I mean its a compiled binary. Theres many variables. And its alot of small picking and assembling, hoping to get as much well translated code as possible and for those translations that are bad. You basically get to work.

 

[leik meris]

The project is definitely intriguing, especially considering the complexity of working with a leaked executable and attempting to rebuild an engine from scratch. But if the goal is to showcase serious reverse engineering work, stating that certain components are "100% ready" or that the map was "converted with precision" isn't enough.

What would truly add credibility is showing concrete comparisons between what's extracted from the binary and what has been reconstructed. For example:

• dumps of original in-memory structures vs their C++ counterparts,
• disassembled functions vs reimplemented equivalents,
• packet captures vs your protocol handler implementations.

Without this kind of evidence, much of the post reads more like a technical teaser than a verified milestone. At the so called "beta" phase, one would expect real technical documentation, validated code fragments, or any form of proof that this isn't just a wrapper around the original binary.

Showing actual engineering results doesn't just build trust it invites collaboration, learning, and proper feedback from other devs in the community.

 

[Ascendia]

The project is definitely intriguing, especially considering the complexity of working with a leaked executable and attempting to rebuild an engine from scratch. But if the goal is to showcase serious reverse engineering work, stating that certain components are "100% ready" or that the map was "converted with precision" isn't enough.

What would truly add credibility is showing concrete comparisons between what's extracted from the binary and what has been reconstructed. For example:

• dumps of original in-memory structures vs their C++ counterparts,
• disassembled functions vs reimplemented equivalents,
• packet captures vs your protocol handler implementations.

Without this kind of evidence, much of the post reads more like a technical teaser than a verified milestone. At the so called "beta" phase, one would expect real technical documentation, validated code fragments, or any form of proof that this isn't just a wrapper around the original binary.

Showing actual engineering results doesn't just build trust it invites collaboration, learning, and proper feedback from other devs in the community.

I dont need validation. Thats not why im here. Im here to give recognition to the work that is ongoing to promote a possible launch with the priority now being to inform people for an upcoming Alpha/Beta testing.

Im simply here to raise awareness of the project thats being built and to raise awareness and reach out to people who potentielly might want to join a closed beta/alpha.

But if you say it will motivate people to join a a test launch then give me a second.

https://imgur.com/wXQayZK

Post automatically merged: May 16, 2025

https://imgur.com/mXwDHXX

 

[Zainox]

I have a big question. Why everybody that have a "leak" wants to downgrade the code?

 

[Ascendia]

I have a big question. Why everybody that have a "leak" wants to downgrade the code?

Because 7.4 is the shit. 7.7 has soulpoints. Requires 4x more mana to conjure runes which means 4x higher level by default. The map was more "classic" with the old borders, No wands. Its many reasons.

And to clarify to everyone else so there is no misconception. This is not a free release of the work were displaying. This is basically a discussion board for an upcoming launch of an alpha, beta and an official launch. This is not a thread designed to release free work but rather to check the interest for potential testers and to have discussions regarding the project being built.

 

[draken1]

but if you have to figure out how to read bytes without knowing the answer to how the data is structured, then yeah, that's for sure reverse engineering.

I don't know what you're trying to say here. Reverse engineering is no more and no less than understanding whats going on in the binary in other words. A perfect example of reverse engineered engine is reHLDS (server of half life 1 engine GitHub - rehlds/ReHLDS: Enhanced version of the HLDS engine with bug fixes, security patches, and optimizations for stable servers. (https://github.com/rehlds/ReHLDS))

to read bytes of a struct and interpret them you have to reverse engineer the struct itself and its nothing hard if u have a working binary and some knowledge how things may work and may look in programming language, on top of that you have countless tools like debuggers, hex-rays decompiler that help A LOT, reclass that helps you build the structures/classes etc

another thing is, 99% of those 'reverse engineered' otservers are just bullshit. I'd like to see reverse engineering work of this thread creator but he ignored this question so you can guess

 

[Adposatnr]

I don't know what you're trying to say here. Reverse engineering is no more and no less than understanding whats going on in the binary in other words. A perfect example of reverse engineered engine is reHLDS (server of half life 1 engine GitHub - rehlds/ReHLDS: Enhanced version of the HLDS engine with bug fixes, security patches, and optimizations for stable servers. (https://github.com/rehlds/ReHLDS))

to read bytes of a struct and interpret them you have to reverse engineer the struct itself and its nothing hard if u have a working binary and some knowledge how things may work and may look in programming language, on top of that you have countless tools like debuggers, hex-rays decompiler that help A LOT, reclass that helps you build the structures/classes etc

another thing is, 99% of those 'reverse engineered' otservers are just bullshit. I'd like to see reverse engineering work of this thread creator but he ignored this question so you can guess

my wild guess is that everything is already done and server will be using revol topic is just to get attention for project also op did nothing beside buying engine

but i might be wrong ofc

 

[Ascendia]

my wild guess is that everything is already done and server will be using revol topic is just to get attention for project also op did nothing beside buying engine

but i might be wrong ofc

We havent bought the engine from Ezzz if that is what you are referring to and he can even confirm it. His launched project with rawesh, fluppix and himself is battle tested and has 300 daily online while ours does not. Hence we are running an alpha/beta to find out the capability of our own engine.

Were not saying anything or claiming anything. Especially not that its a 1000% same engine. But in the game it really feels like it. I havent been able to find a single diff but I guess it will come and I'm open minded to it as there's a human factor and the fact that its been engineered from a compiled binary.

@edit We're human and prone to errors. We can only do as much as our eyes and brain can detect. Hence we rely on the Alpha/Beta. If it was Ezz server we wouldn't need any of this.

 

[leik meris]

I dont need validation. Thats not why im here. Im here to give recognition to the work that is ongoing to promote a possible launch with the priority now being to inform people for an upcoming Alpha/Beta testing.

Im simply here to raise awareness of the project thats being built and to raise awareness and reach out to people who potentielly might want to join a closed beta/alpha.

But if you say it will motivate people to join a a test launch then give me a second.

https://imgur.com/wXQayZK

Post automatically merged: May 16, 2025

https://imgur.com/mXwDHXX

Calling something “CipSoft Leaked Engine Reverse Engineered” is a big statement. That kind of title sets the bar high it implies there’s serious technical work behind it, not just that “the engine runs” or that you’ve got a server launching soon.

But when you follow that up with vague phrases like “threading issues were resolved” or “we’re building a new QueryManager”, and then show some log output or NPC dialogue, it really starts to feel more like promotion for a slightly modified build than a true reverse engineering effort.

Just to be clear I’m not trying to start drama or talk down your project. This isn’t about envy or discrediting anyone’s work. It’s about setting the right expectations and respecting what terms like reverse engineering actually mean, especially when you’re speaking to a community of devs.

If the goal is to get testers or build hype for a new server, that’s totally valid. But if you’re calling it a reverse-engineered CipSoft engine, people are going to expect technical proof. That includes:

• Comparisons between original in-memory structures and your implementations
• Rewritten functions with clear links to disassembly
• Reconstructed protocol or memory layouts
• Anything that shows how you’ve rebuilt internals based on the leaked binary

Without something like that, the title starts to sound misleading even if it’s unintentional. It adds noise instead of clarity, and can turn off the kind of people who actually understand what this work involves.

In the end, being transparent, clear, and technically honest goes a lot further than hype. If you are rebuilding parts of the CipSoft engine, that’s impressive but the best way to prove it is to show it. That’s what earns respect and opens the door to real collaboration.

 

[Ascendia]

Calling something “CipSoft Leaked Engine Reverse Engineered” is a big statement. That kind of title sets the bar high it implies there’s serious technical work behind it, not just that “the engine runs” or that you’ve got a server launching soon.

But when you follow that up with vague phrases like “threading issues were resolved” or “we’re building a new QueryManager”, and then show some log output or NPC dialogue, it really starts to feel more like promotion for a slightly modified build than a true reverse engineering effort.

Just to be clear I’m not trying to start drama or talk down your project. This isn’t about envy or discrediting anyone’s work. It’s about setting the right expectations and respecting what terms like reverse engineering actually mean, especially when you’re speaking to a community of devs.

If the goal is to get testers or build hype for a new server, that’s totally valid. But if you’re calling it a reverse-engineered CipSoft engine, people are going to expect technical proof. That includes:

• Comparisons between original in-memory structures and your implementations
• Rewritten functions with clear links to disassembly
• Reconstructed protocol or memory layouts
• Anything that shows how you’ve rebuilt internals based on the leaked binary

Without something like that, the title starts to sound misleading even if it’s unintentional. It adds noise instead of clarity, and can turn off the kind of people who actually understand what this work involves.

In the end, being transparent, clear, and technically honest goes a lot further than hype. If you are rebuilding parts of the CipSoft engine, that’s impressive but the best way to prove it is to show it. That’s what earns respect and opens the door to real collaboration.

I hear you but I'm not here for the technical discussions. I'm not here to get any confirmation. I posted a gif where if you look closely before the engine runs, it had just compiled at the very top. I've taken a gif of every single source file.

If you ask me about the accuracy? I would say it's as close as can be. I dont want to say 100% out loud because for one I don't lie neither to others nor to myself. I am not certain so I cannot claim it. But I do believe its in its high 95+% possibly higher.

Server is stable but we've been max 3 online on it at once so I cant say there arent anything we have overlooked. What I can say is everything feels authentic as can be.

 

[Codinablack]

I don't know what you're trying to say here. Reverse engineering is no more and no less than understanding whats going on in the binary in other words. A perfect example of reverse engineered engine is reHLDS (server of half life 1 engine GitHub - rehlds/ReHLDS: Enhanced version of the HLDS engine with bug fixes, security patches, and optimizations for stable servers. (https://github.com/rehlds/ReHLDS))

to read bytes of a struct and interpret them you have to reverse engineer the struct itself and its nothing hard if u have a working binary and some knowledge how things may work and may look in programming language, on top of that you have countless tools like debuggers, hex-rays decompiler that help A LOT, reclass that helps you build the structures/classes etc

another thing is, 99% of those 'reverse engineered' otservers are just bullshit. I'd like to see reverse engineering work of this thread creator but he ignored this question so you can guess

So? Exactly like I said? I'm not really getting your purpose or intention on quoting me and then going and saying the same thing as me...

If you are saying, that knowing how the data is structured doesn't make it "any less" reverse engineering, then wrong. That's like saying "i designed this building" when working from someone else's blueprint.... it changes everything if you know how the "struct" is structured....

 

[Ascendia]

1. Reverse engineering is information its the process of taking a compiled product, and gather intel about its inners workings. Its not only reverse engineering if you're working on a product without debug symbols available
   
   
2. This is not a translatiom. This is the original code. Not a port, not a rewrite, not a "replica". Its literally the same code down to the assembly instructions.
3. Asking for "memory structures" is basically asking for the source code as if having the name after the level in the struct means something
   
   

We read the actual decompiled code from the binary. It's not like tibia 7.7 protocol was an undeciphered mystery or something we're still beginning to understand. Almost as if reading just 1 byte wrong won't cause a client debug or a server parsing error.

If you are saying that knowing how the data is structured doesn't make it "any less" reverse engineering, then wrong.

I'm not going to go deeper into this argument. I appreciate you being passionate but if you really want to discredit the work fighting over terminologies I suggest you to go ahead. Translate crnonpl.c for me. And once you are done with the 3185 lines and manually having done most of it by hand. You can say what actual work was done with the phrasing of your choosing.

 

[Codinablack]

Why are you responding to a message I aimed at someone else? Are you loony or what? I in fact dropped out of this conversation until I was quoted and the person basically said the same thing as me, but said they don't know what I'm talking about...

So what exactly provoked you to also shoot a shot at me?

Also, please remove the "quotes" because you are talking to me, but your post says I said those things, which I did not..

Anyways, I could care less what you "think" is reverse engineering... keep advertising w/e you like however you like... I started off trying to help you to give you a reason to compare your project to others and give a purpose in existing and why it should be used or more deserving of attention than the next "Downgrade Server", but apparently you are only interested in controversy...

Good luck, have fun...

FOR THE RECORD, THE ABOVE QUOTE SAYING "Codinblack said" is not actually anything I said, it's just this guy who keeps rebranding the same project every couple months, responded to something I said...

 

[Ascendia]

Calling something “CipSoft Leaked Engine Reverse Engineered” is a big statement. That kind of title sets the bar high it implies there’s serious technical work behind it, not just that “the engine runs” or that you’ve got a server launching soon.

But when you follow that up with vague phrases like “threading issues were resolved” or “we’re building a new QueryManager”, and then show some log output or NPC dialogue, it really starts to feel more like promotion for a slightly modified build than a true reverse engineering effort.

Just to be clear I’m not trying to start drama or talk down your project. This isn’t about envy or discrediting anyone’s work. It’s about setting the right expectations and respecting what terms like reverse engineering actually mean, especially when you’re speaking to a community of devs.

If the goal is to get testers or build hype for a new server, that’s totally valid. But if you’re calling it a reverse-engineered CipSoft engine, people are going to expect technical proof. That includes:

• Comparisons between original in-memory structures and your implementations
• Rewritten functions with clear links to disassembly
• Reconstructed protocol or memory layouts
• Anything that shows how you’ve rebuilt internals based on the leaked binary

Without something like that, the title starts to sound misleading even if it’s unintentional. It adds noise instead of clarity, and can turn off the kind of people who actually understand what this work involves.

In the end, being transparent, clear, and technically honest goes a lot further than hype. If you are rebuilding parts of the CipSoft engine, that’s impressive but the best way to prove it is to show it. That’s what earns respect and opens the door to real collaboration.

Why are you responding to a message I aimed at someone else? Are you loony or what? I in fact dropped out of this conversation until I was quoted and the person basically said the same thing as me, but said they don't know what I'm talking about...

So what exactly provoked you to also shoot a shot at me?

Also, please remove the "quotes" because you are talking to me, but your post says I said those things, which I did not..

Anyways, I could care less what you "think" is reverse engineering... keep advertising w/e you like however you like... I started off trying to help you to give you a reason to compare your project to others and give a purpose in existing and why it should be used or more deserving of attention than the next "Downgrade Server", but apparently you are only interested in controversy...

Good luck, have fun...

FOR THE RECORD, THE ABOVE QUOTE SAYING "Codinblack said" is not actually anything I said, it's just this guy who keeps rebranding the same project every couple months, responded to something I said...

Because somehow you are under the impression im working with TFS implementing some functions from the leaked binary. The entire Engine is CipSoft based.

If you want an engine built on translations you can look at Promise, its literally in my signature. We took functionality from CipSoft and added it to TVP (Ezz edited version of TFS 1.4.2)

 

[Codinablack]

Because somehow you are under the impression im working with TFS implementing some functions from the leaked binary. The entire Engine is CipSoft based.

If you want an engine built on translations you can look at Promise, its literally in my signature. We took functionality from CipSoft and added it to TVP (Ezz edited version of TFS 1.4.2)

I never said shit about TFS... and no, I never believed you to be using any TFS code... so what are you going on about?? Seems like you are pushing your own insecurities on to me....

I believed you to be using leaked and translated code... not TFS code, and definitely not hand rolled, reverse engineered code either, but, I had to ask to be sure, and YOU CONFIRMED THAT FOR ME!




So stop tagging me and stop quoting me...

 

[Ezzz]

I'd like to clarify; this ain't revol engine, revol is not for sale and it will pretty much never will be as well.

 

[Codinablack]

to read bytes of a struct and interpret them you have to reverse engineer the struct itself and its nothing hard if u have a working binary and some knowledge how things may work