reimplement marble behavior, making it more consistent in different directions. Triggers no longer activate from blocked marbles, and bounces take the same amount of time to travel through a chain of marbles in all directions
This commit is contained in:
parent
82d0ff0f37
commit
ae4e84bb90
4 changed files with 167 additions and 100 deletions
|
@ -4,10 +4,12 @@
|
|||
logic mostly like https://git.crispypin.cc/CrispyPin/marble
|
||||
|
||||
## todo
|
||||
make marble movement not order-dependent (`>ooo <` does not behave symmetrically)
|
||||
(more levels)
|
||||
story/lore
|
||||
blueprints
|
||||
scroll level list
|
||||
|
||||
should the output tile consume marbles like the bag instead of needing power? then input and output could be merged to one tile type
|
||||
make marble movement more consistent (`>o o<` depends on internal marble order)
|
||||
decide on marble data size (u32 or byte?)
|
||||
blueprint rotation
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue