I wanted the HUD to stop feeling tiny on larger monitors.

So I added a global UI Scale setting in Settings (85% to 150%, with a one-click reset to 100%). It applies to the full HUD, not just one panel, and it updates live.

I also added automatic scale buckets by viewport height. Bigger displays now get a sensible default boost before any manual tweaking. Final scale is auto * user, so you get a better out-of-the-box layout and still keep control.

This setting is saved as a global device preference and shared across save slots. That means you can swap runs without redoing accessibility setup every time.

I also refreshed the core resource icons (population, bodies, souls, karma, vessels, RP) so the top bar reads cleaner at a glance. Small change, but it makes scanning the economy less noisy.

Player impact: less eye strain, faster reading, and fewer “wait, what number is that” moments.

Next up: keep tightening readability and pacing together, because a clean UI only matters if the economy pacing still feels good.

I did a focused polish pass on clarity this week.

The game now explains itself faster while keeping the tone weird in a good way.

## What changed

I replaced the old fading hint toast with a bottom-center contextual panel that waits for confirmation.

It now supports three channels: Unlock, Gameplay, and Story. You can toggle each channel in settings, and unlock/story messages are tracked once per save so they do not spam every run.

I also added the first story snippets with The Death voice. They trigger from real progression points (first shed, first extractor, first karma engine), so onboarding feels more intentional.

On progression balance, I reworked several achievement targets and rewards:
– Some early goals were too trivial compared to the actual pacing.
– Soul Collector and Karma Farmer now give permanent modifiers.
– Population achievements were moved to meaningful milestones (150k / 500k), so they feel earned.

On upgrades, I adjusted Death Worker branch sequencing and improved descriptions/tooltips. Upgrade and building rows now expose clearer flavor + effect context, so buying decisions are less blind.

## Player impact

You should feel less “what just happened?”

Unlock guidance is clearer, progression rewards are less noisy, and upgrade choices carry more readable intent.

I spent this pass making the game easier to read in the moments where people usually bounce.

Big changes landed in three areas: onboarding hints, upgrade clarity, and achievement pacing.

## What Changed

I added a contextual hint panel with unlock-based narrative snippets.

Now the game can surface short, relevant nudges when you hit specific states instead of dumping static help. It should feel more like a control room briefing and less like a wall of text.

I also cleaned up upgrade descriptions and sequencing, especially around Death Worker progression.

The goal was simple: when you compare upgrades, you should understand what each one does without mentally decoding it.

On top of that, I rebalanced several achievements so progression feedback lands earlier and feels fairer during normal play.

## Why It Matters For Players

Early and mid-game decisions should now be less guessy.

You get better guidance when systems unlock, better readability when spending resources, and less awkward dead-air while waiting for milestone feedback.

In short: less “what am I supposed to do now?” and more “okay, I see the next move.”

## What I Want To Tune Next

I still want to tighten the pacing between the first hint chain and the first big upgrade spikes.

If those beats feel too slow or too noisy, I will trim text and push more signal into visuals.

Quick version: we didn’t do magic SEO hacks. I cleaned up the fundamentals and made the site actually useful for people and search engines.

For both projects Bloodlore and Ghost Trappers, the big shift was this: homepage = not just a pretty trailer wall. I turned it into a proper landing page that explains the game fast, answers obvious questions, and uses clean structure under the hood.

What we changed

I made the homepage content actually say what the game is, who it’s for, and why someone should care. Not in a giant text dump, just clear sections with real headings.

Implementation-wise, we focused on things like:

• one clear H1 (not five fake hero titles)
• clean H2/H3 sections for gameplay loop, features, and platform info
• better meta titles/descriptions (human-readable, not keyword spam)
• meaningful internal links (not “click here” everywhere)

Then we added FAQ blocks based on real user questions: what is this game, where can I play, how do I start, what’s planned next. That helps users, and it helps search engines understand intent. We also wired in structured data (FAQPage) so crawlers can parse it properly.

The technical cleanup (super important)

A lot of SEO gains came from boring but high-impact technical fixes:

• semantic HTML (header, main, section, nav, footer)
• canonical tags to avoid duplicate-page confusion
• up-to-date sitemap.xml
• clean robots.txt
• Open Graph/Twitter tags for better link previews
• performance tweaks (compressed media, lazy loading, layout stability)

For game sites, performance matters a lot because pages are media-heavy. If it loads slow, rankings and UX both take a hit.

Keyword strategy without the cringe

We didn’t do keyword stuffing. We grouped terms by topic and intent:

• core terms (game type, core mechanic, audience)
• support terms (features, progression, modes, platforms)
• intent terms (how to start, requirements, updates)

So the content stays natural, but it can rank for more than one exact phrase.

How we treated SEO overall

We treated SEO like a product loop, not a one-time checklist: ship improvements, track impressions/CTR/ranking spread/organic entries, then iterate. Simple cycle, but it works.

Why this is reusable for any game

None of this is tied to one specific title. It’s a framework you can apply to basically any game site:

• explain the game clearly
• structure content with proper HTML + headings
• add real FAQs
• set technical SEO basics correctly
• keep improving based on data

No gimmicks. Just clean execution that stacks over time.