Learn to code and write games on the Nintendo Game Boy | MVG 

I love the Dreamcast homebrew scene. They've really kept the system alive a lot longer than Sega has. You should cover that.

nice

Do a ps2 scene video, and bring some light to it. That scene has been hurting for a while. Swear Jay-Jays reuploads saved me from tons of broken links years ago. PS thank you for your hard work on the OG xbox!!

original xbox homebrew coding would be cool to see.

Yes please! PS2 in particular is pretty rough to get into.

that would never work

and it's gonna be "our" game not your game

Pfft that game already exists it’s called Super Mario Land... idiot

@@TheRetroFuture2 no its sudoku dumb dumb

Lol, Alexey Pajitnov beat you to it. 😆🤓

you should make him fight a turtle 🤔

A video game about a... Plumber? Who would play that?

Just make sure the plumber doesn't wear a tie. Because plumbers don't wear ties.

They took my snake and they turned it into a plumber. They made the eggs into barrels. The pine tree they made into a gorilla but I recognize my design. Donkey Kong my ass! That's Construction Snake.

Don't forget multiplayer, give him a brother.

basically, you can use C for everything.. C is just a standard all you need is a compiler chances are that someone built a compiler

@@marcello4258 Yeah, but you couldn't use C back when the system was current, because there weren't any compilers for the destination chip. And the compilers of the time were hot garbage about optimization, and on that system you needed every possible edge.

@@nullplan01 that might be right, but wasn't my point though. Just speaking of today mari does as well.

Well in all honesty, if you want your code to be as optimized and as quick as possible, you still have to use assembly. The gbdk is more of a wrapper of sorts, which of course reduces performance, but hell - for 99% of the cases it will be more than enough. It can still get really mind-twisting when you start working with all the registers, seeing as not all of them are mapped in gbdk (or at least not on the version I was using, I think gbdk 2020 is way further in that regard), but it is still quite enjoyable to use! I've ran stuff only on an emulator so far, so the next step would be to get an everdrive or an ez-flash. Oh and btw the gbdk can also be used for gbc stuff, not only gb, but I still can't wrap my head round how pallets work :D Oh and programming sound on the gb is a nightmare... waaaay harder than programming graphics or even game logic, but I'm drifting off here...

@@nullplan01 I thought I remembered reading a post by a guy who worked in the industry back then and that they absolutely did use C to make game boy games, which surprised me.

Considering that 99% of commercial Game Boy game were written in Z80(-ish, the Sharp LR35902 was a mix of the Intel 8080 and the Z80) assembly, C is actually an upgrade. I'm curious how efficient C code generated by this compiler would be compared to the more direct assembly option - I'd be concerned about how well it scales to game-scale projects since RAM and ROM size are so constrained.

@@Damaniel3 C is anything but efficient compared to typical assembly. It's gotten a lot better since the original GBDK, but ultimately with C being a stack oriented language and the stack being slow to use on the GB you'll end up with quite a performance hit compared to assembly, and if you want to push the hardware you pretty much have to write everything in assembly.

There's GB Studio for people that don't.

@@CasualPokePlayer its worse than that -- the Sharp SM83 (and i8080 and to a lesser extent the Z80) is a horrible target for C (for example, it doesn't have some of the addressing modes useful for a C compiler), and the most commonly used gameboy C compiler isn't a particularly good C compiler. However, I would like to point out that these faults are because C is a bad match for the SM83, not because C is particularly less efficient than assembly on a more modern architecture (that's a completely different story, so I won't discuss it).

@@undefinednan7096 Most of the problems with GBDK are fixed with GBDK-2020, and yes I know, the GB is fundamentally a bad platform for C, hence a performance hit over typical assembly.

Download Unreal Engine... you will have more fun than making tetris 2.0 for your gameboy.

@@aluckyshot yes but its waay harder than making a Tetris 3.0

@@rayan0468 lol u wish, Tetris is *very* complicated

Just download Engine001. You don't have to code and its superrrrr easy.

Need an artist and or support writer

Same here. I’ve made some flashcarts years ago, but only recently wanted to really start writing stuff for it.

YEEEEE MADAFACAAA

@@amateusz2137 @thefredo1000 yeah because this is the very first and only bit of information on the Internet on this topic

No you haven't. Probably don't even know how to code.

@@firstlast7112 Hi, I've been in the GBA homebrew community for some years, I'm also a Google intern, so I do know how to code.

writing a gameboy rom in c to try and learn is a bit counter productive tho

So true!!

Many of these co called "courses" are just people bragging about themself with little to none educational value and missing key information. Where as this is a concise pointer in a particular direction whith encouragement to go further.

@@iraniansuperhacker4382 no xD

Same here, I've tried before and I couldnt figure out how to do anything besides printing text when I press the ds's buttons. It would be great if he did it

For that I recommend using the PAlib library, also in C. I created some games about 15 years ago

@@TiagoSantos-lt4do interessante, ill check it out.

You can have a look at devkitPro, specifically the devkitARM. It has a built in library called "libnds". What you do need to be prepared for, is that the ds is an insanely complex console, that still works very similar to the entire gb family, most closely to the gba. So it's probably a better idea to start programming for the gba, since you won't have to juggle between the two screens (and two separate graphic engines) of the ds.

GBA and DS too

Atari lynx as well.

Wii.

@Risen General It is, however the PS2 also had 3D development kits like Renderware which was responsible for being the game engine for many many PS2 titles.

@Risen General I think you might be confused with 'Renderman'.

Hey, no need to throw shade on other youtuber just because there're not qualified enough to talk about the things you want.

@@annedrieck7316 Shouldn't be any bad criticism, but they often talk BS when they dig deeper into the matter :D

Of course Bisqwit, Jeff Gerling, Dave's Garage and others are not channels that exist.

@@BrunodeSouzaLino Of course they exist and they are also super professional. The problem is that you really need to search for them, because the YT algorithm is not preferring these kind of videos

@@karioken Good content does not simply plop on your lap. What plops on your lap it's what's popular.

*cough* GB studio *cough*

Just use GB studio

Just look at a gameboy game called tyrannosaurus tex for the gameboy color. Its a real technical achievement of raycasting on the colorful brick.

@@Sinistar1983 faceball 2000 as well

I've been experimenting with this off and on, and don't have it it fully working yet. I'll post a reply if I get it going.

Hi again - I found a working parallax example using GBDK over on GitHub from 2019 ( github.com/leo-rp/gbdk-parallax-example ), which shows an example of using the add_LCD and add_VBL interrupt methods. What MVG did not show was how to increment the background's position every time the screen refreshes (in the V-blank interrupt method). This example is quite elegant, by bitshifting the movement of the foreground to calculate the movement of the midground and background. He's also checking the LY_REG instead of LYC_REG to figure out what scanline he's on, and he's moving the background with SCX_REG and SCY_REG instead of the move_bkg function. Big respect to MVG and to leo-rp (on Github) for making this information publicly available!

Not a clue, but It happened & I didn't learn much but yea...idk its cool....development of coding & gaming & stuff...

I'd love to hear you two expounding upon this thought.

@@squishmastah4682 Programming is (from a technical perspective) a highly logical endeavour; computers are very unforgiving, and will do exactly what you tell them, exactly how you tell them to, even if what you told them to do was completely wrong. There's no room for nuance, and a computer can't infer from the context what you meant for it to do. Once you get used to that 'model of thinking', it tends to leak through to other aspects of your life. You might start to get annoyed when people give instructions that are missing details that you *could* have guessed at, for example; the stereotypical example is cooking with recipes, which often use ambiguous units of measurement. Likewise, you'll probably start recognizing more processes in everyday life, causes and effects, reason about them as if they were defined in code, and so on. Which can lead to nagging questions like "wait, why *do* things work this way?", or spotting what seems like logical errors in how people approach things. Now I should be clear; this is not an *accurate* view of the world, even if programmers tend to forget this. Code is primarily written for humans to read, not for computers to execute, for example. And often what seems like a logical error in someone elses behaviour actually turns out to make total sense, you just didn't have all the information (but you wrongly believed that you did). But nevertheless, it's how many programmers start looking at the world around them.

"I think differently than you," is a statement hard to articulate, because we all communicate differently as well. So, I'll try to just provide some outlines below, with sources that expound on those ideas. Coding principles help keep your mind disciplined for everyday tasks. As you program and discipline yourself with your code, you'll notice your thought patterns shift to apply some of the key coding principles (in the link below). Discipline is good for everyone. www.geeksforgeeks.org/7-common-programming-principles-that-every-developer-must-follow/ I had a few more paragraphs written up here and realized that I'm not actually able to articulate it well. So, like the best of us in programming, I'm going to import someone else's work! www.quora.com/How-does-programming-change-your-way-of-thinking There are many, many answers on that page which can articulate much better the ways that I've changed my thinking.

@@crytocc Could totally relate man, I solely depend on instructions now and I find it hard to improvise. 😹

Same! Coding for GB suddenly got more interesting, didn't it?

You can still write parts of the code in Assembly because it is C. Even when the gameboy was releassed basically no game developer was interested in wrtiting a game in Assembly since games tend to get complex (try programming pokemon in Assmebly it will take you a few years). This is even worse when you have more than one person working on the same codebase. So C which allows injecting Assembly when needed and it being fast enough was the obvious choice for game development for a long time.

C is only JUST above assembly. In fact translating C to assembly (what a compiler does) is usually pretty straight forward. But it greatly simplifies coding. For example assembly doesn't have a printf so that would have to be copied and pasted from somewhere else. I used to write code for my TI-83 in C++ back in the day. It's a Z80. I think the GB is also a Z80.

@@sakurajin_noa Most roms for the 8 bit era were entirely written in ASM. Even in the 16 bit era, very few games were written in C. ASM really isn't that hard. C does add some overhead in terms of CPU usage, especially the older compilers that would have been available in the actual 8/16 bit days.

@@awilliams1701 I’m aware of that. I had to convert Assembly to C and vice versa for a comp org class back in college. I SHOULDN’T be too surprised, but from what little I know of game development from the 70s to the 90s, it was mostly done in Assembly. It was a pleasant surprise that it’s in a language that I can actually read 😄

Alleyway (Breakout/Arkanoid clone) can’t have taken more than a few weeks even before the gameboy hardware was finished. I look at some videos of Japanese programmers at the time and they’re all in their early 20’s, some of the bedroom game devs on the spectrum were teenagers. this isn’t rocket science but it takes a bored teenager’s enthusiasm 😁

Time to demake doom for gameboy

I'm the best

Firts

I WANT PROOF

what if they tie?

What if they comment on the same frame of existence

brasil enois caralhooo

Além de melhorar o inglês o conteúdo também é excelente. Desbloqueei meu nintendo wii e o PSP depois de assistir os vídeos dele :)

No need to be sorry, you do good.

Sopa do maca

Opa, tamo junto! Tem um outro canal que eu recomendo e é esse aqui. É nessa mesma pegada, mas mais técnico ainda: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-F8kx56OZQhg.html&ab_channel=javidx9

Its like the flint and steel of the consoles. When the power goes down... you put a pair of AA batteries and you can play like a Chad in any environment :) post apocalyptic console xD

I too was also concerned about the hex values lol

How long has it been since you talked to her ?

@@ArpeggioPegasusMusic about a year ago.

ru-vid.com/show-UCVYDU8oQJFiHYLco5qVtayw this is her youtube channel, though.

More details would be nice. Where to find the game, etc.

@@xmlthegreat the game is free and up on her youtube channel. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-G6Kb8_6nPYo.html this is the game with the download link. it's a neat little POC and it can be played on any gb emulator.

Thanks for the link

His code is so simple, it's almost nonexistent. Making games based on it makes no sense.

I've been interested in getting into 3DS development, is there a discord or some other centralised hub for the 3DS dev scene?

Yes, he did

As I said in some comment reply before, it also bothers my soul a lot :P

?

?

You need to know Assembly and have access to Wario Land disassembly to be able to do that or know hex editing and hack away. If you want to do some real work on the Gameboy sooner or later you need to get your hands on Assembly because of the limited resources the Gameboy has. For many things C works fine and you could make a functional little demo on the Gameboy using just C but if you want to know how to truly work with the system you gotta learn Assembly. C has much more overhead, aka bloat than Assembly and on a system like the the Gameboy with limited resources you will be using a ton of CPU to do something that in Assembly will use much less. Assembly is 1:1 with the machine instructions and it is dependent on the microcontroller in question. In modern embedded programming we use C mostly because it is definitely easier and faster to write code for but you will find times where you might need to be really specific with how you want certain things to operate and thats when you might need to use assembly. Many compilers, havent check this one allows you to do what it's called inline assembly which is to use assembly instructions on C which is used when you want to override the compiler on a specific situation. In practice you could use C for things that dont require much CPU while you optimize things using Assembly. That being said this is a great starting point to learn C and you will end up learning a lot about the hardware cause working with the GB will force you to know the ins and out of said hardware.

Similar to what MVG said, there's homebrew scenes for a lot of consoles

It has been around for a long time

I thought so too!

Same here, it bothers my soul xD

Go for it! :D Dabbling with C/C++ will probably make you a better C# programmer as well, as it makes you far more aware of memory allocations (especially if you dive into C, as it forces you to manage dynamic allocations yourself. Modern C++ is a bit less demanding on that front). Getting started on the GBC would be identical if you don't use any GBC-specific features. Games have to specifically opt in to use the extra GBC features, so on boot the systems are almost fully compatible with one another.

I

@@martynrandles check my channel!

@@Klopford Just heard your playlist... liked the lot & subscribed. ru-vid.com/group/PLjogBZPICEFGWIt9YCttDCjGTx48g8JxW I love The Dr Who Theme Song, no surprise for me really as I used to watch it back in the day (I'm a Tom Baker & Peter Davison fan... I was a kid then) & I love The KLF, they were deffo into Dr Who... The Ace of Base - The Sign is bloody good too, haven't heard that in years & never thought I'd hear a chiptune of it.

Please MVG! Am I the only one trying to replicate the code or am I just missing something? Didn't work for me, the parallax scrolling isn't moving, despite copying the glances of code we get.

I think there was a compiler, though most devs ultimately used ASM to squeeze every last drop of performance out.

Back then people programmed games in Z80 assembly, not in comfy C.

didn't notice... but was looking for a good excuse to watch this again lol ... could be down to an artifact of Wide-angle-lens use though, they do trigger us all... I stopped going to a cinema years ago as big screens just made it worse for me lol