Dean Herbert f443cfb93e Move blueprint validity conditions to allow more correct external usage of EndPlacement ... Until now, these were haphazardly enforce inline in blueprint implementations. The only thing stopping complete breakage is that `EndPlacement` wasn't called (too much) from outside the blueprint, leaving them responsible for their own placement. By moving this conditional out of the provided paramters to `EndPlacement`, it allows more flexible usage of that method externally. Coming in a future PR.		2023-05-12 16:02:22 +09:00
..
Components	remove redundant zero check in sv calculation	2023-05-02 12:29:11 +02:00
BananaShowerPlacementBlueprint.cs	Move blueprint validity conditions to allow more correct external usage of EndPlacement	2023-05-12 16:02:22 +09:00
BananaShowerSelectionBlueprint.cs	Remove #nullable disable from Catch.Edit namespace	2023-01-15 17:29:32 +09:00
CatchPlacementBlueprint.cs	Remove #nullable disable from Catch.Edit namespace	2023-01-15 17:29:32 +09:00
CatchSelectionBlueprint.cs	Remove #nullable disable from Catch.Edit namespace	2023-01-15 17:29:32 +09:00
FruitPlacementBlueprint.cs	Remove #nullable disable from Catch.Edit namespace	2023-01-15 17:29:32 +09:00
FruitSelectionBlueprint.cs	Remove #nullable disable from Catch.Edit namespace	2023-01-15 17:29:32 +09:00
JuiceStreamPlacementBlueprint.cs	Move blueprint validity conditions to allow more correct external usage of EndPlacement	2023-05-12 16:02:22 +09:00
JuiceStreamSelectionBlueprint.cs	Remove redundant canBeNull: true	2023-01-15 23:11:59 +09:00