Black Baron broken? (solved)

[Loxley]

A minor issue but the Black Baron oxp seems to be incompatible with Oolite 1.74. On arriving at Teesdi I was told to meet the resistance at system %J93... There are some strange names in the database I know, but not that strange.

Incidentally, I have checked and it is the 1.74 compatible version I'm using.

[Kaks]

A typo: If you change that %J93 to %J093 (zero-nine-three) inside the plist (and press shift when restarting Oolite) you should see the actual planet name!

[Thargoid]

Oops!

I'll ask Rxke to correct and re-upload the OXP (it was my typo).

[Loxley]

Seem to be having trouble here, now my mission screen wants me to go to %J093...

Never mind, since I've been tooling around in the mission text I know what that's supposed to mean and it sounds like the wiki version should be corrected soon. Thanks to all concerned.

[Rxke]

Should be fixed now. (didn't have time to test it though)

[Switeck]

The link to the repaired mission here?:
http://wiki.alioth.net/index.php/Scourg ... lack_Baron

[Rxke]

Oh boy, seems like I dun goofed!

I'll see how to rectify it (don't have much experience with Box.net...)

[Rxke]

Fixed link.

Still didn't do any testing, though...

[richard.a.p.smith]

I just went through this with O 1.76.1.

The %J93 problem is still there with the 1.74.2 version on the Wiki page. It's in \Config\mission.plist at line 24 but altering "%J93" to "%J093" does indeed get the correct text in the mission screen.

That said, there's nothing else to note here as far as I can tell - it's all okay with 1.76.1.

Rich

[Rxke]

Oh Dear...


I *really* do not have the time to look into this anymore. I'm from the XML- plist generation, Javascript is not my cup of tea (ohh.. that was NOT a pun intended! )

Nine weeks old son, renovation, full time job.... Real Life, indeed.


could we not make a list of 'orphaned OXP's' or something like that, so they either get 'adopted' or...

[richard.a.p.smith]

I understand your situation!

The OXP works fine with 1.76.1. The one thing I should have mentioned, though, is that I don't know if red X marks are supposed to appear on f6f6.

As I write this I don't have a box account and don't think I can edit the Wiki - can look into that to send an update somewhere.

In the meantime (ie, so others can edit it if they want to see the system name during the mission) it's very simple:

line 24 in \Config\missiontext.plist has one entry of %J93 that should be %J093

All other entries are already %J093. I used TextPad to edit and re-save. Do a shift-restart (don't even know if that's necessary) and job done.

Rich

[Smivs]

...could we not make a list of 'orphaned OXP's' or something like that, so they either get 'adopted' or...

There is already a 'sticky' thread here on the Expansion Pack forum. Although as it stands it is not much of a 'list', that might still be a good place to start.
Having just read through the thread though, it seems more of a discussion as to how two people 'adopted' the same OXP, which turned out not to be orphaned at all.

[Rxke]

I'll see if I can manage to update during lunchbreak (main problem being my Box account, what the heck is that password again ?? )

[maik]

As I write this I don't have a box account and don't think I can edit the Wiki

What is your preferred Wiki user name? I'll create an account for you so you can edit.

[Rxke]

buxfixed version here: https://www.box.com/shared/f7pkc08unn

(i hope! not easy, doing a bugfix and updating readme's duing lunchbreak, heehee!)