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

Customizable spheres #2

Closed
jakubg1 opened this issue Jul 22, 2020 · 1 comment
Closed

Customizable spheres #2

jakubg1 opened this issue Jul 22, 2020 · 1 comment
Assignees
Labels
D: Change/Suggestion A change to an existing feature. R: Implemented A suggestion has been added into the code.

Comments

@jakubg1
Copy link
Owner

jakubg1 commented Jul 22, 2020

Sphere colors are hardcoded right now. The preferred indexing is as follows:

  • Negative numbers are used for special balls (lightning, wild, fireball).
  • 0 should be reserved for the vise in paths and for the empty sphere in shooters.
  • Positive numbers are normal sphere colors.

A given sphere should have at least the following parameters:

  • sphere image file,
  • text image file (for broken spheres),
  • color bomb image file,
  • next sphere image file (for shooters),
  • RGB color (for reticals) -> defined in main.lua:23, used in Shooter.lua:118,
  • a list of spheres which match the given sphere -> Session.lua:98,
  • an interaction type on touch (append to the chain, destroy surrounding spheres etc.) -> ShotSphere.lua:41,
  • an interaction type on shoot (lightning balls work instantly) -> Shooter.lua:70,
  • a particle path for idle spheres in the shooter,
  • a sound event when the sphere is shot,
  • a sound event when the sphere touches a train,
  • whether a sphere can appear in the shooter.

Additionally, when implementing remember to look at the sphere counting algorithm (Session.lua:46, Session.lua:82).

@jakubg1 jakubg1 added D: Feature Request A feature that may be implemented in a future version. R: Open D: Change/Suggestion A change to an existing feature. and removed D: Feature Request A feature that may be implemented in a future version. labels Jul 22, 2020
@jakubg1 jakubg1 added this to the Full 1.0 release milestone Dec 22, 2020
@jakubg1 jakubg1 added R: Implemented A suggestion has been added into the code. and removed R: Open labels Jan 13, 2021
@jakubg1 jakubg1 self-assigned this Jan 13, 2021
@jakubg1
Copy link
Owner Author

jakubg1 commented Jan 13, 2021

Fully implemented: 40790f1 913e9f0 3f30ed3

@jakubg1 jakubg1 closed this as completed Jan 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
D: Change/Suggestion A change to an existing feature. R: Implemented A suggestion has been added into the code.
Projects
None yet
Development

No branches or pull requests

1 participant