You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2024. It is now read-only.
Currently the platoon assignments follow the order of the platoons. This may result in the following situation:
A certain member can bring a rare unit, say Bindo
That member gets assigned 10 other units before the system reaches a Bindo
The system will then think that it cannot fill in that Bindo
Suggestion, if possible: The script should prioritize rare units in platoons, when their corresponding platoons can be filled. It could perhaps order the units based on their rarity, then assign members to them in that order starting from the most rare units.
The text was updated successfully, but these errors were encountered:
@PopGoesTheWza I believe we could count the amount of characters by rarity, for the side, then sort by rarity for that phase. Then do a lookup assignment in that order, for a defined amount of rare units. lets say the first 5 rare items, then the rest could be as normal
Let aside the special case of Ships (where unit GP is only relevant for those with the alignment which can participate in CM/SM...)
I sense we need multiple passes to properly identified which platoons to fill and which to skip, with an optimal/fair distribution.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the platoon assignments follow the order of the platoons. This may result in the following situation:
Suggestion, if possible: The script should prioritize rare units in platoons, when their corresponding platoons can be filled. It could perhaps order the units based on their rarity, then assign members to them in that order starting from the most rare units.
The text was updated successfully, but these errors were encountered: