Carcassonne

EVENTS

UPCOMING PAST

SOLO

PUZZLES CODE GOLF OPTIMIZATION

MULTI

LEADERBOARDS CLASH OF CODE BOT PROGRAMMING CODING ESCAPE

COMMUNITY

CONTRIBUTIONS LEARN DISCORD FORUM LIVE STREAMS

Carcassonne

Rate this contribution

+19

Make the contribution public (lvl 20+)

The contribution was not moderated in time so the system automatically rejected it.

Comments

8 Comments

CodinBot Unnamed CodinGamer

about 4 years ago

Hey CodinGamer! Your contribution has unfortunately not been moderated on time and will temporarily be removed from the system... But no worries! You can republish it anytime to give it another chance! :)

Zorg1 Unnamed CodinGamer

about 4 years ago

I don't know if you have the right to use the tileset here. Seems to be copyrighted stuff.

wlesavo Unnamed CodinGamer

about 4 years ago

I actually do have the same concern, I probably will have to change that, do not know to what though yet

wlesavo Unnamed CodinGamer

about 4 years ago

Added zooming and dragging to game viewer

tutubalin Unnamed CodinGamer

about 4 years ago

1. Codes for peasants placement and codes for links are similar, but not consistent. For example, links are 0c,1c, etc. Peasant placements are 00, 10, etc. 2. edge_type in link is redundant because: - only same edges of the same type may be linked; - information about edge type is provided in another place. 3. Basically, for peasants placement we don't need edges at all. Peasant is placed in one of the 9 tile zones: center (for cloisters and cities), 4 side zones (for roads and cities), 4 corners (for fields and cities). 4. Names of values are inconsistent: sometimes camelCase is used, sometimes snake_case is used. 5. param1 should be renamed to shield or bonus. 6. For building good strategy it is important to know which tiles exist. It should be either published somewhere, or passed to the strategy in initialization phase before Turn 1.

wlesavo Unnamed CodinGamer

about 4 years ago

UPD: param1 renamed to shield and names of parameters in statement were corrected to camelCase Thanks a lot for your comment, will correct statement and stub soon. To reply on 1, 2 and 3. Its quite clear that this description needs clarification, but ill try to show my way of thinking here, and would really like to hear public opinion on that. Format for links is chosen to make some unification, due to present of the sides of the road (1-, 1+). So its better to have "2 char" names instead of single ones. Also with such naming "-" sides can only be connected to "+" sides of the another tile. Peasant placements is chosen this way also for some simplification. Obviously one can simply use "zones" instead of edges, but you will need to store edges anyway to place tiles correctly. Using +,- and 0 instead of types here is basicaly to simplify placement for simple bots, double char for the same reason. So, to sum up, i see this type of description to be more practical one rather than consistent, but i agree that it can be misleading and probably you are right.

ABOUT US CAREERS PRIVACY FAQ BLOG

The #1 tech hiring platform

SCREENING INTERVIEWING