Dunedan

That 2.9Wh is only for inference and does exclude the vast amount of energy, which is required to train the models. Thanks to "AI" a nuclear power plant is re-opening for Microsoft (https://edition.cnn.com/2024/09/20/energy/three-mile-island-microsoft-ai/index.html) and Google's emissions are growing, instead of going down as they planned (https://apnews.com/article/climate-google-environmental-report-greenhouse-gases-emissions-3ccf95b9125831d66e676e811ece8a18), to just name two examples.

Fair point. I took the liberty to rename the thread to "The toxic player Issue".

This is a gentle reminder that this thread is to discuss the overall issue and not issues with individual players.

What does help us for moderation are reports of violations of the terms of use, like using duplicate accounts, to one of the moderators or me via private message (best here in the forums), with screenshots/logs attached. While we catch some of them without reports as well, we're never going to be able to catch all of them, if the community doesn't support this effort. If you encounter a toxic player, please also don't encourage them to continue to do so, by further participating in games they're also participating in. You can also consider applying that to unknown players as well and only play with players somebody else vouches for. As @Meister proposed, please keep this thread free of personal accusations and focused on the overall issue.

In the cases I've seen, the users rejoined with the same internet provider.

In the time since, thanks to several people pinging me, I was able to investigate additional cases where this happened. What usually happens is: player joins the lobby with connection 1 (everything is fine) player joins the lobby with connection 2 (that being their active 0ad now and no rating is being shown) player leaves the lobby with connection 2 (probably when closing 0ad) player leaves the lobby with connection 1 (maybe when shutting down the PC) Step 2 is usually a direct response of a player having left a game (for reasons I don't know) and wants to rejoin. It's certainly not a timeout issue, as step 4 might happen hours later. To me that zombie process theory sounds somewhat plausible, however I've had no player answering the questions from the first post here yet, so we don't know if and why they restarted 0ad. If the zombie process theory is correct, then that process should be visible in the list of processes and a clean restart of the PC should work around that problem. Instead of a zombie process, I could also imagine 0ad getting confused internally and managing two concurrent connections to the lobby.

The accusations @Seleucids makes about @Norse_Harold's behavior in the past had been investigated back then by WFG staff, without finding evidence of misconduct by @Norse_Harold. On the other hand it's been proven that @Seleucids/@Yekaterina did commit serious violations of the terms of use back then, which did degrade the experience for other players. @Seleucids: Please stop repeating these accusations over and over. If you believe there has been misconduct by @Norse_Harold ever since, report that privately and with proper evidence. With that said, I'm locking this thread now, as any further discussion is unlikely to have a positive effect on the community.

What's so difficult about reporting stuff to me or one of the moderators? Have you done that? I don't think so (at least I don't know about it). We can only act on violations we know about. So stop the complaining and report violations of the Terms of Use privately to me or one of the moderators. Aside from that there is also the possibility for the community to outlaw toxic players by not letting them participate in games.

Ironically it refreshes only the ratings for all players not affected by this bug, because this bug seems to be caused by players (unintentionally?) being connected with multiple instances of 0 A.D. and only one instance would receive these updates. Even if all instances would receive the updates, other players joining is a frequent occurrence when somebody is affected by this bug and doesn't solve it. Registering multiple accounts violates the Terms of Use. Don't do that!

I just retrieved the confirmation that this bug happens unrelated to being in a game or not. So just loosing connection to the lobby and rejoining it, might trigger it.

I just created a thread in the bug reports subforum dedicated for this problem: Let's continue the discussion about that bug there, so this thread can be used for discussing the mod instead.

There have been reports that rejoining games isn't possible sometimes, as the rating for the player rejoining the lobby doesn't show up (https://gitea.wildfiregames.com/0ad/0ad/issues/7185). There was already some discussion regarding this topic in the following thread: Analysis of logs for cases where that happened to players showed that in these cases the players show up as connected with two different instances of 0ad to the lobby server. As we can assume they didn't do that intentionally, it's still not clear how that can happen. Workarounds which would fix this problem as well would be https://gitea.wildfiregames.com/0ad/0ad/issues/5320, https://gitea.wildfiregames.com/0ad/0ad/issues/4203 or patching Slixmpp to let EcheLOn keep track of all connected resources of a player, however these would just be workarounds, without addressing the root cause. What I need for further debugging to find the root cause are: whenever this problem happens to you, ping me in the lobby whenever this problem happens to you, reply here with the following information: operating system kind of internet connection (landline, mobile network, satellite, ...) list of installed mods reason why you left the game in the first place (crash, loss of internet connectivity, ...)

In the cases I've looked into that's not the problem. A connection to the lobby server stays alive the whole time during pregame, as well as during the game itself. Listing possible cases doesn't help. I'm interested in the actual cases which result in that problem.

The cases I looked into so far were all caused by being online with multiple instances of 0ad. So unless that was done intentionally it'd be interesting to figure out why that happened. I believe it might be important to learn why rejoining a running game is necessary in the first place. Is that because 0ad crashes or because the player looses the connection to the host?

Same problem happens for 0 A.D. as provided by Debian/unstable since the most recent OpenAL update. cc @vv221