That is, stuff like tutorials, frameworks, pre-made assets, existing solutions, and common answers to common questions. The more people use the same thing for the same purpose, the better its ecosystem gets. That's not to say engines on Java don't exist, but with the limited time I had to look at Java engines, they've left a much lesser impression than Unreal and Unity. This means if you want to use an Engine (as you should) Java is not the best option.

Unfortunately for Java developers, the few Engines/Frameworks you can use Java with are nowhere near the big players like Unity, Unreal, or even GameMaker and Godot. If your goal is to release a game, you’ll simply waste years for no apparent reason by not using an existing Engine. I've made a simple OpenGL prototype which took me several months of non-full time work, and it’s terrible.

You SHOULD use an existing Engine, and the reason is simple: making a production-ready engine that works on most of the relevant hardware ( especially consoles) would take YEARS. I will, but there are important topics to talk about before we dive into that. You probably expect me to talk about Java’s performance, ease of use, capabilities, and stuff like that. I figured, people on Reddit may prefer reading over listening. This is a text version of this video of mine on YouTube. Feedback Friday Screenshot Saturday Soundtrack Sunday Marketing Monday WIP Wednesday Daily Discussion Quarterly Showcase Related communities 1 For questions, get in touch with mods, we're happy to help you. Free assets OK, be sure to specify license. If you need to use screenshots, that's ok so long as is illustrates your issues.ĭo not solicit employment. Use discord, /r/indiegames, /r/playmygame or /r/gamedevscreens.īe specific about your question. Feedback, praise, WIP, screenshots, kickstarters, blogs, memes, 'play my game', twitch streams. Obviously for a game to work you need a game loop.No show-off posts.

Java game development