Game maker studio procedural generation how to#
Game maker studio procedural generation generator#
Game maker studio procedural generation full#

A lot of PGC stuff I've seen is bottom-up and tries to figure out what suits random chaos by analyzing regions, and that's usually wonky and pretty labor-intense. And of course, if you also keep track of what type of room a room is (banquet hall, bedroom, dungeon cell, armory, courtyard etc) you can fill it with stuff much more intelligently, or have it influence its surroundings in meaningful ways. It's generally useful to try to be as top-down as possible no matter how you generate stuff in the end for instance, you should store info whether a region is a ROOM or a CORRIDOR instead of just having a wall/not wall system - this makes it easier to know where it's OK to spawn stuff, and if you also have a list of where you put rooms and what sizes they are it's much faster to find a valid room cell if you need to spawn something in a room.KISS (and the Unix philosophy, for that matter) applies even more than usual for code that does stuff on its own, so try to rather have multiple generators that does ONE thing and are independent over having one superalgorithm.I've learned a bunch of stuff along the way, though: I've dabbled a lot in PGC myself, but I'm not exactly good at it yet. Here's a few more links that drew me down the rabbit hole (though none are GM specific):Р”Вungeon Building Algorithm (Frankly, the whole of Roguebasin is a great resource for dungeons and proc gen) Just wanted to have a discussion about some proc gen things that you guys have worked on and share ideas about the best way to go about it within the framework of Game Maker.

Game maker studio procedural generation generator#

Of course, it doesn't replace everything, but a finely crafted generator can be a thing of beauty and can add so much replayability and novelty to a game. Creating dungeons and over-world maps, piecing together weapons/spells/enemies, random drops, making or adjusting game art within the code itself, creating lore or names/places/etc on the fly, there's so much to learn. I've been messing around with proc gen a lot recently and, while I've hit a large number of stumbling blocks on the way, I've become more and more fascinated by the way in which content can be created and tuned on the fly.

Game maker studio procedural generation how to#

After doing some research, I found that I could maybe use a compute shader to have the GPU help speed up the generation, but I am not sure how to implement a compute shader in my case.I ran across this article today, which is an interesting breakdown of the processes that go into PCG: So You Want To Build A Generator. I want to be able to generate terrain in real-time to create an infinite landscape. This creates terrain that looks fine, it's just too slow. If (global._testgrid = TILE_FULL) tilemap_set(global.testmap, 1, gx, gy) } else global._testgrid = VOID // set grid position to an empty tile

Game maker studio procedural generation full#

Global._testgrid = TILE_FULL // set grid position to a full tile Generate_simplex_octaves2D(_largestfeature, _persistance, seed) // generate octaves using _largestfeatureР”Р‡or (var gy = 0 gy level) // if below level My code looks like this: var level // height of the terrain I often need to wait 5 - 10 seconds for a somewhat small grid to generate. The problem is that the grid generation is rather slow. I was able to get the noise function working, and I set up a grid of 16 by 16 tiles that uses the noise to generate the height of the terrain. I've been trying to create procedural generated 2d terrain (similar to a game like Terraria) using Simplex noise.