Log Errors in 1.74

JazHaz · Post by **JazHaz** » Tue Jun 15, 2010 10:17 am

Thought we should have a thread for reporting log errors in the new 1.74 test version. Not sure which forum it should go in (A_C feel free to move it if necessary!)

JazHaz · Post by **JazHaz** » Tue Jun 15, 2010 10:22 am

Here's mine (duplicate lines editted out):

Code: Select all

[shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "beacon_torpedo" has a broken flasher definition (should have 8 tokens, has 7). This flasher will be ignored.

[plist.parse.failed]: Failed to parse ../AddOns/nuke.oxp/Config/equipment.plist as a property list.
failed to parse as valid XML matching DTD

[script.debug.syntax.badComparison]: ***** SCRIPT ERROR: in assassins.0.do.321.do.1.conditions.0 ("shipsFound_number less than 20"), unknown comparison operator "less", will return NO.

[debugTCP.disconnect]: Debug console disconnected with message "Lost connection to remote debug console. outStream status: 7, inStream status: 7. Stream error: The operation completed successfully.

"
[debugTCP.disconnect]: Debug console disconnected with message "Lost connection to remote debug console. outStream status: 0, inStream status: 0. Stream error: unknown error."
[debugTCP.connect.failed]: Failed to connect to debug console at 127.0.0.1:8563.

[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning (Automatic Chaff System 1.0): Ship.hasEquipment("EQ_ACS") is deprecated, use ship.equipmentStatus("EQ_ACS") == "EQUIPMENT_OK" instead.

[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning (OXPConfig 1.08): Mission.choice is deprecated and will be removed in a future version of Oolite.
[script.javaScript.warning.ooliteDefinedError]:       ../AddOns/OXPConfig1.08.oxp/Scripts/OXPConfig.js, line 151.

EDIT: re the debug console messages, I didn't have the debug console loaded.

Is there a new version of OXP Config?

tinker · Post by **tinker** » Thu Jun 17, 2010 10:12 pm

I would suggest that oxp specific errors are reported in the relevant oxp thread, the writer is more likely to read something specific to his/her oxp than try to sort through lists.

You can ignore the depriciated warnings, they are basically messages to oxp writers that the oxp will no longer work in 1.75 so they have time to fix it.

The assassins bug has, I think, been brought up several times, it is easy to fix by rewriting all instances of 'less than' with 'lessthan'

Post by **Kaks** » Thu Jun 17, 2010 11:46 pm

JazHaz wrote:

Here's mine (duplicate lines editted out):

Code: Select all



[debugTCP.disconnect]: Debug console disconnected with message "Lost connection to remote debug console. outStream status: 7, inStream status: 7. Stream error: The operation completed successfully.

"
[debugTCP.disconnect]: Debug console disconnected with message "Lost connection to remote debug console. outStream status: 0, inStream status: 0. Stream error: unknown error."
[debugTCP.connect.failed]: Failed to connect to debug console at 127.0.0.1:8563.

EDIT: re the debug console messages, I didn't have the debug console loaded.

Yep, that's what the log actually says, using a bit of programmer's jargon, I suppose...

I'll try to make it slightly more human readable, hopefully in a way that won't confuse programmers...

Post by **Micha** » Fri Jun 18, 2010 6:44 am

Hi Kaks,

I'm working on a slight rewrite of the debug concole tcp client anyway (there's a problem under Linux if you send too much data at once, it disconnects).
I've fixed it but it's messy - cleaning it up. I can improve the messages whil!e I'm at it.

Post by **Kaks** » Fri Jun 18, 2010 9:06 am

Oops, I've already tweaked them messages a bit.
But I'm sure my tweaks could do with some further improvements...

NorthenderPNE · Post by **NorthenderPNE** » Mon Jun 21, 2010 9:13 am

These are the errors that i'm getting in my Log with the latest build 175.3583.

Code: Select all

[plist.parse.failed]: Failed to parse Resources/Config/equipment.plist as a property list.
Parse failed at line 259 (char 7260) - unexpected character (wanted ',' or ')')

Code: Select all

[ship.setUp.missiles]: ----- WARNING: random missile "ecm-proof-missile" used in ship "Boa Class Cruiser" needs a valid equipment.plist entry. Enabling compatibility mode.
[ship.setUp.missiles]: ----- WARNING: missile_role "EQ_MISSILE" used in ship "Boa Class Cruiser" needs a valid equipment.plist entry. Enabling compatibility mode.

Just realized this is for 174 errors and not 175. Oops!

Post by **another_commander** » Mon Jun 21, 2010 9:41 am

In any case, try updating to 3584. The equipment.plist is fixed.

NorthenderPNE · Post by **NorthenderPNE** » Tue Jun 22, 2010 8:48 am

In any case, try updating to 3584. The equipment.plist is fixed.

Yepp, it sure is fixed mate, thanks.

NorthenderPNE · Post by **NorthenderPNE** » Tue Jun 22, 2010 9:08 am

These are the errors i'm getting in my 1.74 test log.

Hyperradio.

Code: Select all

[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning (hyperradio 1.17): Ship.hasEquipment("EQ_HYPER_RADIO") is deprecated, use ship.equipmentStatus("EQ_HYPER_RADIO") == "EQUIPMENT_OK" instead.

Bounty Scanner.

Code: Select all

[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning (Bounty Scanner1.07 1.07): Ship.hasEquipment("EQ_BOUNTY_SCANNER") is deprecated, use ship.equipmentStatus("EQ_BOUNTY_SCANNER") == "EQUIPMENT_OK" instead.

COME ON ENGLAND!

JazHaz · Post by **JazHaz** » Tue Jun 22, 2010 11:51 pm

Here are some more depreciation (and other) errors.

Missile Analyser

Code: Select all

[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning (missile_analyser 1.1.1): Ship.hasEquipment("EQ_MISSILE_ANALYSER") is deprecated, use ship.equipmentStatus("EQ_MISSILE_ANALYSER") == "EQUIPMENT_OK" instead.

System Redux

Code: Select all

[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning (System Redux 1.2 1.2): Planet.setTexture() is deprecated, use planet.texture = "foo" instead.

Not sure but I think the following are from Assassins?

Code: Select all

[script.debug.onOff]: SCRIPT debug messages ON
[script.debug.note.addPlanet]: DEBUG: addMoon 'gas_giantC'
[script.debug.addPlanet]: DEBUG: initMoonFromDictionary: {orientation = "0.0 1.0 0.0 1.0"; polar_color_factor = 2.5; position = "7000000 8000000 25650000"; radius = 240000; rotational_velocity = 0.04; seed = "1 2 3 4 5 6"; texture = hitsplanet2.png; }
[script.debug.addPlanet]: moon position (7000000.00 8000000.00 25650000.00) derived from 7000000 8000000 25650000
[script.debug.onOff]: SCRIPT debug messages OFF

These are definately from Assassins:

Code: Select all

[script.debug.syntax.badComparison]: ***** SCRIPT ERROR: in assassins.0.do.321.do.1.conditions.0 ("shipsFound_number less than 20"), unknown comparison operator "less", will return NO.
[script.debug.syntax.badComparison]: ***** SCRIPT ERROR: in assassins.0.do.322.do.1.conditions.0 ("shipsFound_number less than 20"), unknown comparison operator "less", will return NO.

Post by **Eric Walch** » Wed Jun 23, 2010 7:33 am

- For the missile analyser there is already a version 1.2 since the 1.74 release

- The "less" bug in assassins is already known for at least two years, but Little Bear never updated its version.

- The debug messages are what they are debug messages, although there is no need to have them in released code.

JazHaz · Post by **JazHaz** » Wed Jun 23, 2010 12:59 pm

Eric Walch wrote:
- For the missile analyser there is already a version 1.2 since the 1.74 release

- The "less" bug in assassins is already known for at least two years, but Little Bear never updated its version.

Didn't know there was a new version of the missile analyser. Just downloaded it!

As for the "less than" bug, is it a simple case of searching for "less than" and replacing with "lessthan"?

tinker · Post by **tinker** » Wed Jun 23, 2010 1:28 pm

As for the "less than" bug, is it a simple case of searching for "less than" and replacing with "lessthan"?

Yes I thought I said that earlier in this thread, perhaps I wasn't clear. All you need to do is replace "less than" with "lessthan" I think there are about half a dozen entries. After making just this change you will need to refresh the cache on next restart.

JensAyton · Post by **JensAyton** » Wed Jun 23, 2010 5:33 pm

tinker wrote:
As for the "less than" bug, is it a simple case of searching for "less than" and replacing with "lessthan"?
Yes I thought I said that earlier in this thread, perhaps I wasn't clear. All you need to do is replace "less than" with "lessthan" I think there are about half a dozen entries. After making just this change you will need to refresh the cache on next restart.

Two, in fact. Hence the two error messages. :-)