-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange: player is already assigned to mission 1 through 10 #67277
Comments
It's entirely possible I have some old data somewhere - I'm using the catapult launcher which separates user data out from the game files. |
I've seen the same thing, using the fork of the CDDA Launcher. |
I can confirm this, although I get mission 1-128. |
Error is thrown at L300 of mission.cpp https://github.com/CleverRaven/Cataclysm-DDA/blob/master/src/mission.cpp#L300 |
The cause of this bug appears to be the ten starting missions being assigned to the player more than once. |
Happened to me too, in the most recent experimental version, for me the missions are 1 and 2. DEBUG : strange: player is already assigned to mission 2 FUNCTION : assign |
I think this is probably a problem that occurs with a specific MOD configuration, but the following MOD cannot be found. Fewer Soldier Extras [Fewer_Soldiers], |
I wrote those mods, so you wouldn't have them. Fewer Soldier Extras does what it says on the tin. Cute the number of soldier extras in half. Lonely Evac adds a starting scenario that is identical to the standard start minus the NPC. Other people, presumably with different mod setups, have already reported this issue. |
I tried both the latest development version and the version mentioned in the issue, but was unable to reproduce the issue. It seems that no special settings are required, but perhaps the incidence is simply low? |
I can still reproduce. At least on older worlds. |
I reinstalled the game and cleared my save files - looks like the issue is gone for me. If it's still reproducible with older saves, I feel the issue should stay open, but I don't know if it really counts as a release blocker, since it doesn't actually do much to harm things. That said, I'm not the one in charge. It's the core dev team's call. |
Most people will be reusing their old worlds and if these come with persistent errors this is not acceptable. |
Just encountered this bug in a freshly created world (created by New Game -> Play Now!) ![]() Update: stack trace:
It looks like the game is deserializing past game info from memorial files into the current avatar instance in the new world. Update: Steps to reproduce:
|
That's actually really good info. So a workaround is just to delete the memorial folder. |
Perhaps the cause of this problem lies in |
Describe the bug
DEBUG : strange: player is already assigned to mission 1
FUNCTION : assign
FILE : D:\a\Cataclysm-DDA\Cataclysm-DDA\src\mission.cpp
LINE : 300
VERSION : 6956921
Attach save file
N/A
Steps to reproduce
Expected behavior
No error messages
Screenshots
N/A
Versions and configuration
Dark Days Ahead [dda],
Bionic Professions [package_bionic_professions],
Bionic Slots [cbm_slots],
Disable NPC Needs [no_npc_food],
Fewer Soldier Extras [Fewer_Soldiers],
Slowdown Fungal Growth [no_fungal_growth],
Portal Storms Ignore NPCs [personal_portal_storms],
Lonely Evac Scenario [Lonely_Evac]
]
Additional context
No response
The text was updated successfully, but these errors were encountered: