Choose the task in front of you
Use a workflow when several mechanics could explain the same symptom. Each procedure separates the state to inspect, the decision to make and the result to verify.
Why a production job has stopped ↗
Separate missing inputs, an unavailable output destination and Master behavior before replacing the worker. A full-storage halt is intentional in 0.4.5.
Keep crafting inputs out of sales ↗
A Master normally keeps ingredients, but the documented exception permits their sale when storage is completely full. Check stock pressure before treating every sale as a regression.
Choose a target stock or manual storage route ↗
Use storage when the entire batch is needed internally, storefront when it is intended for sale, and a target-stock policy when only the excess should be offered.
Avoid reserving one ingredient twice ↗
Allocate shared stock across all planned outputs before starting either recipe. Two individually affordable batches can exceed the same combined inventory.
Decide whether to buy an intermediate ↗
Compare the current purchase quote for an intermediate with the complete cost and constraints of making it. A shorter visible recipe does not imply a cheaper supply chain.
Why finished goods are not yet profit ↗
Production, storefront placement and a completed sale are separate events. Keep unsold goods out of realized cash income.
Explain two prices for the same item ↗
Compare matching buy or sell quotes before blaming a database discrepancy. The 0.4.5 tooltip separates price factors that can make two otherwise similar offers differ.
Find an item hidden by market filters ↗
An absent market result may come from the search or out-of-stock filter. Clear interface filters before concluding an item was removed.
Protect operating cash before an upgrade ↗
An affordable construction quote can still leave too little cash for existing commitments. Separate the upgrade payment from the operating reserve.
Choose between repairs and expansion ↗
Inspect current integrity and active bottlenecks before buying more capacity. A larger workshop does not solve damage or an unavailable output destination.
Separate worker mastery from profession rank ↗
Worker grades and a family character’s profession progression are different ladders. A promotion or wage change does not automatically unlock a higher business level.
Diagnose a Master with no empty cart ↗
The 0.4.1 mitigation restricts Masters to empty carts. A cart that exists but still carries goods may therefore not satisfy the current automation requirement.
Review an escort after a cart fight ↗
Check the escort’s actual state after combat. Immediate expiry after the first fight was fixed in 0.4.5, while ordinary expiry remains a separate event.
Record evidence after a cart ambush ↗
Inspect the evidence actually received after an encounter. The published Fight rule is specific to that response and cannot be extended to every crime or transport.
Separate Nuremberg stutters from general slowdown ↗
Use the same save and activity when comparing performance. The Nuremberg-specific 0.4.1 work and the broader 0.4.5 late-game improvements address different observations.
Preserve a campaign before testing a workaround ↗
Create a deliberate manual save before experiments. Four rolling autosaves in 0.4.5 provide less historical depth than the former ten and are not a substitute for a named checkpoint.
Choose how to continue an old demo save ↗
Use the older demo branch for an existing old-demo playthrough, or begin with the updated demo. The launch compatibility warning is not a claim that every EA patch invalidates every save.
Review the heir plan after a spouse dies ↗
Treat remarriage, adoption and heir nomination as separate checks. Adoption is available in 0.4.5, but the developer still lists remarriage after spouse death as unresolved.
Distinguish a candidate from an active courtship ↗
A suitable candidate being present is only the start of a relationship workflow. Check the active courtship state before sending another gift or planning an engagement.
Recalculate dynasty renown after the head changes ↗
The documented 0.4.5 rule counts the current head twice and other dynasty members once. A change of head changes which member receives the extra weight.
Separate child appearance from heir eligibility ↗
A character’s model is not enough to establish adulthood or succession eligibility. The 0.4.5 child-appearance fixes are visual fixes, not a published inheritance formula.
Check an office title before spending influence ↗
Verify title eligibility and the appointing roles before spending on relationships. Good relations cannot be assumed to replace an unmet title requirement.
Distinguish a reference law from the enacted rule ↗
The Lawbook in your current city takes priority over the register’s default. A source default describes the reference, not every campaign’s present legislation.
Distinguish evidence count from evidence strength ↗
Read the strength of each piece independently. Several weak pieces should not be silently converted into one strong piece in an evidence plan.
Triage an unexpected tutorial accusation ↗
False tutorial accusations became less likely in 0.4.1, but the developer explicitly says they may still happen. Preserve the case details before repeating the sequence.
Compare Fencing Master and Colonel suppression ↗
Both offices have documented crime-suppression context, but 0.4.5 describes the Fencing Master action as weaker than the Colonel action without a numerical ratio.
Plan a Beehive harvest for sale ↗
Honey and Beeswax have a current sale route in 0.4.5. Additional production-chain uses are future work and should not be inserted into a crafting plan.
Plan around current Masters while awaiting Overseers ↗
Use the released Master controls and recipe routing for current work. The October preview describes broader management orders and Overseers that are not confirmed as shipped in 0.4.5.
Investigate a training session with no skill change ↗
Confirm the selected training type, completed session and before-and-after field. Hotfix 0.4.1 fixed some failed skill gains, but it did not publish an identical gain for every activity.
Check equipment duration before accepting a duel ↗
Compare the equipped item’s actual effect and remaining duration with the challenged character’s condition. A high reference value is not a combat-readiness score.
Separate city treasury from personal cash ↗
The city treasury is a civic budget with its own updated behavior. Do not treat a reference starting treasury as money available to your dynasty.
Prepare a useful price discrepancy report ↗
Capture the live quote and its expanded breakdown with the exact item, character and destination. A reference value alone cannot demonstrate an incorrect price.
Keep the next step connected
Open the relevant record for attributed fields, use a worksheet for values from your own save, and check patch notes when the observed behavior differs.