Norse_Harold

There is a rule about against having more than one forum account in the draft forum code of conduct. Don't do it without authorization. 2022-10-19 code of conduct revision 2.pdf

Yes, and you can't use any version other than mozjs-78.6.0 with 0ad alpha 26 because 0ad assumes that every player is using the same version of mozjs in order to keep the game in sync. Is alpha 26 the only version of 0ad you're interested in currently? You could look at 0ad SVN master, which uses mozjs-91.13.1, and might in the future use an even newer version of mozjs prior to stable release.

From what I've seen of Slackware, it's almost like Linux from Scratch, meaning that package maintenance duties fall on the users. The issue here is that mozjs-78.6.0 is old, and the build environment you're using is new. By the way, please post the versions of gcc, g++, clang++ and llvm that you have. You can mimic how other distributions of Linux package 0ad, such as Debian, Arch and Gentoo. They have patches that fix building mozjs and build dependencies that control the versions of packages in the build environment. Debian's packaging is not always tested with the newest versions of build packages, but Arch and Gentoo are more likely to support the latest versions of build packages. Debian's packaging is proof that 0ad alpha 26 builds with rustc version 1.63 and lower, clang version 14.0 and lower, and gcc version 12.2.0 and lower. There might be code constructs in mozjs-78.6.0 that are deprecated by newer versions of rustc, clang and gcc. You might try using older versions of build packages. I also noticed that there are other errors logged before the error that you posted. At first, there's a warning about deprecated function. warning: use of deprecated function `std::mem::uninitialized`: use `mem::MaybeUninit` instead Then there's an error from clang++. cargo:warning=clang-16: error: unknown argument: '-fexperimental-new-pass-manager' which is apparently classed as a warning by the calling process. But, maybe if you fix that error (probably by using an older version of clang or adjusting the code to use mem::MaybeUninit) then build will be able to proceed ... until it encounters the next error. Fix the next error, and you'll find another error... Heh, hopefully not, but that's often what happens when one is trail blazing. Later, the use of ::std::mem::uninitialized is considered an error by your version of clang. I don't see that in my build log. I only see the earlier warnings about std::mem::uninitialized being deprecated. Alternatively, you could try using the AppImage, Flatpak or Snap of 0ad to run it from a sandbox. Or, you could try dual booting to a different distribution of Linux in order to build 0ad alpha 26 with known working build environment package versions.

Right, balance in a tournament kinda-sorta matters, but it doesn't matter matter.... Speaking of balance, why not use the map "Mainland balanced"?

Sevda, what is the attachment, "how_to_bypass_lobby_ban.pdf"? It's a broken link anyway. Are you trying to report a security issue? Please report that privately to the lobby admin team. If you want help troubleshooting networking then I can provide that via IRC.

It looks like alpha 23 uses SDL2. If you are sure that you have libsdl2-dev installed then check whether you have pkgconfig installed, as 0ad uses pkgconfig to locate the path to the SDL include directory. A quick way to verify that your build environment is correct is to check whether you can build 0ad alpha 25 or alpha 26 on your system. This command installs the build dependencies of the current version of 0ad, which should get you most of the way to having the build dependencies for alpha 23. sudo apt-get build-dep 0ad You're bound to encounter other problems building alpha 23 unless you use distro-maintained patches. Fortunately, Debian still has alpha 23 maintained for a current version of Linux. You can copy their patches and build rules or mimic them manually. If you have the ability to add a deb-src PPA for Debian packages then you could use apt-get source 0ad/bullseye to obtain the already-patched source code. Just make sure to remove the PPA afterward so that packages are only installed from the Mint repositories. If you obtain the Debian-patched source code for alpha 23 then you can look at the Build-Dep line of 0ad-0.0.23/debian/control and verify that you have installed the packages listed there.

I am the copyright holder of original works I post in the Wildfire Games 0 A.D. Art Development forum. I hereby release all original works I uploaded to this forum in the past, and those I will upload in the future, under the Creative Commons Attribution-Share Alike 3.0 Unported license.

Yes, it's already committed for the next release (for alpha 27), because it's a bugfix. See here for the proof. Notice that it says "Closed by commit rP27599: Use a lower default MTU for ENet hosts, and make it configurable. (authored by Itms)".

Update: G.O.A.T has removed all statements about duplicate accounts from his About Me page. Here is how it looks now. Okay, that's your choice. Removing the claims about duplicate accounts is one of the options that complies with the rules. Thanks for doing this.

@G.O.A.TI've been promoted to a forum moderator and asked to enforce the rules in this situation. WFG's draft code of conduct states that posting inaccurate information is disallowed. Also, libel law says the same thing if the claim is an accusation of a crime, such as an accusation of breach of contract. In line with that the information in your About Me page needs to be accurate. The minimum that should be done is add a note (and link to discussion) about any information that is disputed The maximum that can be done is to remove the disputed information and add a note of apology. Examples of disputed information: by Sevda, by weirdJokes, by guerringuerrin, and by Helicity. Do you want to do that, or should I edit your About Me page to note the disputed information? If you goal is to get rules enforced on duplicate accounts then you need to do the following. Establish a much higher threshold of evidence supporting the claims instead of (apparently) merely basing them on geolocation of IPs. Collect and save evidence that supports the claims. Alternatively, document how a lobby moderator can obtain evidence supporting the claims. Send a forum PM with the information to an active lobby moderator, such as myself or Dunedan.

@HelicityCan you please post here with any inaccuracies and disputes you have about G.O.A.T's list of duplicate accounts on his About Me page? Thanks.

It looks like one Flatpak app related to 0ad was not successfully removed, "com.play0ad.zeroad.Locale". But, that only uses 114 bytes. If you think that some of the objects didn't get removed correctly during uninstallation of 0ad flatpak apps, you can try to repair the flatpak repo with this command as root (or with sudo). Based on this bug report, it should clear objects that don't belong there. flatpak repair As far as what's using 4 GB, note that 1.6 GB of it is likely due to the apps in a default Flatpak system that has Xorg and nothing else. Specifically, org.freedesktop.Platform, freedesktop.Platform.GL.default. Wesnoth uses 475 MB. It looks like you have three copies of the freedesktop platform. You also have Lagrange, Intel drivers, ffmpeg and openh264. There is a possibility that all of that adds up to the 3 GB in use in /var/lib/flatpak. Here are other ideas for freeing storage space. Check for per-user installed flatpak apps with the following command. (sign in as a user that might have 0ad installed) flatpak -u list Also run apt-get clean as root. That removes archived package installation files.

There is an FAQ answer to this question here. Scroll down to read the answer to the question, "Failed to connect to the server. UDP port 20595 not being forwarded." If you need more assistance then talk to me on IRC.

Correct. Follow the rules, people. That said, I'm not able to personally enforce the rules about duplicate accounts because I don't have access to the server logs or ban capability. It's up to @Dunedan and @user1. I can pass information back and forth though, such as information about potentially unauthorized duplicate accounts, request for authorization of certain duplicate accounts (include the names and reasons for each), and requests to delete certain duplicate accounts (include the names and proof that you own the accounts).

Here's an independently developed chat extractor that by default displays only those chat messages that the logging player should be able to see. To use it, install python3, and copy 0adextract_chat.py to the logs directory within the 0ad user data directory. Start a Terminal or command prompt, change directory to the 0ad logs directory, and start the program with information about your lobby user name (and rating) by passing a command line argument. Here's a demonstration of how to start the program once you have changed directory to the 0ad logs directory. Replace "Helicity (1377)" with your lobby username and rating. If you have no rating then exclude the parentheses. python3 0adextract_chat.py --player-name "Helicity (1377)" After the match is finished, you can read all player chat with Helicity's mainlog_extractor.py script or by passing --show-all-chat to 0adextract_chat.py. Please don't use this to cheat. There are many good purposes for this software, including reporting player misconduct, making links copyable to clipboard without using autociv, remembering cool or funny moments from past games, and saving songs generated by ChatGPT and pasted by Larsvandijk. 0adextract_chat.py

I don't think that the issue is UDP being blocked by the ISP. It's more complex than that. It's already known that STUN doesn't work in all cases. It depends on the network configuration of each peer. There's software that can be used to test STUN. The Linux package is named something like stun-client. A Windows version is available here. Here's the manpage for it. Alternatively, if your web browser supports WebRTC, there's a website-based STUN test available here. Here's the output that I get when I run tests 0, 1 and 2. I don't have CGNAT. Notice that the return value of test 0 is 0x000010, and the return value of tests 1 and 2 is 0x000000. STUN client version 0.97 running test number 0 Bad length string 15 problem parsing ServerName Bad length string 15 problem parsing ServerName Bad length string 15 problem parsing ServerName Bad length string 15 problem parsing ServerName Primary: Open Return value is 0x000010 STUN client version 0.97 running test number 1 Bad length string 15 problem parsing ServerName Return value is 0x000000 STUN client version 0.97 running test number 2 Bad length string 15 problem parsing ServerName Return value is 0x000000 Can someone with CGNAT please post the output of this command? stun -v lobby.wildfiregames.com 0 ; stun -v lobby.wildfiregames.com 1 ; stun -v lobby.wildfiregames.com 2

@BeTeSorry I linked to the wrong thread at first. Good job finding the correct one. I've corrected the link in my post as well. The reason that it's important to post these reports in the right thread is so that user1 can find them and process them. This Discussion thread is basically the graveyard for already-processed reports. Only admins can delete posts apparently, so nevermind.

It's a known bug. See here for what causes it, how to fix it, and how to prevent it in the future.

@BeTeThis is the wrong thread for posting reports of ratings offences. This thread is where completed requests and off-topic discussions are moved. You should delete the post from this thread and instead post it in the correct thread for reporting offences. Edit: corrected the link.

I've been telling people about Carrier-Grade NAT for a while. It seems to disrupt STUN negotiation. It's unfortunate that the users who are least likely to be knowledgeable about networking and troubleshooting are also the most likely to be using Internet connections that have CGNAT. It's increasingly common now, due to IPv4 address exhaustion. It's also another step toward creating consumers out of us instead of content creators and empowered Internet peers. How to diagnose whether you have CG-NAT? Login to the administration interface of your modem and check the WAN or Internet IP address. If it's a private IP address (192.168.x.x, 172.16.x.x, 10.x.x.x, or 0.0.0.0) then you likely have Carrier-Grade NAT. Also check your public address with whatismyip.com or similar websites. If the modem's admin interface indicated IP does not match the IP listed by whatismyip.com then you likely have Carrier-Grade NAT. If you have Carrier-Grade NAT and you want to request "public IP address service" then this document could help you with explaining to your ISP what you want. There's usually an additional monthly fee for the service. I'll add a mention of this to the FAQ.

I appreciate that you have good intentions and are trying to support a non-profit open source organization. So far it doesn't seem like you're making an offer to donate the domain names with no strings attached. Realize that simple redirects are still not secure, as they can temporarily redirect to malicious sites or inject JavaScript that then modifies HTTP content served by the legitimate site. This can change the links for downloads to malware-containing install files. A way to prevent this risk is if WFG has ownership and control of the domain names.

Thanks for releasing the source code for mainlog_extractor.py. What license do you choose for it? The FSF suggests using Apache License 2.0 for small programs. I hope that players will have integrity and not use this to cheat during gameplay. And, I hope that people will use this program for good purposes like reporting in-game verbal abuse by others.

So you would transfer the domain ownership to Wildfire Games staff, right? It's important for security to have WFG control the domain if you expect to have downloads of the game hosted there. Otherwise there's a risk that malware is, intentionally or unintentionally, sent to users via the site.

@PieLamIf sound works reliably with a native package of 0ad then here is a potential hypothesis that would explain the symptoms. Snap apparently can have a race condition where not all devices have been enumerated in the sandbox by the time the app is started within the sandbox. Read about it here. (Scroll down to "Too early for operation errors".) That means you should pay attention to whether snapd is already running before each test of audio with 0ad within the Snap sandbox. To check whether snapd is running you can use this command in a Terminal window. ps -A | grep snapd To start snapd before starting 0ad, maybe this command in a Terminal window will accomplish it. sudo systemctl start snapd

Maybe the copy on disk is fine, but the copy of the archive in RAM was corrupted due to malfunctioning RAM or CPU. Then after reboot, the archive was reloaded to RAM from disk and happened to be correct. Or, maybe there is a problem with the transfer interface of the hard drive such that sometimes a correct copy is retrieved and sometimes an incorrect copy is retrieved. Or, maybe something else entirely is the cause. I'm just listing hypotheses that would explain the symptoms.