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
We have a lot of different reward or effect classes right now, whose methods all boil down to some variant of
interface WhateverEffect {
fun applyToPlayer(player: Player, context: SomeClass): Unit
}
Among these, we have
TriviaQuestionReward, which takes only a Player but also has a name: Component field.
CookieEffect, which has cancelsDefault() and its context is CookieEatenAction (stack, player, and death registry).
CakeEffect, which has cancelsDefault() and positivity, and its context is the location of the cake in the world.
These three should, at minimum, inherit from a common super-interface.
As a stretch goal, we also have BowserReward, which is different in that it rewards all players (with one player getting a special reward). It's not as similar to the others, but it's worth mentioning.
The text was updated successfully, but these errors were encountered:
We have a lot of different reward or effect classes right now, whose methods all boil down to some variant of
Among these, we have
TriviaQuestionReward
, which takes only aPlayer
but also has aname: Component
field.CookieEffect
, which hascancelsDefault()
and its context isCookieEatenAction
(stack, player, and death registry).CakeEffect
, which hascancelsDefault()
andpositivity
, and its context is the location of the cake in the world.These three should, at minimum, inherit from a common super-interface.
As a stretch goal, we also have
BowserReward
, which is different in that it rewards all players (with one player getting a special reward). It's not as similar to the others, but it's worth mentioning.The text was updated successfully, but these errors were encountered: