Howdy, Stranger!
Categories
- 6.2K All Categories
- 3.1K Everything Achaea
- 1.5K North of Thera
- 26 Archives of the Terraformer
- 257 The Matsuhama Arena
- 885 The Golden Dais of Creation
- 299 The Scarlattan Theatre
- 149 The Blank Canvas
- 2K Getting Help
- 412 General Questions
- 258 Quick Class Questions
- 1.3K Tech Support
- 313 Client Help
- 486 Curing Systems and Scripts
- 841 Off-Topic
- 255 The Wander Inn
- 586 The Universal Membrane
- 298 Class Discussions
- 298 Individual Class Sections
- 20 Alchemist
- 9 Apostate
- 30 Blademaster
- 9 Depthswalker
- 14 Druid
- 4 Infernal
- 20 Jester
- 19 Magi
- 34 Monk
- 11 Occultist
- 8 Paladin
- 7 Priest
- 29 Runewarden
- 18 Sentinel
- 26 Serpent
- 20 Shaman
- 9 Sylvan
Comments
GMCP documentation: https://github.com/keneanung/GMCPAdditions
svof github site: https://github.com/svof/svof and documentation at https://svof.github.io/svof
As far as I know, there is no setting for that.
GMCP documentation: https://github.com/keneanung/GMCPAdditions
svof github site: https://github.com/svof/svof and documentation at https://svof.github.io/svof
Artemis says, "You are so high maintenance, Tharvis, gosh."
Tecton says, "It's still your fault, Tharvis."
GMCP documentation: https://github.com/keneanung/GMCPAdditions
svof github site: https://github.com/svof/svof and documentation at https://svof.github.io/svof
The problem during start up is fine, really. What really gets me ticked is when I type something really long (in the command line) and the window automatically shrinks back to the minuscule little size it starts off in. This makes customizing ANYTHING pretty challenging.
Is it at all possible to script the main window size to a certain width, pixel wise? I resize my containers this way, and there's ways to make the border sizes vary.. but is it possible with the main window?
only thing I can find about the command line is "minimum height in pixels" setting, and as far as I know it's not possible to script size the main window
I do vaguely recall having your problem a few years ago, can't remember the specifics of how I fixed it - back up your profile and reinstall mudlet?
(also, are you using mudlet 2.1 or mudlet 3?)
Artemis says, "You are so high maintenance, Tharvis, gosh."
Tecton says, "It's still your fault, Tharvis."
GMCP documentation: https://github.com/keneanung/GMCPAdditions
svof github site: https://github.com/svof/svof and documentation at https://svof.github.io/svof
GMCP documentation: https://github.com/keneanung/GMCPAdditions
svof github site: https://github.com/svof/svof and documentation at https://svof.github.io/svof
Results of disembowel testing | Knight limb counter | GMCP AB files
Results of disembowel testing | Knight limb counter | GMCP AB files
1. I'm seeing a random number of small blue (cyan) periods (dots) next to my prompt. I'm using AK, Wundersys, and so far I've only been able to figure out that it isn't a part of owsysprompt().
2. My wsys.doradd("butcher corpse") ends up queuing "touch shield" instead, probably from the alias "ts" which sends -- wsys.dofirst("touch shield"). Not sure why it's doing that.. I've tried clearing the dor queue but it still won't clear it.
3. My DOR has been getting slower and slower, recently with the last update. I've figured it might be due to wsys.myPing() being super high (I've made a quick fix of making it 0.1, which is a LITTLE bit better). the function in the script says wsys.myPing()*3, which makes anything and everything super slow and unusable.
Thanks again for the help! I've been wracking my head and I just haven't been able to find the help in game.
edit: also, problem 1 seems to have occured near around the time I tried to import Keneanung's bashing script.
2 sounds like it's the same thing other people have been mentioning on the forums. Try setting the QUEUESHOWALERTS (or whatever it's actually called) config option to YES/TRUE/ON again in-game.
No idea about 3 though, sorry.
Results of disembowel testing | Knight limb counter | GMCP AB files
#1 is still messing with me, but thankfully it doesn't have any downsides other than visual effects.
#3 is also not as urgent, as I only use DOR for butchering. Also, I managed to get to 157 queued commands using #wsys.doqueue.. so I decided to not use the doqueue until I know how it works
I have improved my prompt triggers beyond belief, so I might go ahead and update that too. Will definitely look into it, though. It can be a pain to take newer logic and revert back into older scripts, so you might get stuck fixing that one on your own. Logs with errors would definitely reveal more.
Edit: can message ig, pm forums, or post here
Also had a problem where my wsys.doqueue and wsys.dofreequeue gets cluttered. I know @Monev had the problem too. I do a quick fix of just making them both =nil.. but is there a way I can do a complete fix?
7.3 – Stateless Iterators
As the name implies, a stateless iterator is an iterator that does not keep any state by itself. Therefore, we may use the same stateless iterator in multiple loops, avoiding the cost of creating new closures.
On each iteration, the for loop calls its iterator function with two arguments: the invariant state and the control variable. A stateless iterator generates the next element for the iteration using only these two arguments. A typical example of this kind of iterator is
ipairs, which iterates over all elements in an array, as illustrated next:a = {"one", "two", "three"} for i, v in ipairs(a) do print(i, v) endThe state of the iteration is the table being traversed (the invariant state, which does not change during the loop), plus the current index (the control variable). Bothipairsand the iterator it returns are quite simple; we could write them in Lua as follows:function iter (a, i) i = i + 1 local v = a[i] if v then return i, v end end function ipairs (a) return iter, a, 0 endWhen Lua callsipairs(a)in a for loop, it gets three values: theiterfunction as the iterator,aas the invariant state, and zero as the initial value for the control variable. Then, Lua callsiter(a, 0), which results in1, a[1](unlessa[1]is already nil). In the second iteration, it callsiter(a, 1), which results in2, a[2], and so on, until the first nil element.The
pairsfunction, which iterates over all elements in a table, is similar, except that the iterator function is thenextfunction, which is a primitive function in Lua:function pairs (t) return next, t, nil endThe callnext(t, k), wherekis a key of the tablet, returns a next key in the table, in an arbitrary order. (It returns also the value associated with that key, as a second return value.) The callnext(t, nil)returns a first pair. When there are no more pairs,nextreturnsnil.Some people prefer to use
nextdirectly, without callingpairs:for k, v in next, t do ... endRemember that the expression list of the for loop is adjusted to three results, so Lua getsnext,t, and nil, exactly what it gets when it callspairs(t).The short version: they're variable declarations, and the actual names chosen are arbitrary (i = index [for ordered lists], k = key [for dictionaries], v = value). So, for each iteration, i/k stores the index/key, and v stores the value that index/key corresponds to.
You can call them whatever you like though, and I find it's helpful - especially when nesting iterations - to actually give them proper names that correspond to what they are. For example, my rite tracking script has a dictionary (I'll call it 'mydict' for this) that maps room ids to another dictionary that stores the duration of each rite in that room. So when iterating over that first dictionary, rather than 'for k, v in pairs(mydict) do' my code would be 'for roomid, rites in pairs(mydict)'. If I was then, inside of that iterator, iterating over that inner dictionary (i.e. what 'rites' refers to), I'd do 'for rite, duration in pairs(rites)'.
Results of disembowel testing | Knight limb counter | GMCP AB files