Some people on the SB community come across as inexperienced, so post in the comments some of your tips and I'll say some of mine on how to not seem nooby! First, don't always ask everyone "key?", especially if they obviously haven't completed the project. If they announce the completion but don't share the key or forget to, then possibly ask in a more complete way.

Second, don't announce projects that you can't commit to. Sure, every now and then you downright SHOULD cancel a project, but don't announce a project and cancel it the same day. Under the right circumstances, sure, but it should be one of the rarest things. Number three, really short, don't ask people to make Minecraft, don't decide to have your first or second project be Minecraft. Seriously.

yeah lol dont make mc your first project i see allot of people try to make a sandbox... and... then they go into the editor like WHAAAAAAAAT?

when you first start out look at tons of other peoples programs play them through then look at them in edit mode pressing the "?" button every time you see a command you don't quite understand.(I suggest doing this with the examples a lot it helps beleive me). and start out small like do not even begin using graphics intell you understand the basics. start out by making a text based game it helps

to not worry about them entill later. also when you get a basic understanding of basic replay your favorite nintendo games and think to yourself "what do I know that can do something like that" then right down your ideas. then later test it out to see if it works.last thing have fun and take breaks. Good luck in programming looking forward to seeing your games.

Thanks for the encouragement and ideas on how to teach myself! I really needed it

I just began to program today. The first thing i made was a text game, and i must say that the ? after a command really does help

My fourth tip (and last tip of today, as far as my time goes) is to make sure that you release games that actually contain a decent amount of content. Sure you can say "it's alpha" or "indev" and play it off, but if you release extremely unfinished games even with updates, people won't want to play it because of first impressions. Also, make updates that can't be released in just a manner of days.

If it can be released in just a couple of days, it probably doesn't contain enough content to be worthwhile, unless you've been pounding in a ton of time in those days or are extremely successful in your programming. Basically, make sure that games and updates contain enough content to avoid poor impressions, and make sure that they are actually playable and not full of bugs.

I have my own noob irks to share: 1. SEARCH before you ask "key?". Sometimes the key was just 4 posts down. 2. DON'T go to the Japanese Petitcom community and ask "key?". They are allowed to post screenshots of copyrighted materials but not allowed to share keys. 3. DON'T go to the Japanese Petitcom community and ask them to speak English! Gawd noob, just don't.

I think these are a lot of great hints, if you are a noob I suggest listening to these hints. I want to say maybe start out with some basic games like moving around the screen and doing something with collisions when you hit another sprite. This will help, I am sure. :)

Tip #5: asking questions. You should ask questions, it is what can make you good at programming, but don't ask questions directly to someone if they don't intentionally mean for you to do it. What I mean is that if somebody makes a post about a program that they're making, don't ask a question directly to them in their comments. Again, if circumstances allow, go for it, but it seems very nooby.

Tip: Don't program the title screen first. I've lost count of how many progams end up being just a title screen. Break the program down into chunks of code that perform functions. If you were designing a car would you start with the little chrome name badge? Work on the engine, transmission, differential, brakes, suspension, steering, windshield wipers, horn, seat belts, etc.

I was guilty of only doing the title screen when I first got this. Don't worry though I stopped a LONG time ago.

Actually making the title screen first helped encourage me to keep going because I think" I do not want this perfectly good title screen to go to waste"

@komodo† same here...

@Komodo It's the same vice versa, "Hey this game is pretty good, I should grace it with a title screen."

My stance on Title Screens is that you should make the game first. If it's worth it, then make the title screen. I've cancelled many (personal) projects because I made the title screen then thought, 'no, I don't want to make an engine' and left it.

One more tip: READ THE MANUAL! It's actually really well written and explains the basics of BASIC! It also solves about half of the questions on this Miiverse community.

Another tip: If you want to add on to a thing that you said, don't make a new thread. Reply to yourself.

Tip #6: Don't request for somebody else to make a game for you. Make the game yourself! What's the point of getting this if when you want something to be made, you don't take action and try to make it yourself?

I believe Zee's comment #6 is also a good hint. I believe if you want a game, make it yourself. I believe it is okay to ask if somebody already made a game like that though. :)