Skip to content
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

update_zombie_pos: wanted to move the blob to 86,89,0, but new location already has the small blob #39545

Closed
TempestMaiden opened this issue Apr 13, 2020 · 4 comments
Labels
stale Closed for lack of activity, but still valid.

Comments

@TempestMaiden
Copy link

Describe the bug

I'm getting a spammy error message in my most recent game, looks like something similar to a bug that was fixed before the 0.E release:

DEBUG : update_zombie_pos: wanted to move the blob to 86,89,0, but new location already has the small blob

FUNCTION : bool Creature_tracker::update_pos(const monster&, const tripoint&)
FILE : src/creature_tracker.cpp
LINE : 127

I've gotten a related error once on load involving two blobs occupying the same space.

It's not a crash or anything, the "continue" option has worked just fine every time it's popped up so far, but it's happening often enough to be annoying.

It may be related to my leading a security zombie into a blob trap and shutting the door behind me.

Steps To Reproduce

Not sure what's causing the error, so I've no idea how to reproduce it in a new game.

Expected behavior

Gameplay shouldn't be regularly interrupted by an error message.

Versions and configuration

OS: Windows 10 Home

  • Game Version: [0.E] (there's no further string listed; it's the stable.)
  • Graphics version: [Tiles]
  • Ingame language: [English]
  • Mods loaded: [core DDA, disable NPC needs]

Additional context

debug.log
ped)
Camelot.zip

@TempestMaiden
Copy link
Author

Ok, correction: now it's crashed.

crash.log

@wapcaplet
Copy link
Contributor

Sounds like #37683 again, which was resolved by #38497, but perhaps this example has a different root cause.

@stale
Copy link

stale bot commented May 16, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not 'bump' or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.

@stale stale bot added the stale Closed for lack of activity, but still valid. label May 16, 2020
@stale
Copy link

stale bot commented Jun 15, 2020

This issue has been automatically closed due to lack of activity. This does not mean that we do not value the issue. Feel free to request that it be re-opened if you are going to actively work on it

@stale stale bot closed this as completed Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Closed for lack of activity, but still valid.
Projects
None yet
Development

No branches or pull requests

2 participants