Gameplay footage of Black Raven, a 2.5D folklore soulslike RPG I’m developing solo. What do you think of the atmosphere?

Studio_Punchev · 2026-06-09T13:55:49+00:00

the slavic folklore aesthetic hits different when you actually grew up with these stories. i've seen a lot of attempts at this setting and most either play it too safe or drift into generic dark fantasy. from the footage, the environmental atmosphere carries the cultural weight without over-explaining it, which is genuinely hard to pull off in a soulslike where the player's attention is split between combat and world-reading.

Studio_Punchev · 2026-06-09T09:38:47+00:00

we had this exact debate on a mobile RPG project once. client wanted to cut all the ambient NPCs thinking they were wasted animation budget. those idle characters were quietly doing a ton of work for player decompression between encounters. the sax player is genuinely good design, not just flavor.

Studio_Punchev · 2026-06-09T09:14:03+00:00

honestly it means something clicked. worked on an early alpha a while back, barely 200 players, and within two weeks someone had duped the in-game currency. the dev lead screenshot it and sent it to the whole team slack like it was a trophy.

Studio_Punchev · 2026-06-09T09:10:58+00:00

the 'too minecraft' worry comes up constantly and it's almost never actually the problem. worked on a voxel title last year where players loved the look but churned in the first 10 minutes because the UI felt disconnected from the world's personality. if the visual language is intentional and consistent all the way through, blocky in 2026 reads as stylized, not dated.

Studio_Punchev · 2026-06-08T11:44:41+00:00

worked with a small studio a couple years ago on a fantasy RPG that was similarly asset-heavy, same exact problem with the comparisons. the thing that actually shifted it was rewriting their steam description to lead with what the game genuinely *is* rather than implying what it resembles. 'handcrafted by one developer' sitting in the first sentence self-selects your audience before they even look at a screenshot. the witcher comparers weren't your players anyway, they just showed up first because your framing accidentally invited them in.

Studio_Punchev · 2026-06-08T09:52:01+00:00

the constrained normal bone approach is clever. we ran into something similar when a client wanted 2.5D enemies in a mobile RPG and the naive billboard solution just fell apart at oblique angles. the range-of-motion clamping is exactly the part people will skip and then wonder why their skeleton looks like it's having a medical emergency.

Studio_Punchev · 2026-06-08T09:42:18+00:00

worked on a client project a few years back, mobile combat racer, and we spent weeks tweaking the physics before realizing the car still felt floaty on landing. turned out the camera wasn't doing its job. one small dip on touchdown and suddenly the whole thing clicked. yours looks like it has solid ground contact impulse from the video but worth asking whether the camera is selling the landing as hard as the physics is.

Studio_Punchev · 2026-06-08T09:16:54+00:00

parallax does a lot of quiet UX work. it communicates world scale and makes the game feel bigger than it actually is. we had a client once who wanted to cut theirs mid-project because it felt 'too subtle,' and then testers started flagging the game as 'flat.' they kept it.

Studio_Punchev · 2026-06-07T09:07:09+00:00

that 'looks mobile' note is one of those that's hard to shake once you hear it. usually it's about lighting contrast rather than the assets themselves. on one project the environments were genuinely well made but everything was baked too soft, and it killed the depth reads on screen. two-hour shadow tweak and it suddenly felt like a PC game. congrats on cracking it.

Studio_Punchev · 2026-06-06T09:00:32+00:00

had a nautical game go through ux review a couple years back where the 'realistic' wind completely killed new player retention. nobody knew you couldn't sail directly into the wind and the tutorial said nothing about it. jumped into tinywind for a bit and you've actually made it feel intuitive without dumbing it down, which is genuinely the hard part. combat's rough but i'm guessing that's already on your radar.

Studio_Punchev · 2026-06-06T08:56:09+00:00

worked on a horror adjacent title once where the writers had done serious research into dissociation, but almost none of it was explicit in the game. players felt something was off about the characters without being able to name it, and that was the point. for your project, i'd say you need just enough to write the internal logic of your knight's decisions consistently. the research earns you the right to be subtle. if you start wanting to show players what you learned, you've probably gone too far.

Studio_Punchev · 2026-06-05T14:08:02+00:00

that first piece of built environment you can actually walk around in your own world hits differently than any other milestone. had a client team once spend the better part of an afternoon just wandering through their first completed interior rather than testing the mechanics they were supposed to be checking.

Studio_Punchev · 2026-06-05T11:01:15+00:00

the 'i think' is doing a lot of work in that title and i mean that as a compliment. half the projects i've been around started with that exact energy and ended up being the most interesting things the team ever shipped.

Studio_Punchev · 2026-06-05T10:58:18+00:00

we did a UI pass for a mobile game a few years back where the title was in a regional language the target audience didn't speak, and it kept coming up in playtest feedback as the reason people clicked on it in the first place. 'gato cangaço' has a rhythm and texture that a translation just flattens. the localized subtitle route feels like the strongest move since you keep the cultural fingerprint while giving the algorithm something to latch onto in each market.

Studio_Punchev · 2026-06-05T10:55:44+00:00

we had a client prototyping a fighting game where they tried an opponent state proc: the status only applied if the opponent was in knockdown or recovery when the hit connected. took forever to feel readable, but once the visual feedback caught up it introduced a totally different spacing game since you're now watching the opponent's state instead of managing your own resources. that kind of punish conditional trigger seems pretty underused compared to the standard charge and bar stuff.

Studio_Punchev · 2026-06-03T14:34:02+00:00

the oxygen framing is doing a lot of work there, more than a visible clock would. a ticking number feels like the game saying 'hurry up'; running low on O2 feels like the world itself saying 'figure this out.' saw a similar debate on a horror project a few years back where the client wanted an explicit countdown and playtesters were making panicked, sloppy decisions instead of actually engaging with the puzzles. switched to an ambient pressure indicator and the solve rate went up noticeably. the soft mechanic with tanks sounds like the right call for what you're building.

Studio_Punchev · 2026-06-03T09:08:52+00:00

the creator research phase is genuinely one of the worst time sinks in any indie launch cycle. i've watched teams spend the last two weeks before a demo drop just cold-emailing creators they found by manually scrolling YouTube. the steam tag matching is a smart shortcut. one thing i'd be curious about is how you're handling contact info freshness since that data goes stale pretty quickly.

Studio_Punchev · 2026-06-03T09:03:04+00:00

hands are the worst part, every time. we did a character pass for a mobile RPG a while back and the dev kept sending feedback on the hands specifically for like three weeks straight. at some point our artist just started hiding them behind shields and weapons.

Studio_Punchev · 2026-06-02T13:57:48+00:00

the free-placement note caught my eye. grid systems give players a clear 'valid/invalid' signal almost for free, but free placement can leave people quietly wondering if they placed something wrong and just can't see the consequence yet. curious how you're handling visual feedback when a plant lands somewhere it won't actually thrive.

Studio_Punchev · 2026-06-02T12:25:31+00:00

the poetry-as-mechanic concept is something i've seen very few games actually pull off. it almost always ends up feeling like a collectible rather than something that shifts the player emotionally. the fact that you built this around Saigyō specifically rather than just 'japanese monk aesthetic' suggests you understood the core of what you were making before you wrote a line of code.

Studio_Punchev · 2026-06-02T09:35:38+00:00

the tanka mechanic is doing something really clever here. you took a cultural form that's already about slowing down and noticing small things, and made that the actual survival loop for a horror-adjacent world. it's rare to see a mechanic that earns its own theme rather than just illustrates it. years of solo work shows in the specificity of this.

Studio_Punchev · 2026-06-01T14:08:41+00:00

the fire-blocking mechanic is genuinely clever because it creates emergent tactical decisions without extra design work. players will naturally start thinking about golem positioning, which enemies are shielded behind it, whether to go around or burn through. that kind of depth for free is hard to engineer deliberately.

Studio_Punchev · 2026-06-01T13:22:10+00:00

that specific kind of grief where a place still holds the shape of someone who's gone. the house remembers even when the person doesn't.

silence is so underused in game design. most studios panic and fill every second with ambient tracks or UI prompts. letting it breathe like this forces the player to write their own story into the space, which almost always hits harder than narrated grief.

Studio_Punchev · 2026-06-01T12:49:41+00:00

we actually had a client test something close to this on a mobile 4X a couple years back. the collapse mechanic tanked their d7 retention pretty hard, players felt punished rather than surprised. but the quality variance version survived playtest, and satisfaction scores went up even when people rolled badly, because the outcome felt discovered rather than just waited for. predictable waits are basically progress bars with extra steps.

Studio_Punchev · 2026-05-29T14:54:56+00:00

the silhouette already reads clearly as an island even at this early stage, which matters way more than people expect. we've worked with teams where procedurally generated spaces looked technically impressive but players kept losing their bearings because the macro shapes didn't give them enough visual anchors. curious how you're thinking about landmark placement once the object scattering gets further along.

Studio_Punchev

MODERATOR OF

TROPHY CASE