Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!

1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


Member Since 10 Aug 2001
Online Last Active Today, 12:37 AM

Posts I've Made

In Topic: How to build my first game

01 March 2015 - 10:35 PM

Here is my $0.02:


1. You are relying way too much on finding the answers via tutorials in making your game, when you need to realize that the tutorials only provide you with the basics on which to build. The phase that follows the tutorial following is entirely down to you, you need to decide specifically where your weaknesses lie and either address them through research, trial and error, and asking on forums like this.


2. I'm having a hard time working out if you are a designer or programmer type! This is pretty important in deciding the path you wish to follow: Are you a more technically-minded person who thinks along the lines of how a game was made to do what it does at the code level as you play it, or do you look for ways to improve the gameplay, look and feel of the game with little concern for the technical detail? I think you are taking on a little too much in trying to wear both hats.


3. If something isn't working for you, like the tutorials, adapt! It is pretty easy to find many types of information outside tutorials once you have nailed the specifics of what you need to know.


4. Clinging to the basics is a hopeless thing to do when you are looking to make your own game, you have to be prepared to dive in the deep end frequently to see if you can actually do it. Knowing the basics tells us almost nothing, as those who have no interest in making games also know the basics.


Move forward and discover yourself, and try not to take on too much at one time.

In Topic: How do I know if I'm an intermediateprogramming level?

26 February 2015 - 04:36 PM

Seniority doesn't just come from learning the basics of a language, it also comes from actually completing software development projects. Notice that I said "completed" and not something like "unfinished projects" or "projects in progress"? I have certainly learned the most from completed project, either solo or part of a team, and when you have a few of these completed projects under your belt professionally then that is when you can start ranking yourself as intermediate or whatever. 


Until you have completed projects you cannot be anything more that junior/novice. Others here have made excellent points that I don't need to reiterate.

In Topic: Will game maker hurt me in the long run?

26 February 2015 - 04:20 PM

I had my time with Unity during my years in games, and it was great. Gamemaker has certainly moved on from what it was a few years ago when it was certainly a novice tool.

In Topic: temporary force, how to best code

26 February 2015 - 04:09 PM

I think the word you are looking for is an "impulse". This is a momentary force that dies away or is otherwise altered at the point of contact between two or more objects. See the following link for an explanation:




Note the time component (dt) such that if you increase the time difference you end up with a greater impulse.

In Topic: New Coder Struggles - What To Do Next?

26 February 2015 - 03:57 PM


You can:


1. Look at other people's projects, like on Github.

2. Write the game subsystems, like the audio, rendering, etc.


Harvest ideas from elsewhere. The reason why you are lost is because you have never written a game before, as I'm sure you know.

Thanks, that's somewhat helpful. I don't really think I'd need to do much in the way of rendering though, considering I'm using Monogame and am not working from scratch. I also realized I have to create a GUI so that levels can be accessed and whatnot.


No problem. I wasn't really being specific to Monogame really. Eventually, if you enjoy making games with Monogame you will want to break free and write your own everything - see this as a heads-up! :)