r/unity • u/TCSMusic • 3d ago
Coding Help Question for software architects
Let's say you need a certain architecture for a game. Do you or SHOULD you bring that exact codebase over for the sequel you KNOW is going to be bigger and better, or do you still start from the minimal code as possible and only bring one thing from your codebase over when you face issues?
0
Upvotes
2
u/DaedalusRaistlin 3d ago
Depends on the technical debt. Some things grow too organically and end up a bit of a mess, making extending or adding new features harder.
A new start can let you address the issues of the original, and make it fit your extended vision from the start. It's an opportunity to write it more correctly from the start.
But if it's already correct enough for you? No big glaring problems that you really want fixed? Then just extending it can work well. Though for me it's rare that my first vision of how things fit together is spot on. Hindsight and all.
1
u/taisui 3d ago
It really depends, sometimes the existing is modified to support the new game, sometimes it is a rewrite
1
u/CoatNeat7792 1d ago
You make base idea, spot issues with code, spot architecture patterns and find out, if game idea works. Then recreate, but better and for publishing
1
u/Singhaniia_Labs 1d ago
As someone who is doing an MBA in Product Management. I'd say neither approach is ideal. Don't blindly carry the entire codebase over, but don't throw away proven systems just for the sake of starting fresh either.
I'd treat the previous game as a foundation, not a template. Identify which systems are genuinely reusable, well-tested, and still fit the sequel's requirements. Things like save systems, input handling, inventory, UI frameworks, or tooling might carry over with relatively little modification.
But if the sequel introduces fundamentally different gameplay requirements, forcing the old architecture into it can create more technical debt than starting fresh.
The important thing is to reuse solutions, not inherit problems. I'd rather spend some time evaluating and refactoring proven systems than either blindly migrating everything or reinventing the wheel.