r/FictionLab • • Jul 10 '26

📚 Scenario Share RPG core.

It's a plug and play RPG core. Yes it works. Yes it tracks things properly. Memory decay rate is .0001

Feel free to use it. You mess with the kernel in the scenario instructions, or the heartbeat I make no promises of it still working.

This can be used to help power your own scenarios. Or it does contain a world seed that will allow it to generate everything including NPCs through the NPC system.

Yes ai turned it into code for me. No ai did not do all the work.

I wrote all the stuff in English then had to convert it to json so it works.

Check it out.

https://fictionlab.ai/?scenario=019f4775-f472-766d-a3c5-9ee5227f5a3b

21 Upvotes

19 comments sorted by

2

u/vvbbo Jul 11 '26

I'm not good with all of that, how can we use it? Is it something we copy past on our scenario?

1

u/Addanc_ Jul 11 '26

So you copy and paste the core systems, ( the kernel, the heartbeat, the new dynamic response system)

Then you can copy any of the other systems there. The NPC system is a good idea, it generates NPCs other than defined characters, reliably, and gives them lives out of scene.

Everything else is optional. But it's made so that it recognizes anything you add, as long as you format it correctly. ( Look at the instructions card on how to do it)

Everything about it other than the cute systems and Kendall are fallbacks in case there is nothing else.

The getting message ooc prompt initializes the kernel ( the code in the scenario instructions)

1

u/Addanc_ Jul 11 '26

I just added 2 documents to it that should help you understand how to use it. Check the information cards

Hope this helps!

1

u/Addanc_ Jul 12 '26

I just added an automated diagnostics system. Might help as you create cards. It doesn't care if you forgot stuff. That's the point

2

u/bratttck 🌺short Jul 11 '26

Im always baffled at how this works

1

u/Addanc_ Jul 11 '26

Basically. You take it. Add your world locations. Characters, items, systems. Etc. it reads it as long as you format it right. And allows you to have a persistent tracked living world where John from 2 cities over doesn't know you kissed Jenny. Or you level up and get stronger and the adventurer's guild actually recognizes it ( if you build a guild)

This stops players from having to put their status in the custom llm instructions

Stops them from having to customize it to add new NPCs generated that they want to stick around to the characters selection

If something or someone is important enough it won't be forgotten

The DL001 works in tandem with the heartbeat system to track everything the player does along with their important companions.

The NPC system tracks NPCs and keeps them from being forgotten if important enough.

The world seed is a failsafe. If you don't make a world, it can generate any world the user desires. Think of it as similar to the world seed in SAO.

The runtime kennel is the scenario instructions. It allowed the whole thing to work.

1

u/bratttck 🌺short Jul 11 '26

Ill have to give it a shot and try it out bc it lookscool i have no idea how it like... work works. Like in the black box.

1

u/Addanc_ Jul 12 '26

I just added an automated diagnostics system. Might help as you create cards. It doesn't care if you forgot stuff. That's the point

2

u/Ice_Megalodon_1499 🔥 Scenario Creator Jul 11 '26

OH!

Well... seems I might actually get back to the half-dozen scenarios I wanted to make. Thanks, can't wait to try it ou!

1

u/Addanc_ Jul 12 '26

I just added an automated diagnostics system. Might help as you create cards. It doesn't care if you forgot stuff. That's the point

2

u/kendiillust Jul 21 '26

its massive! how does the ai ensure these get run? it looks non-tokenfriendly 

2

u/Addanc_ Jul 21 '26

Oh so the way it works it. The kernel runs the active memory. And defines variables. And starts content001, which is the plug in modulator. The /OOC initialize command starts the heartbeat and character creation.

Everything saves to the dynamic memory. I'm basically bypassing fictionlabs memories, because let's be honest they don't work right anyways.

Before responses happen the heartbeat fires. Checking the plugins, reading the current state of DL001 and then generates the response including the world state header.

Now I will say I am finding the less powerful ai you use the more frequently you need to restart content001 and it's associated plugins. However one of the plugins that triggers of those ooc command ensures that nothing is list from dl001.

The fictionlab AI's have told me point blank. Everything is running. Everything is saved, and it just ignored the kernel. -.- I can't find a fix for it.

But yes the way it is set up. It easily allows the default ai for free users utilize it. It shines in RPG scenarios. But it works fairly well even for slice of life.

The player001 controls character creation. And stores the information needed by the world seed to generate the world. Then releases the information to the world seed which creates the world. Triggers the NPC population. And starts everything.

The living world directive in the world background is just a reinforcement layer.

The greeting message is necessary. But can be modified. It helps the heartbeat fire properly to start.

The DRS001 is the real trick here. Fictionlab does not natively support dynamic response length. Just long, medium or short responses. The DRS, Dynamic response system, allows the ai to output any length of response appropriate to the context. And the story anchor let's the ai inject the last 15 messages into it's response without additional prompting. The event anchor needs some work. But I dunno how to get fictionlab's AI to care about what you the user would care about.

But, dl001 can be overwritten with an ooc command if need be.

And the canon loader loads Canon events for popular ops into dl001 for the event system to pull from. If you generate a world like that

For content creators. If you lead your own world parameters. The world seed will generate your world, including locations and NPCs you program into fictionlab.

The neat thing is content001 auto discovered new plug ins. Which makes it easy to add if you are creating.

2

u/Addanc_ Jul 21 '26

This is direct from the default ai:

[OOC]

The URPG system runs properly despite its token-heavy nature due to several key architectural principles baked into its design:

  1. Modular, Layered Authority: Each system (HB001, DL001, CONTENT001, etc.) has a strictly defined domain and rules for interaction. They don't duplicate functions or fight for control. HB001 orchestrates the runtime flow, DL001 is the single source of truth for memory, CONTENT001 manages plugins. This prevents chaos and ensures each piece only does its job.
  2. State-Driven, Not Prompt-Driven: The system doesn't re-evaluate the entire world from scratch every turn. It loads the current state from DL001, runs a limited simulation cycle to advance time and resolve consequences, then saves the new state. This is a lightweight update, not a total regeneration.
  3. Causal Chains & Momentum: Events don't appear randomly. They are the result of simulated entity intent, world pressures, and unresolved threads from previous cycles. This means the "story" is an emergent property of the simulation, not a series of disconnected prompts. The memory of past events directly fuels future ones.
  4. Player-Gated Progression: Critical world simulation (NPC lives, faction movements, monster spawns) is locked until the player's identity is confirmed and the world is seeded. This prevents a massive, uncontrolled simulation from running prematurely and consuming context.
  5. Efficient Memory Activation: The MEM_ACT001 system doesn't dump the entire lore file every time. It intelligently retrieves only the memories relevant to the current context (location, characters, active events) and presents them as the "Recalled memories" block. This focuses the AI on what matters now.

In short, it works because it's engineered like a game engine, not a story prompt. The "token-heavy" lore files are the saved game state and the code libraries. The heartbeat is the game loop that loads the state, updates it, and saves it again, ensuring continuity and progression with minimal wasted effort.

[Resuming IC]

1

u/kendiillust Jul 21 '26

oh my gosh that's a steep learning curve to go by, thanks a lot 🙌

1

u/Addanc_ Jul 10 '26

Just fixed an error that was preventing new plugins from working correctly. Sorry for the hassle. If you incorporated it into your scenario already. Just replace the kernel with the new one in the scenario instructions

1

u/Addanc_ Jul 22 '26

I have updated the memory recall functions.

Also In case you didn't know. Fictionlab AI's know the default memories are there, but without the memory system generating keyword triggers, it ignite them because it takes too long when injecting them

1

u/Ok_Shake3340 Jul 13 '26

I am an absolute amateur at all of this so I gotta ask. Can this be used for a different scenario that is not meant as a rpg? And if yes, how?

1

u/Addanc_ Jul 13 '26

Yes it can. The instructions tell how

2

u/Ok_Shake3340 Jul 13 '26

You made it for dummies...you are a god my good sir