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
You need to create labels in a specific order. The first label is on the bottom, the next will be created on top of the first, and so on.
Example label with a background image where the container is an HBox:
tab_all = Geyser.Label:new({ name = "all channels tab", x = 0, y = 0, height = 20 }, tab_container) tab_all:setBackgroundImage([[C:\path\to\tab_all_inactive.png]])Above is my code. I'm just learning, so it's pretty rudimentary, I know, but I'm having some serious problems.
When I use the alias on a target that is not curing, it first gives then nausea/paralysis, then it does nothing. Absolutely nothing. If the target is curing, it does nothing when they have paralysis. After fiddling around, I found that when the target has paralysis, the activated/deactivated box next the script's name is the ladybug, and this bug message appears:
Lua syntax error: ./mudlet-lua/lua/TableUtils.lua:101:bad argument #1 to 'pairs' (table expected, got string)
I have 0 idea what that means. Any help?
You'd be much better off using a table like this:
targetafftable = {
The table.contains function source:paralysis = false,
...
}
if targetafftable.paralysis then
...
Can you reference a script to make it run again?: No. Well, maybe (there's probably a function in Mudlet somewhere for it). But you shouldn't. If you want to run something in a script, have the script define a function that does that thing, then call the function from your trigger or alias or whatever. If you want whatever the function does to run at startup too, just call the function right after defining it in the script.
Can you exclude a script from running at startup?: Just uncheck it.
Like, if I wanted to make a setup for milling inks or gathering herbs, could I write a script for the bulk of the work and just feed in values, and only run it when I tell it to run?: What you are describing is a function, not a script.
One thing that seems to be a really common hangup is thinking that your code and the stuff it produces are the same thing. They aren't. Your code is like a recipe and the computer is the cook that takes you recipe and produces some invisible state. Don't get the recipe and the dish it makes confused. When you say [target = "rat"], that isn't the variable itself, that's a recipe for the variable - you're saying "dear computer: set the contents of your invisible target variable to "rat"". When you reference your target variable later, you're saying "dear computer: please use whatever is contained in the variable called target".
Defining a function is a way of saying "Dear computer: set the contents of an invisible variable named <function name> to this list of instructions that I don't want you to follow right now, but I want you to remember them under this name so I can tell you to follow them later". The script that defines your function isn't the instructions you want the computer to follow later, it's an instruction to remember those instructions (it's the recipe for a recipe). You usually want to put function definitions like this into Scripts in Mudlet because you want to get the functions set up as soon as possible, so they're ready to call whenever you need them.
And "feeding in values" is exactly what functions let you do.
So here's an example of a really simple function (note: any time I use brackets below, it's just to make it clear what is and isn't code):
Now if you just have this in your script, it doesn't do anything. All you've done is told the computer to store this list of instructions under the name helloName. When you want to actually use them, you do:
helloName("Tael")Now that tells the computer: look for the function called helloName and run it. Notice how I passed the function the string "Tael" - that gets passed as the first argument to our helloName function which we called [name] (we could have called it anything we want, the point is that when it comes up again inside the function, it refers to the value of the argument - so name gets bound to "Tael" and when the function execution goes to see who to say hello to, it looks up the value of name, which is "Tael").In fact, functions are even neater - there are two other important things you can do with functions.
The first is local variables. Let's say I want to say hello to two people:
(I could have just done send("say Hello " .. nameOne .. " and " .. nameTwo), but bear with me.)
The thing is, what if you have a variable named [toSend] somewhere else? Or some other function that uses a variable called [toSend]? You don't want those variables interfering with each other. Well, you don't have to worry: local variables only exist inside the function, so it won't matter. If you called this function then tried to print toSend, Mudlet would tell you it has no idea what toSend is. It's a good habit to keep as many variables local as you possibly can. Arguments are local variables too. If you run this function and then ask what nameOne or nameTwo is, the computer won't have any idea - it only knows about them while running the instructions inside the function.
The other thing functions can do is return things.
Let's say you want to remember the last message you sent. You could just save it to a normal global variable, but let's say you only want to save it sometimes. Or maybe you have two aliases that both call your helloName function, but you want to save the messages it sends independently. This is where return comes in.
So now instead of your aliases both looking like [helloName(matches[2], matches[3])], one can look like [savedCommandOne = helloName(matches[2], matches[3])] and the other can look like [savedCommandTwo = helloName(matches[2], matches[3])]. These run the function, passing it the arguments, then save whatever was returned to a variable.
The only thing to remember about this is that return must be the last thing in the function (the computer stops executing the function as soon as it hits a return).
1) Condense mindnet party announcing to do one line for multiple enemy entrances/departures instead of an announce for each individual person.
2) I have a fullsense script that will announce all enemies in the area. What I want to do is to somehow include the room name with the area. I've already learned that gmcp.Room.Info.name does not do that, hehe.
If I call targetaffadd("weariness"), will this function set
targetafftable.weariness = true
and
targetafftable.mighthaveweariness = false
?
Or do I need to do it another way?
2. There's a function somewhere in the Mudlet mapper scripts you can steal borrow. Can't recall offhand the name though (mmp.locateandecho?), so you'll have to search for it.
targetafftable = {
paralysis = false
}
Still need quotes?
In the definition of the function, you don't use quotes. You're declaring a parameter for the function - or, in other words, you're defining the name of a variable (locally-scoped to the function) to be created when that function is called. When calling that function, you'd want double quotes (because you want the affliction variable inside the function to have the actual string value "weariness"). Calling targetaddaff("weariness") would essentially make the body of the function (for that specific call) the same as this:
Results of disembowel testing | Knight limb counter | GMCP AB files
With serverside turned on : https://ada-young.appspot.com/pastebin/197c7382
With serverside turned off : https://ada-young.appspot.com/pastebin/041eef99
Salve prios : https://ada-young.appspot.com/pastebin/ba496169
Has anyone else run into this problem?
[ SnB PvP Guide | Link ]
That's gmcp.Char.Vitals
If it was tracked, it would be somewhere in this (I believe), so I would have to assume that it isn't listed in gmcp.
Penwize has cowardly forfeited the challenge to mortal combat issued by Atalkez.
[ SnB PvP Guide | Link ]
--I'd like a categorized list if plausible to note the very basics/foundation of a system.--
2. Making an affliction tracker, what do I need to account for? timers, etc.
3. How would someone track smart afflictions(i.e smash high, sicken) I'll use sicken - it gives paralysis > manaleech > slickness. For any means of writing an affliction tracker - how would someone account for the ability giving different afflictions and more importantly how would they use that logic in the selection of afflictions?
The very basic foundation of a system is the list of requirements for what you need it to do. If you don't have that you shouldn't really be writing any code. You can always change or add requirements later on, but you have to have an initial list of things you want to accomplish. If you're wanting us to provide that, the absolute basics:
an alias to store a target in a variable
aliases for all of your attacks which use that variable
How complicated you want to get is up to you, and will to some degree be dictated by how competent you are as a coder, but the first thing you need to decide is what you want/need.
Results of disembowel testing | Knight limb counter | GMCP AB files