this post was submitted on 23 Jun 2025
106 points (96.5% liked)
Games
19869 readers
453 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Moreover: changes that big go in the next game.
If you decide to roll your own engine, from the start... awesome. Especially when content-creation tools aren't a huge deal, like if your game world is procedurally generated. Understand your scope, steal freely from existing libraries, avoid wasting your artists' time.
If you try to switch engines mid-development, you are fucked. John Romero couldn't make that shit work, just going from Quake to Quake II. Daikatana could have shipped before Half-Life and only missed colored lighting. Instead it's a cautionary tale. Duke Nukem Forever didn't even ship. They had a nearly-complete game, several times, but threw those out and started over.
You don't have to throw anything out, to start a new project from scratch. Ship the damn game. Put different tech in the next one. If you don't ship, there won't be a next one.
Yeah, there's a certain risk for rolling with your own engine, but if you start the project with the idea of having a custom engine you probably know what you're doing and have taken into account the complexities of having a custom engine. IMO if you're a group of small experienced devs having a custom engine is not really a show stopper, if you're a junior the project probably isn't even getting off the ground.
But changing the engine mid-project is almost always a huge decision and more often than not a killing blow for most projects. Depending on the stage of the project you're guaranteeing adding a year or two to your development. It's better to accept the limitations of the existing engine and compromise on the vision rather than swap engines in hopes of realizing the vision that got refined during development.
Duke Nukem Forever did ship... Years late and it was a total mess of a decade's worth of gimmick mechanics that killed the franchise, but it did make it out the door.
Still fits as a cautionary tale about switching engines, I just had to double check I didn't hallucinate that game.
A game with that title shipped. I don't think it was, in any sense, the same project. Not even as a ship-of-Theseus situation. A different studio started from scratch.
Oh, I see what you mean, fair enough.
Duke Nukem Forever had wall-tits that you would slap and they give you health, and I'm pretty much going to remember that forever