Page 1 of 1
SMALL WORLD is finally in Beta!
Posted: 16 September 2024, 22:51
by AndyM
Happy day!
Re: SMALL WORLD is finally in Beta!
Posted: 16 September 2024, 23:03
by ElNSTElN
Don't play it in real time for now, you don't get extra time!
Re: SMALL WORLD is finally in Beta!
Posted: 16 September 2024, 23:34
by Thomas
ElNSTElN wrote: ↑16 September 2024, 23:03
Don't play it in real time for now, you don't get extra time!
Seems like someone has already created a bug report:
https://boardgamearena.com/bug?id=138519
Re: SMALL WORLD is finally in Beta!
Posted: 18 September 2024, 13:55
by TheBigL7
I don't know if this qualifies as a bug, but in the first game that I played the first race pairing that I had was Sorcerers/Seafaring. When I put that race into decline, I had tokens in all three Seas & Lakes. The second race pairing that I had was Halflings/Spirit. When I went to put that race into decline, it stated that I would lose three regions, even though the Spirit ability is that it does not count towards the "1 race in decline" limit.
Now, when I actually put the race into decline it did not remove my Seafaring tokens, but I did think that the message was misleading.
Enjoyed the game-- Thanks for the implementation!
Re: SMALL WORLD is finally in Beta!
Posted: 06 November 2024, 04:29
by Stu_1977_SEmelb
TheBigL7 wrote: ↑18 September 2024, 13:55
I don't know if this qualifies as a bug, but in the first game that I played the first race pairing that I had was Sorcerers/Seafaring. When I put that race into decline, I had tokens in all three Seas & Lakes. The second race pairing that I had was Halflings/Spirit. When I went to put that race into decline, it stated that I would lose three regions, even though the Spirit ability is that it does not count towards the "1 race in decline" limit.
Now, when I actually put the race into decline it did not remove my Seafaring tokens, but I did think that the message was misleading.
Enjoyed the game-- Thanks for the implementation!
That message wasn't misleading, it was outright incorrect. That's definitely a bug. Hopefully it has been corrected by now.