When the World Says No

It is going to refuse you. Here is how to read it when it does.

A refusal arrives marked >ooc, and that marking matters — it is the world stepping outside the fiction for one line to tell you this did not happen, rather than narrating a failure at you.

Why it refuses

Because the world has edges. Not the GM's mood, not a difficulty setting, not a dice roll gone bad. Something about the situation genuinely does not permit what you asked for. The door is locked and you have no key. The person does not know you well enough. The thing you want does not exist here and never did.

A world that grants everything is a world where nothing you achieve means anything, because achievement requires the possibility of not achieving.

What not to do

Do not argue in OOC. It will not work and it is not meant to. The refusal is not an opening bid.

This is the single hardest habit to unlearn if you have played other AI games, where pushing back reliably produces a yes. Here, pushing back produces the same no, phrased differently, and you have spent a turn.

What to do instead

Change the situation. Get the key. Earn the trust. Come back when the person is awake. Almost every refusal is conditional on something you can actually change.

Or change the file. If you genuinely believe the world is wrong — that your character would know this person, that this item should exist — edit the sheet, or take it to Orbit. The GM will honour a file change completely and without resentment. That was always the legitimate path, and using it is not cheating; it is the difference between the fiction and the record.

The offer

Sometimes a refusal comes with a hook attached — that does not exist here, but here is what does. Take those seriously. That is the world telling you where it is actually interesting, which is usually not where you were looking.