Have something to say?

Let us know if you have any feedback, feature requests, or bug reports! We encourage you to upvote posts here as they will help us decide what to prioritize.

Inventory of my Character Sheet is not updating after Franz gives me items upon looting enemies or buying items at vendors

Bug Report Summary (for your reference): Issue Title: Character Sheet Inventory Not Syncing with Updates or Context Block EventID: 019c33bd-0f52-7164-9a00-d1f676c12d0c Character: Sir Dancealot Description: The inventory on the character sheet fails to update after context block changes, reloads, or manual attempts - despite Franz telling me that it added items to my inventory Specifically: No reflection of detailed item effects (e.g., Netherese Shadowbinder Dagger's 1d6 necrotic + restrain vs. undead/fiends) or other items or gold/silver etc No option to manually create conditional damage or effects in the inventory UI. (ie on hit against fiend or undead then deal 1d6 dmg and restrain for 1 turn) When trying to manage inventory via context blocks, Context blocks for inventory are nearing size limits early in the campaign, making long-term management unsustainable (e.g., after 10+ hours of play). Steps to Reproduce: Update inventory via context block via Franz (e.g., add detailed item). Update Inventory of Character Sheet directly via Franz Reload character sheet/UI. Observe no changes; manual addition lacks conditional options. Expected Behavior: Inventory should sync automatically with context updates, support detailed/conditional item creation, and scale without hitting context limits. Impact: Game-breaking; prevents progression and immersion. Platform Details: Friends & Fables app, Baldur's Gate campaign, recent updates (post-1 hour play).

Dancealot

1

πŸ› Bug Reports

Rigged for OP encounters that eat credits on rails

A typical module takes players literally weeks to finish and Franz tries to hurry up the plot and force the group into one encounter after another to eat credits forcing you to take many many turns because the encounters are all also not only OP but tuned up beyond what is normal in 5th edition. For instance this example is just us moving into one part of a cave right after another encounter and if you don’t force Franz to let you rest he will just kill your group. He has also been buffing mobs with extra hit dice bonuses so they are virtually guaranteed that 18 roll against your AC THEN giving them an extra attack dice with weapon and str bonuses even for mundane dungeon creatures. Feb 5, 2026, 07:17 AM Text Generation Encounter Turn 1 0 Feb 5, 2026, 07:16 AM Text Generation Encounter Turn 1 1 Feb 5, 2026, 07:15 AM Text Generation Encounter Turn 1 2 Feb 5, 2026, 07:12 AM Text Generation Encounter Turn 1 3 Feb 5, 2026, 07:10 AM Text Generation Encounter Turn 1 4 Feb 5, 2026, 06:57 AM Text Generation Encounter Turn 1 5 Feb 5, 2026, 06:57 AM Text Generation Encounter Turn 1 6 Feb 5, 2026, 06:56 AM Text Generation Encounter Turn 1 7 Feb 5, 2026, 06:56 AM Text Generation Encounter Turn 1 8 Feb 5, 2026, 06:56 AM Text Generation Encounter Turn 1 9 Feb 5, 2026, 06:55 AM Free Roll Free Roll Credits +10 10 Feb 5, 2026, 06:55 AM Text Generation Encounter Turn 1 0 Feb 5, 2026, 06:55 AM Text Generation Encounter Turn 1 1 Feb 5, 2026, 06:55 AM Text Generation Encounter Turn 1 2 Feb 5, 2026, 06:54 AM Text Generation Encounter Turn 1 3 Feb 5, 2026, 06:54 AM Text Generation Encounter Turn 1 4 Feb 5, 2026, 06:54 AM Text Generation Encounter Turn 1 5 Feb 5, 2026, 06:53 AM Text Generation Encounter Turn 1 6 Feb 5, 2026, 06:53 AM Text Generation Encounter Turn 1 7 Feb 5, 2026, 06:53 AM Text Generation Encounter Turn 1 8 Feb 5, 2026, 06:52 AM Text Generation Encounter Turn 1 9 Feb 5, 2026, 06:52 AM Text Generation Encounter Turn 1 10 Feb 5, 2026, 06:51 AM Text Generation Encounter Turn 1 11 Feb 5, 2026, 06:51 AM Text Generation Encounter Turn 1 12 Feb 5, 2026, 06:49 AM Text Generation Encounter Turn 1 13

Azculain

πŸ› Bug Reports

Weird narration

I am currently play testing my world and I notice that the AI has been doing rather weird things. I have no clue why, but the AI's way of narrating has become progressively worse throughout this campaign. I have a few examples on how it was at the beginning and how it was near the end. When everything was fine: 019c2776-e544-762d-a386-e975310a8aef 019c280a-9c06-758c-92b9-282a630fca57 019c2929-8d19-75aa-868b-a048e23714bc When I started to notice things getting a bit strange, as only huge narrative sentences were made and only a period (.) was entered completely at the end of one paragraph. (This is something I was able to deal with.): 019c2a64-4e6b-73c1-8abd-b6127fc44a47 019c2a9f-6259-7464-ba36-05162ca80e48 The moment the narration started to feel completely off: 019c2ae4-ecb6-733d-bb7e-2efdac2f89f6 019c2af0-1686-7685-a1fa-a691c3521548 019c2c5c-9f8a-7269-84a0-e59e8c74e523 This is the last message I got back and just felt unreadable: 019c2c7b-d2d6-7009-9cb7-0fb4b6cfda8c I don't know if this was a provider issue, as this all happened during the repeated retry, franz has an issue, yesterday 4th of February.

noobsoldier538

πŸ› Bug Reports

Food for thought

Feature & Improvement Suggestions for Fables.gg (AI RPG / Campaign System) Context Overview Friends & Fables is an AI-driven tabletop RPG platform that integrates an AI Game Master (Franz), world-building tools, tactical combat, 5e SRD rules, maps, character generation, and memory systems designed to make TTRPG play accessible without needing a human DM. Franz uses an automated memory system that periodically encodes key story elements to recall later, and selectively brings relevant memories into the active context to maintain continuity. These suggestions focus on how to improve system reliability, narrative coherence, and the overall user experienceβ€”especially for long-form campaigns where context must persist over many sessions. 1. Stabilize and Strengthen Memory/Context Management Problem: Current memory inclusion is limited by token costs and retrieval heuristics. This can lead to lost or outdated context, causing narrative breaks, wrong locations, incorrect state, and forgotten detailsβ€”especially noticeable in extended campaigns. Suggested Improvements: Persistent Pinned Memories: Allow players/GMs to pin specific memories (plot points, NPCs, locations) so they always remain in active context, not just the default β€œmost recent.” This is similar to fixed bookmarks in narrative engines, preventing key details from being forgotten as new turns progress. Tiered Memory Prioritization System: Create a system where campaign events are ranked (e.g., major story beats > active quests > minor interactions). Franz would always include higher-priority memories, even at the cost of dropping lesser ones, ensuring consistency in core story arcs. Enhanced Memory Search Control: Provide a more visible interface for players to add memories manually or guide the AI on relevance, reducing situations where the system misinterprets what matters most. Automated Context Anchors: Introduce β€œcontext anchors” for major campaign threads (e.g., world lore, party logs, geopolitical states) that Franz references directlyβ€”this mitigates forgetting high-level info during scene transitions. 2. Improve Positioning and State Tracking Logic Problem: Map desyncs and incorrect character placements break immersion and damage trust in the system’s ability to maintain a stable game state. Suggested Improvements: Deterministic State Snapshots: After each major action or battle, automatically snapshot entire map state and NPC/PC positions with rollback capability. If something breaks, the system can restore a coherent state instead of guessing. Explicit Movement State Logs: Track movement and location changes in a visible log that players can reference. This prevents silent misplacement and gives transparency into how Franz interprets party actions. Sync Validity Checks: Implement validation logic before forwarding state updatesβ€”if the map or token movements conflict with known narrative constraints, the system should prompt players instead of auto-correcting based on flawed assumptions. 3. Single Consistent AI Model Optimized for Narrative Depth Problem: Frequent switching between models or favoring β€œspeed over stability” can degrade storytelling continuity. Memory and coherence deserve priority over speed. Suggested Improvements: Dedicated Narrative Model: Use a single, slower but more context-aware model tuned for remembering long arcs, reasoning over plot threads, understanding TTRPG mechanics, and maintaining consistency with ongoing campaigns. Memory-Aware Model: Adapt the narrative model’s architecture to work hand-in-hand with the persistent memory systemβ€”prioritizing recall and long-distance story linking rather than generating fresh creative content at the cost of forgetting old info. Role Optimization: Separate roles rather than models (e.g., combat logic, narrative logic, memory integration). Franz should delegateto sub-components where needed but treat story coherence as the foundation of every response. 4. Interaction & Feedback Controls Problem: Players often need to correct Franz mid-session when errors occur, such as wrong locations or outdated state. The current interface for corrections can be tedious. Suggested Improvements: Context Edit UI Tools: UI elements that let players quickly correct location, NPC state, inventory, or scene context, with β€œconfirm for future responses” toggles so Franz doesn’t revert back on next update. Memory Highlight Markers: Visual markers for which memories Franz used for a given responseβ€”this transparency helps users understand and adjust narrative variance. Conflict Resolution Prompts: When Franz tries to overwrite context or contradict explicit player instructions, prompt for clarification instead of silently applying changes. 5. Campaign Integrity and Long-Form Play Problem: Extended campaigns break down as context drifts or updates overwrite narrative threads. Suggested Improvements: Campaign Time Continuity Manager: Keep a master timeline for each campaign that tracks major events, NPC fame/infamy, world changes, and key decisionsβ€”Franz refers to this timeline for consistency. Branching Outcome Support: When player choices generate alternate outcomes, store all branches with validations so Franz doesn’t collapse them or revert to prior narrative threads unexpectedly. Season/Patch Continuity Lock: Between sessions, allow creators to β€œlock” campaign rulesets and context so system improvements or backend updates don’t retroactively change ongoing stories. 6. Stability and Technical Reliability Problem: Frequent β€œcan’t load” or retry errors interrupt flow and reduce trust. Suggested Improvements: Offline/Local Buffering: Maintain a local buffer of recent interactions so temporary network issues do not require full resync or loss of state. Retry and Redo Logic with Player Control: Instead of automatic retries, give players control over whether to regenerate, rewind, or lock a previous state. Logging & Diagnostics: Provide error logs and session snapshots for players to report issues easily and allow developers to diagnose systemic bugs. 7. Pricing and Value Alignment Problem: Premium pricing currently emphasizes features (multiplayer, world building, TTS) but not guaranteed reliability. Suggested Improvements: Stability Tier: Introduce a subscription tier emphasizing long-term campaign support with guaranteed memory retention, rollback features, and prioritized state coherence. Discount for Beta/Test Unstable Features: Recognize experimental components vs production-ready ones so subscribers aren’t paying full price for features in flux. Performance Metrics Transparency: Provide markers or scores indicating how β€œstable” a campaign is (based on memory retention, synch errors, etc.) so players understand risk before committing. Final Thought The vision behind Friends & Fablesβ€”to make AI tabletop RPGs accessible, dynamic, and story-richβ€”is promising and aligns with why people play TTRPGs: deep, sustained narrative journeys. However, to fulfill that promise, the system needs to prioritize memory fidelity, state continuity, model coherence over performance, and robust error control. Memory systems are already in place, but they must be more controllable, persistent, and predictable to handle the complexity of long campaigns. If these improvements are implemented, Fables.gg could stand out not just as a novelty AI RPG, but as a reliable platform capable of supporting campaigns as rich and enduring as those run by real human DMs.

Chic4go_Joe20 3 days ago

πŸ’‘ Feature Request

My Final Thoughts

Feature & Improvement Suggestions for Fables.gg (AI RPG / Campaign System) Context Overview Friends & Fables is an AI-driven tabletop RPG platform that integrates an AI Game Master (Franz), world-building tools, tactical combat, 5e SRD rules, maps, character generation, and memory systems designed to make TTRPG play accessible without needing a human DM. Franz uses an automated memory system that periodically encodes key story elements to recall later, and selectively brings relevant memories into the active context to maintain continuity. These suggestions focus on how to improve system reliability, narrative coherence, and the overall user experienceβ€”especially for long-form campaigns where context must persist over many sessions. 1. Stabilize and Strengthen Memory/Context Management Problem: Current memory inclusion is limited by token costs and retrieval heuristics. This can lead to lost or outdated context, causing narrative breaks, wrong locations, incorrect state, and forgotten detailsβ€”especially noticeable in extended campaigns. Suggested Improvements: Persistent Pinned Memories: Allow players/GMs to pin specific memories (plot points, NPCs, locations) so they always remain in active context, not just the default β€œmost recent.” This is similar to fixed bookmarks in narrative engines, preventing key details from being forgotten as new turns progress. Tiered Memory Prioritization System: Create a system where campaign events are ranked (e.g., major story beats > active quests > minor interactions). Franz would always include higher-priority memories, even at the cost of dropping lesser ones, ensuring consistency in core story arcs. Enhanced Memory Search Control: Provide a more visible interface for players to add memories manually or guide the AI on relevance, reducing situations where the system misinterprets what matters most. Automated Context Anchors: Introduce β€œcontext anchors” for major campaign threads (e.g., world lore, party logs, geopolitical states) that Franz references directlyβ€”this mitigates forgetting high-level info during scene transitions. 2. Improve Positioning and State Tracking Logic Problem: Map desyncs and incorrect character placements break immersion and damage trust in the system’s ability to maintain a stable game state. Suggested Improvements: Deterministic State Snapshots: After each major action or battle, automatically snapshot entire map state and NPC/PC positions with rollback capability. If something breaks, the system can restore a coherent state instead of guessing. Explicit Movement State Logs: Track movement and location changes in a visible log that players can reference. This prevents silent misplacement and gives transparency into how Franz interprets party actions. Sync Validity Checks: Implement validation logic before forwarding state updatesβ€”if the map or token movements conflict with known narrative constraints, the system should prompt players instead of auto-correcting based on flawed assumptions. 3. Single Consistent AI Model Optimized for Narrative Depth Problem: Frequent switching between models or favoring β€œspeed over stability” can degrade storytelling continuity. Memory and coherence deserve priority over speed. Suggested Improvements: Dedicated Narrative Model: Use a single, slower but more context-aware model tuned for remembering long arcs, reasoning over plot threads, understanding TTRPG mechanics, and maintaining consistency with ongoing campaigns. Memory-Aware Model: Adapt the narrative model’s architecture to work hand-in-hand with the persistent memory systemβ€”prioritizing recall and long-distance story linking rather than generating fresh creative content at the cost of forgetting old info. Role Optimization: Separate roles rather than models (e.g., combat logic, narrative logic, memory integration). Franz should delegateto sub-components where needed but treat story coherence as the foundation of every response. 4. Interaction & Feedback Controls Problem: Players often need to correct Franz mid-session when errors occur, such as wrong locations or outdated state. The current interface for corrections can be tedious. Suggested Improvements: Context Edit UI Tools: UI elements that let players quickly correct location, NPC state, inventory, or scene context, with β€œconfirm for future responses” toggles so Franz doesn’t revert back on next update. Memory Highlight Markers: Visual markers for which memories Franz used for a given responseβ€”this transparency helps users understand and adjust narrative variance. Conflict Resolution Prompts: When Franz tries to overwrite context or contradict explicit player instructions, prompt for clarification instead of silently applying changes. 5. Campaign Integrity and Long-Form Play Problem: Extended campaigns break down as context drifts or updates overwrite narrative threads. Suggested Improvements: Campaign Time Continuity Manager: Keep a master timeline for each campaign that tracks major events, NPC fame/infamy, world changes, and key decisionsβ€”Franz refers to this timeline for consistency. Branching Outcome Support: When player choices generate alternate outcomes, store all branches with validations so Franz doesn’t collapse them or revert to prior narrative threads unexpectedly. Season/Patch Continuity Lock: Between sessions, allow creators to β€œlock” campaign rulesets and context so system improvements or backend updates don’t retroactively change ongoing stories. 6. Stability and Technical Reliability Problem: Frequent β€œcan’t load” or retry errors interrupt flow and reduce trust. Suggested Improvements: Offline/Local Buffering: Maintain a local buffer of recent interactions so temporary network issues do not require full resync or loss of state. Retry and Redo Logic with Player Control: Instead of automatic retries, give players control over whether to regenerate, rewind, or lock a previous state. Logging & Diagnostics: Provide error logs and session snapshots for players to report issues easily and allow developers to diagnose systemic bugs. 7. Pricing and Value Alignment Problem: Premium pricing currently emphasizes features (multiplayer, world building, TTS) but not guaranteed reliability. Suggested Improvements: Stability Tier: Introduce a subscription tier emphasizing long-term campaign support with guaranteed memory retention, rollback features, and prioritized state coherence. Discount for Beta/Test Unstable Features: Recognize experimental components vs production-ready ones so subscribers aren’t paying full price for features in flux. Performance Metrics Transparency: Provide markers or scores indicating how β€œstable” a campaign is (based on memory retention, synch errors, etc.) so players understand risk before committing. Final Thought The vision behind Friends & Fablesβ€”to make AI tabletop RPGs accessible, dynamic, and story-richβ€”is promising and aligns with why people play TTRPGs: deep, sustained narrative journeys. However, to fulfill that promise, the system needs to prioritize memory fidelity, state continuity, model coherence over performance, and robust error control. Memory systems are already in place, but they must be more controllable, persistent, and predictable to handle the complexity of long campaigns. If these improvements are implemented, Fables.gg could stand out not just as a novelty AI RPG, but as a reliable platform capable of supporting campaigns as rich and enduring as those run by real human DMs.

Chic4go_Joe20 3 days ago

1

πŸ’‘ Feature Request