Zugg Software :: Search

From what I'm seeing in the docs, it appears you can get at those predefined variables simply via zs.x1(), zs.x2(), etc. When using the zs object, it will look for commands first of that name, then fu ...

As you can see from my other post, I'm clearly not the authority on LUA integration yet, but the help file you are looking for is 'zs Object'. For pretty much every object in cmud (aliases, triggers, ...

I had tried zs.func.funcname() without success... but considering the other silly issues I was having I don't put much stock in it. Your way did seem clean, and would make a clean way to build a libra ...

Woo, thank you. That was exactly what I was missing - the concept of creating actual LUA functions (function..end) vs a CMUD function containing LUA code (which is what I couldn't figure out how to ca ...

Sure enough, stupidity on my part as expected. I had "Show information messages" unchecked under Options->General->Scripting->General Scripting. Combined with not using #call, I was led down ...

The pasted code is the actual broken function. I stripped it down to the most basic 'broken' state I could just to eliminate silly things like typos. Thanks for pointing out the #call though... I some ...

It is as simple as described :) Something interesting I discovered: the below worked fine _until_ I tried adding parameters to the function. As soon as I did that, attempting to call @testlog("para ...

I'm sure this is just me doing something silly, but I couldn't seem to figure it out.

I have a simple function called 'log' that takes two parameters (classname and message). It is set to use LUA, ...

I've wanted to get into one of the Iron Realm games (Achaea, etc) just for the scripting as well... the fact that 'systems' are allowed (encouraged/required/whatever) is very very interesting. Just ca ...

I play on 3-kingdoms (3k.org). It was one of the first muds I came across back in 1993, and luckily happens to be one of the top remaining LPMuds. It plays very differently from most muds, and I encou ...

More important than the cmud mapper?! *gasp* ;) Thanks for the updates! Very excited to see it.

I use #gag quite a bit to block out a per-room 'compass' and extract the room title. 2.36 does seem faster, as there is less 'flicker' when moving from room to room as it gags the compass and rewrites ...

Probably overkill for what you are looking for, but RocketDock is pretty slick: http://rocketdock.com/

I tried a few times to dig up the original author, but to no avail. I definitely agree this belongs in the package library - I didn't realize how many people would take to it. Thanks all for sprucing ...

Thanks Fang. It was one of those things I never bothered to touch because it always worked so perfect. Tad easier to read now in the new format :)

This isn't really what you were asking for, but the following set of variables will allow you to create ASCII gauge bars in the status window. They are, in fact, quite excellent. This is not my code, ...

No worries, wasn't intended as a quick fix item. Not a showstopper, just an oddity.

Interesting screen refresh issue:

I have a trigger that captures a HP/SP line on each round of combat, #gags it, and #echos instead a round indicator (the line being captured is not a prompt). With ...

No worries, that's what beta's are for :)

Confirmed after an install of 2.01beta on top of a previously existing 1.34. This appears to be a fatal showstopper error.

Good news on the gag fixes! I've frequently seen the 'ghosting' that Guinn mentions. I wouldn't be surprised if this ghosting is what causes people to think z/cmud is "slow" - it has the appearance of ...

And I believe Zugg mentioned in another thread that #MENU is fixed with the automapper for 2.0 (or at least on the bug list _to_ be fixed).

I'm curious what you mean by slow and what mapper issues you are having? I'm running with the same system specs, and don't have any issues with either 1.34 in terms of speed or the mapper...

All sounds very encouraging!

A question on the ATCP stuff... if we can just create the telnet triggers ourselves, couldn't someone just release a Package with whatever mud's options already trigge ...

You _might_ get away with just #tagging your prompt. The mapper really likes to have the prompt explicitly identified, especially when it is one of these simple-style ">" prompts. Obviously use Fan ...