bug? in !entity

I have the impression that when the server re-sends an !ENTITY line Mushclient doesnt replace (overwrite) the first definition.

The spec gives the impression that this can be used to actualize an MXP variable in the client:

"The <!ENTITY> tag allows the MUD server to set the value of a variable without displaying the value to the user."

And this does work in cmud.

I am sending for example (omitting MXP encoding):

!ENTITY HP 100
!ENTITY HP 77

The second line doesnt register a change in the menu "world configuration->variables".

Entities don't change variables. Use:




See:

http://www.gammon.com.au/forum/?id=226

*Elements* can change variables, eg.



That would change mxp_hp variable.

Hm, but using an predefined !ELEMENT or VAR tag outputs the value to the player in-stream. Using !ENTITY hides it.

I dug around a bit and found this thread
http://forums.zuggsoft.com/forums/viewtopic.php?t=14249 (third post)

"OOps, syntax should be:
...
<!ENTITY Hp 50>
depending upon whether you want to display the variables or not"

If you are wanting a variable set, this is for scripting, right? So my solution lets you get at the number.

uh, no. I'm thinking server -> to -> client. Should have made that clear.

I'm sorry, I don't understand the problem. Can you explain in more detail what you are trying to do, and in what way my earlier suggestion does not solve that?

I'm a server admin and I want my server to update MXP variables in the client. For example to tell the client the HP just changed.
The client-user can then use them in his scripts.

As I understand the spec there are two ways of the server setting MXP variables in the client:

1.) using a <var> tag or a custom element definition as you proposed abvoe. This will look like this: <var HP>60</var> and the value 60 will be displayed to the user. Servers will use this method if they want to display the value anyway, like in prompts or a character vitals screen.

2.) using !ENTITY like this: <!ENTITY HP 60> and nothing will be displayed to the user. Servers will use this if they want to silently update the value in the client.

Mushclient seems to not correctly implement 2.) but I'm pretty sure now that it is the way the spec was supposed to work (see my quotations for example and cmud does show this behaviour).

Of course I could work around that just for Mush, but I think it is a bug and I wanted to confirm and report it.

I'm not sure exactly which part of the spec MUSHclient is not following, but I assume you are referring to this:

http://www.zuggsoft.com/zmud/mxp.htm#ENTITY



I note that you didn't mention "publish" in your example so I am guessing a bit here.

*Are* you referring to that? In which case a more complete example, mentioning the word "publish" would have helped.

I think the MXP spec has changed since I implemented it. I am getting a bit tired of having the spec change without me being informed, and then getting "bug" reports that some behaviour, of which I know nothing about, is not implemented.

In any case, I don't like the idea of the server randomly changing client variables. If you mean that your example should change the "hp" variable, what if the client was using that variable for some other purpose? And in the case of MUSHclient, you can have multiple plugins. Should the variable be changed in every plugin script space, or just the main world?

In the case of the "element" variable setting which I mentioned, I specifically prepended "mxp_" to the variable being set, in case that variable was used by the client for some other purpose.



You don't need to work around it. MUSHclient and cMUD have different scripting anyway, so as long as the variable is accessible to the script, what do you need to worry about? You can hardly have identical scripts running on both clients, and since they have to differ, they can differ in the way they grab that variable. What is the problem exactly?

Problem: I (the server) am sending variable updates with the ENTITY-Tag and Mushclient-users are not registering them.



No, I am only sending <!ENTITY name value> and referring to:



from the VAR section of http://www.zuggsoft.com/zmud/mxp.htm (just beneath the ENTITY section).
Since this can be misinterpreted, I looked for confirmation elsewhere and found:


Summing up: The server sending the sequence
<!ENTITY HP 50 publish>
<!ENTITY HP 40>
should create a variable in the client called "hp" (in Mushclient prependet wit an "mxp_") and initialize it to 50, then set it to 40.
Mushclient does parse the second line but does not update the variable as I would have expected.

(the second line may or may not have a publish - I am not quite clear on that)

On that page you quote:



There is no talk about "<!ENTITY hp 50>" updating a *variable*.

I still don't understand your problem - this isn't a bug, according to the MXP spec variables should only change if you use the PUBLISH keyword, and you said you are not doing that. So what is the bug? There isn't one.

If you are trying to draw a gauge, and in MUSHclient you have to script to do that, you would do something like this:

The relevant part of the MXP spec says:



Note that it says that Entity sets MUD Server variables - not client variables. It would be a crazy system if the server could just change client variables willy-nilly. The current version of the MUD Server variable set by the !ENTITY command is stored in a lookup table inside MUSHclient and can be queried with GetEntity(<name>). This is logical and what MUSHclient does.

Aaah, I just had an epiphany why we are so utterly confusing each other!

I think you are seeing the "thing" the server sends in <var> tags as something different than what the server sends in a <!entity> tag. Am I right?

Look, if I send
<var HP>40</var> to mushclient the "mxp_hp" variable shows up in world-configuration->scripting->variables.

If I send
<!ENTITY HP 40 PUBLISH> to mushclient "mxp_hp" doesn't show up.

Before we start quoting the spec at each other again I should ask: Is there a reasoning on your side behind this?

Before I answer that can you please explain in what way you can't use MUSHclient to display the gauge you want to display, using the method I described above?

I am not looking to display a gauge. The linked discussion referred to a gauge, but this was a MXP <GAUGE> tag, which connects a gauge with a MXP entity/variable - displaying the gauge with the value of that entity/variable sent from the server. The post in question I used as an example for how to correctly send the value == entity/variable.

sever sends: <GAUGE HP MaxHP> (syntax by heart) will tell the client to display a gauge in cmud/zmud with the values of "HP" and "MaxHP".
server sends: <var HP>60</var> or <!ENTITY HP 60> will update the cached value in the client and thus change the gauge.

I can also find other examples on using <var> and <!ENTITY> if you wish, so please ignore the <gauge> reference. It is not relevant to my intention.

ps: When I write: "I send ..." I'll always mean that the server sends. Le server, c'est moi.

The real issue here has nothing to do with the spec. MUSH implements the spec just fine. It has to do with how MUSH handles MXP entities versus MXP variables when it comes to automatically storing them as script variables.

As Xtian said in his other post, MUSH does not automatically produce "mxp_"-prefixed script variables for MXP entities like it does for MXP variables. Even though these entities are still available to scripts through the GetEntity() interface as Nick pointed out, the problem here isn't one of availability; it's of convenience.

It would be -convenient- if MXP entities produced "mxp_"-prefixed script variables like MXP variables do. This, however, has nothing to do with the spec. As long as MUSH is making entities accessible to its users (it is), it's complying with the spec.

So, in short, this is not a bug. It's a feature request.

Drrcknlsn, thanks for clarifying that.