View Issue Details

Jump to NotesJump to History
IDProjectCategoryDate SubmittedLast Update
0027818Heart Of The MachineBug - OtherMay 1, 2023 4:51 pmMay 1, 2023 8:00 pm
ReporterChris_McElligottPark Assigned ToDraco18s  
Severityminor 
Status resolvedResolutionfixed 
Summary0027818: Spawning logic errors -- to detect on game startup.
DescriptionSo, if you start up any game, and do two dispatches, then you'll start getting a flood of errors. These are based off of some data that is bad. There are two key problems here:

Problem 1: we don't find out about this until the encounter is considered.

Problem 2: we keep getting told about this over and over.

----------------------------

Here's the offending line:

<req_considering_cohort_has_status_level cohort_status_type="Wealth" must_be_at_least="500" must_be_at_most="1000"/>

This adds a bunch of things like "Encounter: SueCult_Religion EncounterCohortStatusSpawnRequirement error: cohort 'Spirology' does not use the requested status 'Wealth'"

This is true -- the cohort in question does not use this cohort status. Instead, there are some sub-cohorts that use it.

Goal: when in the cross-table walk section for req_considering_cohort_has_status_level, take a look at all of the cohorts of the tag that is specified, and then complain, one by one, about any of them that do not have it. So we should have a bunch of exceptions, once, on startup.

Part 2: make it so that this specific error is no longer checked at runtime, it just does a continue or whatever it already does. We'll already have been told about it on program start up.

I suspect we will see this pattern again in the future, but for now this is the only one.
TagsNo tags attached.

Relationships

duplicate of 0027820 resolvedDraco18s req_considering_cohort_has_status_level -- ability to tie to "any subcohort" 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
May 1, 2023 4:51 pm Chris_McElligottPark New Issue
May 1, 2023 4:51 pm Chris_McElligottPark Status new => assigned
May 1, 2023 4:51 pm Chris_McElligottPark Assigned To => Draco18s
May 1, 2023 4:57 pm Chris_McElligottPark Relationship added related to 0027820
May 1, 2023 8:00 pm Draco18s Status assigned => resolved
May 1, 2023 8:00 pm Draco18s Resolution open => fixed
May 1, 2023 8:00 pm Draco18s Relationship replaced duplicate of 0027820