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
I would like to propose some changes to the Rumour enum, as in it's current state it has booleans for whether or not it's a novice, adept ...etc rumour.
However, these booleans are never actually used and don't make too much sense even if they were used.
Because even if some rumour is an adept rumour, it doesn't necessarily have to mean both adept hunters are able to assign these.
So what I'd propose us doing is change these booleans to be a list of possible hunters that can assign these rumours.
Which means that once we get our side panel up and running, we could add a tab that can list out these rumours per hunter (or vice versa).
The text was updated successfully, but these errors were encountered:
I would like to propose some changes to the Rumour enum, as in it's current state it has booleans for whether or not it's a novice, adept ...etc rumour.
However, these booleans are never actually used and don't make too much sense even if they were used.
Because even if some rumour is an adept rumour, it doesn't necessarily have to mean both adept hunters are able to assign these.
So what I'd propose us doing is change these booleans to be a list of possible hunters that can assign these rumours.
Which means that once we get our side panel up and running, we could add a tab that can list out these rumours per hunter (or vice versa).
The text was updated successfully, but these errors were encountered: