local function getUser(msg)
local user = ""
local userEnd = msg:find(">")
local closeBr = msg:find(")")
if closeBr == nil or closeBr > userEnd then
return msg:sub(5, userEnd-1)
else
return msg:sub(closeBr+1, userEnd-1)
end
end
add_hook("console", "", function(msg, t)
-- 8 => public msg from someone else
-- 16 => public msg from you
if t == 8 or t == 16 then
echo("user: "..getUser(msg))
else
echo(t)
end
end)Signature temporarily out of order.
Thank you very much, just needed to change
Also, do you know if they recently made some changes for lua in toribash? Drawing seems to be much faster now at least.
Edit: Now if a user without an unofficial clan write ) it still works
local closeBr = msg:find(")")local closeBr = msg:find(")") or msg:find("%]")Also, do you know if they recently made some changes for lua in toribash? Drawing seems to be much faster now at least.
Edit: Now if a user without an unofficial clan write ) it still works
local function getUser(msg)
local user = ""
local userEnd = msg:find(">")
msgName = msg:sub(0,userEnd)
local closeBr = msgName:find(")") or msgName:find("%]")
if closeBr == nil or closeBr > userEnd then
return msg:sub(5, userEnd-1)
else
return msg:sub(closeBr+1, userEnd-1)
end
end
add_hook("console", "", function(msg, t)
-- 8 => public msg from someone else
-- 16 => public msg from you
if t == 8 or t == 16 then
echo("user: "..getUser(msg))
else
echo(t)
end
end)
Last edited by IceColor; Oct 21, 2014 at 06:02 PM.
Fukin spice and wolf
Originally Posted by psycore
Also a quick tip: You can write 'a:find("%[")' instead of 'string.find(a, "%[")'. Note the colon though, it's necessary. Works only for variables so '"asdf":find(...)' won't work.
Actually, "asd":find won't work because of the parser, if you do ("asd"):find it will work, another thing, string.find has a 4th parameter that let's you pass non-pattern strings, like this:
lua code:
("asd()"):find("()", 1, true)
Originally Posted by IceColor
Also, do you know if they recently made some changes for lua in toribash? Drawing seems to be much faster now at least.
No idea. The lua API (the part we get to used) hasn't changed. Of course there could have been improvements on the parser.
Originally Posted by RickyRicon
Actually, "asd":find won't work because of the parser, if you do ("asd"):find it will work, another thing, string.find has a 4th parameter that let's you pass non-pattern strings, like this:
lua code:("asd()"):find("()", 1, true)
I didn't know the parser thing. That seems very odd to me. Doesn't that imply that "asd" and ("asd") are different language constructs? Shouldn't they both be equal in every aspect? Is this a general problem of Lua or did the parser used by TB just get that wrong?
I've read about the 3rd argument of find() but it's useful so rarely that I keep forgetting about it.
Signature temporarily out of order.
Originally Posted by psycore
I didn't know the parser thing. That seems very odd to me. Doesn't that imply that "asd" and ("asd") are different language constructs? Shouldn't they both be equal in every aspect? Is this a general problem of Lua or did the parser used by TB just get that wrong?
This isn't a problem with Lua nor is it a problem with the parser used by TB (afaik, they shouldn't be using a custom parser but rather implementing the native Lua parser through C/C++).
My guess is that the difference between "asd":find("blah") and ("asd"):find("blah") is the order which things are evaluated. In the case of "asd":find() you are attempting to call the find function before the string has actually interpreted as such. In the case of ("asdf"):find(), Lua first interprets "asdf" as a string and then calls the find function on that. Parentheses place priority on whatever is inside of the parentheses: without them though, the function will take the first priority.
Last edited by motota; Oct 22, 2014 at 06:19 AM.
