Vadi
Vadi
Comments
-
getColumnNumber(window) was broken - fixed quickly with 3.17.1.
-
Yes, I'd love to see this happen if anyone's got the time to add this. I don't have a HiDPI monitor myself so testing this isn't really feasible for me.3.11.1 fixes this up, sorry about the issue!
I'm afraid not until someone adds a wayGreat example of using functions as first class variablesThere isn't one at the moment.It would not have been lost btw, Mudlet makes backups of the stuff in the moduleSync folder (for anything else reading this).
Ah I meant https://github.com/Mudlet/MudletThat might be true too!
Also, found this interesting tidbit while looking up the history of Lua:It turned out that Bret Mogilefsky was the lead programmer on Grim Fandango, the main adventure game Luca…I don't think you can right now, but with a good use case we can consider adding such a thing!There are keybindings, would that work?I don't know what a pkgbuild is but I know that I report new versions of Mudlet against the Arch package and xabre puts out a new one within a day... he's done one for 3.4 already too.I don't have a toBoolean function in my system at all... there's a reason it's not in Lua's stdlib! Here's how Svof captures balance: https://github.com/…If you PM me, we can teamviewer and see what's going onShould still be there as-is. Are you setting any new errors in the errors window?The forums linker is buggy and made it be a giant link. I'm on mobile, but manually doing them separately will work!The mapper has always just spammed movement as fast as it can, so maybe the games movement has been reduced? You can ungag the "too fast" messages to check if it's the case.
If your S: number bottom right is high, it would mean some trigg…If you need something right now, I recommend looking into stopwatches - adding them to your prompt function and drilling down as necessary. I've found those to be help useful to tune the performance of the systems I built ( in Mudlet 3.1.0 Comment by Vadi July 2017Perhaps we need a way to track down performance issues in scripts that run. This one sounds pretty hard to pin down without sprinkling stopwatches everywhere.Oystir not sure, nothing changed in the mappers walking speed. Is this still an issue?(Quote) This has been improved - it'll now mention the script name + line number in it, which'll let you pin it down: https://www.mudlet.org/2017/05/mudlet-3-1-0/I think a better solution would be to have the MMP include special exits - if Mudlet starts persisting them, when rooms get deleted and moved about your exits will start becoming invalid.
That said, custom labels and such aren't persisted…