Meta — Word Games Tactics
Evidence scope: The behavior below is from the pinned Solidity source. A source-file hash does not establish deployed bytecode equivalence. Check the selected deployment and caller before sending a transaction.
ACRONYM and UserVote are data types. UserVote’s uint8 Submissions field can represent 0–255, but that does not prove a 255-submission gameplay limit or that a 256th transaction reverts.
The pinned domain/old/nym.sol increments Submissions only while it is below 5 in the submission reward branch. Its Vote path can reset the counter when the stored round is less than or equal to RoundNumber. These are historical source rules, not evidence of a current deployed game.
The play
Section titled “The play”No current submit, vote or round-advance deployment is established by these struct pages. STRINGLIB.CheckAcronym and CheckPalindrome can check text; RandomAcronym is a separate generator. Do not turn those helpers into invented gameplay entry points or prescribe a transaction schedule without a verified implementation.
Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.
STRINGLIB.CheckAcronym(string _A, string _B)Read
Open this function to load its call form.
STRINGLIB.CheckPalindrome(string S)Read
Open this function to load its call form.
STRINGLIB.RandomAcronym(uint8 MaxLength)Simulate / call
Open this function to load its call form.