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.

Sign up for GitHub

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

Jump to bottom

Refactor Spells #3

Open
nikolawhallon opened this issue Jun 1, 2022 · 0 comments
Open

Refactor Spells #3

nikolawhallon opened this issue Jun 1, 2022 · 0 comments

Comments

@nikolawhallon
Copy link
Collaborator

There is a lot of code duplication with Spells. Spell could be a class, to help remove some of this duplication. A Spell would need:

  • a "word" to cast the spell ("fire", "lightning", "ice")
  • a range for how many to cast (say, ~2-5, ~4-8, etc)
  • a list of ranges of angles to cast
  • a path to the Scene to spawn
  • integers for keeping track of how many spells there are currently, and max

Some questions are:

  • who should be responsible for spawning? the class itself?
  • how should UI updates happen? should the class objects be sent to the HUD once per frame? how tightly coupled should the objects and HUD be?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nikolawhallon