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

Banishing a robot leaves behind a broken robot #64530

Closed
Standing-Storm opened this issue Mar 24, 2023 · 1 comment
Closed

Banishing a robot leaves behind a broken robot #64530

Standing-Storm opened this issue Mar 24, 2023 · 1 comment
Labels
(S1 - Need confirmation) Report waiting on confirmation of reproducibility stale Closed for lack of activity, but still valid.

Comments

@Standing-Storm
Copy link
Contributor

Describe the bug

When using a spell with the "banish" effect, like Lesser Banishment or Greater Banishment from Magiclysm, on a robot, the robot is destroyed successfully but still leaves loot behind, unlike other monsters who leave behind no corpse or loot.

Attach save file

N/A

Steps to reproduce

  1. Start a world with Magiclysm enabled
  2. Debug in the Greater Banishment spell to max
  3. Spawn in a TALON UGV
  4. Cast Greater Banishment
  5. Broken Secubot and other loot remains

Expected behavior

Banishment removes all loot, the same as when used on other targets.

Screenshots

image
image
image

Versions and configuration

  • OS: Windows
    • OS Version: 10.0.19044.2728 (21H2)
  • Game Version: 12abc70 [64-bit]
  • Graphics Version: Tiles
  • Game Language: English [en]
  • Mods loaded: [
    Dark Days Ahead [dda],
    Disable NPC Needs [no_npc_food],
    Portal Storms Ignore NPCs [personal_portal_storms],
    No Fungal Growth [no_fungal_growth],
    Bionic Professions [package_bionic_professions],
    Magiclysm [magiclysm]
    ]

Additional context

No response

@Standing-Storm Standing-Storm added the (S1 - Need confirmation) Report waiting on confirmation of reproducibility label Mar 24, 2023
@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot added the stale Closed for lack of activity, but still valid. label Apr 23, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
(S1 - Need confirmation) Report waiting on confirmation of reproducibility stale Closed for lack of activity, but still valid.
Projects
None yet
Development

No branches or pull requests

1 participant