Skip to content

Instantly share code, notes, and snippets.

@stowball
Last active July 28, 2023 22:46
Show Gist options
  • Save stowball/e6f787ec92b802faf8f947cced9a634c to your computer and use it in GitHub Desktop.
Save stowball/e6f787ec92b802faf8f947cced9a634c to your computer and use it in GitHub Desktop.
ChatCPT rules help

The game contains various cards, each containing a flower, such as Red Daisy. The Red Daisy card appears multiple times, but 1 of them has a Bee on it. The aim of the game is for players to draft and arrange flower cards in a 3x3 grid to achieve the highest score.

When players place a flower card with a bee, they score 1 point for each adjacent card that has an identical flower as the one with the bee. I'd like to write this rule succinctly, starting with "Earn 1 point…" ChatGPT


Earn 1 point for each adjacent card that shares the same flower type as the card with the Bee.


I came up with this: "Earn 1 point for each identical flower that is adjacent to a flower with a bee". Which do you think is clearer? Or is there another better version? ChatGPT


Both versions are clear and convey the same meaning effectively. However, I would suggest a slight modification to make the rule even more concise and straightforward:

"Score 1 point for each adjacent card with the same flower as the one with a Bee."

This version keeps the key elements intact while eliminating unnecessary words. It clearly states that you earn a point for each adjacent card that shares the same flower type as the card with the Bee. It's concise and easy to understand. But if you prefer your original version, it is also perfectly fine! Ultimately, the most important thing is that the rule is clear and understandable for all players.


That's good. I think I'll go with this slight adjustment: "Earn 1 point for each adjacent card with the same flower as one with a Bee" ChatGPT Great choice! Your adjusted version, "Earn 1 point for each adjacent card with the same flower as one with a Bee," is clear and concise. It effectively communicates the scoring mechanism without unnecessary complexity. Players will easily understand how to score points when playing your card game.

Players can plant up to 9 tulip cards in a 3x3 grid. There are 10 tulips in the game, 2 each of 5 separate colours. Players score points based on how many orthogonally adjacent tulips they have in their grid. However, if 2 identically coloured tulips are together, only the "first" one counts towards your score. However, I'm not sure how to explain that. I currently have "Adjacent, identically coloured tulips do not count towards your adjacency score", but this makes it sound like neither of the adjacent tulips score. Can you help?


Certainly, I can help clarify this rule in a way that avoids potential confusion. To make it clear that only one of the identically colored tulips counts towards the adjacency score, you can rephrase the rule as follows:

"Only the first adjacent tulip of each color counts towards your adjacency score. If you have two or more identically colored tulips together, only the one that is closest to the center of your grid counts."


That's an improvement, yet the centre has nothing to do with it. Another problem is that the one that doesn't score effectively stops the adjanceny count. So, for instance, if a player had 7 tulips (starting from row 1, column 1, and then travelling right around the outside of the grid to row 3, column 1) and two identical tulips were in row 2, column 3, and row 3, column 3, they would lose out on scoring 3 tulips, because the second one "broke" the adjacency


Thank you for providing more context about the adjacency rule. I understand the concern about the "breaking" of adjacency in the current wording. Let's try to clarify the rule to avoid this issue:

"When scoring adjacency for identically colored tulips, only count the one that is part of the longest continuous chain of adjacent tulips of that color. If two or more identically colored tulips are together, only the one in the most extended chain will count towards your adjacency score."

With this revised explanation, players will understand that they should look for the longest continuous chain of adjacent tulips of each color. If there are multiple identical tulips together, only the one in the longest chain will contribute to their adjacency score. This way, players won't miss out on scoring tulips just because of the placement of identical tulips nearby.


Hmmmm how about this:

If two identically coloured tulips are adjacent to each other, only one of them counts towards your total and may prevent other tulips from scoring if the non-scoring tulip breaks the continuous chain of adjacent tulips. ChatGPT


Your rephrased rule is clear and concise, effectively conveying the impact of having two identically colored tulips adjacent to each other. It addresses the issue of the non-scoring tulip breaking the continuous chain of adjacent tulips, which can prevent other tulips from contributing to the player's total score.

So the final rule would be:

"If two identically colored tulips are adjacent to each other, only one of them counts towards your total, and the non-scoring tulip may prevent other tulips from scoring if it breaks the continuous chain of adjacent tulips."


Brilliant. I'll change it slightly to make shorter sentences like so:

If two identically coloured tulips are adjacent to each other, only one of them counts towards your total. The non-scoring tulip may prevent other tulips from scoring if it breaks the continuous chain of adjacent tulips.


Excellent! Your revised version is clear and concise, breaking down the information into two separate sentences for better readability and understanding. Shorter sentences often help players grasp the rules more easily, making your card game's rules more approachable and enjoyable.

This phrasing effectively explains the adjacency rule and its implications without overwhelming the players with dense text. It will help ensure that players can enjoy the game with a good understanding of the scoring mechanics.


This phrasing effectively explains the adjacency rule and its implications without overwhelming the players with dense text. It will help ensure that players can enjoy the game with a good understanding of the scoring mechanics.


Certainly! To make the scoring reference cards more concise and accurate, you can use the following text:

"Score: Count your largest chain of unique adjacent tulips. Ignore duplicates."

This condensed version captures the essence of the adjacency scoring rule while remaining succinct enough to fit on the reference cards with limited space. Players will understand that they should look for the longest chain of unique, adjacent tulips, and that duplicates are not counted.


Instead of "ignore duplicates" , how about "Duplicates excluded"? Does that sound even clearer?


Yes, "Duplicates excluded" sounds even clearer and more explicit than "skip duplicates." It effectively conveys the idea that duplicates are not included in the scoring without leaving any room for confusion. Players will understand that only one of the identical tulips will be considered for scoring, while the duplicates are excluded from the final count.

So, the revised scoring reference card text would be:

"Score: Longest unique chain of adjacent tulips. Duplicates excluded."


How about: "Score: Longest chain of adjacent tulips. Adjacent duplicates excluded."? Does removing unique in the first sentence make it better or worse?


"Score: Longest chain of adjacent tulips. Adjacent duplicates excluded." is a clear and concise version that effectively conveys the scoring rule. Removing "unique" from the first sentence does not make it worse; in fact, it streamlines the text while retaining its clarity.

With this phrasing, players will understand that they need to aim for the longest chain of adjacent tulips in their garden. Additionally, it explicitly states that adjacent duplicates are excluded from the scoring, leaving no room for confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment