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

Pressing "Esc" when prompted to place batch crafted items causes them to cease to exist. #39579

Closed
mentos046 opened this issue Apr 15, 2020 · 2 comments · Fixed by #44145
Closed
Labels
<Bug> This needs to be fixed

Comments

@mentos046
Copy link

Describe the bug

When batch crafting without a designated workspace to place the items, the player is prompted to place excess items somewhere. Pressing "Esc" during this makes the items disappear,

Steps To Reproduce

  1. Batch craft 2 or more of something when not near a workspace.
  2. The first item will be wielded, replacing the in-progress craft pseudo-item, and the game will prompt the player to place the excess.
  3. Press "Esc", once for each excess item.
  4. Marvel at your ability to flout the law of conservation of mass, then despair at the fact that this ability can't do anything useful like disappearing Hulks.

Expected behavior

Perhaps it should keep prompting you to deal with the item until you do, or just default to dropping it at your feet.

Screenshots

Versions and configuration

  • OS: Windows 10 64-Bit
  • Game Version: 0.E-689-G32E6AAB
  • Graphics version: Tiles
  • Ingame language: English
  • Mods loaded: Dark Days Ahead

Additional context

This seems to occur only as a result of batch crafting while empty-handed and not adjacent to a craft spot. The game will prompt the player to place the items a number of times equal to the number of items batch crafted minus the one that ends up being wielded. Pressing "Esc" only de-atomizes one item at a time, so one can drop or store a few items while evaporating others.

@stale
Copy link

stale bot commented May 15, 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 15, 2020
@stale
Copy link

stale bot commented Jun 14, 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 14, 2020
@kevingranade kevingranade added the <Bug> This needs to be fixed label Jun 14, 2020
@kevingranade kevingranade reopened this Jun 14, 2020
@stale stale bot removed the stale Closed for lack of activity, but still valid. label Jun 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
<Bug> This needs to be fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants