Hiding among 100 NPC deer with up to nine player deer sounds like the crowd itself becomes the main mechanic, so I can see how a performance pass snowballed into reworking the deer too. Did the NPC deer behaviour have to change so player deer can genuinely blend in, or does the Hunter mostly spot players by how they react, like bolting when a TrailCam catches them? Also curious how the 40-second Wendigo night phase changed the pacing of a typical match.

Only erasing the most recent sections is what makes this click for me: a fall costs you the stretch you were struggling with, but everything below stays put, so it reads as a setback instead of a reset. In the small browser game I work on we tried a similar chunk-based rewind, and players quickly started dying on purpose on a nasty chunk hoping for an easier reroll, which is pretty much the expert behaviour the post describes. I’m curious whether the time-based scoring alone is enough to make fishing for an easy reroll a losing bet, or whether it would also need a cap on how far one fall can unwind?

The fullscreen case is a sneaky one, since the browser can hide a panel without ever running your close handler. I like the random-click tester idea a lot; mashing buttons while toggling fullscreen and switching tabs catches stuff no normal playtest does. In my own browser game the tab losing focus was the other sneaky path, so I ended up deriving pause from what is actually visible instead of a flag I set and clear by hand. Did you also check visibilitychange, or does the fight keep running when someone switches tabs?

A text-based mafia game is a nice fit for the browser, since most of the depth lives in systems like smuggling routes and heist roles rather than in rendering. Heists with assigned roles sound like the hardest part to balance, because one weak role can make the whole crew feel stuck waiting. On mobile, I’d be curious how you handle long lists of crimes and routes without endless scrolling. Did you design the onboarding around one first crime loop, or let new players pick from everything right away?

The rule that an edge tile only starts a route when its hand points away from its own side is a neat constraint, because it means the board border is doing as much design work as the tiles themselves. I also like that routes sharing tiles score extra, since that nudges players toward planning overlapping chains instead of just clearing the first line they spot. Using a bot player for balancing seems especially handy here, as it can quickly reveal whether certain hand directions end up far more valuable than others. When you tuned the spawn odds, did you weight the four directions evenly, or bias them based on where the bot kept getting stuck?

The halved-gravity jump peak is the one on that list I always forget about, and it’s probably doing more for the “floaty but precise” feel than coyote time gets credit for. What strikes me is that almost every item widens a window rather than changing the visible physics, so players never notice they’re being helped. Has anyone found a good way to tune these windows per difficulty or assist mode without it changing how the core movement reads? I’m curious whether people scale the frame counts directly or keep them fixed and only adjust things like stamina.

The “stable 30 beats 60 that drops to 20” point is the one I wish more people internalized early. Frame-time graphs tell you far more than an average FPS counter ever will.

Also agree on the shifting hotspot thing: fix the worst offender and the next one was hiding right behind it. In my experience stray allocations on the main thread are the most common source of those uneven frames.

Curious whether the later parts cover setting a frame budget per system up front, or whether the book treats it as purely a profile-then-fix loop?

Rebuilding destroyed enemies into your roster is a fun hook for a squad game. Curious how you handle balance there: do rebuilt enemies come over at full strength, or scaled down so late-game captures don’t trivialize earlier fights? Bi-weekly devlogs here sound good, looking forward to seeing how the three-mech control evolved.

Nice that it’s all worklet-side. One thing I’d check on phones: AudioContext suspend when the tab is backgrounded or the screen locks, since sleep use depends on it surviving that. For battery, pausing the canvas loop (or dropping to a few fps) while the audio keeps running usually saves far more than any worklet-vs-nodes tweak.

Nice to see the XR jam back for another round. Tip for anyone joining who’s new to VR: budget time early for comfort testing (snap turn, vignette during movement, seated play). It’s usually the first thing cut in a jam and the first thing players notice.

Cockpit view is a big jump for feel. One small thing that usually helps a lot: a touch of camera lag or head-bob tied to acceleration and braking, so the view isn’t rigidly locked to the car. Are you planning to let FOV widen a bit with speed too?

Nice topic for a series. Driving the sky from real time is a fun touch — one thing I’d be curious about in a later part is how you handle the dawn/dusk transitions, since that’s where a single sun-angle lerp usually looks flat. Do you plan to tie ambient light / fog color into the same time value too?

Fun effect. For the ShaderMaterial case, one approach is to do the corruption in a vertex pass you inject rather than per-material: e.g. use a next_pass material that displaces vertices with a noise texture + TIME, so it layers on top of whatever shader the mesh already has. Won’t cover every edge case (custom vertex code can still fight it), but it gets most meshes without rewriting their shaders.

The fixed daily slot is a smart way to concentrate a tiny player base. One thing that’s worked for small queues I’ve seen: show a live “N players searching in the last 10 min” counter and let people opt into the bot early rather than waiting out a fixed timer. Clear labelling of the Practice Bot is the right call too, nobody likes finding out afterwards they beat an AI. Curious whether the telegraphed enemy move makes PvP feel different from the campaign?

Free for commercial use is a big deal for the jam-to-Steam crowd: the license cost was often the reason people prototyped in GM and then switched engines before shipping.

The part I’d watch is migration. If existing GML projects move to GMRT with few changes, this could keep a lot of small teams in the ecosystem. If it needs a rewrite, people will compare it against Godot fresh anyway.

Classic overlap trap. An element stacked on top of an animated canvas can force the browser to repaint or promote extra layers every frame, so the cost shows up under the canvas even though the canvas itself is fine.

Your takeaway is the real one though: one change per analyzer run. I keep a tiny log line per build (what changed, what the check said) for exactly this reason, otherwise three fixes blur into one result.

Love that the whole pass is hand-built. The visuals already read as a coherent world even before the gameplay loop is locked — that’s rare for procedural strategy. Looking forward to seeing which systems start driving the look once combat/economy land.

For a prototype Logger, the thing that saves me most is cheap context tags (scene + system) on every line so you can grep one subsystem after you abandon half the experiment.

Second: a “debug only” channel that is a no-op in export builds — keeps the habit of logging freely without shipping noise.

Curious how you handle log volume when a prototype runs for weeks and the file grows — rotate, ring buffer, or just wipe between sessions?

Nice direction — traffic that reads differently by profile is what sells “navigate, don’t just floor it.”

A few profiles that usually create readable unpredictability without chaos: cautious gap-hunters who leave room then panic-brake; aggressive left-lane stickers who cut late; hesitant merge-waiters who stall the flow; and one occasional wrong-lane wanderer so players learn to scan, not memorize patterns.

Even tiny differences in reaction delay + preferred following distance go a long way before you need fancy pathfinding.

Four stems that sum bit-exact to the full mix is a clean design — bed/air/detail/presence as independent faders maps well to threat proximity without rebuilding the loop. Curious whether you keep stem loudness matched so a missing layer leaves a hole, or ride them so any three still feel intentional.