Most RPGs tell you exactly what to do. Talk to this person. Go to this marker. Collect five things. Return for a reward.
That structure works. It is clear, readable, and familiar. But it also changes the way players think. The world becomes a checklist, and NPCs become delivery mechanisms for objectives.
Lowborn Rising is built around a different question:
What if progress came from what your character knows, not what the UI tells you?
Knowledge as Progress
In Lowborn Rising, NPCs do not exist to hand you quests. They have problems, opinions, fears, loyalties, rumors, and blind spots.
Talking to people can reveal topics. Those topics can then become things you bring up in later conversations. A farmer might mention the lord’s taxes. A priest might talk about charity. A merchant might complain about bandits on the north road.
None of that has to become a quest entry. It becomes part of what you know.
No Checklist Safety Net
This is risky by design. If a game removes the quest log, it has to earn that decision. Players should not feel abandoned or tricked.
The goal is not to make the player wander aimlessly. The goal is to make them pay attention.
If someone tells you the miller has been shorting grain, the game should not need to add “Speak to the miller” to a journal. You should already understand that the miller might matter.
Conversation, Not Errand Design
I want conversations to feel closer to investigation than quest pickup. The player is not collecting tasks. They are building a mental map of the world: who has power, who is desperate, who is lying, who is afraid, and who might be useful.
That also means missed opportunities are part of the design. If you never hear the rumor, you may never discover the path. If you insult someone, they may stop helping you. If you gain someone’s trust, a door may open that other players never see.
The Hard Part
The danger is obvious: this could become frustrating.
If every NPC can respond to every topic, the system becomes bloated. If every topic feels equally important, players will click everything out of fear. If critical information only comes from one person, missing that conversation could break the experience.
So the design has to stay disciplined. Topics need context. Important knowledge needs redundancy. NPCs should only care about what makes sense for who they are.
What I’m Building Toward
Lowborn Rising is still early, but the direction is clear:
- No traditional quest log.
- No floating markers.
- No objective checklist.
- Progress through knowledge, reputation, and consequence.
I do not want players to ask, “What does the game want me to do?”
I want them to ask:
Who do I know? What have I learned? Who can I use it on?
That is the heart of Lowborn Rising.