LagosLife’s 28 October governorship ballot now has a third official notice worth reading alongside the original rules. On 29 October, the game’s account said it was reviewing votes and removing bot activity before publishing verified counts. That adds an integrity review to the earlier voting-error report; it does not supply a final winner. [3]
Three notices, three different questions
| Notice date | What it says |
|---|---|
| 28 October, 18:23 UTC | Voting scheduled for 8:05 PM that day, for 24 hours; valid rented or owned property required in the state. |
| 28 October, 20:30 UTC | Some players could not vote; the team was working on it and would extend the end time if necessary. |
| 29 October, 11:10 UTC | The operator said votes were being reviewed, bot activity removed and verified counts would be published later. |
The opening-time post did not identify a timezone. The failure notice made an extension conditional, without a replacement deadline. The review notice did not publish a final count, an appeal outcome or a new closing time. None of those missing details should be filled in by treating an old “tonight” poster as current. [1] [2] [3]
What the bot-review announcement establishes
The official account said some people had tried to manipulate the election with bots and that it had the data to identify the activity. It said every vote was under continuing review and promised verified counts at the end. These are the operator’s statements about its process; we have not audited its records or independently measured fraudulent votes. [3]
A changing scoreboard can prompt questions, but a screenshot alone does not establish which votes were invalid or who caused a problem. Keep a campaign’s claims, the live numbers someone captured and the operator’s final results in separate categories. A confident player post is not a substitute for the promised verified tally.
The original home rule still explains eligibility
The opening announcement allowed voting in a state where the player held a valid property, rented or owned. Renting therefore counted in the announced rule. It also required real, active players and said fake votes would not count. The post did not give a universal candidacy fee or a salary for the winners. [1]
For a future race, check the property recorded on your account rather than assuming a visit to someone’s mansion makes you resident. For this particular race, first check the current election panel. Our 1 November source review did not verify a still-open ballot or a completed result.
If your own vote is the issue
- Record the election, state and exact message shown on your account.
- Keep the screenshot’s date and timezone; an old capture should stay labelled as old.
- Check whether the game already records a vote before repeatedly trying to cast another.
- Use the official support route for account-specific errors, without publishing passwords or recovery details.
Those steps make a report easier to investigate; they are not a tested workaround. The original error notice confirms a problem affected some players, but it does not show that buying a second house, moving cities or repeating the same action will fix it.
What would close the story?
A dated official publication of verified totals would resolve the results question. A separate confirmed schedule would resolve any extension. Until then, the fair update is narrower: the operator acknowledged the voting failures and later described an ongoing integrity review. We have added that notice while preserving the original dates and the limits of the evidence.
