MUSHclient Plugin Development Thread

[Olyn]

It looks like MUSHclient and TinTin++ still be the big two clients for those off us interested in msdp. Msdp support is the biggest gamechanger that I can think of in our game's history. I'm curious to see who is interested/capable of helping to developing a true AR plugin for this client. I came across this screenshot of another game's plugin. We can definitely do this and more.

http://www.slothmud.org/images/splork/v2.5%20MC.PNG

[Davairus]

thats j ust generic gui
you can get that here

http://www.godwars2.org/download/Generic_Plugin.zip

unzip to root of mushclient or something

[Olyn]

It's a place to start.

[Mikoos]

Sign me up. set up the main repo and I'll do a pull I'm guessing we'd want to basically clone the webclient? so something like these features:

minimap,
affects,
group members listed,
health, mana, and move bars,
character sheet,
inventory,
an exp bar
and whatever else.

hell, we could find an open sourced client and hack the crap out of it (as long as it already supports MSDP)

[Faelon]

I think Mudlet is open source and it supports msdp.

[Davairus]

mudlet supports ATCP and our code doesnt support that, but it does support fallback to MSDP through ATCP (the two protocols are actually very similar). i tried to figure this out a couple nights ago but eventually dropped all the fucks i gave.

client/server requests and responses

Client: IAC SB ATCP "MSDP" IAC SE
Client: IAC SB ATCP "REPORT HEALTH MANA" IAC SE
Server: IAC SB ATCP "MSDP.HEALTH 500" IAC SE
Server: IAC SB ATCP "MSDP.MANA 100" IAC SE

You can probably do that with any actp supporting mud client


the alleged mudlet script

sendATCP("MSDP", "")
sendATCP("REPORT", "HEALTH MANA ACTIONS")
display(atcp)

Displays:

table {
'MSDPMANA': '150'
'MSDPACTIONS': '1280'
'MSDPHEALTH': '1352'
}

using

int TLuaInterpreter::sendATCP( lua_State *L )
{
string msg;
if( ! lua_isstring( L, 1 ) )
{
lua_pushstring( L, "wrong argument type" );
lua_error( L );
return 1;
}
else
{
msg = lua_tostring( L, 1 );
}
string what;
if( ! lua_isstring( L, 2 ) )
{
lua_pushstring( L, "wrong argument type" );
lua_error( L );
return 1;
}
else
{
what = lua_tostring( L, 2 );
}
string _h;
_h += TN_IAC;
_h += TN_SB;
_h += 200;
_h += msg;
_h += " ";
_h += what;
_h += TN_IAC;
_h += TN_SE;

Host * pHost = TLuaInterpreter::luaInterpreterMap[L];
pHost->mTelnet.socketOutRaw( _h );
return 0;
}


source: http://forums.mudlet.org/viewtopic.php?f=7&t=1418&sid=bba9e608ebea617ecb2f13494f763941&start=20
look for this file on that thread that should be of help. http://forums.mudlet.org/download/file.php?id=306

[Olyn]

mudlet 3.0.0 alpha was just released 2 weeks ago and has native msdp support

[Mikoos]

hmmm seems workable. I can't believe it's 2014 and there's not a java(or even python) client with MSDP support. I hate Lua in mudlet, but if we can do everything in cpp, then I won't have a problem with it.

[Vanisse]

just wanted to temporarily threadjack and say you guys are awesome. that's all. and now, back to programming

[Rothak]

Is there a way to send a time once a certain trigger happens in game? I use mush client but I'm not savvy by any means. If someone knows one, could you send it here? Thanks

[Vanisse]

there's a timestamp thing in this chat thing somewhere http://abandonedrealms.com/forum/viewtopic.php?t=8378

[Mikoos]

alright so I'm an idiot. Mushclient does do everything we want and is more customizable than I realized(the source is open, but we won't have to mess with that for this) anyway the generic plugin sort of blows up and I had to download a new one to mess with(I would post a screenshot, but not advertising another mud). basically the goal here for mushclient would be to develop XML with lua inside of it. the XML will format the client for the display and the lua will take care of the MSDP protocal. once that's done we'll flesh it out with specific scripts and aliases. will post a link to the repo once I have the basics going.

[Mikoos]

[Mikoos]

Alright so, below this is a simple lua script I made, just to see what lua was all about. originally it was suppose to be OOP, which is why everything is encapsulated in mines, but OOP inside of lua, because it's inside of mushclient, is fugly so I didn't go with that. Anyway, it collects silver ore and it should work, but you may have to tinker with the path, might have broke it. This will be the last lua script I make for the mushclient plugin, I hate tje so called 'timer' which is why it's not in the script. the way it increments and decrements is retarded (which is why you see variable = variable +1, instead of variable++) and all around it got on my nerves, thankfully mushclient supports python, so I'm going with that. AFTER I do the MSDP thing. And if anyone with l33t XML skills wants to hop on the project, that would be great.

[Mikoos]

Something else for the list I forgot to mention. In the function you make to call up the script, make it so that that it accepts a parameter for total silver ore you wanted collected. The variable is already there, max_silver_ore

[Mikoos]

UPDATE: So I have the mini map being drawn to a mini-window of MUSHclient, unfortunately the colors are not working properly, due to an issue in MUSHclient. The client can handle all kinds of colors from strings, but only if you can get what's called 'style runs' of the string. unfortunately this is almost impossible with strings collected from MSDP variables. The good news is, I'm talking to Nick Gammon, the gentleman who programmed MUSHclient, and seeing what we can do...if we hit a roadblock, or if he comes up with a ridiculous way to get around this, I may submit a patch to MUSHclient (or he may write his own.) ...stay tuned.

[Davairus]

THATS not going to work because you are supposed to use the autmapper not try to process the one we send
read help color code + use substitutions is probably your answer

[Mikoos]

Why send a map, if clients are not suppose to use it? It works for tintin++ just fine, in fact Tintin++ automatically formats and colors everything from ROOM_MAP, but not MUSHclient. My goal is to keep the processing of the mud client minimal as possible, and having the map automatically sent by the server should do that. And plus it's sent via MSDP, which is what I thought the purpose of this was.

[Davairus]

ok

[Mikoos]

actually, with more thought I see what you're thinking: That his client was designed for his automapper alone and not originally for MSDP, which would make sense, but on the other hand all I'm doing is parsing a string for basic ANSI codes...which his client should have been able to do (and it does, but only when packets are received, not with strings that are already stored in a table.)