Oolite Bulletins

Thanks, Hiran. But here I see the following. Extra Thargoids Unresolved dependency reference to oolite.oxp.UK_Eliter.Ferdelance_3G:6.5 Unresolved dependency reference to oolite.oxp.UK_Eliter.Ferdelance_3G:6.5 Interstellar Tweaks Unresolved dependency reference to oolite.oxp.UK_Eliter.ferdelance_3G:...

Hiran: good detective work. Thank you. But the message says that one side has a DIGIT ZERO character whereas the other has a 'n'. So it looks to me as if version information is missing in manifest.plist. Now that I've fixed the missing version information, hopefully the warning about that informati...

EDIT: Hold that.. Just realised it's working without actually hitting the redirect. Hunting for the old config that must be getting hit. Will update when done. Managed to clobber the errant config file and tested it properly. All good. Do I understand you managed to patch the binaries? And all that...

Hiran: good detective work. Thank you. But the message says that one side has a DIGIT ZERO character whereas the other has a 'n'. So it looks to me as if version information is missing in manifest.plist. Now that I've fixed the missing version information, hopefully the warning about that informati...

EDIT: Hold that.. Just realised it's working without actually hitting the redirect. Hunting for the old config that must be getting hit. Will update when done. Managed to clobber the errant config file and tested it properly. All good. Do I understand you managed to patch the binaries? And all that...

I'd suggest your credit balance reverting was a simple case of thought you'd saved after making changes, but actually forgot to save. Alas, no. It happened several times (G1, G2 & G7) - and each time I'd changed the name of the Jameson save file. Disclose the message you see in the logs. We mig...

Since when is this check in the game?

I was wondering myself that there is no such check when I raised my money to buy big ships or increased the auto repair kits to benefit from in-combat repairs.

Took me a little to remember that I can view my current contracts by pressing F5 twice. That (and the primary function of F5) isn't mentioned here: https://wiki.alioth.net/index.php/Oolite_Keyboard_Controls There is a reference sheet on GitHub which does mention this but it's stamped with "Out...

Confirmed, the correct PDFs are now packaged with the Windows installer too. In case it can be of help in the future, the Windows installer executables are accessible as LZMA archives by 7-zip. At least on Windows, I can open them inside 7-zip and extract any part of their contents without actually...

Run unzip -o artifacts/oolite-doc.zip Archive: artifacts/oolite-doc.zip inflating: oolite/Doc/AdviceForNewCommanders.pdf inflating: oolite/Doc/OoliteRS.pdf inflating: oolite/Doc/OoliteReadMe.pdf extracting: oolite/Doc/OOLITE_VERSION.txt Verified: The Linux artifacts do contain the generated files. ...

Seems like I found the culprit! The extract command would only extract newer or non-existing files (the -u option). I switched to -v -o and have this output in a test branch: Run unzip -v -o artifacts/oolite-doc.zip Archive: artifacts/oolite-doc.zip Length Method Size Cmpr Date Time CRC-32 Name ----...

Now this is strange. When the documentation is built (that means the PDFs are generated), there is an artifact called oolite-doc.zip. That one contains the correct files. Then this artifact gets downloaded and extracted. During extraction I see this log output: 2025-05-05T00:01:54.9016942Z ##[group]...

another_commander wrote: ↑Tue May 06, 2025 4:37 am

No, I downloaded from GitHub.

Interesting. When I get to it I'll take a look. May need your support as I don't do Windows...

Plus the odt document is bundled into future releases - if there are any. Actually, just checked and this is not the case. The current pre-release installers contain the outdated PDFs instead of the current ones. That is unexpected. Here is the line that generates fresh PDFs based on the .odt: http...

Only the PDF Reference Sheet is outdated. The .odt (LibreOffice) source Reference Sheet file found in the same Doc folder on github is fully up to date. Plus the odt document is bundled into future releases - if there are any. The PDF version is there solely because not having it breaks the build.