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

Warlock no longer immobilized during Psyblast #16966

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Runian
Copy link
Contributor

@Runian Runian commented Jan 21, 2025

About The Pull Request

Warlock is no longer immobilized when casting with their psyblast ability.

Why It's Good For The Game

Makes it consistent with how Pyrogen can cancel their fireball ability. It is also annoying when you misclick or get shuffled so you just shoot into a wall and waste your cooldown.

Changelog

🆑
balance: Warlock is no longer immobilized when casting with their psyblast ability.
/:cl:

@Lumipharon
Copy link
Contributor

Warlock was balanced around having to immobilize to make it vulnerable while casting... but psyblast has been nerfed into the ground so eh, enjoy the slop I guess

@Runian
Copy link
Contributor Author

Runian commented Jan 22, 2025

Warlock was balanced around having to immobilize to make it vulnerable while casting... but psyblast has been nerfed into the ground so eh, enjoy the slop I guess

I will enjoy the slop. 👍

@ivanmixo
Copy link
Contributor

ivanmixo commented Jan 22, 2025

Wonderful, it's not only gonna be edge of screen gameplay, it'll also be able to kite with it. Do we really need to make warlock even more risk free and unkillable?

@TiviPlus TiviPlus added the Balance Changes to functionality that modifies how effective certain methods are at powergaming. label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Balance Changes to functionality that modifies how effective certain methods are at powergaming.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants