Zugg Software :: View topic

Adept Joined: 18 Jun 2019 Posts: 279

Hi all,

I know I may just be dense but I am trying to auto-colour the mud rooms according to (primarily) room type. Aardwolf supplies area/room info via gmcp functions so this provides a surefire way to get correct room data.

I have two events for new rooms and for checking/adjusting existing rooms. Both work only (obviously) when in MAP mode.

OnRoomCreate

#IF (%ismember(%gmcp.room.info.details, "shop|healer|bank|questor")) {#CALL %roomcol(,coral);%roomnote(,%gmcp.room.info.details)} {#RAISE PaintRoom}

and

OnRoomEnter

#IF (%ismember(%gmcp.room.info.details, "shop|healer|bank|questor")) {#CALL %roomcol(,coral);%roomnote(,%gmcp.room.info.details)} {#RAISE PaintRoom}

I assume (quite naturally) that if the room DETAILS equals one of the supplied items (shop, etc) that the room gets coloured according to the roomcol call...and it does. The roomnote adds the roomdetails to the room properties so that it may be possible to search for room types in the notes.

I also assumed (quite incorrectly) that the #IF conditional would do the other option if the room details were not in the list, and paint the room according to the 'PaintRoom' event. It seems that this 'elseif' option is never called.

I have raised a support ticket as the PaintRoom script seems to only colour highlight a few lines of code, the rest are just plain. From switch option 'field4' to the end, all code is plain black and not highlighted. I have checked the code in a plain text editor and there is nothing untoward: no tabs, no formatting, nothing, just text.

PaintRoom

Adept Joined: 18 Jun 2019 Posts: 279

OK. So, even after no manual input...all is working again for the #IF condition...aside from the ismember logic not working against multiple inputs. There is something flaky about all this.

I have also noticed some extreme lag from time to time where a restart of the cMUD application corrects the delays.

Posted: Fri Jul 12, 2019 7:47 pm

#IF (this is true) {do this} {else to that}

Is, in fact, a valid way of expressing your code.
If you got no results off of an #IF statement of similar design, the issue is with what it is doing, not with the #IF statement.

This likely stems the fact that trying to change colors by script, still requires you to put the mapper into mapping mode first.

#CALL %maplocked(0)
#IF
#CALL %maplocked(1)

The lag could potentially be caused by bad user code elsewhere.
CMUD is a notorious memory hog and I suffered from similar issues until I got my current machine with excessive amounts of RAM.

Adept Joined: 18 Jun 2019 Posts: 279

It is possible that the insane lag happens after doing a find room. In which case it could well be database related.

[Update]

It seems this is the case. In every instance when I do a find room, after I walk to the room the client enters extreme lag mode and only restarting it resolves the problem.

Given that development on this software has ceased I doubt a fix will be forthcoming.