[SOLVED] Error with Neolite 1.1 and Thargoid missile set up

[DredgerMan]

Code: Select all

<key>death_actions</key>
		<array>
		   <string>spawn: qbomb 1 (0.1)</string>
		</array>

Any idea what the values should be?

Code: Select all

<key>death_actions</key>
		<array>
		   <string>spawn: qbomb 1</string>
		</array>

No idea when the '(0.1)' was supposed to do.

The Terrapin is quite an old OXP, when general knowledge about the finesses of the scripting engine was still relatively low. Perhaps it was an attempt to put a random factor to the spawn method (spawn a qbomb in 1/10th of all cases)? That's of course pure speculation.

Anyway, glad that a rather long-standing OXP bug was found.

Hmmm, just a thought. Is a bug truly a bug if it doesn't bug anyone?

But with the Neolite 'error' you wouldn't know there was one unless you kept checking the latest log at regular times. I guess the same holds true for the Terrapin 'bug'.

[Cody]

... you wouldn't know there was one unless you kept checking the latest log at regular times.

This becomes an automatic function, even for dumb pilots like me!

[DredgerMan]

... you wouldn't know there was one unless you kept checking the latest log at regular times.

This becomes an automatic function, even for dumb pilots like me!

Same here.

[Commander McLane]

Hmmm, just a thought. Is a bug truly a bug if it doesn't bug anyone?

Coming from you that sounds a little strange. It did bug you, or why else have you posted about it?

[DredgerMan]

Hmmm, just a thought. Is a bug truly a bug if it doesn't bug anyone?

Coming from you that sounds a little strange. It did bug you, or why else have you posted about it?

You have a point there!

[Commander McLane]

Also, a bug is still a bug, even if nobody notices it. Concerning the Terrapin: it was clearly the OXP author's intention that the ship should 'go out with a bang', or else he hadn't included the death_actions in the first place. But it never did. The fact that the intention wasn't visible for a player who didn't check the log (and therefore nothing was missed) doesn't change that.

Therefore there's no reason for me to call it a 'bug' with marks around it. Besides, using a syntax that is invalid in the programming language is a bug in and of itself, regardless of everything else. It's like spelling mistakes in normal writing.

[DredgerMan]

Also, a bug is still a bug, even if nobody notices it. Concerning the Terrapin: it was clearly the OXP author's intention that the ship should 'go out with a bang', or else he hadn't included the death_actions in the first place. But it never did. The fact that the intention wasn't visible for a player who didn't check the log (and therefore nothing was missed) doesn't change that.

Therefore there's no reason for me to call it a 'bug' with marks around it. Besides, using a syntax that is invalid in the programming language is a bug in and of itself, regardless of everything else. It's like spelling mistakes in normal writing.

True. Fair points. Not having looked too deep into the code behind the game before, I originally didn't know whether the syntax used was for a previous Oolite version and simply never got updated. The line in the latest log said it wanted to see a role and a number, which (if the 1 counts as the role and 0.1 as the number, but not sure why the brackets should have been there then) were provided in the syntax. But after I found the source of the problem, I did a search on the forum and found the issue had been reported before and a clear statement that it was a failure.

[DredgerMan]

The Terrapin is quite an old OXP, when general knowledge about the finesses of the scripting engine was still relatively low. Perhaps it was an attempt to put a random factor to the spawn method (spawn a qbomb in 1/10th of all cases)? That's of course pure speculation.

Anyway, glad that a rather long-standing OXP bug was found.

The energy bomb error popped up its head again. The Terrapin is definitely correct now but according to notepad ++ the problem lies in:

C:\Oolite\oolite.app\GNUstep\Library\Caches\Oolite-cache.plist (1 hits)
Line 9300: specular_map

Any ideas on this?

[Commander McLane]

Have you cleared the cache (starting Oolite with pressing SHIFT until you see the spinning Cobra)?

[Tricky]

Force a reload of the cache with the shift key???

EDIT: Ninja'd!

[DredgerMan]

Have you cleared the cache (starting Oolite with pressing SHIFT until you see the spinning Cobra)?

Hmm, I thought I did yesterday but I just did it again and the q bomb entry is now gone (apart from the previous log )

Thanks again, Commander and Tricky!

As a by the by I have seen the Ninja'd edits before. I assume they are to say that someone beat you to it?

[Commander McLane]

As a by the by I have seen the Ninja'd edits before. I assume they are to say that someone beat you to it?

Yep.

[DredgerMan]

As a by the by I have seen the Ninja'd edits before. I assume they are to say that someone beat you to it?

Yep.

Good to know.