Mudlet features and API requests

User avatar
Vadi
Posts: 4728
Joined: Sat Mar 14, 2009 3:13 pm

Re: Mudlet features and API requests

Post by Vadi » Sat Sep 23, 2017 6:16 am


azure_glass
Posts: 97
Joined: Wed Jul 25, 2012 12:35 pm

Re: Mudlet features and API requests

Post by azure_glass » Sat Sep 23, 2017 5:19 pm

I think the "create Label" on mapper needs to be rethink to something more useful.

Maybe the text should be added first and then calculate width or height....
English is not my native language. If you don't understand what im writing ask. :)
Ubuntu 17.04, Mudlet 3.1

Esqurel
Posts: 1
Joined: Sun Dec 03, 2017 11:40 pm

Re: Mudlet features and API requests

Post by Esqurel » Sun Dec 03, 2017 11:44 pm

I'm not seeing a way for prefix() to work with colors. If that's true, I'd love a way to do so, perhaps cprefix() and dprefix() like exist with echo()?

schil
Posts: 1
Joined: Thu Dec 07, 2017 3:08 am

Re: Mudlet features and API requests

Post by schil » Thu Dec 07, 2017 3:14 am

A really great feature would be an option to delay lines sent to a mud. For example as a mud building I like to write help files in a text document then paste it all into the mud client. The issue however is when you paste over a certain amount of lines too fast it causes a buffer overload on the mud and it disconnects the user. A nice feature would be something to delay set a delay between the lines. This has been implemented in other popular clients and i would love to see it here.

User avatar
Vadi
Posts: 4728
Joined: Sat Mar 14, 2009 3:13 pm

Re: Mudlet features and API requests

Post by Vadi » Thu Dec 07, 2017 3:52 am

This could be implemented using a script in Mudlet, actually! Perhaps reach out for help on the help forums - it's possible using sysDataSendRequest and denyCurrentSend().

Smegz0r
Posts: 2
Joined: Fri Dec 22, 2017 10:06 am

Feature request

Post by Smegz0r » Fri Dec 22, 2017 10:10 am

I need to be able to enable/disable Mudlet scripts. I can do that with triggers and timers but not scripts. I currently have a script that I need to disable across all of my distributed code via an online update but at the moment that is not possible. Also just wondering why scripts were excluded in the first place from having this ability?

Thanks.

User avatar
Vadi
Posts: 4728
Joined: Sat Mar 14, 2009 3:13 pm

Re: Mudlet features and API requests

Post by Vadi » Fri Dec 22, 2017 2:44 pm

Well say a newbie copy/pastes some Geyser code to create a GUI, and then wants to disable the script to hide it. It won't work even if we had a function because even though a script is disabled, any functions or code that ran as part of it already exists.

The only thing it could affect are event handlers - and we've already added killAnonymousEventHandler() for that. Hope that helps!

Jor'Mox
Posts: 1100
Joined: Wed Apr 03, 2013 2:19 am

Re: Mudlet features and API requests

Post by Jor'Mox » Fri Dec 22, 2017 5:45 pm

I always build "enabled" type variables into all the public functions of my scripts, so they can be disabled that way. Switch the variable, and suddenly the script stops responding.

User avatar
Vadi
Posts: 4728
Joined: Sat Mar 14, 2009 3:13 pm

Re: Mudlet features and API requests

Post by Vadi » Fri Dec 22, 2017 7:16 pm

Yeah, killAnonymousEventHandler() is pretty new...

Smegz0r
Posts: 2
Joined: Fri Dec 22, 2017 10:06 am

Re: Mudlet features and API requests

Post by Smegz0r » Sat Dec 23, 2017 4:51 am

In this case that won't work as the script I want to disable is sysIrcMessage so I can register it elsewhere in my code at a later point in time.
I'm not sure that using killAnonymousEvent will work either since the script is built into the profile currently. My best solution is to distribute a new script with a script version flag.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 3 guests