[RELEASE:] Interstellar Tweak OXP

[another_commander]

[...] but: there used to be a plist verifier doogit. Cholmondely, could you point me towards a version of that that will work on Oolite 1.91 (which is the version of Oolite that I'm using), if there is one? I tried

Code: Select all

>C:\Oolite\oolite.app\oolite.exe --verify-oxp "S:\Games\OOLITE\OXP CONSTRUCTION\InterstellarTweaks\oxp\oolite.oxp.UK_Eliter.InterstellarTweaks.oxp"

but so doing ran the game, which I don't think it is meant to do, and gave me no debugging output except the standard log.

The --verify-oxp option is available only in Test Release builds. You are probably running a standard deployment build.
Just download the version named OoliteInstall-1.91.0.XXXX-YYMMDD-<github commit hash>-win-test.exe and you should regain access to the OXP verifier.

[Cholmondely]

The --verify-oxp option is available only in Test Release builds. You are probably running a standard deployment build.
Just download the version named OoliteInstall-1.91.0.XXXX-YYMMDD-<github commit hash>-win-test.exe and you should regain access to the OXP verifier.

Can I presume from this that the "full build" is the Test Release - and so the Nightly is really a newer Test Release. And that the Test Release "extras" are then disabled in the Standard Deployment when it eventually comes out?

[another_commander]

Can I presume from this that the "full build" is the Test Release - and so the Nightly is really a newer Test Release. And that the Test Release "extras" are then disabled in the Standard Deployment when it eventually comes out?

Yes, with the clarification that the way we are set up now, the nightly is built in all flavors (Test, Deployment and Dev (which is just the same as Test but with an on-screen watermark showing the version)) and the option to convert to the "full build" Test Release is still offered when an actual release of the game is made so OXPers can use it to better test and debug their work.

[Cholmondely]

The --verify-oxp option is available only in Test Release builds. You are probably running a standard deployment build.
Just download the version named OoliteInstall-1.91.0.XXXX-YYMMDD-<github commit hash>-win-test.exe and you should regain access to the OXP verifier.

I've added this information to the relevant sections of our wiki (OXP howto & OXP tutorial‎) - the other mention in "Hidden Settings in Oolite" already stipulates this.

[UK_Eliter]

Thanks, both. I had forgotten about the need for a 'test' release.

Can anyone advise on whether I ought to do something in response to the following output from the verifier?

Code: Select all

12:50:43.586 Scanning files
  12:50:43.589 ----- WARNING: "GNUstep/Defaults" is a nested directory, ignoring.
  12:50:43.589 ----- WARNING: "GNUstep/Library" is a nested directory, ignoring.

EDIT: it would be nice to stop the verifier's output from opening, in Windows (Windows 10) in bloomin' WordPad too. I told Windows to always open .log files in Sublime Text, but the verifier - or Windows - is not honouring that. Is the problem the double extension, viz., .oxp.log? (I wish I could develop my OXP on Linux, but the computer of mine that is most suited to Oolite is a Windows box.)

[another_commander]

Thanks, both. I had forgotten about the need for a 'test' release.

Can anyone advise on whether I ought to do something in response to the following output from the verifier?

Code: Select all

12:50:43.586 Scanning files
  12:50:43.589 ----- WARNING: "GNUstep/Defaults" is a nested directory, ignoring.
  12:50:43.589 ----- WARNING: "GNUstep/Library" is a nested directory, ignoring.

This means that you have a GNUstep folder inside your OXP. Check and move it outside.

EDIT: it would be nice to stop the verifier's output from opening, in Windows (Windows 10) in bloomin' WordPad too. I told Windows to always open .log files in Sublime Text, but the verifier - or Windows - is not honouring that. Is the problem the double extension, viz., .oxp.log? (I wish I could develop my OXP on Linux, but the computer of mine that is most suited to Oolite is a Windows box.)

The call to Wordpad is hardcoded in the game. You are right about stop sending output to it but for a slightly different reason: Microsoft removed Wordpad from the latest versions of Windows so now we are sending output to the void if running on Windows 11. I'll switch the output to Notepad instead, as it exists on any Windows version.

[UK_Eliter]

Thanks, as ever, Another Commander. Here are two follow-up questions.

1) May I without consequence simply delete the GNUstep directory that lies within the OXP? What is that directory doing / meant to do, anyway?
2) Why hardcode a call to a particular editor? Can't one (somehow) tell the operating system to open the file in the default editor.

[another_commander]

1) Yes, this is used by the game itself and I have no idea how it ended up inside your OXP folder, but it should not be a problem removing it.
2) I'll see what I can do. I will try to query the OS for the app set by the user for opening log files and use that, It will be Windows-only though.

[UK_Eliter]

Thanks!

Re opening the editor: well, Linux and presumably Mac have the concept of a default editor, so I don't understand.

[UK_Eliter]

Also - and hopefully finally - I can't find the website where one uploads one manifest. This doc says the URL is http://www.oolite.org/oxps/, but that gives a 404.

[another_commander]

We have a new nightly (commit 0031890) where now the OXP verifier uses the default application set by the user for opening .log files. If it fails to find such an app it falls back to Notepad. This feature is implemented for the Windows build only.

[phkb]

Also - and hopefully finally - I can't find the website where one uploads one manifest. This doc says the URL is http://www.oolite.org/oxps/, but that gives a 404.

The old system died with the loss of the original domain. Update the wiki with your new version, and I'll initiate the process to rebuild the OXP index.

[UK_Eliter]

Thanks, phkb. New version - version 6.97 - uploaded. Must we now then ping you on every OXP update?

[phkb]

Thanks, phkb. New version - version 6.97 - uploaded. Must we now then ping you on every OXP update?

Not necessarily. You can also log a ticket at the GitHub site here: https://github.com/OoliteProject/oolite ... on-catalog
That way, if I'm not around, someone else from the team can do it.

[phkb]

Thanks, phkb. New version - version 6.97 - uploaded

Your OXZ is missing the manifest.plist file for some reason. The cataloging process fails because of it.