# Flashbacks and Time Skips in TTRPGs: Which Rules Let You Jump Through Time Mid-Campaign? Published: 2026-11-01 Updated: 2026-11-01 Compare flashback and time-skip rules across three RPG systems and learn how to handle continuity, costs, and downtime. ## Article I’d use [Blades in the Dark](/item/bladesinthedark) for past preparation, [Fate Core](/item/fate-core) for character changes between story beats, and [Ars Magica](/item/ars-magica) for months or years of downtime. These rules help you skip or revisit time - not rewrite history through literal time travel. - Blades in the Dark: Add earlier preparation during a score. Flashbacks cost 0, 1, or 2+ stress; downtime activities cost 1 coin or 1 rep instead. Rolls may still apply, and established events stay fixed. - Fate Core: Use milestones to adjust characters as the story moves forward. They don’t track skipped activities or automatically heal injuries. - Ars Magica: Resolve study, research, and other work across 4 seasons per year, tracking progress, resources, and aging. Before any jump, I’d agree on elapsed time, allowed changes, and facts that stay fixed. The main trade-off is less planning now versus more bookkeeping across the skipped time. Quick Comparison Game When it applies Cost or permission What to track Blades in the Dark Preparation revealed during a score Stress, or coin/rep for downtime Rolls, costs, and fixed events Fate Core Milestone between story beats Allowed character changes Off-screen events and recovery separately Ars Magica Seasonal downtime Time, activity limits, and resources XP, projects, supplies, and aging TTRPG Flashbacks and Time Skips: Blades vs. Fate vs. Ars Magica ## 1. Blades in the Dark ### Flashback triggers During a score, a player can invoke a flashback if earlier preparation could plausibly solve the current obstacle. Establish what the character did, resolve that action, then return to the score. This makes Blades best suited to filling in a plan while the score is underway. ### Costs and rolls The GM sets the stress cost based on how plausible or involved the preparation is. From there, it’s a quick cost-and-roll decision. Paying stress doesn’t guarantee success: risky preparation may still need an action roll, with consequences and resistance handled as usual. Use a fortune roll to determine quality, quantity, or timing. Flashbacks involving downtime activities cost 1 coin or 1 rep instead of stress. Other rolls and costs still apply, including those for crafting. ### Character effects Stress spent on flashbacks leaves less room for resistance, assists, group actions, and pushing yourself, which costs 2 stress. Filling the stress track causes trauma and takes the character out of the immediate conflict. Heavy spending also puts pressure on later downtime, when indulging vice competes with other activities. ### Continuity Established events stay fixed. Before accepting a flashback, check that the character had the access, ability, and opportunity to carry out the preparation. A flashback adds context; it can’t erase an injury, discovery, or consequence already in play. Trigger Resource cost Continuity effect Character impact Ideal campaign use Ordinary preparation, easy opportunity 0 stress Prior arrangement Preserves stress Routine prep Complex preparation, unlikely opportunity 1 stress Added preparation Less stress capacity Difficult prep Elaborate preparation, special contingency 2+ stress Prior contingency Greater trauma pressure Complex contingency Downtime activity 1 coin or 1 rep Past downtime action Spends coin or rep Downtime projects Where Blades fills in preparation within a scene, the next system, Fate Core, advances characters between scenes and major story beats rather than revisiting earlier actions. Flashbacks in DnD & [Daggerheart](/item/daggerheart) | The Ultimate Guide ## 2. Fate Core Where Blades uses flashbacks during a score, Fate advances characters between scenes through milestones. ### Milestone triggers Fate Core ties advancement to story beats, not elapsed time. Each milestone sets out what you can change - and what stays as it is. ### Advancement permissions Minor milestones allow one reconfiguration. Significant milestones add 1 skill point, while major milestones add 1 refresh and more advancement choices. Buying a stunt requires enough refresh, which cannot drop below 1. None of these changes automatically alters injuries or downtime. ### Character changes and recovery Milestones do not heal consequences. Recovery still requires enough in-fiction time and an overcome action. Significant milestones can reopen severe consequences for recovery; extreme consequences require a major milestone to be renamed. Beyond those character changes, the table must decide what remains true after a time skip. ### Continuity Before a skip, agree on elapsed time, off-screen events, relationship changes, setting changes, and unresolved consequences. Record those decisions alongside character-sheet changes. Milestones neither define off-screen events nor authorize retcons. Fate therefore works best for planned jumps between scenes rather than retroactive changes within a scene. Milestone level Permitted character changes Campaign transition Continuity questions Minor Choose one: swap two skill ranks, replace an Average (+1) skill, change or buy a stunt, or rename a non–high concept aspect. Session break or small development; no automatic skip. What changed, and has enough time passed for recovery? Significant Minor benefits plus 1 skill point; severe-consequence recovery may begin when permitted. Scenario ending or major plot event; downtime decided separately. What changed off-screen, and what remains? Major Significant benefits plus 1 refresh; may rename the high concept or an extreme consequence, or exceed the skill cap when permitted. Arc ending or major setting change; suits a long campaign jump. What changed in the setting, and what persists? ## 3. Ars Magica Where Fate advances between story beats, Ars Magica advances one season at a time. ### Seasonal procedures Each character gets one main activity per season. Study, training, teaching, and spell learning follow this seasonal clock rather than individual scenes. In [Ars Magica Fifth Edition](https://www.atlas-games.com/product_tables/AG0205), four seasons make a year. Study, training, and teaching award experience according to the source and applicable rules. Record the subject, source, XP, and any restrictions. ### Laboratory work and costs Laboratory work follows the same clock. Each season, spell invention adds progress equal to the amount by which the Lab Total exceeds the spell’s level. The spell is complete when accumulated progress reaches its level. Track laboratory research, experimentation, assistants, vis spent, and unfinished work separately. Enchanted items need the applicable preparation, time, and vis; charged items generally take one season. Setting up a standard laboratory takes two seasons. Time, lab access, materials, and vis limit what each seasonal project can achieve. ### Character and covenant changes Seasons improve Arts and Abilities, bring projects to completion, and change covenant resources. Some rules for covenant-scale construction, laboratory improvement, and economics come from supplements such as Covenants. ### Continuity across a skip Keep a dated covenant log covering locations, wounds, obligations, laboratory progress, books, vis, income, and expenses. Apply annual aging under the Fifth Edition rules. Before play resumes, reconcile resource balances and unfinished projects. A spell only counts as complete if its recorded seasonal progress supports that result. Time unit Available activities Mechanical outputs Bookkeeping demands Continuity risks One season Study, training, teaching, laboratory work; travel, adventures, or covenant duties as applicable XP, project progress, completed work, or interruption results Activity, location, source, costs, wounds, and project progress Conflicting locations or double-spent resources Several seasons Spell invention, item creation, laboratory setup, extended travel Completed projects, accumulated XP, changed resources Seasonal progress, assistants, interruptions, completion dates Treating unfinished work as complete One year Four seasons, aging, covenant accounting Character development, aging results, income and expenses Reconcile health, obligations, inventories, and accounts Forgotten aging or unpaid obligations Multiple years Extended study, covenant development, long projects Large changes to characters and the covenant Annual summaries with unresolved projects and commitments Assuming everyone remained available and unchanged ## Compare Triggers, Costs, Changes, and Continuity Trigger tells you when a rule applies. Cost or permission determines whether the change can happen. What changes describes the result, while continuity keeps earlier events intact. Criterion Blades in the Dark Fate Core Ars Magica Trigger During an active operation, when a player needs past preparation. A milestone marks a story break. A season advances the campaign. Cost or permission 0, 1, or 2+ stress; downtime flashbacks cost 1 coin or 1 rep. Milestones permit limited character changes. Each activity takes seasonal time. What changes Adds past preparation to the current operation; success may still require a roll. Changes the character build; campaign state can shift between scenes. Activities produce XP, progress, or completed projects. Continuity Adds preparation without undoing established events or consequences. Allows only changes supported by the fiction and milestone; earlier scenes aren't replayed. Season logs track completed activities, finished projects, and unfinished work. Each tool handles time differently: Blades changes the setup, Fate permits character development, and Ars Magica resolves work done over elapsed time. Choose based on what you want skipped or revisited time to do: Campaign need Strongest fit Limitation Retroactive preparation Blades in the Dark Preparation may cost stress, coin, or rep and still require a roll. It can't erase established outcomes. Brief narrative transition Fate Core It abstracts the intervening period, giving less detail about activities and resources. Extended downtime Ars Magica Seasonal bookkeeping takes more effort and requires tracking activities and experience sources. Multi-year campaign jump Ars Magica The calendar, projects, and interruptions need careful records across many seasons. Character advancement Fate Core for milestone-based revisions; Ars Magica for detailed activity-based growth Fate abstracts the learning process; Ars Magica requires more tracking. Detailed resource accounting Ars Magica More precision means more bookkeeping. The next section weighs each system’s payoff against its speed, bookkeeping, and impact at the table. ## Benefits and Limits at the Table At the table, these rules differ in how much they speed up play, what they track, and what they leave off-screen. System Advantages Limitations Blades in the Dark Retroactive preparation keeps scenes moving without lengthy planning breaks. Flashbacks use the same resolution tools as present-time actions. Spending stress puts pressure on other options, and established consequences still apply. Fate Core Between meaningful story beats, the group can skip routine travel or training and pick up at the next conflict. Milestones don’t track off-screen events over time. Aging, obligations, relationships, and enemy progress require separate decisions. Ars Magica Seasonal progress gives research, teaching, and covenant development time in the spotlight alongside adventures. Records maintain continuity through skips of months or years. That continuity comes with bookkeeping: activity records, finances, obligations, health, and aging. - Blades: Record new obligations right away. Flashbacks buy leverage, not protection from fallout. - Fate: Keep a skip log for elapsed time, off-screen goals, and relationship changes. Milestones govern advancement - not the passage of days. - Ars Magica: Use one seasonal ledger for activities, resources, obligations, and aging. Multi-year skips still need full bookkeeping. Bundle routine seasons, but pause when an interruption changes the current situation. ## Choose the Right Rules for Your Campaign Use the comparison above to match your campaign’s time jump to the right rules. - Blades in the Dark fits retroactive preparation during an operation. Flashbacks cost stress, and you may still need to roll. - Fate Core handles advancement between story beats without replaying skipped time. Milestones determine which character changes are allowed. - Ars Magica suits jumps of several months or years when you want to track the results of extended downtime through seasonal play. Before the jump, agree on elapsed time, allowed changes, and fixed facts. These rules cover preparation, advancement, and downtime - not literal time travel. ## FAQs ### Can I adapt flashback rules to my current campaign? Yes. Set clear boundaries: flashbacks shouldn’t change major plot points or control other players’ characters. Agree on costs and scope before introducing these rules. For retroactive preparation, let players spend a resource, such as stress, to establish actions they took earlier. This lets them skip lengthy planning. For broader changes, use milestone-based advancement after major story arcs, or seasonal downtime rules to handle long gaps between major events. ### How do I keep time skips fair for every player? Treat knowledge as progress. Once players solve a challenge - like getting past a guard or cracking a code - let them skip the repeat work and move on to new developments. Set clear, consistent rules for flashbacks and time skips during session zero so everyone knows the boundaries. Skipping actions shouldn’t erase their consequences: players’ choices should still leave a lasting mark on the world. ### When should downtime become a played-out scene? Play out downtime as a scene when decisions, roleplay, or [resource management](/category/resource-management) shape the campaign’s direction. [Forged in the Dark](https://bladesinthedark.com/basics) systems build downtime around recovery and project advancement. But character moments, complex interactions, or complications may need more than a single roll. Use these scenes to build emotional connections, resolve character arcs, or give characters room to explore - all while keeping a steady rhythm between action and recovery. {"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Can I adapt flashback rules to my current campaign?","acceptedAnswer":{"@type":"Answer","text":"Yes. Set clear boundaries: flashbacks shouldn’t change major plot points or control other players’ characters. Agree on costs and scope before introducing these rules. For retroactive preparation, let players spend a resource, such as stress, to establish actions they took earlier. This lets them skip lengthy planning. For broader changes, use milestone-based advancement after major story arcs, or seasonal downtime rules to handle long gaps between major events."}},{"@type":"Question","name":"How do I keep time skips fair for every player?","acceptedAnswer":{"@type":"Answer","text":"Treat knowledge as progress. Once players solve a challenge - like getting past a guard or cracking a code - let them skip the repeat work and move on to new developments. Set clear, consistent rules for flashbacks and time skips during session zero so everyone knows the boundaries. Skipping actions shouldn’t erase their consequences: players’ choices should still leave a lasting mark on the world."}},{"@type":"Question","name":"When should downtime become a played-out scene?","acceptedAnswer":{"@type":"Answer","text":"Play out downtime as a scene when decisions, roleplay, or resource management shape the campaign’s direction. Forged in the Dark systems build downtime around recovery and project advancement. But character moments, complex interactions, or complications may need more than a single roll. Use these scenes to build emotional connections, resolve character arcs, or give characters room to explore - all while keeping a steady rhythm between action and recovery."}}]}