A character sheet knows how strong they are now. The world must know when they became that strong.

Once a character reaches fifth level, the character sheet tells you they are fifth level.

Their hit points have increased.

They have gained new abilities.

Their spells, resources, or proficiencies may have changed.

If they multiclassed, changed class, or gained a new identity through the story, the class field on the sheet has changed too.

That is all reasonable.

A character sheet is supposed to show the character’s current state.

The problem appears when the DM looks back at a record from three sessions earlier.

At that point, the character was not yet fifth level.

They did not have the abilities they gained later.

They may not have taken on another class.

They may not even have experienced the event that changed their identity, faith, species, or lineage.

But a character sheet does not return to an earlier version when the DM reads an old session record.

It continues to show the latest answer.

A character sheet remembers who the character is now.

A long-running campaign also needs to remember when they stopped being the person they were before.

Leveling up adds new conditions to the future

It is easy to think of leveling up as adding points.

The level increases.

Hit points go up.

Abilities become stronger.

The character gains new spells, feats, or class resources.

From the perspective of world state, however, leveling up does more than increase numbers on a sheet.

It changes what the character can do afterward.

Options that were previously unavailable may now become possible.

An enemy that was once too dangerous may now have a weakness the character can exploit.

An ability that once required someone else’s help may now belong to the character.

Certain organizations, quests, locations, or rituals may also begin to treat them differently.

The people inside the world do not need to describe this as “the character leveled up.”

They may have no concept of levels at all.

But the world still has to acknowledge that the conditions governing the character’s actions have changed.

More importantly, the change happened at a particular time.

A character cannot use an ability gained at fifth level to solve a problem that happened when they were second level.

The DM should not accidentally carry later qualifications back into an earlier session.

Leveling up is not only receiving larger numbers.

It is the moment from which the future begins allowing the character to do more.

Changing class changes how the world recognizes the character

A class is more than a name on a character sheet.

Fighter, wizard, rogue, cleric, or any custom class or identity does more than describe a character’s style.

It may determine how they were trained, which abilities they can use, which resources they depend on, and which restrictions they have to accept.

When a character multiclasses or changes class, more than a title changes.

They may gain a new qualification.

Gain access to another system of abilities.

Receive recognition from a new organization.

They may also lose the trust, duties, or position attached to their previous identity.

Some changes are not entirely voluntary.

A curse may change a character’s species.

A crisis of faith may take away their former identity.

Joining an organization may grant them a new role.

Death, resurrection, a contract, or a ritual may turn them into something the world has to recognize differently.

These are not simple edits to a character biography.

They are events that happen during the campaign.

Before that moment, the world recognizes the character in one way.

Afterward, a different set of abilities, qualifications, and restrictions begins to apply.

The real change is not a new line on the character sheet.

It is the point from which the world begins to recognize that character differently.

Shared attributes and class-specific attributes are not the same

Character values in a TTRPG do not all come from the same place.

Some attributes may apply to every character.

Health, stress, sanity, exhaustion, corruption, reputation, or any other value created for a custom ruleset may continue across classes.

Other attributes make sense only for a particular identity.

A class may have its own source of power.

A species may suffer from a particular hunger.

A religious order may use faith or favor.

A type of spellcaster may accumulate magical backlash.

An organization may use loyalty, rank, or merit to determine what its members can do.

If every value is placed in one undifferentiated list, a character sheet quickly fills with fields that have nothing to do with that character.

But if every attribute is attached only to the character’s latest class, changing identity may erase states that were accumulated earlier.

A character system therefore needs to distinguish between two questions:

Which attributes belong to the character?

Which attributes exist only because of a particular species, class, or identity?

This distinction is not about making character sheets more complicated.

Different values answer different questions about the world.

Shared attributes describe what the character is carrying or enduring.

Identity-specific attributes describe what they must carry or endure as the person they are now.

Not every number has to be visible to the players

TTRPG values usually appear on a character sheet.

Players need to know their hit points, resources, and abilities before they can make meaningful choices.

But not every state has to be completely visible.

The DM may want to track corruption the character has not noticed yet.

A curse that is slowly accumulating.

A faction’s hidden trust in the character.

The cost left behind by a ritual.

Pressure being applied to the character by a rule of the world.

These values can remain in the DM’s notes.

The players do not always need to see them immediately.

Even a campaign record written as prose does not need to expose every numerical change as interface data.

The reader may need to see only the result.

The character begins to tire.

An injury slows their movement.

After losing faith, they can no longer make the same choice.

Once corruption reaches a certain point, the world begins responding to them differently.

The purpose of a value is not to force the story to display every calculation.

It is to let the creator know that the character’s reaction did not appear from nowhere.

A number can remain behind the screen.

The limits and costs it creates should remain in the world.

Bounded values and accumulating values behave differently

Different attributes need different boundaries.

Hit points may have a minimum and maximum.

Sanity, stress, or another resource may also remain within a fixed range.

Reputation, debt, corruption, merit, or another custom value may not need the same limit.

It may continue increasing.

It may also fall below zero.

These differences affect how the DM understands a character’s state.

A bounded value usually places a character somewhere within a clearly defined range.

An unbounded value behaves more like a trace that can accumulate throughout the history of the campaign.

Some attributes are particularly important.

When one of them reaches zero, the change may mean more than the number becoming zero.

It may mean death, incapacitation, or another vital state that has to be resolved separately.

At that point, the change cannot remain only on the character sheet.

After a character dies, their location, items, relationships, faction membership, and unfinished consequences may all need to be accounted for.

A value may look like a single field attached to a character.

Once it touches the rules of the world, it can become the beginning of an entire chain of causality.

The mistake usually appears when you return to the past

A level-up or class change is usually easy to remember when it happens.

The party has just completed an adventure.

The player is choosing new abilities.

The DM knows what changed.

The real mistakes appear much later, when someone returns to an earlier part of the campaign.

The DM may want to confirm which abilities the character had during a particular encounter.

Turn early sessions into a written campaign record.

Rewrite part of the story.

Or check whether an old event truly supports what is happening now.

If the only available character sheet has been overwritten repeatedly, it shows only the latest version of the character.

A class gained later may appear too early.

Attributes increased later may contaminate the past.

Values that have been spent, restored, or recalculated may make it impossible to tell what was true at the time.

The DM has to search through session notes and reconstruct the character’s earlier state.

The longer the campaign runs, the harder that becomes.

Character progression is not made of only a few major milestones.

It is a history built from many small changes.

How strong the character is now is only one answer.

A long campaign also needs to preserve how that answer came to exist.

InkWeave places character progression back on the story timeline

InkWeave does not apply D&D leveling rules automatically.

It does not choose a class for the player or decide whether a character qualifies for multiclassing.

It does not decide how the DM should develop the character.

The creator first defines the identities and attributes needed by the project.

They can create species and classes or combine them into the identities the story actually requires.

Attributes can be shared by every character or restricted to a particular identity.

They can have minimum and maximum values or remain without fixed boundaries.

When needed, a bounded attribute can also be marked as vital, allowing its reaching zero to become a condition that affects life and death.

The important part is that this information does not have to preserve only the latest value.

When a character changes identity in the text, that change can become an event on the timeline.

When an attribute increases or decreases, the change can remain at the position where it happened.

If the cursor is placed before the identity change, the world still sees the earlier character.

After the change, the world recognizes the new identity and its relevant attributes.

This is different from overwriting a character sheet.

The character sheet tells you who the character is now.

The story timeline preserves how they became that person.

Character progression should not overwrite the character’s past

D&D characters grow.

That is one of the reasons long-running campaigns are so compelling.

A character who was once afraid to open a door may later become someone capable of deciding an entire battle.

Someone who once belonged to a single class may follow another path through choice, training, betrayal, or a bargain.

A state that began as one number on a character sheet may eventually become the cause of death, transformation, or redemption.

These changes should do more than make the character sheet look stronger.

They should leave time behind in the world.

The time when the character gained an ability.

Lost a qualification.

Began carrying a new restriction.

Stopped being recognized as the person they were before.

The character sheet preserves the latest answer.

Causality preserves how that answer came to exist.

Leveling up is more than adding points.

Changing class is more than replacing a name.

Attributes are more than numbers beside a character description.

They are changes that happened to the character inside the world.

A living long-running campaign remembers more than who the character eventually became.

It remembers the moment they first stepped onto the path that made returning to their old self impossible.