(Quick Question) LUA rotation "switch" without unlocking LUA

[reliasn]

What I'm doing: running rotation profiles with Lua_DoString()
What I want to do: implement an in-game "switch" that would allow me to switch between burst, AoE and single-target mode without unlocking LUA.

My tests:
- Macro in-game: /script if targetN == 0 then targetN = 1 else targetN = 0 end
Then reading targetN in my profile to then decide which mode to run.
This, however, triggers the "Blocked action" by WoW UI, because (I think) I'm running a script in Lua_DoString() (unprotected) that references/reads another variable that was set by a macro in-game (protected).

What worked for me: using a CVar as "dummy"
- RegisterCVar("test","0")
- Macro in-game: /run x = GetCVar("test"); if x == "1" then SetCVar("test","0") else SetCVar("test","1") end;
Then in my profile targetN = GetCVar("test"), from which I decide which mode to run.

The idea is basically to use some setting that can be set/read as "dummy". This method worked, but I'm concerned about its safety. Does anyone have a better method for this "mode switch" without unlocking LUA? I thought about reading pressed keys, but that will probably flag my tool as a keylogger. Finally, can Warden scan registered CVars and are these CVars uploaded to the servers in some way? I suppose it's YES and NO for this last question...

Regards and thanks for your attention!

[MaiN]

As far as I remember, you will taint variables like that (which is what you're seeing), but you cannot taint variables in tables like that:

/run if not abc then abc = {} end if not abc.targetN then abc.targetN = 1 else abc.targetN = 0 end

My memory is foggy, but I'm pretty sure I was able to read variables from tables like this without tainting.

Also as long as your stuff is private you do not need to worry about Warden finding these variables/cvars.

[reliasn]

As far as I remember, you will taint variables like that (which is what you're seeing), but you cannot taint variables in tables like that:

/run if not abc then abc = {} end if not abc.targetN then abc.targetN = 1 else abc.targetN = 0 end

My memory is foggy, but I'm pretty sure I was able to read variables from tables like this without tainting.

Also as long as your stuff is private you do not need to worry about Warden finding these variables/cvars.

Thanks for the reply! I used this macro:

/run if not abc then abc = {} end if not abc.targetN or abc.targetN == 0 then abc.targetN = 1 else abc.targetN = 0 end

And in my .LUA, something like this:

if abc.targetN == 1 then
	HunterRotation()
end

The "Blocked Action" frame is still showing though... I will keep on trying! I have to read more about this tainting thing and see what other people have done to avoid it. Thanks once again! (PS: "You must spread some Reputation around before giving it to MaiN again.")

[-Ryuk-]

Why don't you just keep your 'switch' in your external code? and then have your bot/hack check if switch before it uses the correct function?

[aeo]

As lame as it is you could keep control of the variable in your external code and force the lua value each frame. Use GetSynckeystate to alter the variable and then each from just run

DoString("if not rotationActionType then
rotationActionType = nil
else
rotationActionType = single/aoe/...
end");.

The chances of this variable being tainted are pretty slim as you are resetting the value each frame.

[reliasn]

I was mainly afraid of my tool being flagged by an Anti-Virus as a Keylogger. I appreciate everyone's reply and I ended up implementing the switch on my External tool.

SetWindowsHookEx + global hook, without using DLLs. I suppose this is better than implementing a loop calling GetAsyncKeyState() all the time. Anyways, 0/54 on Virustotal so I guess it's all good!

Regards everyone!

[Wildbreath]

try to use wow bindings (using xml), check my addon (to offspring). it's protected, but configurable out of combat

[Travelformed]

you can do a trick w/o xml right from your lua code:

-- Bind a function to a key combination
-- bindingName - unique name for binding
-- key - key combination
-- handler - handler function
function bindButton(bindingName, key, handler)
	local name = "BindButton_"..bindingName;
	local button = CreateFrame("BUTTON", name)
	print("Binding: "..key)
	SetBindingClick(key, name)
	button:SetScript("OnClick", handler)
end