vorld2011-11-25 19:10:22
Fixed that Thank you Zarquan
vorld2011-11-27 21:31:50
I got another problem
Here is my bashing attack
if mm.stats.momentum == 0 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 1 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 2 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 3 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 4 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 5 then
send("kata perform ".. tar .." bash_high")
end
The problem is this
The bash_high Kata form is too complex for you to execute at this time.
How do I fix this?
Also how would I track shielding?
Here is my bashing attack
if mm.stats.momentum == 0 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 1 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 2 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 3 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 4 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 5 then
send("kata perform ".. tar .." bash_high")
end
The problem is this
The bash_high Kata form is too complex for you to execute at this time.
How do I fix this?
Also how would I track shielding?
Lilia2011-11-28 01:47:52
The problem is probably due to switching targets. Hitting a new target reduces momentum by two, but it doesn't actually happen until you hit. So if you have three momentum, when you try to hit with a two momentum form, you get the 'too complex' message, because your momentum after hitting the new target would be one. It's hard to account for this in the sort of bashing function you have. The way I did it was to simply have two attack aliases, and figure out for myself which one to use. After I initiated, the regular logic would take over. You could also add a variable into your logic that helps account for the momentum loss. Something like, trigger ^You have slain .+$ to set newtar = true, then make these changes to your logic.
if mm.stats.momentum == 0 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 1 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 2 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 3 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 4 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 5 then
send("kata perform ".. tar .." bash_high")
end
vorld2011-11-28 17:30:06
Lilia:
The problem is probably due to switching targets. Hitting a new target reduces momentum by two, but it doesn't actually happen until you hit. So if you have three momentum, when you try to hit with a two momentum form, you get the 'too complex' message, because your momentum after hitting the new target would be one. It's hard to account for this in the sort of bashing function you have. The way I did it was to simply have two attack aliases, and figure out for myself which one to use. After I initiated, the regular logic would take over. You could also add a variable into your logic that helps account for the momentum loss. Something like, trigger ^You have slain .+$ to set newtar = true, then make these changes to your logic.
if mm.stats.momentum == 0 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 1 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 2 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 3 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 4 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 5 then
send("kata perform ".. tar .." bash_high")
end
Yes that is the problem actually my thanks. So do I have to make a new trigger for this code to work then?
Also is this the right syntax?
local commands = {"n", "s", "w", "e","nw","ne","se","sw","in","out","down","up"}
send("mislead " .. "commands")
send("backflip " .. pvptar .. " down")
will the random choose down if I do it this way?
Lilia2011-11-28 21:39:01
Just one, for when you kill something. And add newtar = false at the very end of that alias code, too.
vorld2011-11-28 21:48:37
Made this
It gave me a syntax error. What did I do wrong?
also another syntax error
^You have slain .+$
set newtar = true
It gave me a syntax error. What did I do wrong?
also another syntax error
if mm.stats.momentum == 0 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 1 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 2 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 3 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 4 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 5 then
send("kata perform ".. tar .." bash_high")
end
add newtar = false
Enyalida2011-11-28 21:49:20
vorld:
Made this
^You have slain .+$
set newtar = true
It gave me a syntax error. What did I do wrong?
Ignore the 'Set'?
vorld2011-11-28 22:03:16
That did the trick
vorld2011-11-30 16:52:30
I seem to have broken the key because it won't work now
Never mind fixed it.
well sort of it gets to this pint then stop
never mind fixed problem too
Never mind fixed it.
well sort of it gets to this pint then stop
elseif mm.stats.momentum == 2 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 3 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 4 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 5 then
send("kata perform ".. tar .." bash_high")
end
add newtar = false
never mind fixed problem too
vorld2011-11-30 17:56:46
@script_target is suddenly surrounded by cobalt blue sparks\\.$
(.*?)@script_target(.*?)mutters and traces a cobalt blue pentagram
^A dizzying beam of energy strikes you as your attack
A soft moan rises up from the ground as a shadowy bubble forms around @script_target
Eyes glowing red\\,(.*?)@script_target(.*?)
Spreading (her|his) arms wide\\, @script_target spins clockwise
^A spinning diamond around(.*?)@script_target(.*?)weaves a glittering shield around (her|him).$"
Is there a way I can change this to work with mudlet?
Also the if statement is broke again.
(.*?)@script_target(.*?)mutters and traces a cobalt blue pentagram
^A dizzying beam of energy strikes you as your attack
A soft moan rises up from the ground as a shadowy bubble forms around @script_target
Eyes glowing red\\,(.*?)@script_target(.*?)
Spreading (her|his) arms wide\\, @script_target spins clockwise
^A spinning diamond around(.*?)@script_target(.*?)weaves a glittering shield around (her|him).$"
Is there a way I can change this to work with mudlet?
Also the if statement is broke again.
Lilia2011-12-01 02:39:11
^(\\w+) is suddenly surrounded by cobalt blue sparks\\.$
^(\\w+) mutters and traces a cobalt blue pentagram in the air that remains hovering before (?:him|her)\\.$
^A dizzying beam of energy strikes you as your attack rebounds off of (\\w+)'s shield\\.$
^A soft moan rises up from the ground as a shadowy bubble forms around (\\w+\\).$
^Eyes glowing red, (\\w+) (I don't know what the rest of this line looks like, but you technically don't need the whole thing)
^Spreading (?:his|her) arms wide, (\\w+) spins clockwise and a shimmering white orb springs up around (?:him|her)\\.$
^A spinning diamond around (\\w+) weaves a glittering shield around (?:him|her)\\.$
matches will be the person's name. So for example: echo(matches.." is shielded"). If you want to use this for bashing as well, replace (\\w+) with (.+) in the appropriate triggers.
For your if statement, the only thing I see is at the end. It should just be 'newtar = false'.
^(\\w+) mutters and traces a cobalt blue pentagram in the air that remains hovering before (?:him|her)\\.$
^A dizzying beam of energy strikes you as your attack rebounds off of (\\w+)'s shield\\.$
^A soft moan rises up from the ground as a shadowy bubble forms around (\\w+\\).$
^Eyes glowing red, (\\w+) (I don't know what the rest of this line looks like, but you technically don't need the whole thing)
^Spreading (?:his|her) arms wide, (\\w+) spins clockwise and a shimmering white orb springs up around (?:him|her)\\.$
^A spinning diamond around (\\w+) weaves a glittering shield around (?:him|her)\\.$
matches will be the person's name. So for example: echo(matches.." is shielded"). If you want to use this for bashing as well, replace (\\w+) with (.+) in the appropriate triggers.
For your if statement, the only thing I see is at the end. It should just be 'newtar = false'.
vorld2011-12-01 05:55:52
Well here is my if statement currently.
So could I add another thing to this for shielding?
like this?
also it still gives me the bash_high is too complex to do message after a certain point
if mm.stats.momentum == 0 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 1 then
send("kata perform ".. tar .." bash_low")
elseif mm.stats.momentum == 2 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 3 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 4 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 5 then
send("kata perform ".. tar .." bash_high")
end
newtar = false
So could I add another thing to this for shielding?
like this?
if hassheild then
send("kata perform ".. tar .." rbash_low")
else
send("kata perform ".. tar .." rbash_high")
end
also it still gives me the bash_high is too complex to do message after a certain point
elseif mm.stats.momentum == 2 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 3 then
if newtar then
send("kata perform ".. tar .." bash_low")
else
send("kata perform ".. tar .." bash_high")
end
elseif mm.stats.momentum == 4 then
send("kata perform ".. tar .." bash_high")
elseif mm.stats.momentum == 5 then
send("kata perform ".. tar .." bash_high")
end
add newtar = false
vorld2011-12-13 18:40:03
Lilia:
^(\\w+) is suddenly surrounded by cobalt blue sparks\\.$
^(\\w+) mutters and traces a cobalt blue pentagram in the air that remains hovering before (?:him|her)\\.$
^A dizzying beam of energy strikes you as your attack rebounds off of (\\w+)'s shield\\.$
^A soft moan rises up from the ground as a shadowy bubble forms around (\\w+\\).$
^Eyes glowing red, (\\w+) (I don't know what the rest of this line looks like, but you technically don't need the whole thing)
^Spreading (?:his|her) arms wide, (\\w+) spins clockwise and a shimmering white orb springs up around (?:him|her)\\.$
^A spinning diamond around (\\w+) weaves a glittering shield around (?:him|her)\\.$
matches will be the person's name. So for example: echo(matches.." is shielded"). If you want to use this for bashing as well, replace (\\w+) with (.+) in the appropriate triggers.
For your if statement, the only thing I see is at the end. It should just be 'newtar = false'.
So something like this?
^(.+) mutters and traces a cobalt blue pentagram in the air that remains hovering before (?:him|her)\\.$
^Eyes glowing red, (.+)
^Spreading (?:his|her) arms wide, (.+) spins clockwise and a shimmering white orb springs up around (?:him|her)\\.$
Unknown2011-12-13 21:47:21
Matters little, although you might want to take look into "namespaces".
http://www.lua.org/pil/15.html
http://www.lua.org/pil/15.html
Lilia2011-12-13 23:09:06
It matters to him, because he's talking about matching player names vs matching mobs. Yes Vorld, that is exactly right. And there's no need to confuse yourself with namespaces, that has nothing to do with what you need.
Unknown2011-12-14 01:09:21
Lilia:
It matters to him, because he's talking about matching player names vs matching mobs. Yes Vorld, that is exactly right. And there's no need to confuse yourself with namespaces, that has nothing to do with what you need.
Might want to read a little into what I actually wrote there. I never even so much as insinuated that the previous posts mattered little, but rather that namespaces mattered little, although he might want to look into using them seeing he is using Mudlet.
If you could kindly take your attitude elsewhere? Many thanks.
http://forums.mudlet.org/viewtopic.php?f=8&t=1211
Lilia2011-12-14 03:11:54
Draylor:
Might want to read a little into what I actually wrote there. I never even so much as insinuated that the previous posts mattered little, but rather that namespaces mattered little, although he might want to look into using them seeing he is using Mudlet.
If you could kindly take your attitude elsewhere? Many thanks.
http://forums.mudlet....php?f=8&t=1211
Sorry, but I'm not seeing any other way to interpret what you posted. And if you think it doesn't matter, why would you even bring it up? If you had looked at any of the other things Vorld has posted about, you would have realized that he needs very specific instructions. Introducing an entirely new concept that has no bearing on what he's trying to do is extremely unhelpful. If you think this, or what I posted before, contains any sort of 'attitude', then you are much too sensitive. I'm just trying to make sure someone who has questions get the right answer, and lead not off track by stuff he's not ready for yet.
vorld2011-12-14 16:48:25
all well and good but the trigger doe not seem to work. Here is what I have in the codebox
echo(tar .. " is shielded")
Lilia2011-12-15 21:10:04
What I like to do when a trigger is giving me trouble is check the highlight box. If nothing gets highlighted, the problem is in the pattern. If it does highlight, the problem is in the code.
vorld2011-12-15 21:20:35
It must be the code then because it did not highlight