From Gamer to Developer: My First Steps

Side_Burn

Formerly 'Tyler777'
Sep 12, 2017
5
4
Hey everyone, glad you stopped by and got interested in this topic!


First, I want to share a bit about where I’m starting from and where I’d like to go. Here I’ll be writing about the challenges I’ve run into, and sometimes just throwing in some “philosophical” thoughts on the subject. I’m posting here because this forum has the kind of audience that’s really into this stuff. On Patreon or similar platforms it’s hard to find the same level of engagement (though I’ll probably repost some things there too).


I’ve been playing games of this kind for a long time, and I really enjoy them. So a lot of the time I look at things from the player’s perspective. But I only started making games very recently — just a couple of months ago. At first, I just wanted to learn more about AI, finally get into programming, and improve my English (which is still pretty weak). Somehow, all of this naturally led me to start working on a visual novel. I always dreamed of making one, but I never thought I’d actually try. Guess fate had other plans.


There are plenty of great beginner guides on this forum, but I want to focus on the small details and nuances that are also important, yet don’t get talked about much.


So, here’s my very first takeaway — something I picked up through years of playing games, and that I only now see from the developer’s side.


The first and most important thing: if you start making a game, you need to know how it ends. The ending should be written before you even begin. Create a scenario — doesn’t matter if it’s on paper or in some app. I used XMind myself. Think carefully about the ending (or endings, if you plan on having multiple).


If your game has no ending, then it has no goal. And if there’s no goal, it’s just a dream — which almost always turns into another unfinished project. I’d say there’s a 99% chance it’ll be dropped. And as a player who has seen this many times, I can tell you: it’s frustrating. Especially when the game had real potential. That’s why you shouldn’t take it too personally if someone leaves a not-so-nice comment about it — it’s a fair point.


That’s it for now. Next time I’ll probably write about Git — I’m learning it this week.
If you’re curious, you can check out what I’ve done so far via this link:

 

Side_Burn

Formerly 'Tyler777'
Sep 12, 2017
5
4
Just a quick note: the game is focused on the theme of the NTR. If this topic isn't for you, the game might not be what you're looking for. Here, I'll be sharing content related only to the development process, not the game itself. Thank you for your understanding.
 

Side_Burn

Formerly 'Tyler777'
Sep 12, 2017
5
4
Today I want to share how I first discovered GIT. For experienced programmers, this might sound funny, but for me it was a real revelation.


When I started programming a simple game, everything went quite smoothly. But as soon as I tried to make it a little more complex, everything broke. I made a copy of the project folder, then broke it again, then made another copy… and repeated this process several times.


Eventually, I learned about GIT, watched some tutorials on YouTube, and now I really enjoy using it. If you’re just starting your journey in programming like I was, I highly recommend learning the basics of GIT as early as possible. It takes your project organization to an entirely new level. With GIT, you gain confidence: you won’t ruin anything permanently, and even if you make mistakes, you can always roll back.


With that sense of security, learning programming becomes much easier. So, if you’re a beginner and you’ve already thought about making backup copies of your folders, it means you should have learned the basics of GIT yesterday. Maybe for many people this is obvious, which is why it’s rarely mentioned in beginner guides. But for me, it was an important discovery, and I hope it will help someone else too.