Lookup Windows API Virtual Key Codes by pressing keys on your keyboard. Get instant C++ code to check if that key was pressed.
Month: February 2020
I was originally going to title this article “The Art & Science of Code Documentation”, but the more I thought about it, the more I realised there isn’t a lot of science behind it. It really does become a fairly subjective thing. Some people comment and document more than others, some files 100’s of lines long don’t need documentation, some that are under 100 lines desperately do.
But there is an art to it, and there are a set of good, strong guidelines that if followed, will ensure that your code remains readable for yourself in 2 years time, or to the next person to try and decipher just what the hell you were doing.
Let’s go over them.
I’m Dan, founder of Noobles Studio, and I’ve recently released my first game, The Taller I Grow. Currently, it’s available for free on PC and Mac. It was in development for around six months, and I spent a good portion of my free time between high school and other stuff working on it.
The Taller I Grow is a puzzle-platformer game that is stylized to look and sound like it’s being played on an old DOS-like computer from the 80s. The main game mechanic is your ability to connect to objects in the environment, which makes your character taller in the process. This mechanic is used in a number of ways to solve puzzles and get through 30 levels.
Today, I’d like to give you all a behind-the-scenes look at the development of the game — its inner workings, the motivations for it, and some of the tools used to create it.
Whether you’re a solo auteur crafting an experience that remains true to your vision, or you’re the chief ideas guy of your three man team; every game needs to start with a Game Design Document.
When making your game there’s really no better way to begin getting noticed than by making a devlog. You can keep yourself motivated by getting encouraging feedback all the while gaining new fans, before the game is even done.
But I see a lot of bad devlogs that aren’t giving the developer these things and instead they lose motivation and they never finish their game. I’ve read enough devlogs and written my own that I think I can give some pointers on writing a good devlog.
Well, you’ve definitely got some ambition in you. Making a Video Game from Scratch is not an easy task. In fact, I would say it’s the hardest thing I’ve ever done, but you know what? It’s also the most rewarding. In this article I’ll help you get started and point you in the right direction.
So you’ve decided to bite the bullet and are ready to make that video game. Excellent. You do a little bit of planning and you’ve got your game scheduled for release in three weeks time. Let’s get this done.
One of the first things I like to do when I start a new project is Input Handling. I think it’s generally an underappreciated and underdeveloped aspect in a lot of games. Input is one of the core parts of how you play a game and you will use it constantly during development.
There’s a couple of reasons you might want to make a video game. Maybe you just finished the latest blockbuster AAA cinematic game released on the latest platform and you have ideas. Or perhaps you’ve seen some of those nifty little “indie” games that keep getting released that you see on Steam and think, yeah I can do that! Hey, maybe you’re a software developer and you’ve heard that game development will build up your skills.
Whatever the reason, you’re here, and you want to know how to make a video game. So let’s get started.
Hello, I am Konotoko; the developer of a game in progress named Their Radiance. The game is intended to be a unique and unconventional video game and has been in development for about 2-3 years. On the surface, Their Radiance is a 2D platformer with no enemies. It’s intended to be about a quest of …