WTS [WTS] Interface sources [any protocol]

[Pleyne]

Hi, I'm selling Interface sources.
I was working with one of bigger Essence projects (for ±1 year) delivering them Interface source KR.
Per this period gathered knowledge about UE, UE Scripting, saw a lot of tools and their progression.
So finally I decided that I can open up my own sales topic.

• I'm selling source for any protocol - If I don't have source, I will need you to provide whole system folder or for Essence/main - provide me protocol number.
• Sources are acquired by my OWN decompiler - written in Java, so we're not using popular UEExplorer upgraded by anyone.
• Decompiler extracts already compile ready sources. It outputs clean code, however constants are mapped 60-70%. Why only 60-70%? Well tl;dr when you compile any sources, they take at that time constant value and place it instead of = CONST_NAME to = THAT_CONST_NAME_VALUE, so it's not possible to have const name instead of value.
• Example of output: https://pastebin.com/cjyXcJvT for bigger .uc class (557p). p.s pastebin messed up encoding, but KR symbols are preserved - you won't see "?" symbols, rather you will see proper original korean text. I will give you guide as well, how not to mess it up with your editor VS Code/Notepad++ or what you use it to make them preserve it.
• You will get source + my compiler wrapper (written in java) - works on Windows/Mac/Linux - it has small GUI but supports CLI.

Small notice, who thinks 'this is decompiled source' - basically all sources that are on sale are made by decompiling .u and applying changes. I think powerhouse few years ago was ArtToKill/kick (kick added support for INT64 to the publicly available compiler sources) etc. So no - there are no straight from 'creator' sources anywhere, all sellers offer the same - just the quality is different. UEExplorer upgraded was a big step, however, it introduces still a lot of nesting, if statements wrapping incorrectly which could lead to bugs. There are many things how to identify poor quality sources, as if the seller tries to sell 'out-of-box' when they see it compiles - sad news, some bugs are in the logic due to seller focusing only on 'it compiles' rather than issues that their decompiler is not capable so solve.
On request I can restore ±100% const mapping.

 

Later I can attach compiled .u to try.
Price is 400EUR.
Payment methods USDT (Crypto).

I'm still in debate with myself, wether to start selling XDat Editor with structures and ClientDat with 100% all files openings (no unk namings) and improved experience (such as comments support in .dat files, mass sync, improved performance and so on).

P.s. If you ask me to give you some project's custom interface - the price may vary - there are couple things per project that need to be hand checked and adjusted (for example Innadril completely changes tokens which then I need to adjust my program to their token Ids). So it might take more time = more money.

P.s.s. I have more things in the garage, like my own dsetup source that can allow you 'unlocking' system with your desired encrypting - you don't need to wait till 'patched' systems start appearing and so on, but I think at this time everyone who needs it make them selves it. AAC crypt removals and so on, BuildZone, everything that 'unlocks' client, however, I don't plan to make them on sale as mentioned, everyone can do them.
 

Edited yesterday at 09:44 AM by Pleyne