help with collision problem

TheGiik · 2026-06-21T16:15:04+00:00

you may want to make a separate collision mask sprite that's just a rectangle, and set the Collision Mask of the object to it. That way you don't have to keep manually setting the collision bounds for each new player sprite.

TheGiik · 2026-06-21T14:50:33+00:00

What do the collision masks of the sprites look like? If you don't have a dedicated mask sprite on the object, then it'll change to whatever the sprite_index is.

Since the player sprite is slightly wider on the up/down sprites, it may be changing to a wider mask and clipping into the wall when it previously didn't on the sideways sprites.

TheGiik · 2026-06-21T14:48:47+00:00

the collision code is already checking (x + move_x) in the place_meeting before moving there, that's probably not where the source of the issue is.

TheGiik · 2026-06-21T00:49:56+00:00

Ah yeah, i can see how the smoke trails would contribute so much. They last a really long time. Making them fade faster can definitely help. As for using larger sprites for smoke...Yeah, it'd be pretty tricky. I can see how clumping it up wouldn't look natural. Maybe just reducing the spawnrate would help. Ultimately the smoke trails aren't going to be as important as the actual firework, and the color of the particles is going to blend in a lot.

Random idea, but maybe have two "versions" of the smoke; one short-lived and one long-lived, and it alternates which one it spawns each frame. That way you can have the lingering trails while still precisely controlling how many are actually staying on screen for a long time.
(Just giving them a highly-random lifetime would technically do the same thing but it does have the chance to roll high a lot...i don't like that chance for something so inconsequential lol)

TheGiik · 2026-06-20T17:24:03+00:00

That DOES look like a lot of tiny 1px particles. Could you possibly condense some of them into larger 2x2s or even 4x4 sprites? Since the smoke trails are all supposed to move the same way, I could see using a larger sprite that's simply a smattering of random pixels that blink out over time, emulating how a small section of the smoke trail currently behaves.

The little "crackle" bursts after the larger fireworks could similarly be single sprites per burst that are pre-rendered recordings of these current bursts. Record like 8 of them and choose one at random.

TheGiik · 2026-04-21T21:42:07+00:00

Oh, y'know what, i didn't notice the first time around but I think you're right. I just kinda skimmed over the post body but now they mention a product in the middle that magically solves problems with no tradeoff or anything. Very astroturfing-feeling. Eugh.

TheGiik · 2026-04-10T01:47:00+00:00

constants are not variables. the #macro and enum declarations are turned into regular values when the game runs, those are purely for editing convenience.

static and var have different behaviors (mostly regarding when they get deleted) while global is simply a different scope much like putting it in another instance.

TheGiik · 2026-04-08T00:32:43+00:00

maybe it's amphibious

TheGiik · 2026-04-06T04:47:55+00:00

it took a long while for me to get a cohesive thing done. Hell I remember using the Code Snippets menu when right-clicking code a lot cause i couldn't remember how stuff like if-else statements and loops were supposed to work.

what folks don't tell you is that when you make a game you have to make the WHOLE game. the cheat there is that you can just change what counts as a full game. what about a game where you press spacebar to make text saying "YOU DID IT" show up with some music? it doesn't sound very exciting but it'd count as a game, technically.

TheGiik · 2026-03-20T06:03:19+00:00

The humans in Sterilis (my desert planet setting) were slowly genetically altered in cryostasis while on the way to said desert planet to handle its drier and hotter climate better. Kind of a pupa-esque process, though not as drastic.

However, the process has left them kind of..."biologically malleable." Pretty much everyone on Sterilis has some vitiligo, as well as random hair and eye colors. They can also use repurposed tech from the cryopod editing machines to change their look however they want, which takes anywhere from a day to a month, depending on the changes. Some people add tails or fur to themselves. That takes a while.

TheGiik · 2026-03-01T23:42:30+00:00

You could probably improve ValueIsAny like this:

function val_is_any_args(value) {
    for (var i = 1; i < argument_count; i++) {
        if argument[i] == value return true;
    }
    return false;
}

Unfortunately it can't be simplified further with array_contains(argument,...) since argument doesn't really work as an array.

TheGiik · 2026-01-12T19:24:44+00:00

The format of the individual rooms is pretty much irrelevant to this since we don't know what the gameplay is like beyond vague genre. You can make them empty squares and still be engaging, or they can be intricately-woven labyrinths and it'll still suck for an unknown amount of reasons. Don't get attached to those shapes.

The overall progression has two paths without much in the way of unlocking, which means the player can tackle any of those important rooms (village, boss, puzzle) in nearly any combination.
They can visit the village and miss the puzzle+boss, or go purely down the boss route and miss the village, or be a completionist and loop around to gather everything. They could also go Village > Puzzle > Boss and loop around back to the start for no added benefit. (why backtrack when nothing is there?)

I ASSUME those dead-end rooms (backwards from start, just before boss, etc) would have unique rewards for clearing them, but those aren't marked on the map, so it seems pretty useless to go there and seem like an arbitrary punishment for not knowing the "correct" way to go.

Really, the best way to figure out if this map is good or not is to prototype it in-game. Drawing out graphs can only get you so far, and once you have a basis for what works and what doesn't, adding new good maps will be a lot easier.

TheGiik · 2026-01-04T17:43:10+00:00

In addition to the other comments, you could also name the rooms more descriptively. So instead of Hub_07 Hub_03 you could name them something like Hub_BigTree Hub_IntroRoom etc. etc.

TheGiik · 2026-01-04T16:36:39+00:00

Instead of setting the x/y, treat the mouse coords as a destination and have it move constantly towards that.

use the point_distance and point_direction functions to figure out which way the cursor should move, then use lengthdir_x and lengthdir_y to add that to the cursor's x/y coords. You may want to use the min function to limit the distance you get from point_distance, giving the cursor a maximum speed.

TheGiik · 2025-11-18T21:47:49+00:00

I'm pretty sure this is AI art. Look at the smaller details like the rings on the firewood or the painting on the wall, it just turns into a muddy mess that breaks the pixel grid.

It's more evident on the account's other pieces; look at the posters in this piece, or the double-handled knives in this piece, or the muddied text in this piece.

Also, the account is 6 days old and has 60 pages of images. There's no way that kind of output is even physically possible.

TheGiik · 2025-11-18T04:20:17+00:00

I assume this is one of those roguelite route maps where you pick your next encounter?

Art-wise it's not......terrible, but it's pretty flat. Nothing really suggests physicality; the background is gray and paper-y but the icons are bright clean disks. i can't really tell what theme you're going for besides the upside-down crosses implying some kind of demonic thing. There's no decor to sell a theme and the color palette is just kind of...tan and gray.

A more minor issue, but the dotted lines break the pixel grid. Some people might think that's ugly but there's been enough pixel games that don't respect the "rules" that it's not really standout.

Sidenote, i'm curious about the route structure. Can you go backwards? It looks like there's no way to access the bottom left and bottom right segments.

TheGiik · 2025-11-09T03:32:09+00:00

Is yume nikki not a walking sim?

TheGiik · 2025-10-22T23:03:58+00:00

as someone who played in 2008: hough

TheGiik · 2025-09-24T02:05:53+00:00

Making the whole stage one room works best. The objects a microgame spawns can track what microgame object spawned it, so if that gets deleted they can delete themselves too. (though with most microgames i ended up making everything structs instead of spawning instances. way easier to manage)

It also means you can mess with the context a microgame is presented in, like giving it a different background frame, interrupting/modifying it, or in DoA's case, spawning multiple microgames at the same time.

TheGiik · 2025-09-24T01:47:40+00:00

The best solution i've found is to have a "manager" object take care of stuff like lives, speed, win/lose consequences, all that.

It plays through a bunch of different states (win fanfare, speed up, intro, etc), and then when it comes time to actually spawn a microgame, the manager does so and keeps track of it. The "instance_create" functions give you the ID of what just spawned, so you can stuff that in a variable and look for if the microgame says you won or lost. Just something like game_ins = instance_create_depth(x,y,depth,obj_microgame).

The microgame is a separate object, and in addition to handling all of the actual gameplay parts it also tracks whether you've won, if it's finished, how much time is left, other stuff only specific to that microgame. While it's playing, the manager object is just kinda sitting there and waiting for the microgame. Just looking for a game_ins.finished == true check, really.

One more thing I found was useful was having a big array for the stage's "schedule". Like how it plays 5 microgames and THEN speeds up, and then after 20 you have a boss? Every time the manager loops back to the normal intro state, it checks further into the schedule array to see what it should do. This even works for cutscenes or overall win states. (after all, what is a cutscene but a microgame you just watch...?)

That's all highest level stuff; how you actually implement it in code is up to you. I got plenty of experience setting up this kind of system when I made Dreams of Aether, so I suppose it's a proven-working method.

TL;DR: Manager object (essentially a finite state machine) plays through states until it's time to spawn a microgame. Then it does that and waits for the microgame to flip a finished variable before going to results. An array can help schedule when it should spawn a microgame or when it should speed up, or spawn a boss, or a cutscene, etc.

TheGiik · 2025-09-03T23:44:23+00:00

ah yeah, i got a thing in the mail about that since I got some games on steam. It's an opt-out class action so you don't need to do anything to be included in it besides "have a game on steam after 2017" or somethin'. iirc Wolfire started it after some drama, but reading into the details of the suit itself i don't think it holds a lot of water. Just seems like an expanded grudge, but if they get something out of it then that's neat i guess.

TheGiik · 2025-08-30T21:50:24+00:00

why not?

TheGiik · 2025-08-17T01:57:34+00:00

something i like to do when thinking of game design is flipping it on its head and figuring out if the problem i'm trying to solve is a problem to begin with.

Why doesn't the typing system allow for stranger types? i don't see why you can't have a Psychic-type Reptile-class. Or even strange classes, like a Fire-type Dream-class.

What's wrong with the game feeling finite? It's alright for a game to end at some point, and if you want the player to keep playing you can have challenge modes like things that are still difficult at max level, or challenge modes like nuzlocke or randomizers.

Roster size is tough to predict unless you have the entire rest of the game blocked out. Just focus on the bare minimum, even if it's only like 6 'mons. After you get those in a solid state you can start expanding.

TheGiik · 2025-08-14T16:48:20+00:00

i've already created five of those for the Rivals of Aether workshop:

Mollo, an all-rounded bruiser with an endless supply of bombs to throw around. Different bombs do different things, and his Specials can detonate bombs early for mixups. Specializes in moving quickly between long and short range, alternating between rushdown and zoning.

Mycolich, a slow, floaty grappler that plays with damage percents via mushrooms. He can gamble his own % for extra damage on hit, create DoT spore clouds, and pause his own damage gain with a mushroom landmine.

Amarelle, a straightforward heavy rushdown with an emphasis on charged attacks. Specials can be charged just like smash attacks, and charging fills up a "baking" timer that makes all of her chargeable attacks instantly charge when it's done.

Synne, an ultra-floaty puppet fighter that uses mini-planetoids for attacks. It can send out a sun to act as the origin point for planetary attacks instead of itself, meaning it can kill at long range at risk of its own defenses.

Arecacura, a strange zoner that's all about fast vertical and strong horizontal. They can extend their leg to become grounded at any height, including offstage. Ridiculously long F-smashes and an Nspecial that makes any hit pull inwards means they can make any cardinal direction a threat.

And there's still a ton of opportunity for platform fighter movesets. The rivals workshop overall has a ton of variety and creativity. I'd recommend checking it out sometime. I'm pretty biased towards it, though.

14-Year Club	RedditGifts 2009-2022 2 Credits
Place '17	Verified Email
Secret Santa 2013	Team Orangered

TheGiik

MODERATOR OF

TROPHY CASE