Skip to main content

Browse GamesGame JamsUpload GameDeveloper LogsCommunity
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
Sunday Drive Games11 hours ago

Thank you for the feedback! It’s really helpful. I was actually trying to keep the hitboxes a little less exact because I wanted the snowboarder to be able to squeeze through tight spaces and help sell the depth of the mountain. I think I may have pushed that balance a little too far in some spots though 😅

 As for the skiers overlapping objects, I think I might have some scripts conflicting each other because sometimes skiers acknowledge the obstacles and sometimes they don’t… I’ve been trying to get that behavior consistent, so that’s really helpful to know. Glad you enjoyed the game overall!

Reply
Scharf39 hours ago(+1)

What I saw when looking into infinite scroller was that you could instead of spawning objeects design specific regions to come next. You could hardcode these regions and implement their path without having a dynamic or self aware calc. For a selfaware calculation you could use rays and detect wether something is "in front" and thereafter turn.

Reply
Sunday Drive Games8 hours ago

Yeah, this is actually really interesting. I tried using an array for the spawn regions, but when I was testing it I wasn’t really getting good results, so I ended up going with the dynamic spawning approach.

I’m curious about how you would structure the region/path system though. Would each region basically have a set of predetermined obstacles/enemies and their paths, then the game just moves through those regions as the player progresses? I’d definitely be interested in picking your brain on it!

Reply
Scharf37 hours ago

Yeah that's what the tutorial said, but one should always go from there. When scaling I'd differentiate between moveable and non moveable objects and in which layer they would be (e.g. skier ->moveable + collision with other objects ->calculation necessary, tree -> static + collision)

You could also build the it semi static into individual regions and put them together like tetris blocks when generating the next spawn. You would have a set variety, but through variation and orientation changes you could do this well (needs playtesting).

If going full dynamic you would need to either track and recalc the routes, or set a ray of length [e.g. 1m]. You could also evaluate each collision and on collision turn the skier around. You would need to differentiate the individual collisions and maybe work with different collision layers.
At least that's my non-professional-developer view. It also depends on how your game is currently implemented. Godot also has Path-Nodes, but I haven't used them yet.

Reply
AboutFAQBlogContact us
Copyright © 2026 itch corp · Directory · Terms · Privacy · Cookies