You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer
I want GP to use TileState to determine whether to protect an inventory-based block
So that there is no need to update GP when new block-based inventories are released.
This is in essence a "chore" type task given that it's a refactor, but it could be made into a feature since it would "automatically support all current and future block-based inventories without an update."
Which in that case the why can be rewritten into something like this:
As a server admin
I want GP to protect all block-based inventories without requiring updates for new blocks
So that I don't have to worry about updating GP when I update my server
Not a very good/strong why, but that's the best I can come up with offhand. So maybe I should just make a "chore" label.
Oh wait, I do have such a label, I just remembered. "Improvement."
As a developer
I want GP to use TileState to determine whether to protect an inventory-based block
So that there is no need to update GP when new block-based inventories are released.
This is in essence a "chore" type task given that it's a refactor, but it could be made into a feature since it would "automatically support all current and future block-based inventories without an update."
Which in that case the why can be rewritten into something like this:
As a server admin
I want GP to protect all block-based inventories without requiring updates for new blocks
So that I don't have to worry about updating GP when I update my server
Not a very good/strong why, but that's the best I can come up with offhand. So maybe I should just make a "chore" label.
Oh wait, I do have such a label, I just remembered. "Improvement."
#642 (comment) has some good ideas
The text was updated successfully, but these errors were encountered: