Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Hello EE veterans!
You might remember me as a bot maker in 2015 (I think?). C# assistance though TeamViewer was a rather common things for me to do. However, times have changed. Most of the people I've met should've reached adulthood by now - and EE is dead as it was. Time also brought experience. Not only my English writing skills but also those in C++ have improved ever since.
Two years ago I remembered back to when I still played EE and thus wanted to bring it back alive. At least a little bit. I began developping an Everybody Edits lookalike and called the project "OpenEdits". Unlike many other projects out there, this is by 100% Free/Libre Software licensed under LGPL 2.1+. The long-term goal is to provide an engine to add your own blocks and functionality by Lua scripting. That's however still heavily Work In Progress, thus disabled by default.
Here's a few screenshots to get started:
The block selector:
A very simple imported EELVL:
The UI might not be the most beautiful ever, but it does its job and appropriately reflects my Keep It Stupid Simple development approach.
Here are a few video of the development process: https://krock-works.nex.sh/u/openedits/
This project is still far from complete. However, all basics are ready to play some minigames. If you would like to give it a go, here are the binary files. If in doubt, use https://www.malwarebytes.com/ .
Binary downloads: https://github.com/SmallJoker/OpenEdits/releases
MacOS users: Please use Wine. I do not own a Mac.
Test server: krock-works.nex.sh (or play locally by hosting on 127.0.0.1 or 0.0.0.0)
If your world is messy enough, other players will see it in the Lobby screen. This is to give players some content to play while no-one else is online. Also check out the "Imported worlds" tab (EELVL). Unfortunately, most of these worlds are yet not well playable.
I follow a clear direction, which can be found here: https://github.com/SmallJoker/OpenEdits … RECTION.md
In contrast to other EE spin-offs, the following IS NOT part of the roadmap:
100% compatible physics with EE
100% block pack recreation
Please do not expect any quick development progress. My interest in this project varies over time. I sometimes need a break to free my mind and work on other stuff before coming back with new motivation and ideas. Furthermore, I plan to go by the policy of the sqlite3 developers: You may propose changes but do not expect them to be integrated.
Where can I report bugs?
This thread. I will check it every once in a while.
Create a bug report on GitHub.
Let me know on IRC: Rizon, #nimg_lobby. Channel has private logs. Often online around 19:00 UTC. Here's also a good place to ask questions, if you have any.
Is there any Reddit/Matrix/Discord/Slack for this project?
No (various reasons). Refer to xkcd 1782.
Are there bots?
Not yet, although the code is separated such that there are no server or GUI dependencies.
Similar projects that you might enjoy playing:
https://escapade.fun/ - Lovely UI design by Zumza et al. Unfortunately Firefox did not perform well at rendering when we had the meetup.
https://pixelwalker.net/ - Pointed out by HG. I had the chance to meet John in-game soon after. You guys even wrote bots for this game. Impressive.
And with that I wish you a nice day and if you have got a few minutes to spare, I would be very happy to hear some testimorials. Cheers!
Offline
I commented in the past about the risks of developing an EE-like game in a language like C++, especially given this community history with hacking incidents.
This project is however different: I don't believe Krock has picked C++ just because it seemed like a cool programming language to make a game in, but because he has many years of experience with this language. Krock is an important contributor of another open-source multiplayer 3D game named Luanti (formerly Minetest) which is similar to Minecraft.
Krock's experience with C++ is a greencard for this project's security.
OpenEdits is more than just a simple name for another EE remake, it is also a concise summary of what this project stands for. Not only this project has an open-source license, but also anyone will be able to add functionality to it using Lua (think of Roblox experiences). This means, in the future, if you want to have an interesting action block you might be able to ask ChatGPT to code it for you, and you'll be able to add it to your worlds in this game.
If you don't know how to enter IRC, you can use this web-client, to connect and chat. #nimg_lobby is a beautiful community, especially for the technical-inclined.
If you're a developer, that wants to starting working on an open-source project, this could be a very nice pick.
This is not a project thats just another attempt from the same group that has disappointed before and kept players stuck in a loop of failed promises. This is a true alternative.
Good luck Krock! Good luck OpenEdits! <3
Warning!
This user has been found guilty by The Committee of Truth of using honesty, and reminding people of the past, without permission and outside of the allotted timeframes.
I’ve been asked if I’m ChatGPT5.
The answer is no.
I hope this helps! Let me know if you have any other questions.
Everybody edits, but some edit more than others
Offline
Good luck Krock! Good luck OpenEdits! <3
Oh hello Zumza! I do not know the backstory that made necessary to defend me; but thank you for the heads-up and praise.
Server-sent Lua scripts can indeed be a security concern if Lua is not sandboxed. In OpenEdits, this is currently done by whitelisting the known good built-in functions and banish all others from the lua_State. Fewer functions also mean reduced attack potential in case of newly discovered CVE's. Garbage-collected languages, memory-safe languages or IL might seem like a better choice in terms of security. That's however only one side of the deal. Perfectly functioning code may still contain logic errors or be malicious in nature. As you pointed out, I rely on my experience on C++ to get the most out of it.
For what it's worth - the "game" world shown above does render at 2200 FPS zoomed out - without VSync enabled - on my 8-9 year old desktop PC. Batch rendering the UI elements might bring another leap in performance, but I have yet not figured out on how to properly handle depth sorting.
Let's see what the future brings.
Offline
Cool stuff. Quite some time went into this.
Would the blocks you add be shared through the server or differently?
I won't be running unknown binaries fast these days. Heck, that's how I got hacked a couple of years back. Any reason for going for C++ instead of something more portable (just curious)?
Also quite nice to see you made your own sprites (I think). Gives it quite an unique vibe from what I can see
I commented in the past about the risks of developing an EE-like game in a language like C++, especially given this community history with hacking incidents.
This project is however different: I don't believe Krock has picked C++ just because it seemed like a cool programming language to make a game in, but because he has many years of experience with this language. Krock is an important contributor of another open-source multiplayer 3D game named Luanti (formerly Minetest) which is similar to Minecraft.
Krock's experience with C++ is a greencard for this project's security.OpenEdits is more than just a simple name for another EE remake, it is also a concise summary of what this project stands for. Not only this project has an open-source license, but also anyone will be able to add functionality to it using Lua (think of Roblox experiences). This means, in the future, if you want to have an interesting action block you might be able to ask ChatGPT to code it for you, and you'll be able to add it to your worlds in this game.
If you don't know how to enter IRC, you can use this web-client, to connect and chat. #nimg_lobby is a beautiful community, especially for the technical-inclined.
If you're a developer, that wants to starting working on an open-source project, this could be a very nice pick.
I don't want to get too off-topic, but your message reads like it was generated using ChatGPT?
This is not a project thats just another attempt from the same group that has disappointed before and kept players stuck in a loop of failed promises. This is a true alternative.
There is a time and place for everything. I don't think it's fair to bring those kinds of words into this thread of this quite unique approach on a EE remake.
Offline
This is kinda sick actually, well done!
Miss Everybody Edits and your old friends? Check out PixelWalker.net and reconnect with the community!
[imghttps://mm.sirjosh3917.com/PW?scale=1img]
Online
Would the blocks you add be shared through the server or differently?
Yes, the server does share Lua scripts, sounds and textures for the client to use. This way, physics and effects can be customized by the server and run entirely on client-side afterwards. The long-term goal is that the client exposes enough functionality through Lua such that truly unique content can be provided by server owners. For example: bouncy blocks that depend on specific key states or time.
Any reason for going for C++ instead of something more portable (just curious)?
Considering that currently about 70% of the desktop PCs run Windows, I would argue that providing a compiled Windows binary is sufficient for the vast majority of this game's target audience. Compiling is not difficult; just getting the toolchain installed can take a few minutes. You might be thinking towards a web-based application - I am simply not well-versed in that regard. Some projects make cross-compiling C++ to WebAssembly possible but I prefer to work with raw file I/O and a program that can be debugged with gdb.
About the textures: yes, they are new. All game textures are currently 32x32. 16x16 no longer fit into the era of 1080p and 4K screens.
This is kinda sick actually, well done!
Thank you!
Offline
[ Started around 1743377662.717 - Generated in 0.083 seconds, 12 queries executed - Memory usage: 1.51 MiB (Peak: 1.67 MiB) ]