- 404
- IGN
- Telesphoreo
Hey everyone. I have been heads down on Oasis for a while now and figured it was time to share where things are and where they are going.
So the elephant in the room: someone deobfuscated 1.0.1. Look, I am not going to pretend I thought obfuscation would keep anyone out forever. Anything can be reverse engineered, and I released it knowing that. The obfuscation was never meant to be some impenetrable wall, just a speed bump to slow down anyone trying to copy the ideas before I could get further ahead. What bothers me is not the act itself but the entitlement behind it. One disrespectful security engineer had neuron activation when she saw an obfuscated jar and could not be bothered to read the README that explains exactly why the source is closed. But I cannot sit here and act like my obfuscation was some big secret that got blown open. It was not. So we move forward.
About 1.0
I wrote version 1.0 in a 30 hour sprint because we got hit with 78 million rows of grief and CoreProtect could not roll them back on any amount of memory we had. I raw dogged that entire sprint, no caffeine, just pure focus and sleep deprivation that I definitely paid for with my sanity. That jar was held together with hopes and prayers, and if I am being honest it really shows. Version one of anything is that thing at its worst, and 1.0.1 is no exception: it had bugs, it was rough around the edges, and while the performance was solid it was nowhere near as polished as what has come since. If you have that jar and you are running it, I am not going to stop you, but I also would not recommend it.
If you already downloaded the JAR, keep in mind that no license was ever attached to it. Oasis is all rights reserved, including the copies already out there. I have no plans to go after anyone for running a copy they downloaded while it was public, but that is a statement of intent, not a permission, and it does not extend to sharing the file, deobfuscating it, or publishing anything derived from it.
Since then we have made a lot of changes. We crossed the million block threshold, which felt like a big deal at the time, and then kept going. On a quieter server without a bunch of plugins eating up your CPU, Oasis can push almost 1.5 million blocks per second. A lot of bugs got squashed along the way, and none of that work is in the deobfuscated jar. So if someone is trying to learn from it or worse, trying to maintain it, they are working with a rough draft while the real thing keeps moving forward. Good luck with that (not to mention that it is illegal).
2.0 is ready
I am releasing 2.0 as trusted access only. If you want Oasis for your server, come talk to me and I will give you the jar directly. And to be clear, 2.0 is not obfuscated. It is the regular jar.
The reason for trusted access is not primarily about protecting the code, though Oasis remains all rights reserved and that has not changed. It is about wanting to work with people who are actually willing to dogfood this thing with me. Oasis is still in its early days, and I would rather give it to server owners who are going to help me find rough edges, diagnose issues when they come up, and work with me to make it better. I want to know who is running it and help them succeed with it, not just drop a jar and hope for the best. This is a grief prevention and rollback plugin. It is kind of a big deal. If something goes sideways you need proper backups, you need to understand what you are running, and I would rather help you get set up right than find out later that someone was treating it like a production ready finished product when it is still being actively developed.
So if your server is interested, reach out. I am looking for people who want to work with me on this, not people who feel entitled to it.
3.0 is coming
This is the part I am actually excited about.
3.0 is in progress, and we are going deep. Like, really deep. If you look at some of the micro optimizations in 2.0 you will already be asking yourself how we went that far into the weeds, but 3.0 is going further. We are going deep into the ClickHouse internals, contributing optimizations specifically tailored for how Oasis uses it. We are going deep into Minecraft's internals, deeper than 2.0 already went. We are rethinking how the data flows through the whole system from end to end. By the time 3.0 ships, the architecture is going to be so fundamentally different from 1.0.1 that having the deobfuscated code is not a shortcut to it. It is not even the same shape anymore.
And when 3.0 is ready, I am going to open source the whole thing. This was always the plan, by the way. The deobfuscation did not change my mind about that. I always intended to open source Oasis once it was far enough ahead that copying it would be harder than just using it. By the time 3.0 drops, we are going to be so far ahead of any other grief prevention plugin that trying to shoehorn our ideas into something else would basically mean rewriting that plugin from scratch. At that point, why bother? Just use Oasis.
That is the real response to the deobfuscation. Just building something so much better that the old jar becomes completely irrelevant. By the time 3.0 is out, having 1.0.1 is like having a flip phone in 2026. It technically still makes calls. But come on.
Watch out for sketchy jars
Do not download Oasis from anyone except me.
I have no idea what is floating around out there and I cannot vouch for anything I did not build. If someone modified a JAR to put something nasty in it, that is on them, not me. My jars are clean.
If you want to verify you have an official copy, here are the SHA256 checksums:
If the hash does not match, do not run it. This is the kind of plugin that has access to your whole world, so maybe do not hand that access to a jar you downloaded from some random person.
See you in 3.0.
So the elephant in the room: someone deobfuscated 1.0.1. Look, I am not going to pretend I thought obfuscation would keep anyone out forever. Anything can be reverse engineered, and I released it knowing that. The obfuscation was never meant to be some impenetrable wall, just a speed bump to slow down anyone trying to copy the ideas before I could get further ahead. What bothers me is not the act itself but the entitlement behind it. One disrespectful security engineer had neuron activation when she saw an obfuscated jar and could not be bothered to read the README that explains exactly why the source is closed. But I cannot sit here and act like my obfuscation was some big secret that got blown open. It was not. So we move forward.
About 1.0
I wrote version 1.0 in a 30 hour sprint because we got hit with 78 million rows of grief and CoreProtect could not roll them back on any amount of memory we had. I raw dogged that entire sprint, no caffeine, just pure focus and sleep deprivation that I definitely paid for with my sanity. That jar was held together with hopes and prayers, and if I am being honest it really shows. Version one of anything is that thing at its worst, and 1.0.1 is no exception: it had bugs, it was rough around the edges, and while the performance was solid it was nowhere near as polished as what has come since. If you have that jar and you are running it, I am not going to stop you, but I also would not recommend it.
If you already downloaded the JAR, keep in mind that no license was ever attached to it. Oasis is all rights reserved, including the copies already out there. I have no plans to go after anyone for running a copy they downloaded while it was public, but that is a statement of intent, not a permission, and it does not extend to sharing the file, deobfuscating it, or publishing anything derived from it.
Since then we have made a lot of changes. We crossed the million block threshold, which felt like a big deal at the time, and then kept going. On a quieter server without a bunch of plugins eating up your CPU, Oasis can push almost 1.5 million blocks per second. A lot of bugs got squashed along the way, and none of that work is in the deobfuscated jar. So if someone is trying to learn from it or worse, trying to maintain it, they are working with a rough draft while the real thing keeps moving forward. Good luck with that (not to mention that it is illegal).
2.0 is ready
I am releasing 2.0 as trusted access only. If you want Oasis for your server, come talk to me and I will give you the jar directly. And to be clear, 2.0 is not obfuscated. It is the regular jar.
The reason for trusted access is not primarily about protecting the code, though Oasis remains all rights reserved and that has not changed. It is about wanting to work with people who are actually willing to dogfood this thing with me. Oasis is still in its early days, and I would rather give it to server owners who are going to help me find rough edges, diagnose issues when they come up, and work with me to make it better. I want to know who is running it and help them succeed with it, not just drop a jar and hope for the best. This is a grief prevention and rollback plugin. It is kind of a big deal. If something goes sideways you need proper backups, you need to understand what you are running, and I would rather help you get set up right than find out later that someone was treating it like a production ready finished product when it is still being actively developed.
So if your server is interested, reach out. I am looking for people who want to work with me on this, not people who feel entitled to it.
3.0 is coming
This is the part I am actually excited about.
3.0 is in progress, and we are going deep. Like, really deep. If you look at some of the micro optimizations in 2.0 you will already be asking yourself how we went that far into the weeds, but 3.0 is going further. We are going deep into the ClickHouse internals, contributing optimizations specifically tailored for how Oasis uses it. We are going deep into Minecraft's internals, deeper than 2.0 already went. We are rethinking how the data flows through the whole system from end to end. By the time 3.0 ships, the architecture is going to be so fundamentally different from 1.0.1 that having the deobfuscated code is not a shortcut to it. It is not even the same shape anymore.
And when 3.0 is ready, I am going to open source the whole thing. This was always the plan, by the way. The deobfuscation did not change my mind about that. I always intended to open source Oasis once it was far enough ahead that copying it would be harder than just using it. By the time 3.0 drops, we are going to be so far ahead of any other grief prevention plugin that trying to shoehorn our ideas into something else would basically mean rewriting that plugin from scratch. At that point, why bother? Just use Oasis.
That is the real response to the deobfuscation. Just building something so much better that the old jar becomes completely irrelevant. By the time 3.0 is out, having 1.0.1 is like having a flip phone in 2026. It technically still makes calls. But come on.
Watch out for sketchy jars
Do not download Oasis from anyone except me.
I have no idea what is floating around out there and I cannot vouch for anything I did not build. If someone modified a JAR to put something nasty in it, that is on them, not me. My jars are clean.
If you want to verify you have an official copy, here are the SHA256 checksums:
Code:
Oasis 1.0: sha256:e73073b245d57085d2a2ba677845469348579c161e29cb7aec188a565611cf0f
Oasis 1.0.1: sha256:0f2fc0c839cf7051c2e10e485049d56b48c559e7b23000a16d9ce2d8f8d61b54If the hash does not match, do not run it. This is the kind of plugin that has access to your whole world, so maybe do not hand that access to a jar you downloaded from some random person.
See you in 3.0.
