Yeah this is expected and you will respawn too if you get your last army (with no outpost) killed during the neolitic era, this is because major faction are not supposed to be easily eliminated at any point in the game and this is to avoid you pesky human player to bully too much our poor AI.

Good catch, I think the issue is with the warning because there is no real difference to the lost at sea damage made to cog and to triremes (cog take just less damage but it work exactly the same way to us).

Hotfix 0.13.135

• Fixed a crash when stealing territory
• Fixed a crash when using settlers to found cities
• Fixed turn progress being blocked by an "idle city" notification if your only outpost or city got ransacked
• Fixed the game not saving that you had seen the intro video if it crashed

Hotfix 0.13.128

• Fixed sources of crashes. Some may still remain.

Hi Bridger!

I'll try to look into this! If you happen to stumble upon it again and get a save, I'd love to get ahold of it! Saves are located in Documents > Humankind > Save Files.

Thank you!

Hi everyone!

If you encounter any bugs while playing the Lucy OpenDev, please report them in this subforum using the following template:

EXAMPLE

• Summary / Title: Tooltip displays placeholder text
• Description: After building an Emblematic Quarter of a Classical Era Culture, the tooltip of the tile displays a placeholder text
• Steps to Reproduce: 1. Enter the Classical Era // 2. Build their Embelmatic Quarter // 3. Hover over the tile to check the tooltip
• Reproducibility: 5/5
• Expected Behavior: The tooltip should display localized text.
• Notes
• Attachments: Save, Screenshots, Logs etc...

Below, I'll add more details for those who want it.

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

1. Bug summary / Thread Title

If you're making a new thread, the bug summary should be the title of your thread, if it's not a new thread, include it above the rest of the bug report.

In your bug summary, you should try to explain the bug in a single sentence, as briefly as you can.

Please only add to a thread if you believe you have run into the same bug. Otherwise start a new thread, but try to keep the summary short and clear.

2. Bug description

The bug description is here to complete the information given in the summary: you can add more detail, explain what are the items within the wide terms you used (ex: if you say "[...] certain technologies [...]" in your summary, you can expand in the description by detailing "Bronze Working, Irrigation" for example.)

You can consider the bug description as a way to clear any ambiguity in your summary.

3. Steps to reproduce

This is a step by step guide to help the poor soul trying to fix the bug. It needs to list everything relevant in order to reproduce your bug.

The clearer and more detailed your steps to reproduce are, the more likely we'll be able to reproduce the issue from scratch.

(Also, bug reports usually have no-brainer steps like "Start the game", "Load a save or start a new game". Unless it's relevant to your issue, I guess you guys can spare yourself the trouble of including those steps)

4. Reproducibility

It is a score, usually out of 5, that shows how consistent the problem is.

Here's a little rundown if the different "Reproducibility":

5/5 - Consistent, happens every time with the described steps and even in other cases that might not be included in the report

4/5 - Mostly consistent, easy to reproduce but sometimes it doesn't happen

3/5 - Mostly inconsistent, feels like it happens only half of the time. At this point, it might be wise to reevaluate the steps to reproduce

2/5 - Inconsistent, it happens... sometimes. At this point, the steps to reproduce are not going to be very helpful

1/5 - Very inconsistent, basically it's either random or the steps to reproduce aren't correct

Once - It happened once. Never managed to reproduce.

5. Expected behavior

This might be the most tricky part for you guys since in some cases you can only guess what the expected behavior is.

This section is usually the part you use to describe what you think is supposed to happen and how it differs of the current state of things.

6. Notes

This is the place to shove any additional information or remark that didn't feel like it belonged anywhere else.

7. Attachments /!\

Don't forget to attach useful files if you feel like they are relevant.

• Saves are possibly the most valuable attachment you can supply, as they will help us reproduce your situation much more quickly and accurately.
• Screenshots (you can edit them to add a beautiful red circle made on MS Paint to help us identify the issue)
• Video If you want to go the extra mile, feel free to share a brief video of the issue, e.g. by uploading it unlisted on youtube.
• Diagnostic files (located by default under "\Users\[username]\Documents\Humankind\Temporary Files," select the correct file by looking at the name like "Diagnostics - 2020'10'11 @1407'46''" that gives you the date and hour which should correspond to a save file)
• Output logs (one output_log.txt located under \Users\[username]\AppData\LocalLow\AMPLITUDE Studios\Humankind\ )
• DxDiag: Attach a DxDiag report. This is only relevant if your bug has to do with crashing, artefacts or something. If it's only affecting gameplay, a DXDiag isn't necessary.
  • In Windows 7:

    1. Click on the "Start" Button.

    2. In the Search Box type dxdiag and press <Enter>. The DirectX Diagnostic Tool pop-up window should appear.

    3. Click on “Save all Information.”

    4. Save the information to your Desktop, keep the file name as is.

  • In Windows 8, Windows 10:

    1. Press the [Windows]+[R] keys on your keyboard to bring up the Run command.

    2. In the "Run" command box, type in dxdiag and press <Enter>. The DirectX Diagnostic Tool pop-up window should appear.

    3. Click on "Save all Information."

    4. Save the information to your Desktop, keep the file name as is.

!-- If your upload is larger than 4MB, there's a chance you'll encounter an error. Either compress the files into a .zip or a similar archive format (.7z / .rar) --!

Thanks for your help!

Hey everybody!

We're happy for all of you to try out the Lucy OpenDev for Humankind, and even more happy some of you take the effort to report bugs to us. That said, there are a few issues we are already aware of, so you can save yourself the time to report them:

• If you have played in the previous Steam OpenDev, please remove the registry.xml from the Documents\Humankind\Users\ directory as well as your saves directory.
• Some options in the settings menu are disabled.
• The Intro video with Jeff is not affected by volume settings.
• Some tooltips will make reference to content that is not available in this OpenDev, especially on the TechTree.
• The tile overlay when placing Districts may display wrong icons.
• The Competitive Deeds list will also display some removed content from later eras.
• AI and auto-exploring armies may ignore closed borders.
• Districts on Water Tiles may become invisible upon reloading a save.
• The "Inherited Land" option of "Land Rights" does not display its effect in the Civics Screen. (Use money instead of Influence for outposts and attaching.)
• Some tooltips may be out of date, in particular Veterancy and Extension Limit.
• "Go To" button does not work for Religious Conversion Started events.
• You may see an Industrial Era intro video when selecting an Era 5 Culture to end the game. This video may have corrupted audio.
• The Hittite Awari, Hunnic Ordu, and Mongol Orda do not use their proper 3D model
• Occasionally the game will freeze or crash when founding a city with a Settler, or when laying siege to an AI city
• Rarely, a save becomes corrupted and cannot be loaded