On Tue, 18 Feb 2025 04:38:20 -0500 Kurt Mosiejczuk <k...@cranky.work> wrote:
> On Mon, Feb 17, 2025 at 01:12:24PM -0500, Thomas Frohwein wrote: > > On Thu, 23 Jan 2025 21:24:01 -0500 > > Thomas Frohwein <tfrohw...@fastmail.com> wrote: > > > > Please find attached the tarball for freeciv21. This is a fork of > > > Freeciv that diverged from it to better serve larger, long-turn > > > online multiplayer games. There is information on what exactly is > > > involved at the homepage [1], including how to register for the > > > periodic coordinated matches. What stands out is that turns in > > > online multiplayer last about a day, allowing for a global > > > playerbase in different timezones. > > > > The game still has singleplayer mode which works just fine. A > > > tutorial is included. > > > > The port itself is fairly straightforward, not even needing any > > > patches. I'm including 3.1rc2, as this is what is also used in > > > upcoming long-turn events at this point, and has been stable on my > > > testing and also some regular freeciv21 players. > > > > ok to import? > > > > [1] https://longturn.net/ > > > *ping* > > > A rather well-maintained fork of freeciv suitable for single or > > multiplayer. Re-attached for convenience. > > The port looks okay and it does build. The game seems to play. > However, it consistently throws errors about sound files: > > [critical] freeciv21-client - Can't open file > "/usr/local/share/freeciv21/stdmusic/Per-Kiilstofte__Battle-of-Kings.ogg" > [info] freeciv21-client - Starting freeciv21-server at > /usr/local/bin/freeciv21-server [critical] freeciv21-client - Can't > open file "/usr/local/share/freeciv21/stdsounds/foot3.ogg" > > That last one repeats each time I move a unit. > > The files _are_ there though. Have you selected the sound backend in the options? I think it's not set up by default, but can be enabled easily by going into Interface Options -> Sound and then selecting Soundset: stdsounds, Musicset: stdmusic, and Sound plugin: sdl. Sound is working here with these settings. > > Nitpick: The lines in the DESCR go right up to 80 columns. I usually > prefer the results from running the DESCR through fmt(1) It's formatted with fmt -w 80, which is in line with Porter's Handbook: "Lines should be no longer than 80 characters." If for some reason there is a consensus to stick to fewer characters, can we update the handbook accordingly? > > That said, ok kmos for import if you're okay with the sound being > broken. Thanks, I went ahead with it! > > --Kurt
