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

Fix spells crashing when they can't find a target. #36507

Merged
merged 3 commits into from
Dec 28, 2019

Conversation

BevapDin
Copy link
Contributor

SUMMARY: None

Fixes #34813.

This handles the case when no target point can be found.

Changed all callers accordingly to ignore the action when no target has been found.
…l. They sound similar, but they are not exactly the same. Thanks for the reminder.

Co-Authored-By: Anton Burmistrov <[email protected]>
@KorGgenT KorGgenT added <Bugfix> This is a fix for a bug (or closes open issue) [C++] Changes (can be) made in C++. Previously named `Code` Mods: Magiclysm Anything to do with the Magiclysm mod labels Dec 28, 2019
@ZhilkinSerg ZhilkinSerg merged commit 311b795 into CleverRaven:master Dec 28, 2019
@BevapDin BevapDin deleted the bpo branch December 28, 2019 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
<Bugfix> This is a fix for a bug (or closes open issue) [C++] Changes (can be) made in C++. Previously named `Code` Mods: Magiclysm Anything to do with the Magiclysm mod
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Casting spell with "RANDOM_TARGET" without a valid target in range leads to fatal crash
4 participants