Hello all,
Im a small dev and have only made 1 project. Im expanding the game made by Brackeys (The How to Unity Game (Cubeathon) and i want to make it an infinite autogen game. Any help as i honestly don’t know where to start.
Regards,
Try to break the problem into smaller problems, reduce its complexity. Then, implement one thing after another. You could even simplify all steps by implementing a minimalistic version or a stub. Once you’re satisfied with the complete system and the order everything is going to execute, start to exchange the minimalistic implementations with something that comes closer to the actual version.
Always do revisions and improve the complete iteratively.
If you really want to know “where to start”, just try do think of it logically. What would need to happen first? Is it actually the thing that you need to code or is there anything else that needs to exist before anything of that can happen?
It’s worth building this in theory, on a sheet of paper, as a flowchart or anything that helps you to grasp and understand the overall complexity of a problem.
Cool, thx man. Im really a noob and just making a UI is complex for me. Spend a few weeks now to add pause, main and options menu and music/sound effects so thought autogen is the next big step.
Then it’s even more important that you try to simplify the problem and approach it step by step, add more detail and flexibility to it during your journey of that implementation. It’s very important to not just go straight forward for something complex and just code it with its full complexity. You’ll (and probably have to) learn alot along the way.
There’s no concrete input we can provide (about how to approach this), as there are a lot of factors that may contribute to decisions on how to implement it. Well, now you could start writing down the detailed idea that you’ve got in mind and hope someone comes along throwing in a basic structure for the scripts, but I’m not sure if that helps you alot, because you’ll be given a structure that you have to use to build something on and there’s usually a lack of understanding why it was recommended and written like that - at least for beginners.
Anyway, if you wrote it down just for yourself, you’d already automatically do the first step of breaking down the problem - getting an abstract description of your problem. It’s the first you do when you follow the divide&conquer approach. If you’re able to write it down, it’s just one step away from implementing a first, prototyped version of the system - which doesn’t need to be super complex.
Ok, thx for the awesome and helpful advice!