/v/ - Video Games

>>15791345

There's a thread on this board call /agdg/ it's a general thread for amateur game devs, I imagine that would be the best place to ask.

Look up gamemaker tutorials on jewtube.

>>15791351

/thread

Start with the easy stuff.

Like the Book

The C Programming Language

or if you realy want NES just read the ASM Manual for the 6502 get CA65, LD65 and some emulator and work away

>>15791351

Thanks. I'll check it but I don't think I wanna post where guys already know what they're doing.

I'd probably feel like on the first day of school. I'll keep an eye on those threads though.

>>15791345

NESMaker or Pico-8 are the simplest. Game Maker has many tutorials

>>15791345

Do you actually want to make 8-bit/16-bit games, or games that look 8-bit/16-bit? The former will be very difficult if you're a beginner to programming. I recommend >>15791351 and >>15791368

>>15791345

learn programming

>>>/agdg/

do not make another pixelshit because that is low effort, it limits your brainpower

>>15791565

also bonus tip: if you're underage b& and have enrolled in some kind of game dev course or game design course, drop out immediately

1. Learn to code

2. Read up on the basics of a game loop so that you have a grasp of how games conceptually work, what it means to say that a game runs at a certain "FPS", etc.

3. Experiment, experiment, experiment! Get into the habit of just making bullshit to get familiar with the process of building a game. You'll be slow as hell at first, but you'll eventually get faster at churning out boilerplate code so that you can get to the meatier part of making a game faster.

4. When you've git'd gud, which will probably take you at least a year or two, this is where you start thinking about a real project.

>>15791404

>Thanks. I'll check it but I don't think I wanna post where guys already know what they're doing.

We get at least a couple posts like that per general thread, don't worry. And most people there don't really know what they're doing. You learn as you go, that's the whole point.

>>15791593

I guess you can just jump into some game engine if you already know programming but don't want to deal with the intricacies of making an engine?

>>15791446

If you want to have lots of control over what you do and want to make 8-bit games you'll need to learn 6502 assembly or pick up a compiler like cc65 and learn C (or whatever languages it's compatible with).

That being said, it appears NESmaker will give you plenty of freedom with regards to design and you could make an entire game with it alone, but when it comes to hardware you're more limited. NESmaker games as far as I can tell use a special mapper. It's a bit of a technical term that I really won't be able to explain well, but basically the gist is that a mapper is a limiting feature on an NES ROM that only allows it to be copied to a specific type of cartridge board/chip. The mapper that NESmaker devs chose is a strictly homebrew one, so you'll need to go to their specific supplier to get a cartridge that would actually be compatible with the game you made.

>>15791612

You can, but I do suggest trying to build an engine at least once during your bullshitting around phase so that you have a better understanding of how engines are laid out. Only niggers use things without understanding the basic principles behind them. You don't hold handguns sideways, do you?

First off, think about what you want to make. Then break it down into smaller components… What sort of "pieces" would go together to make the sort of game you want to make? Can any of those "pieces" be made as standalone things fully functional on their own? Pick one of them that applies and doesn't seem too hard and look up tutorials for how to do it. Follow along, but don't just mindlessly copy the code presented to you. Tweak it and customize it to fit your own purposes.

That's how I started anyways. The very first thing I coded for my /agdg/ project is a dialogue system. Funnily enough, while it's completely functional, I haven't shown it off in any of my demo day builds because I don't have a place to use it yet.

>>15791446

Oh I should also add: to get a feel for the way NES games function it might do well to try your hand at modifying an existing game first. There are plenty of tutorials on how to edit graphics and edit hex values using pre-made programs that require virtually no coding.

Keep in mind though that many modders do have experience writing their own programs for ease of access when it comes to modding something like level design or collision detection, so don't expect to be able to change too much of the game on your own.

>>15791345

if you want to be a game developer you need to either have a firm basis in either coding or artwork, or have a lot of time and drive to learn. If you want to work with other people then you need to know them very well; you're not going to end up making a game with people you met on disorder or something. Mount and Blade, for example, was originally made by one dude and his wife but he had a degree in computer engineering.

>>15791345

>I've wanted to develop simple games for the NES and SNESsince I was a kid, I'm a very good artis and I'm very creative but I don't know anything about coding. Not only I don't know anything about coding, I don't even know what it is that I should know.

Good fucking luck with the NES and SNES

t. someone who's been screwing around with NES 6502

>>15791404

>guys already know what they're doing.

We do not, don't kid yourself we are no pros

Just post in there, the thread is almost dead right now

>>15792351

>>15792649

RE or SH would take some decent knowledge since they have more mechanics than the usual indie walk simulator with spoopy jumpscares

I suggest doing it in RPG maker or some very simple 2D engine

Look Ao Oni and Corpse Party for examples

>>15792649

1. go to youtube

2. type unity tutorial

2.5. kill yourself if you as an artist non-programmer have a problem unity

3. follow it

Game development IS NOT for beginners. Even with a degree in computer science, you'd be hard pressed.

>>15791351

There's also a whole board called >>>/adgd/. I suspect they should have some resources to help OP get started.

Get friends. Doing all aspects of a game yourself and doing them good is reserved for exceptional savants. It's better to gather specialists and combine their talents.

>>15791345

Learn a scripting language like Lua or Python to grasp programming fundamentals in an easy environment that doesn't require any compiler or IDE setup. Work on patronizingly simple projects like Pong, Space Invaders or Snake until you're comfortable enough structuring your game that you don't need to constantly be looking up documentation. These practice projects also teach you different things like managing inputs, game loop and simple collision systems that you'll build your knowledge upon later. At that point explore other languages like C and C++ where you're expected to be more specific about what you're doing and the data structures you're using. At this point also explore different paradigms as it's likely you'll have been learning things in a specific way (most likely OOP with how much it has infested the industry) and another may be more productive or intuitive for you.

That's assuming you really want to learn how to program though. If you just want to learn enough to get by you can stick with scripting languages and use something like Love2D with Lua, which is very approachable for beginners.

>>15793003

Of course, I know that.

>>15791351

Woops, board's >>>/agdg/.

I'm pretty much 100% an ideas guy and always jot down my ideas for games I want to make (documents full of mechanics and story, spreadsheets, etc). Sooner or later it's time to spread out and maybe actually try to work in order to get even a remote of skill (art, music, programming), so maybe I'll start to hang around /agdg/ to transition in this process of just not sitting around doing nothing.

Outside of starting with smaller types of games, I always heard that small fangames were a good way to get experience too before you try to tackle on a major project.

If only there was a recurring general thread for amateur gamedev.

Perhaps an "amateur gamedev general"

If only this existed as a thread, or with it's own board, abbreviated >>>/agdg/