Scripting HelpersARCHIVE
A little piece of Roblox history. Preserved for everyone, one question at a time.Read about the archive →
✓ ANSWER ACCEPTED

What are some good planning strategies for game code?

I have a game project at the moment, which I have become stalled at the coding portion. I am unsure of how I should approach having multiple scripts, such as what should be coded first and ensuring they flow together. What are some strategies I can use to tackle this issue?

1 comment

0

Start by asking questions that can be answered, not discussed, and ask on-topic questions

1 answer

✓ Accepted answer

I'm currently making a game as well, and through my experience, I'll list things that you should take a look at:

  1. Plan your game out

This may seem very simple but most people don't do this, literally just plan out the game such as how to play it, what features it would have and etc. Not knowing what to do is the worse thing possible because then you keep changing the game and at one point you either give up or produced a mess

  1. Start with the frame work

After you plan out your game, the frame work is most important. Based on the type of your game you will have different setups. For example, say I have an magic based game where you can use abilities and such, the frame work would consists of:

A. Client Sided Move Recognition (1 Local script to run all the moves) B. Client sided debounces as well as Server sided debounces (Includes cooldowns) C. Client and Server sided status managers (if you have condition in your game such as stunned, burned, etc) D. Client sided effects (I normally run my effects on the client side but this is up to you)

There are many other things depending on the type of combat you would like such as Blocking, Stamina, etc.

Overall you want a script that is able to handle the requests of using abilities and do a bunch of checks on cooldowns, debounces and such.

  1. Start small

Once you have the framework setup; you might want to start by adding small things to test it such as security, and fixing bugs and glitches. You also want to see if everything seems good in terms of the gameplay itself. Is it what you were looking for? I 100% recommend going over everything before proceeding as changing things beyond this point can be mentally painful.

  1. Now that you're done with frame works, security issues and such you can start adding things to your game

At this point you're good to go! You have an engine running everything and made sure that there are no errors. The last thing you want to do is just test for any other possible bugs and so on.

Hope this list helped. This is based on personal experience and so it may not be what you are looking for.

This discussion is preserved as it was. New answers, comments, and votes are closed.