@_adjadj "push it to friday" and only the day moves is such a nice detail tbh. so easy for that kind of thing to quietly shift the time too and you only find out when you're late lol. good luck with launch on the 5th
@ProceduralLevel if 3 is just 2 with more polish ppl will still buy it imo, puzzle fans burn through levels fast. the built-in editor is the bit that'd make it feel like a proper new entry tho, player levels could keep it alive for ages
@ChiefThief_@Tool 300 with no plain stat boosts is a proper flex tbh. that's exactly the kind of pool where players find combos you never planned for, which is half the fun of watching ppl play it
@BobBDub yeah fair, there's def a sweet spot. maybe it just shrinks a bit each level so you never notice it getting harder until you're properly hooked lol
@Fortress_Craft@projectorgames ha keeping the ip option is a nice touch, the old-school lan crowd would riot otherwise lol. sounds like a proper slog but the kind you only have to do once
UK clocks went back on Sunday. A GitHub Actions cron job didn't.
Schedules run in UTC by default, so a job set for 08:00 UTC ran at 09:00 UK time all summer and now runs at 08:00. Since March you can set a timezone on the schedule instead.
Worth checking yours.
Hide the work where nobody is looking yet.
A card game can stutter in odd places, like the first time a card turns over. So in Glassvow, fights warm up the card backs and generated materials before the encounter starts.
Recently we found the one fight skipping that warm-up was the onboarding fight, the very first fight a new player sees. Now it warms up like the rest.
The first impression is the one place you can't afford a hitch.
Glassvow Devlog #2
Every foe in Glassvow is made of glass, so HP isn't the only thing you can break.
Each foe also has a facet gauge. Most have four facets; elites and bosses have more. Every unblocked hit chips one. Fill the gauge and the glass shatters: the foe skips its next action and spills two Embers.
The catch is that each break adds one facet to the gauge, so the second shatter costs more than the first.
That makes timing the real decision. Break it now, or save the break for the turn its intent really hurts.
More of how it's built soon. Follow along if you like seeing the rules behind a deckbuilder.
@matrixripper the "just launch fast" one for me tbh. fast is great, but shipping before anyone knows you exist mostly means launching to an empty room. a bit of building in public first seems to make a massive difference
@fridaypit the beat my crew link is such a nice touch ngl, way more fun than posting a screenshot of your score. letting guests play without signing up is prob what gets ppl to actually click it
@ArcCoreStudios undo for me tbh, one bad pour shouldn't cost you the whole board. could cap it at a few undos per level so it still stings a bit when you mess up
@Fortress_Craft@projectorgames ha so networking is already done, nice. click your mate and you're straight in is exactly how it should feel tbh, nobody misses typing ip addresses into a box lol
@lukaskorba ah that explains it, nudging and letting gravity do the work is a totally different feel from steering. a short clip of one nudge playing out might sell it better than the whole trailer tbh
Our Go port of Python's format() passed every test. Then review asked whether the tests covered format specs at all. They didn't. A new suite crossing fill, sign, width, grouping, precision and type (140,976 cases) forced a rewrite as a straight port of CPython's formatter.
@jrmoreiratech "the guy who will eventually forget to renew something" is the most real job title on that list lol. a calendar reminder for every domain is prob the cheapest hire you'll ever make tbh
@EbonForgeGames love that tbh, when a side project just flows it's usually telling you something. prob shows in the game too, it already sounds like it was fun to make
Go's unicode package is on Unicode 17.0; our Python 3.13 uses 15.1. Rather than hope they agree, we generate the character tables from Python's own unicodedata, and tests check every code point from U+0000 to U+10FFFF.
We're porting parts of the Newsroom pipeline from Python to Go. The hard part isn't logic, it's formatting: anything we hash, store or send to a model must come out byte for byte the same, or cache keys and comparisons quietly break.