So this will be a thread covering almost everything to help make good games, from A to ∞. anyways stuff like making important features, easter eggs and title screens. -feel free to add your own tips too!

ok so please do not comment stuff here just to talk, any comments like that will be taken down, however you can freely say anything on your own tips, joking, (trolling is allowed, but if done PLEASE do it in a nice way) btw by talking i mean like: *joe* "hey dude nice post!" *joey* "thanks man how are you btw?" *joe* "pretty good, you?" *joey*"good, hey dude lets play MK7" -you get the point-

*tip #1* -deciding to make your game- im pretty sure we all have had that moment where your making a game and realize that either A: you have run out of ideas and dont know what to do B: you have ideas but arent interested in making the game anymore or lastly C: you have made an overly hard to program game and are stuck on main things. so to help with those annoying things! ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

there are many simple ways to help squash these pesky problems, so first remember to go through this list of things before starting development (after coming up with a general idea for the game) 1: make sure you have enough ideas to actually make the game, writing ideas down helps a lot. 2:make sure your game has a story or you know what you want it to end/continue from. ↓↓↓↓↓↓↓↓↓

3: -to help in not getting bored with your game- make sure its something you wont have to go only one direction with, by this i mean dont make it have one story, make it so if you get bored with one thing maybe the story, change it, maybe make multible possible stories. also make sure you personally like it, if you dont like your game it will really show in the gameplay, (tbc later) ↓↓↓↓↓↓↓↓↓↓↓

Here are some of my of my own tips: 1) Don't get yourself locked up in one specific idea. This ALWAYS will lead to discouragement and eventually failure to deliver. Base your games around your skills.

yes and continuing off what Something...said,before making your game,make sure you have the knowledge to make the game,like dont try to make a fully 3d gta5 game,you may have ideas but *one does not simply make gta5 on SB*(lotr memes) if you have little skill though, worry not! ive seen some of tne best sb games made using print wait and goto(lol),like one of my fave SB games, the EVERYTHING quiz

2) Do NOT make your project (especially your first one) a clone of an existing game or an overly ambitious project. Keep it small, keep it simple.

To emphasise on planning.Use paper, have an understanding of what functions your game will need and how you will implement them. Most games have some sort of direction, so draw a map, even simple squares which show which rooms connect.

Pro Tip: Don't get ahead of yourself in the programming. For instance, dont start programming level 1 or designing a gun before you've got things working first.(completely working). If you skip it, bugs will likely occur and be harder to find/fix.

Another thing is don't be afraid to test or ask for help! trying to just do a game all by yourself is way too hard, also testing can help in future events, a way you could test is take a few things you may or may not know how to do that you will need in your game and try making a very small program testing it to make sure you know how to use it.

Thank you! I'll keep these in mind when making my game.

Make a quick mock-up design of your framework for your game or project, then see what is wrong with it. Next, start over completely and make a second version incorporating what you wanted in the first version, then you can start working on graphics and game ideas fulltime. In my experience, this actually works if you stick to it, compared to just the freestyle mess that usually happens when you

don't organize your development.

(Guess I'll try to help?) There are symbols constantly used to make the program faster or shorter: : ↑ Treated as "new line", easier to know what before this symbol does. Example→ PRINT "Ding Dong!": BEEP 5 ? ↑ Faster alternative to PRINT code. A little harder to use for beginner. Example. ((Instead of ___PRINT "Hello!"___, use it as ___? "Hello!" )) you can add more if ya like

I don't recommend use : as new line because the code became hard to read. Try to organize your code in a way that is easy to read. Some tips: - Use commentaries to separate parts of your code. - Try to write what your code do on process that are complex. - Avoid programming in one line. Try to keep the length of each line less than 40 char to have a clear view of whats going on. ...

- Don't use goto or gosub. Use DEF instead of gosub. - Don't repeat yourself. Try to create functions (Using DEF) instead of copy paste. That way, you have to do less changes in the future. Finally, I recommend search in google "game programming patterns". I know this is not a OOP language but there are useful information to make things with less code, easier to understand and faster.

(i have to close this discussion because i need another one btw) so last tip until #2. title screens. for some this means nothing and are like "eh.. put the name.." BUT for some this means war! -so ideas on how to make good ones- 1st off it MUST have to do with your game, so if you have created strites (or not) put something cool from in your game, the best looking sprites guys!

2nd is putting bg screens, you can put a bg screen behind everything to make it look awesome! 4 different layers too! -use bg screens to thier fullest- 3rd is the name (title) of your game. DO NOT (unless it fits your game) JUST PUT IT IN TEXT! like: "(not) COOL RPG GAME" make sprites for it! its not that hard and is way worth it. 4th is maybe adding graphics like a box outside/insd the title.