01-05-2021, 04:41 PM
Hi,
Still a bit hard to answer to you. But I can say something for sure, that's impossible for a BooleanFunction to return true and false in the same time. So if you saw a popup with 2 possible moves that's because 2 different conditions were true in your description at that moment.
For the RoleType related question, some roletypes can return nothing yes in some ludemes, depends of their uses and if they have sense for the ludeme. For example Each is working only for the components in the equipment and only for that. I saw in other thread you are talking about NonMover not working as expected, that's simply because that RoleType is not implemented for some cases. I did not make the NonMover RoleType, so I would not advise to use it and I can not help with it.
As a general answer you can use all the P1 to Pn (and Team1 to Teamn) with n the number of players, Prev, Mover, Next, All, Neutral, Shared safely.
The RoleType Each is only workable for the equipment and that's what we want for it.
The RoleType Player is only workable in case of a (forEach ...) iterating the players.
For the 2 last ones: Enemy and NonMover, I did not make them, so they are probably not fully implemented and can be removed/modified in the future. So for the moment, please do not use them.
I will add a short explanation on the Ludii Logic Guide for that.
For the compiler warnings, I told you in another thread, the warning will be more precise in the future, we have an idea to return the exact first argument on the expanded version which is not compiling. But that's not something on what we are working for the moment, so do not expect that soon.
----
For the other question about the value. That has changed some versions ago. The value has now to be defined in the place ludeme and not in the equipment (like for the state of a piece for example). The values of the pieces are now dynamic and not static. If you saw an example with that in the last LLR or Ludii Logic guide version please tell me where to remove it.
Regards,
Eric
Still a bit hard to answer to you. But I can say something for sure, that's impossible for a BooleanFunction to return true and false in the same time. So if you saw a popup with 2 possible moves that's because 2 different conditions were true in your description at that moment.
For the RoleType related question, some roletypes can return nothing yes in some ludemes, depends of their uses and if they have sense for the ludeme. For example Each is working only for the components in the equipment and only for that. I saw in other thread you are talking about NonMover not working as expected, that's simply because that RoleType is not implemented for some cases. I did not make the NonMover RoleType, so I would not advise to use it and I can not help with it.
As a general answer you can use all the P1 to Pn (and Team1 to Teamn) with n the number of players, Prev, Mover, Next, All, Neutral, Shared safely.
The RoleType Each is only workable for the equipment and that's what we want for it.
The RoleType Player is only workable in case of a (forEach ...) iterating the players.
For the 2 last ones: Enemy and NonMover, I did not make them, so they are probably not fully implemented and can be removed/modified in the future. So for the moment, please do not use them.
I will add a short explanation on the Ludii Logic Guide for that.
For the compiler warnings, I told you in another thread, the warning will be more precise in the future, we have an idea to return the exact first argument on the expanded version which is not compiling. But that's not something on what we are working for the moment, so do not expect that soon.
----
For the other question about the value. That has changed some versions ago. The value has now to be defined in the place ludeme and not in the equipment (like for the state of a piece for example). The values of the pieces are now dynamic and not static. If you saw an example with that in the last LLR or Ludii Logic guide version please tell me where to remove it.
Regards,
Eric