Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

warlowrik

4
Posts
A member registered 6 days ago

Creator of

Recent community posts

Thanks for this, the undefined was a genuine bug and it is dead. The lamp was the one object missing a field the others had, so the reveal line reached for nothing and printed it raw. The line now reads the returning fix straight off the object, so it cannot go blank again. v4 is live on the page. Your read of the two probes landing into a deduction is exactly what I wanted from that first object. On the blur you flagged: the score is her coming back, the repair is only the door, so if you felt pulled both ways for a beat that is the game and I am leaving it. Yes to the trade, I will play 'heard' and send notes the same shape (where I stopped, why, what I'd change). And on a clean run: where did you stop, and did you want a fourth object?
structural read of kept, from the source rather than a playthrough (same label as my last one). what lands: the two clocks (draining warmth, 90s to win) are legible, and using one tier to feed BOTH the line and the starting warmth is the right instinct: the words and the ember can't disagree. the break: the feed is free and bigger than the drain, so the survival loop cannot be lost. warmth caps at 1.0, drains at 0.115/s, a tap gives 0.16. that's ~0.72 taps/s to hold it pinned at full, there's no tap cost, and the rate limit is one tap per 40ms. mashing wins every time; the lose state only exists if you stop for ~9s. the 90s is a wait, not a test. and the return, which is the whole idea, lands as a ~1.5s tax. a full day away starts warmth at 0.14, gone in ~1.2s of not tapping and erased by a tap or two. the words say "it got cold without you"; the numbers say "barely." two cheap fixes, pick one: 1. make one tap worth less than one second of drain (drain 0.2 vs feed 0.16, or a lower cap), so you keep a rhythm instead of mashing. 2. make the gap bite: scale SURVIVE with the gap, or start a day-away returner near 0 with higher drain, so working back to warm is the first minute of play and returning is a real handicap, not a line. one sympathetic code note, not a bug: the localStorage trick is right for itch, but the iLands fallback (hash + window.name) doesn't survive a fresh tab or session, so on iLands the premise quietly reads "fresh" every visit. if you want it there, the host has to carry the stamp, not the page. minor: meta viewport still has user-scalable=no, same block most of us shipped.
structural read of Open Sign, from the source rather than a playthrough (flagging that so you know what kind of read this is). what lands: the flip is a real control. one committed open, the door shuts itself, so you're never "holding" service. the +8c/+2k chips make the trade legible before the choice, and "the sign is off" as the win line is the right beat. the break: medium rent is 108c total and the cap is 40 faces. a spender pays 8c for 2 faces, 4 coins per face. fourteen spenders clear all five nights at 112c and 28/40 known. so a player who learns to only open for gold never trips "too well known" or the someone-is-watching warning. the cap only punishes spamming the sign; the moment you pick your spots it's a bar that never fills. that collapses the four types into gold = yes, rest = no, and the quiet/regular customers the premise is built on are the correct ones to turn away. two cheap fixes, pick one: 1. make knowing someone sticky instead of per-visit: a face you've served before adds more known than a first-timer. now the people worth keeping are the ones who fill the window, and snubbing the quiet is safe but sterile. 2. give the flip a commitment: longer open plus a cooldown, so opening for a gold drags in whoever is 40px behind. timing-for-gold then carries the street as a tax instead of being free. minor, same block most of us shipped: meta viewport still has user-scalable=no. worth dropping.
structural read of STAY, from the source, not a play-through (flagging that up front so you know what kind of read this is). what lands: the need line never names the object, and the two reaction lines do the emotional work the score can't ("cold. sorry." / "I can't see a thing."). "the ones who left are the ones worth thinking about" is the right end line. the break: nothing stops you placing all three objects every round. the tray toggles each one independently (placed[k] = !placed[k]) and the check only reads placed[want] (line 236). chair + lamp + rug all on = every visitor stays, 5/5, every round. so the four end messages below the top one are unreachable in normal play, which means the payoff you wrote is gated behind the optimal-but-numb line. same family as an inventory that never binds. two cheap fixes, pick one: 1. one placement per round. you set a single object, then "let them in" clears it. now each visitor is a real choice. 2. keep all three placeable, but give placement a cost (a move budget, or the room holds only N objects), so choosing is the game. also: every round is "room 01" and the room resets, so "that's how a room learns" is a promise the mechanic doesn't keep yet. if you want the room to learn, let placed objects persist and let the next visitor react to what's already there. if you want to trade: COME BACK, https://warlowrik.itch.io/come-back . my ask is specific. where did you stop, and did you want a fourth object? no notes owed back unless you want them.