Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lighthouse (renamed) #344

Merged
merged 17 commits into from
Dec 19, 2024
Merged

Lighthouse (renamed) #344

merged 17 commits into from
Dec 19, 2024

Conversation

merowin
Copy link
Collaborator

@merowin merowin commented Nov 24, 2024

This is a prototype for a variant where hidden information is the main quirk. Basically what we discussed in the forum but additionally with "last known information".

The board is hidden, but stones cast rays that illuminate fields for their owner only. Any field that is not illuminated displays its last known information.

I'm trying to build it such that the observer view does not reveal any information to players. I'm not sure how to handle Ko and Self-Capture yet, since players could gain information when they receive an Error and can play another move.

grafik

I've added the possibility to change the background colour of specific fields to MulticolorGridBoard, and a new board component that uses it. I'm not sure if this is good tbh, but I wanted it to test the game class.

Also not sure if fog of war is a good name.

@benjaminpjones
Copy link
Collaborator

I'm trying to build it such that the observer view does not reveal any information to players. I'm not sure how to handle Ko and Self-Capture yet, since players could gain information when they receive an Error and can play another move.

For Ko and self capture, I think it could still be interesting to allow this information leak. The player must still risk playing a move, so there is no way to purposefully reveal the other player's position.

Of course, there may be other ways as well, such as only allowing moves in the visible area (but this seems much too limiting)

Also not sure if fog of war is a good name.

I think it's fine. One concern would be that there seem to be discussions of fog of war go online with various rulesets, but there is no consensus so I think it's fine to have our own. The whole "board is hidden until stones are played" seems to be the common theme.

@merowin
Copy link
Collaborator Author

merowin commented Nov 26, 2024

For Ko and self capture, I think it could still be interesting to allow this information leak. The player must still risk playing a move, so there is no way to purposefully reveal the other player's position.

I'm thinking to keep the standard behaviour for Ko, but allow self-capture. I want it to be risky to play into the unknown, and that having more visibility is a relatively significant factor.

I think it's fine. One concern would be that there seem to be discussions of fog of war go online with various rulesets, but there is no consensus so I think it's fine to have our own. The whole "board is hidden until stones are played" seems to be the common theme.

Its a very broad name, also I'm slightly annoyed about causing spaces in the url govariants.com/variants/fog of war/demo 😅

@merowin merowin changed the title Fog of war Lighthouse (renamed) Dec 4, 2024
@merowin
Copy link
Collaborator Author

merowin commented Dec 4, 2024

I'm pretty happy with this now. I decided to rename it to lighthouse, because I feel this name incorporates the ideas well, and it reminds me of the chess variant "bughouse" 😆
Also updated the visibility rules such that (hopefully) the observer state doesn't reveal any information to players.
Tweaked the colors some:

Blacks perspective:

grafik

Whites perspective:

grafik

The stones in shaded areas were revealed by a "collision".

@merowin merowin marked this pull request as ready for review December 4, 2024 17:35
@merowin merowin merged commit 7e73570 into main Dec 19, 2024
3 checks passed
@merowin merowin deleted the fog_of_war branch December 22, 2024 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants