You're asking this question a lot, and nobody has answered, so let me try - a lot of OXP writers don't want issues with the Trunk to reported to them as errors in their OXP, so when the Devs say version X.YY.Z is the latest stable test version then the oxp writers set the max_version to be X.YY.ZZ
…thereby sabotaging the testing process and increasing the number of bugs in the next version of Oolite, including bugs they themselves will need to work around.
max_version exists because using the wrong version of Debug.oxp with a Mac version of Oolite can cause a crash. After MNSR, I intend to merge the Mac-specific parts of Debug.oxp into Oolite proper, then remove max_version.
DaddyHoggy wrote:
(for example - current stable test is 1.73.4, so max_version is often set to 1.73.99, thus allowing for incremental tweaks - but as the trunk is currently has the working title 1.74.xx
I knew I'd erred a moment after hitting submit and foolishly hoped that a) nobody would notice b) it would be allowed to slide as I was trying to indicate why...
However, given your need to test the trunk I can see why max_version is a bit of a headache for the devs...
Flight Log is excellent - allows me to keep an eye on my money and kills in an easier way. Works with the latest nightly after editing the requires.plist - no bugs.
This OXP is now up to v1.04, ready for Oolite 1.77.
Under 1.76.1 it will work exactly the same as v1.03, but on trunk from version 5328 onward it will also appear under the new F4 ship and system interfaces menu when docked.
Downloaded and installed version 1.04.
It works fine whilst docked - appearing nicely under the F4 screens.
However, when you launch I am now getting a series of error messages
Having checked the script.js file it would seem that the check for version 1.77 is continually called and of course will fail since the ship is in flight. Think this needs a check to see if the ship is docked or not before the rest of the function is called.
Ironfist
64bit Mint 10 and Win 8 64bit on E8400 at 3.6GHz - ATI HD5750 graphics.
Concentration is the ability to think of absolutely nothing when it is absolutely necessary.
Happy to report that version 1.05 does not produce the errors.
Irtonfist
64bit Mint 10 and Win 8 64bit on E8400 at 3.6GHz - ATI HD5750 graphics.
Concentration is the ability to think of absolutely nothing when it is absolutely necessary.
Since I spend a lot of my time in interstellar space, particularly multiple misjumps in a row...I hacked Flight Log OXP so the list wasn't cluttered with multiple interstellar space entries in a row.
In the this.startUp = function()
section, almost at its very end, I added:
Now that 1.77 is fully out, I've up'd this to v1.06 to remove the F5-F6 route to the log when docked (it's still F5-F5-F6 when in flight). Access when docked is now fully via the interface (F4) screen.
Minimum Oolite version is now 1.77, with download via the links below as normal.
Can you put a total (and an average per system) on the page? Individual credit changes by system are fairly useless, since they vary depending on what you bought and sold. So it could report a loss at a system when there was a virtual profit. But a 10 system total and average would shoe the trend.
Can you put a total (and an average per system) on the page? Individual credit changes by system are fairly useless, since they vary depending on what you bought and sold. So it could report a loss at a system when there was a virtual profit. But a 10 system total and average would shoe the trend.
Sounds like you're looking for my Ship's Accountant oxp - it tracks profit and loss based on mark-to-market accounting, not just cash balance.
It's just about usable now - I'll probably make the first "WIP" release this weekend.
It now logs the last 100 systems visited, with the most recent 10 available in-game. The full log can be dumped out to latest.log as before. Functionality and operations are exactly the same, just the memory has been expanded.