Home Creators Posts Import Register Favorites Logout

Content

Hi adventurers,

This is a post going over the design for the upcoming status effect system I've been talking about for months. I've gone back to the drawing board a few times with this, but I think I finally have something feasible I'd like to share before I start implementing this system into the game to add some dynamic variety throughout it.

Tailraise is a narrative game, which means I want this to affect both gameplay and writing where appropriate.

The goal is to make the player feel like their current state matters without forcing me to write every scene in the game to manually check hundreds of possible variables.

I'm working on the next content update alongside this. There will be new stuff coming this weekend most likely and several scenes added to characters!

Also, we might have our first sneak peek of the new Thimble art soon! 👀

This is a LONG post with a lot of technical detail on the upcoming system! I don't have an ETA on when it'll be implemented fully and ready, but the work has begun on this already.

If you're curious about how I'll be implementing various status effects, displaying that in game, and how it ties in with imprint drift, keep reading below!

Because this post is going to contain some SPICY details, the rest is paywalled to supporters! Sorry, free members, but I can't include those details out in the open due to Patreon policy!

Shared Categories

Instead of every status being an isolated thing, the game will instead track a few shared player values and body conditions as categories.

This might be:

  • Appearance conditions

  • Scent-related conditions

  • Temporary modifiers

A scene (whether it's on a game tile or via an NPC) can then have a check for specific conditions to see if they exist, and change lines appropriately where it makes sense.

Walked into the Adventurer's Guild while covered in cum? Stone might comment on that, or people might give you some looks.

Player Values

Some conditions don't need a category and can simply be represented by a single number to track. An example would be...

Arousal

Arousal would be 0-100 probably.

It can rise during certain scenes that don't let the player cum. It could decay over time when you're doing stuff that's not horny. Being horny or not being horny could also then influence if you have access to specific choices. It could also influence flavour text.

For example, depending on your arousal level, you might see:

Low (0 to 33): "As you walk into the tavern, you glance around, not looking for anyone in particular."

Medium (34 to 66): "As you walk into the tavern, you glance around, a few attractive patrons catching your eye."

High (67 to 100): "You bump into someone as you walk into the tavern, your mind wandering. You apologize, your pants tight, feeling yourself throbbing underneath your clothing."

Not every scene needs a special arousal branch, but it becomes a shared value that scenes and choices can use to influence the writing.

Fatigue

This would be a 0-100 value, for example.

It could make encounters more difficult and impact your rolls. It could make choices available to you more limited. Resting would clear this.

These ones would change on their own over time, but also have modifiers to either increase/decrease them, cap them to specific values (or prevent going higher/lower than specific ones), and so on.

Body Conditions

For these, I'm leaning towards a single BodyCondition structure rather than separate systems for everything.

A body condition might be:

  • Wet fur/skin

  • Muddy paws/feet

  • Freshly-showered

  • A scent clinging to your fur/skin

Each condition would be an object with various data/fields, such as:

  • ConditionID (coated_in_sap, covered_in_cum, etc.)

  • ConditionType (appearance, scent, modifier, special)

  • DescriptorID (shared categories like sticky, wet, sweaty, musky, etc.)

  • Source (Optional, things like Flint, Thimble, Taw, etc.)

  • BodyRegion (all, paws, head, footpaws, etc)

  • Intensity (how much it stacks and priority)

  • Duration (how long it lasts, if not indefinitely until cleared)

  • ClearCondition (time passed, specific action like showering, etc.)

This means I can ask for specific conditions in various parts of the game when I spend time thoroughly crafting scenes where I want them to be more dynamic.

For example, I could use:

has_body_condition_type("appearance")

To pull any active appearance conditions if it doesn't matter which and we just trigger if any are active.

has_body_condition("coated_in_sap")

If I'm looking to see if the player is currently coated in sap somewhere.

has_body_condition_source("flint")

So when you approach Flint again, he can still smell himself on you from a previous encounter with him.

has_body_condition_region("face")

So if your face is covered in cum or something else, NPCs might react to your unkempt appearance.

Dynamic Descriptors

One thing I want from this is a way to generate useful descriptions too, not always look for specific things I need to write or account for, especially as things grow, more conditions get added into the system, and so on.

I don't want to have to check every scene like:

Is the player sticky from cum?

Is the player wet?

Are they covered in sweat?

Are they freshly showered?

The game should be able to derive general appearance descriptions instead based on which descriptorID and intensity is the highest currently. If two are the same intensity, we use the most recent one.

Then the game can derive the appearance to see something like the player is currently:

  • wet (1 stack)

  • cum_marked (3 stacks)

  • musky (1 stack)

  • sweaty (3 stacks)

and determine that they are sticky primarily.

Then, when writing, I'd simply do (excuse the lack of code formatting):

~ temp appearance = get_primary_appearance_description()

{ appearance = "muddy":

Stone looks you over, pausing at the mud clinging to your fur. "You're making a mess of my lobby. Were you raised in a barn?"

}

{ appearance = "cum_marked"

Stone looks you over, pausing at the cum clinging to your fur. "While I'm not asking my recruits take a vow of chastity, I expect them to at least shower afterwards and clean up. Shameful."

}

This allows for some flexible writings, once I figure out which categories each thing should go into.

Flavour Text

Another thing this allows for is flavour text as you explore the game, dynamically inserted into each tile, based on your conditions, using a few shared fields between the Conditions above and the FlavourTextPool.

These would have lines that can be shown based on whether you are in private or in a public area around others. These can also have overrides based on where the source came from for that condition. It also can have multiple lines for each category, mixing it up to add variety.

So then I can do something like:

~ temp line = get_condition_flavour("tile", "public")

{ line != "":

{line}

}

This would then run in order:

  1. Find an active condition (system sees player has scent_marked)

  2. Then it loads that object and looks at the source and context. So in this case, it might see the source is Flint, and the area is public.

  3. So the system will try to find Flint-specific public lines that scent_marked has defined in it.

  4. If none exist, it'll instead try a generic public line if they exist.

  5. If those still don't exist, try generic lines if they exist (public or private).

  6. If these STILL DON'T EXIST, we return "" and it won't show anything at all, as a fallback.

So if Flint-specific scent_marked lines exist for public, you might see:

You can still smell Flint's scent lingering in your fur, distracting you as you wander through the crowd.

If only generic lines exist, it might instead do:

You can still smell the lingering scent saturated in your fur, distracting you as you wander through the crowd.

The reason I have it this way is because sometimes you might be in your private room, for example, and we don't want something here about how "Everyone stares at you because your fur is sticky with cum." when there's no one around. That wouldn't make sense!

Of course, this system won't be used everywhere, to avoid repetition, which leads to...

Anti-Repetition Logic

The system is planned to have guardrails to prevent you from seeing the same flavour text over and over and becoming annoying.

There will be a cooldown in place when these checks run to try not to show the same exact line over and over, and if we have the flavour text pulled already from one movement ago, we're not going to show another immediately.

These will inject periodically into the existing tiles and locations where appropriate, while other places might have hand-crafted reactions based on a few conditions to add some extra dynamic variety.

Imprint Drift

"Okay, this is cool, Taw, but what about imprint drift? Where's my fox TF!?"

Imprint Drift is going to be an adjacent system that utilizes conditions and status effects, which will be a progression system.

This is because it will need several things tracked and assigned, more than the conditions should have, so having it adjacent but utilizing this system I think works best.

It will have stuff like:

  • targetSpecies (what you're turning into)

  • progressLevel (how far it's progressed total)

  • stage (how far advanced is it)

  • lastTriggeredStage

  • stabilized (true or false, basically stopping it from progressing)

How it works is the progress might hit level 40, which triggers stage 2 (every 20 progress = 1 stage).

This might apply a body condition where you now have a visible tail. When a stage is reached, it queues a special event to happen on your next movement somewhere. So this might inject this scene to interrupt your movement:

You stop mid-step as a strange pressure gathers at the base of your spine.

(if you have no tail) Moments later, you feel a tail sprout out behind you, the added weight almost knocking you off balance. You now have a [[drift.tailDescription]].

(if you have a tail) Moments later, you feel your tail change, adjusting suddenly. The change in weight almost knocks you off balance. You now have a [[drift.tailDescription]].

It twitches back and forth, already wagging.

This then ties into the condition system, where it adds a "drift" ID with a high priority. So flavour text might show something like:

A passerby stares at you, as if wondering if something is off.

or later on:

With how much your body has changed from your original imprint, several people glance your way, sharing hushed whispers.

I think this is the cleanest way for me to set this up for now.

I might make imprint drift a bit different when I get to that portion of writing the system, since I want imprint drift to be more than just species TF related, it might be a TF that swaps your anatomy around or something else. I want to keep my options open and not lock myself into a rigid system.

That's all I have for now to share on this!

Comments

No comments found for this post.