Oolite Bulletins

I have investigated some more. I think I have a result. The problem seems to owe to the size of the whole archive (or perhaps the combined size of the images). When my OXZ (ExtraThargoids, but I bet this applies to any of my OXPs) is smaller than 1MB, it uploads. When it is larger than 1 MB, it fail...

Just to see if I understand: the images are contained within your OXZ when the upload is denied, and same OXZ file is accepted as an upload if the pack doesn't contain the folder with these images..? Yes. Very weird. Is there anything unusual about the format, these types of images have worked befo...

Good news indeed, thanks to our ArchWizards and Space Lord Winston. However, the upload limit for images is now at 1 MB, I believe [. . .] Just now I encountered this problem - but not exactly this problem. I got the 'too large' error, but none of my images is >= 1MB. Rather: Note that those are th...

@Cholmondely: Hah! I seem to recall something about that (semi-colons on a mac being a problem with Oolite; I use Oolite on Windows). Yet, does the problem occur even with Javascript files? The Javascript files in my own OXPs - the OXPs that I wrote - have all the semi-colons that my Linter (JsHint ...

Nite Owl: thanks. Two things. (1) Commenting-out seems drastic. Why not instead insert a null check? (2) Can anyone make the change to the OXP itself (as against merely to her/his own instance of it)? EDIT: Re 1, here is what I mean: /* EDITS by UK_Eliter: I have commented out the next (extended) li...

Dear all I am seeing, [oxz.manager.error]: Downloaded OXZ does not contain a manifest.plist, has been left in C:\Oolite/oolite.app/GNUstep/Library/Caches/org.aegidian.oolite/Oolite-download.oxz Yet, the archive in question - in the version extracted from that path - does seem to contain a manifest f...

Hi all. This is just to say that, for TargetAutolock Plus, version 1.14, I am seeing a lot of the following in the log, sometimes: 21:17:06.834 [script.javaScript.exception.unexpectedType]: ***** JavaScript exception (targetAutolock 1.14): TypeError: ptarget.scannerDisplayColor1 is null 21:17:07.084...

no offence: your ooniverse, your game, more power to you Well, one needs something like that, or else witchspace remains 'suicide space'. Also, the ship is very expensive. Indeed I notice that it was ludicrously more expensive than the next model down (the next '3G' model down - though in some ways...

Redspear wrote:

Best equipped ship I ever flew was a second hand adder with one energy bank.

You are pulling my leg!

Redspear wrote:

What are you flying there? A space station?

A Fer-de-lance 3G 'Delux-o-tank' (sic) variant - which I noticed is not listed here. I'll try to add it to that page.

Redspear: in that case, I fear that you would not last long against . . this . .



Also, though: you don't die in real life if you get killed in the Ooniverse! So why not give interstellar space a go?

RedSpear: good stuff: But, are you aware that the 'Thargoid takeover' is implemented already, in my InterstellarTweaks pack?

Cholmondely Those ideas are fun - I for one would like to rescue a fair lobster - but I am not volunteering to try to implement them! Still, actually I have implemented docking with a generation ship, already: one can do this with the hijacked generation ship that lurks within one of my expansion pa...

Hey all, and happy Christmas I notice that many an OXP generates an error because the OXP presumes that player.ship.position is defined, which, when the player has jettisoned, it is not. I have no errors of precisely that kind in my most recent log, but I do see the following, which may be of the sa...

This is indeed not really the place for general discussions of Thargoid matters (though my Interstellar Tweaks OXZ does spawn some inactive thargons.) Moderator: move? I think that inert thargons should have a bounty of only some ten credits (even though a Thargoid attack can kill the player or cost...

Dear both

Thanks; fixed.

I tidied up enboxed comments in the file at issue and in other js files. Also, I added some persons that I had neglected to the acknowledgements section of the README.