zematus / worlds Goto Github PK

Just a simple overlay that shows cells as green if people migrated in and red if people migrated out (intensity scaled by proportions)

check wolrd seed 780667237 (this situation doesn't happen if save is done beforehand):

Running Worlds 0.03 (release)...
Generating world with seed: 780667237
[Date: Year 913361, Day 217] - replaced clan split event with old Id: 333376982705801007 with Id: 333386107705801007
[Date: Year 913386, Day 217] - _newClanCoreGroup with Id: 174960506025029 has HighestPolityProminence Id: 20060741001705801
[Date: Year 913386, Day 217] - replaced clan split event with old Id: 333386107705801007 with Id: 333395234705801007
[Date: Year 913386, Day 217] - Group with Id: 174960506025029 - HighestPolityProminence set to null
[Date: Year 913386, Day 217] - Exception: highestPolityProminence is null - Clan Id: 20059828501705801, Group Id: 174960506025029, Event Id: 333386107705801007
Clan.Split ()
World.SplitFactions ()
World.Update ()
GuiManagerScript.Update ()

Running Worlds 0.03 (release)...
[Date: Year 647433, Day 333] - Generating world with seed: 350393830
[Date: Year 0, Day 0] - NullReferenceException: Object reference not set to an instance of an object
Manager.SetGeneralOverlayColor (.TerrainCell cell, Color terrainColor)
Manager.GenerateColorFromTerrainCell (.TerrainCell cell, Boolean highlightCells)
Manager.UpdateMapTextureColorsFromCell (UnityEngine.Color32[] textureColors, .TerrainCell cell, Boolean highlightCells)
Manager.UpdateMapTextureColors (UnityEngine.Color32[] textureColors)
Manager.UpdateTextures ()
GuiManagerScript.Update ()

For example, to trigger a save or execute a specific decision

The reason for this is that CanTrigger only validates if an Event should trigger at a certain date according to the established conditions. If CanTrigger fails then it means that the status quo should be maintained (no updates).

1. add Region Snapshots (to store historic info about regions that disappear)
2. agents should only need to store in disk:
   • Id (which works as seed)
   • Cell Info
   • RegionSnapshot (for name generation purposes)
   • Language Id
3. everything else should be generated on demand using lazy ev

https://forum.unity.com/threads/fatal-error-in-gc-too-many-heap-sections.58746/

It should be similar to the cell update highlighting mode but instead of highlighting all cells that had updates it should highlight specific cells that have been flagged by debug triggers (ie. if a condition is triggered on a cell due to some debug criteria being met, add the cell to a list of cells to highlight this frame)

LINQ tends to cause too many memory allocations and we want to reduce that.

I implemented a workaround by ignoring IOexceptions of this kind but this is not the correct way to handle this issue.

lambdas and anonymous functions tend to trigger unnecessary memory allocations

delegates will always generate memory footprint when created. Try to generate them beforehand

see: https://jacksondunstan.com/articles/3264

see: https://jacksondunstan.com/articles/3250

Running Worlds 0.03 (release)...
[Date: Year 683842, Day 25] - NullReferenceException: Object reference not set to an instance of an object
AcceptedMergeTribesOfferEventMessage.GenerateMessage ()
WorldEventMessage.get_Message ()
GuiManagerScript.GetMessageToShow (.WorldEventMessage eventMessage)
GuiManagerScript.ShowEventMessageForPolity (.WorldEventMessage eventMessage, Int64 polityId)
GuiManagerScript.ShowEventMessage (.WorldEventMessage eventMessage)
GuiManagerScript.Update ()

This would be useful to avoid race-condition-like issues between multiple concurrent events and would reduce the need of special function sets like the faction-splitting method set

examples: polity mergers, faction-mergers

I think this is how it happened:

1. Loaded world with seed 1899559040 at date: Year 410053, Day 209
2. Selected tribe 13695421028612600 who was going to merge with 14430977028112100 in Year 410685, Day 289
3. Let that event happen
4. Immediately reload world
5. Tribe 13695421028612600 merges with 14430977028112100 right away long before the event was supposed to happen

Things that are needed:

• Log correctly the current world's seed
• Log every action/decision taken by the players within the game to be able to reproduce crashes (Caution: avoid storing user data of any kind)