b5db24553e
Spotlights do not cast shadows
...
This really helps the framerate... to an extent
1 year ago
6f613d730e
Undo temporary board change -- oops!
1 year ago
9f3b9151b3
Fixed dissolve for pieces crossing canal
1 year ago
c319ecab61
Just left click (now for de-selecting pieces)
1 year ago
9c396e3183
Loading is fixed and merging is partially fixed
...
Still have to get rid of one of the two merged pieces
1 year ago
82b1f00d14
loading is blocking again
...
Thank glob.
1 year ago
2295de0043
Loading is borked, but tutorial worked...
1 year ago
2a33dd7464
Revert to old game board
2 years ago
0c56bd18a1
Wait I think merging works?! fuck yeah.
2 years ago
098df2998b
Fixed moves correctness!
...
Sans merging which we still haven't wired into the real game...
2 years ago
80738dd217
Merging moves implemented ish
...
At least on the backend. Not sure they're rendered.
God bless test driven development, amirite?
2 years ago
40b40ae887
Tests pass
...
Feels good man
2 years ago
33f37d57c4
I think it's working again
...
*wipes brow* thank god.
2 years ago
2fb524643d
Saving place. Broken but don't want to go further...
2 years ago
b86aea043e
Parsing board from ascii
...
Mostly useful for testing!
2 years ago
6e2d96a17b
audio intensity
2 years ago
1a056277c9
Fixed a small amount of jank with the alpha on the title
...
Still a small amount of alpha jank on buttons sadly...
2 years ago
a0c50a88c6
Slightly improved valid move indicator, title rendered text
2 years ago
3d6ca40e67
There are some bugs in the rewrite, need some elbow-grease to iron them out
2 years ago
3157666d84
Re-architecture for moves
...
Now that moves are a bit more complicated I did a pass at calculating
which moves are valid for a given piece.
The speed/memory usage on this version is likely higher, but we're
dealing with really small numbers of moves so I'm not worried about
it. Optimizations should be simple if I look for them.
As for the re-architect, we generate a list of possible moves for a
piece, check that against some candidates spot, and if it _could_ be a
valid move, we do additional checks like if this is a capture, if this
is an invalidating move, or if this would "Jump" (which was my main goal
with this refactor).
2 years ago
f0befe0928
Queen "no jumping" is _mostly_ implemented.
...
You can still jump over enemies which is BS.
That is going to require some... magic... to fix.
2 years ago
0edfcfec5b
Drone has "no jumping" implemented
2 years ago
0972d2ef91
Welp I broke something...
2 years ago
c9cf364c13
Saving my place before making a big change
...
Going to try simplifying the piece updating logic into one method
2 years ago
618d0c87b4
Remove examples
...
Too much work to maintain wrt upgrades
2 years ago
023dd9dc00
Clippy fixes
2 years ago
877f7001b1
Mostly updated to bevy 0.13
2 years ago
d3c2289d41
why you no iter_many_mut().for_each()???
2 years ago
a7ffd6e0f9
Button images rough implementation
...
Tuning font sizing and need to add font changes upon interaction
2 years ago
8e2d4ab7af
Still not sure how to get rid of fog at startup...
2 years ago
ca95bf46ec
escape is handled gracefully in most situations
2 years ago
1ffb34b93b
Well I got endgame working, then I kept going
...
Probably broke something, but I'm working on escape handling in
different contexts. Mostly going to the "expected" menu.
2 years ago
aef8c719f2
tutorial menu works
2 years ago
3091a15dea
main menu works!
2 years ago
4b5c90f1ba
saving my place working on menus
...
Also refactored my custom any_component_X methods to act more like other
conditionals
2 years ago
5fc0706c10
Saving my place
...
Adding a little 'just_pressed' helper for system conditionals
Replaces that lambda I kept using all over the place
2 years ago
82b817a614
State management refactor
...
Have not run this, almost certain things are broken.
The general idea is we mark entities with components and have a general
purpose "OnStateChange" trigger that marks all "active state" entities
as visible and all "inactive state" entities as invisible.
This should simplify state management -- unless of course there are
exceptions which there will be and will require having some sort of
"Sticky<T>" component that says "When this state transition occurs,
don't touch this one entity"
2 years ago
80ee571cb1
it is ugly, but it works. Intro is idempotent
2 years ago
59755d2bdd
cargo fmt
2 years ago
666609e419
Not sure why, but resetting is not as elegant as I had hoped
...
This is definitely the right approach, but why is everything becoming
red??
2 years ago
dc981aafea
cargo fmt
2 years ago
e6be125c7d
Fixed placing captured pieces on the side of the board
2 years ago
54167d1f5f
factor in piece when scoring
2 years ago
f9197ab157
Merge PlayState with Side
2 years ago
983314faac
Fixed "reject move" logic.
...
Added a system for tracking a pieces last move, which is not
necessary...
2 years ago
438358aab2
Endgame kinda sorta implemented...
2 years ago
0e2308929c
cargo fmt
2 years ago
18f3797340
Adding endgame tracking
2 years ago
fe2e023036
cargo fmt
2 years ago
609ae8ebb9
In a good-ish spot, going to save
2 years ago
Elijah C. Voigt