The current Pueblo enhancer's guide (ref: Pueblo/UE, pueblo.sourceforge.net) suggests that the following string from the server should be ok:
This world is Pueblo 2.50 Enhanced.
When I send this string in PennMUSH, MUSHclient stops using Pueblo (Settings are "on demand" and "detect initiation string")
When I have the server send 1.10 Enhanced instead of 2.50 Enhanced, all is well.
This seems like a problem.
(I did debug packets this time. :)
- Alan
I think the Pueblo enhancements have overtaken MUSHclient. I think MUSHclient only supports 1 and 1.10.
That's fine - then MUSHclient should just return "PUEBLOCLIENT 1.10 md5="blah"" and the server will know the client only handles up to 1.10 (not that there's a lot of difference yet)
But I think you still want to be liberal in what server version you accept as a valid intiation string.
(Can you tell we're doing Pueblo cleanup in Penn? :)
I just implemented what the spec said, it expected Pueblo 1, or 1.10, not Pueblo *, however maybe that was a bit anal of me.
Still, can't you send both strings?
This world is Pueblo 1.10 Enhanced.
This world is Pueblo 2.50 Enhanced.
That's a clever solution. However, it will cause the other pueblo client (Pueblo/UE, at least) to response twice with PUEBLOCLIENT requests. Not, that's not a disaster, since a mud is supposed to always use the latest PUEBLOCLIENT it receives.
To my eye, anyway, it seems an inferior solution than having the client pick up the version number (which it might want to make available to the user for information, scripting, etc.) But if you don't want to do that, hey, you're the author. :)
Next version, Javelin. :)
I was trying to do a workaround for now.
You rock.
My workaround for now is to keep with the old 1.10 string in PennMUSH until I know my favorite client will work with the new one. :)
I thought Pueblo wasn't under development any more, so I thought I was safe. :) Ah well, just when you think it is safe ...
I am new to this and want to make Pueblo settings on the mu* I RP at, that actually is NOT pueblo enhanced; but Pueblo works there anyway.
I'm exchanging pueblo for mushclient (spellchecker is a quite good reason) and I would like to know in smalll details how to send this pueblo string to the world.
Do I simply put @emit This world is pueblo enhanced upon log on?
Thanks.
Why do you want to do this?
In MUSHclient you can have MXP (Pueblo) on permanently. Why not just do that?