• About
• What I build
• Tech & Tools
• Featured Projects
• Open Source Work
• Contact
• How to support & collaborate
• Contributing
• License

I’m Elias — a passionate JAVA developer from France focused on Java, web development, and Minecraft plugin systems. I build scalable server-side systems, multiplayer game systems, and engaging web interfaces. I run Oreo Studios where I publish Primarly minecraft plugins, tools and game projects.

High-level experience:

• Java, Spigot/Paper plugin development (professional Minecraft plugins)
• Full-stack web development (HTML/CSS/JS, Node.js, PHP, REST APIs)
• Databases & infra: MongoDB, Redis, MySQL, Docker, RabbitMQ
• Tools & patterns: Docker, CI, microservices patterns, message queues

• Modern essentials & server tooling (cross-server sync, GUIs, performance-minded)
• Custom gameplay systems for Minecraft (drops, lotteries, item systems)
• Web dashboards & backend services to support game ecosystems
• Game worlds & narrative universes (Afelia)

Languages

• Java — 100%
• Python — 100%
• JavaScript / TypeScript — 90%
• C# (.NET) — 80%
• PHP — 60%
• Bash / Shell — comfortable

Datastores & infra

• MongoDB, Redis, MySQL
• Docker, Linux, Pterodactyl
• RabbitMQ

Frameworks & libraries

• Spigot / Paper, MythicMobs, ModelEngine, ItemsAdder
• Express, Node.js, REST APIs
• Spring / Java tooling

Below are some of my highlighted projects. Click to visit each repository.

(If any repo names or links are different, tell me and I'll update them.)

I maintain and publish plugins and tools. Check my pinned repositories on my GitHub profile to explore code and usage docs.

• Email: [email protected]
• Discord: OreoStudios
• Website / Shop: https://www.oreostudio.store/
• GitHub: https://github.com/el211

• Star the repositories you find useful ⭐
• Open issues or feature requests in the repo you want improved
• If you want custom work, email me or reach out on Discord

Contributions are welcome — bug reports, improvements, documentation updates, or new features.

1. Fork the repository
2. Create a feature branch (git checkout -b feat/my-feature)
3. Commit your changes and push (git push origin feat/my-feature)
4. Open a pull request with a clear description of changes

Please follow the repository's code style and include tests where relevant.

Most of my public repositories use permissive licenses. If you want me to add or change a license for a specific repo, tell me which one; I can add an MIT or Apache-2.0 license file and update the README.

Thanks for visiting — if you like my work or want help on a plugin, game system, or web tool, reach out. And yes — I love Oreos 🍪