00:00
[Zomis/Games] 9 commits. 3 opened issues. 4 closed issues. 6 issue comments. 408 additions. 97 deletions.
8 hours later…
08:40
[Zomis/Games] GustaMagik added label game-splendor to issue [#80: [Splendor] Mark selection of gems from bank](github.com/Zomis/Games/issues/80)
[Zomis/Games] GustaMagik added label game-hanabi to issue [#79: [Hanabi] [Idea/suggestion] Highlight most recently played card / discarded card](github.com/Zomis/Games/issues/79)
[Zomis/Games] GustaMagik edited issue [#79: [Idea/suggestion] Highlight most recently played card / discarded card](github.com/Zomis/Games/issues/79)
[Zomis/Games] GustaMagik added label game-splendor to issue #85: Splendor: Show round number indicator
[Zomis/Games] GustaMagik added label game-splendor to issue #81: Remove bottom most display of active player
[Zomis/Games] GustaMagik added label game-hanabi to issue [#77: [Hanabi] Swap way of showing active player to be highlighted border](github.com/Zomis/Games/issues/77)
[Zomis/Games] GustaMagik edited issue #77: Swap way of showing active player to be highlighted border
[Zomis/Games] GustaMagik added label game-splendor to issue [#76: [Splendor] Change Noble claiming visuals](github.com/Zomis/Games/issues/76)
> This might be a feature that all games want.
A toggleable transaction log:
Player A made move X
Player B made move Y
...
A toggleable transaction log:
Player A made move X
Player B made move Y
...
[Zomis/Games] GustaMagik added label game-hanabi to issue #71: Hanabi: Change view of discarded cards
[Zomis/Games] GustaMagik added label game-hanabi to issue [#60: [Hanabi] Investigate if yellow clue is not properly displayed](github.com/Zomis/Games/issues/60)
[Zomis/Games] GustaMagik added label game-hanabi to issue #59: Watching the game as a guest is confusing
[Zomis/Games] GustaMagik added label game-hanabi to issue [#51: [Hanabi] Remove user icons on top](github.com/Zomis/Games/issues/51)
[Zomis/Games] GustaMagik added label game-hanabi to issue [#54: [Hanabi] Make it more ovious when the game has ended](github.com/Zomis/Games/issues/54)
[Zomis/Games] GustaMagik added label game-hanabi to issue [#50: [Hanabi] Mimic table seating for more intuitive UX](github.com/Zomis/Games/issues/50)
[Zomis/Games] GustaMagik added label game-hanabi to issue [#49: [Hanabi] On player turn, indicate with ring bell sound](github.com/Zomis/Games/issues/49)
[Zomis/Games] GustaMagik created comment on issue #49: On player turn, indicate with ring bell sound
1 hour later…
10:41
[Zomis/Games] Zomis added label site-wide to issue [#79: [Idea/suggestion] Highlight most recently played card / discarded card](github.com/Zomis/Games/issues/79)
[Zomis/Games] Zomis added label site-wide to issue #77: Swap way of showing active player to be highlighted border
[Zomis/Games] Zomis added label lobby to issue [#55: [Guest] Possibility to swap display name](github.com/Zomis/Games/issues/55)
[Zomis/Games] Zomis added label site-wide to issue #54: Make it more obvious when the game has ended
[Zomis/Games] Zomis added label site-wide to issue #49: On player turn, indicate with ring bell sound
[Zomis/Games] Zomis added label site-wide to issue #43: Highlight most recent move (for each player?)
2 hours later…
12:49
[Zomis/Games] build for commit b4b333d5 on dependabot/npm_and_yarn/games-vue-client/acorn-6.4.1: This commit cannot be built
13:48
@Duga Week 1756: (Not that you have asked but still). Days exercising online with a friend, only one. Knees hurting, one. Days of knees hurting, three. Factorio played, only once I think. Projects renamed, one. Work on ZomisGames done, A LOT. Friends helping out with ZomisGames, one. Games implemented in ZomisGames, one (Splendor). One day late Current Covid-19 stats: 4834449 / 319031 / 1801461. Covid-19 in Sweden, 30799. Active Covid-19 cases worldwide: 2713957 (+292303 since last Monday).
2 hours later…
1 hour later…
And one of the things I like and dislike about tabletops is excatly that, rules are not enforced. I've played a lot of Marvel Legendary and sometimes a rule is not clear or understandable to me, I have no way of knowing how to properly play it. Yes sometimes it's nice to bend the rule as you like it to make it more fun, but most of the times I just want to be sure of the rule.
> In some games - such as Splendor - an action is related to a card, like "Buy card". However, a card can not easily be serialized always for the purpose of storing in database (or sometimes even sending to frontend).
So implement a way to make it possible to still use the card object in the DSL, but have a way to serialize the card so that it can be stored in the database. Going from the database information to the card object is then possible by enumerating all possible actions (which is do
So implement a way to make it possible to still use the card object in the DSL, but have a way to serialize the card so that it can be stored in the database. Going from the database information to the card object is then possible by enumerating all possible actions (which is do
> It's probably very often easier to define a game by its rules rather than saying when each possible action is allowed.
Especially in games like Splendor where you can't do that much if you have 10 or more tokens (only discard, basically). Currently in Splendor this is copy-pasted a bit: `isCurrentPlayer(it) && it.game.currentPlayer.chips.count <= it.game.config.maxMoney` among other things.
Some effects are duplicated as well, such as `it.game.endTurnCheck()`.
Possible structure could
Especially in games like Splendor where you can't do that much if you have 10 or more tokens (only discard, basically). Currently in Splendor this is copy-pasted a bit: `isCurrentPlayer(it) && it.game.currentPlayer.chips.count <= it.game.config.maxMoney` among other things.
Some effects are duplicated as well, such as `it.game.endTurnCheck()`.
Possible structure could
> At the moment there is a lot of this pattern in the game code (Splendor and Hanabi):
val state = scope.replayable().string("card") {
game.deck.cards.first { it.level == card.level }.toStateString()
}
val replacementCard = game.deck.findState(state) { it.toStateString() }
game.deck.card(replacementCard).moveTo(game.board)
Basically:
1. Get state of cards to use
2. Lookup the cards to use based on the state
3. Do something with cards
This occurs in: Sple
val state = scope.replayable().string("card") {
game.deck.cards.first { it.level == card.level }.toStateString()
}
val replacementCard = game.deck.findState(state) { it.toStateString() }
game.deck.card(replacementCard).moveTo(game.board)
Basically:
1. Get state of cards to use
2. Lookup the cards to use based on the state
3. Do something with cards
This occurs in: Sple
21:08
[Zomis/Games] Zomis pushed commit 9ce0555d to master: Fix bug with probability calculations considering duplicate assignments
[Zomis/Games] Zomis pushed commit ee037f88 to master: Adjust Hanabi probability AI calculations, in need of further adjustment
« first day (2117 days earlier) ← previous day next day → last day (1742 days later) »
