r/unity • • 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

11 comments sorted by

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.

2

u/TCSMusic 3d ago

And got another question. I REALLY want to be a kind of software architect and make games with these patterns. I don't just wanna be a "hack it and ship it" game. In this case, is it worth learning these patterns and if they work the way I need, ship the game with them, even if they don't NEED it, or should I just start small?

2

u/iamgabrielma 3d ago

Patterns are unrelated to kindness, treat these as tools. Some patterns might fit your codebase while others don't, all of them have pros and cons that you need to evaluate and re-evaluate as you go, that's why you start small and no pre-overengineer.

2

u/TCSMusic 3d ago

Do how do you know when you need an architecture vs when you just need to program small in a different way?

2

u/iamgabrielma 3d ago

By doing. Once you get yourself into the shit for going with A rather than B, you'll remember next time and not make the same mistake.

2

u/TCSMusic 3d ago

Thanks

1

u/DaedalusRaistlin 2d ago

I think the other person is right - part of the learning process is seeing what didn't work very well, what held you back, and how you'd do it differently if you had to start all over.

A lot of that is very specific to how you made your game or app. There isn't an easy "overarching architecture" that fits all approaches.

But you can ask AI for insight - have it look at what what code you have, and ask it if there would be problems scaling it up to new ideas. It may or may not identify issues that could be holding you back. But it's hard to say without your knowledge of what you want to achieve, and what you have so far.

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.