[Fixed for V0.39] Counters with no action and value of zero

Messages are moved here (should anyone ever want to see them again) once they are no longer applicable to the current version (e.g. suggestions that have been implemented or bugs that have been fixed).

Moderator: George Gilbert

Forum rules
Please read the Forum rules and policies before posting. You may Image to help finance the hosting costs of this forum.
Post Reply
User avatar
Sophia
Concise and Honest
Posts: 4307
Joined: Thu Sep 12, 2002 9:50 pm
Location: Nowhere in particular
Contact:

[Fixed for V0.39] Counters with no action and value of zero

Post by Sophia »

Counters can't seem to have both no action and a value of zero, at least as set up in the editor. The compiler complains vigorously.
User avatar
George Gilbert
Dungeon Master
Posts: 3022
Joined: Mon Sep 25, 2000 11:04 am
Location: London, England
Contact:

Post by George Gilbert »

Nope - can't reproduce this. Can set it a zero count, null action in the editor and then compile it without any warnings, let alone errors.

What ends up in your text file?
User avatar
Sophia
Concise and Honest
Posts: 4307
Joined: Thu Sep 12, 2002 9:50 pm
Location: Nowhere in particular
Contact:

Post by Sophia »

This ends up in the text file:

Code: Select all

ref000304-1	WALLITEM_COUNTER			3	4	0	CENTRE
I get this:

Code: Select all

---- Reading file "Modules/test.txt" ----
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Could not get parameter 7 on line number 414. Line begins with "ref000304-1	WALLITEM_COUNTER			3	4	0	CENTRE"
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Attribute identifier "@@@NO-MORE-STRINGS@@@" not supported. Expecting string of form COUNT=(xxxx).
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Expecting single numeric value.
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Could not get parameter 8 on line number 414. Line begins with "ref000304-1	WALLITEM_COUNTER			3	4	0	CENTRE"
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Could not get parameter 9 on line number 414. Line begins with "ref000304-1	WALLITEM_COUNTER			3	4	0	CENTRE"
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Attribute identifier "@@@NO-MORE-STRINGS@@@" not supported. Expecting string of form TARGET=(xxxx).
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Expecting 1 to 8 values for item identifiers for this trigger to target. e.g. TARGET=(1000,1001,1002).
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Attribute identifier "@@@NO-MORE-STRINGS@@@" not supported. Expecting string of form ACTION=(xxxx).
*** CRITICAL ERROR (line 414, item reference ref000304-1 - WALLITEM_COUNTER): Action "NULL_STRING" not supported. Expecting NULL, ACTIVATE, DEACTIVATE, TOGGLE, RELEASE or DESTROY.
User avatar
George Gilbert
Dungeon Master
Posts: 3022
Joined: Mon Sep 25, 2000 11:04 am
Location: London, England
Contact:

Post by George Gilbert »

Well, the compile error will inevitably follow from what ends up in the text file - so the problem lies in the editor (rather than the compiler).

What you should have got (and what I get) is:

Code: Select all

ref000000-1 WALLITEM_COUNTER 0 0 0 CENTRE COUNT=(0) ACTION=(NULL) TARGET=(NULL)
So...what's the difference between how you create your counter, and I create it.

I'm right clicking on a wall, selecting edit, adding a counter, editing the counter to check that it's got None/zero parameters, closing all the menus and saving. What are you doing![/quote]
User avatar
Sophia
Concise and Honest
Posts: 4307
Joined: Thu Sep 12, 2002 9:50 pm
Location: Nowhere in particular
Contact:

Post by Sophia »

I'm just adding the counter. I don't touch it. So, none of that stuff apparently gets put in. :)
User avatar
George Gilbert
Dungeon Master
Posts: 3022
Joined: Mon Sep 25, 2000 11:04 am
Location: London, England
Contact:

Post by George Gilbert »

Ah right; that would explain it.

Now fixed for V0.39.
Post Reply