Issues with MXP in MudPortal

Just letting people know that I addressed all the issues I saw yesterday. Thanks for reporting.

Sometimes, when you add a lot of new stuff fast, some of the stuff that used to work breaks. So I rely a lot on testers.

Zivilyn wrote: Thanks a ton for dropping in plamzi, I'll let you know if other things pop up.
Did you have a chance to check the pull-down menu's vanishing? Say if you had 'north' with autoexit turned on. You go over north and the 'north|scan north|listen north' menu pops up, but then goes away before you can click. I believe mostly when over the top of another link (ie the mobs in the room).

Thanks!
- Dave.

Can you clear your browser cache and try again? This issue should have been fixed.

Zivilyn wrote: Did you have an API on creating new windows?
(Was thinking say char status things, also eventually graphical map (using MSDP to pinpoint room/graphic), perhaps a compass type controller for movement etc.
Thanks!
- Dave.

For an example of how to create new windows, look at the MacroPane.js plugin.

For char status, take a look at the MistyBars.js plugin. You can see it in action when you connect to Bedlam and open your browser debugging console. It's driven by GMCP data, but if you're comfortable with JS, you can adapt it fairly easily to use MSDP instead.

If you have an ASCII / UTF-8 map, you can redirect it to another window pretty easily. I was thinking that would be one of my next plugin examples.

For a graphical map, my advice is to wait until I release the vector map plugin that I'm currently working on. Unless you are really comfortable with JS, in which case we should team up

A couple of other plugins will be released soon: multi-tabbed chat window, group status bar, a window in which you can show iframe content (e. g. your web-based help files).

arholly wrote: I'm still getting the problem with MXP sometimes exposing the code. Clicking on anything after that causes the app to crash.

Quickest way to reproduce?

Turns out MXP was a bit broken after some code refactoring I did over the weekend. Can you still reproduce the issue you saw earlier today?

Zivilyn wrote: Hey plamzi, I was testing out MudPortal on Ansalon again and the MXP isn't functioning (yet on my account I do have MXP checked via the site). Is there a setting we need to check or variable we need to pass in the connection string to say 'yes use MXP' or such now?

Thanks much man, love what you've done for mudding!
- Dave.

Hi,

I had to disable the aggressive IAC DO MXP negotiation because it caused issues with games that don't have MXP support and don't implement TELOPT fully.

Basically, you have two options. One is to make sure the server sends IAC WILL MXP on connect. The other is to set "Config.forcemxp = 1" in your official JS code, an option I just added.

My guess is other clients have workarounds for this inconsistency. I can't think of one yet that will not dent performance, but if I do, I'll add it.

And yes, I will document the Config options very soon, it's just things are happening fast.

plamzi wrote:

Zivilyn wrote: Basically, you have two options. One is to make sure the server sends IAC WILL MXP on connect. The other is to set "Config.forcemxp = 1" in your official JS code, an option I just added.

Ignore the above. I believe I sorted out the negotiation issue today and you don't have to do either for MXP to be working again.