Skip to content

Add Azul game implementation #1347

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

fenghaolw
Copy link

Azul: https://boardgamegeek.com/boardgame/230802/azul

Please review carefully :) I haven't written C++ in years.

I am using Apple M4 so forked #1335 to get it compiling. The .gitignore change is to ignore clangd caches (am I the only one who ran into this?)

@lanctot
Copy link
Collaborator

lanctot commented Jun 4, 2025

Wow.. thanks!

This is great.

It might be a bit hard to merge right away due to reasons listed in #770

But, we recently had a success story with Hive and was able to pull it in as a result (we contacted the publishers and they gave us permission). It'd be great if we could do it again here. There are 20+ publishers are listed on the BGG page.. I wonder if you know a "main" one that we can contact.. do you know?

@lanctot
Copy link
Collaborator

lanctot commented Jun 4, 2025

Looked a bit into the publisher.. Asmodee is listed. This could be good news. Hanabi was one we previously got permissions for and it's also published by Asmodee. So it's possible that we could get permission for this one too.

But, it is something that we would need your help to take on. Let me know what you think.

@fenghaolw
Copy link
Author

Makes sense, hadn't considered the legal implications 😢

I am happy to take on this if you can give me some pointers. (I work at Google too, if that helps anything :) I assume the primary part is contacting the publishers though)

@lanctot
Copy link
Collaborator

lanctot commented Jun 5, 2025

Please revert install.sh as the new abseil still causes some tests to fail on Github CI. (I will try to find time to fix that properly in master-- next week I hope -- as you're the second person to have been blocked by this)

@lanctot lanctot added the legal Potential risk, we can discuss with our legal team label Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legal Potential risk, we can discuss with our legal team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants