My problem is not because patch, patch time will be about 14 hours later, i have just some bug or smthing like that when pqr is not really attach to wow . firepong have you got any idea?
My problem is not because patch, patch time will be about 14 hours later, i have just some bug or smthing like that when pqr is not really attach to wow . firepong have you got any idea?
after a quick lil check, i've decided to postpone adding in the ability for the function to work without PQI...
things like the Text and Select widget would break 90% of the profiles, and i would need to recreate the Hotkey function inside my own function for the hotkeys to be recorded properly xD
im not saying its impossible, but the function would get WAY to bloated and uglier![]()
Paintpauller's solution is fine but it annoys me that i have to maintain a variable set in the profile just in case PQI is not loaded. It would be so much better if i could pass the default (non PQI) value right at the check.
Shortly i would like to make the following snippet more friendly when PQI is not loaded:
if not PQI_MaxUnholy_Conversion_enable then return false end
local ConvHP=PQI_MaxUnholy_Conversion_value
...
And it is even worse when you have to set hotkeys... Maybe a function like PQICheck(varname,defvalue) would do the job and i could check for the addon inside the body and return the def value if PQI is not loaded.
Edit: nvm i am going to use paintpauller's method but don't drop the idea to improve your code![]()
Last edited by Maxitor; 08-28-2013 at 01:47 AM.
Instead of recreating the wheel, wouldn't it just be better to update PQI as it is though? If you're going for the root of the problem right away no one would need the extra function(s) added to their code. =)
There is a few things that could be improved with PQInterface, but I dunno how Mich diesall is checking the thread or how much he wants to work on it.
Sent from my HTC One using Tapatalk 4
i like making as little of a splash as possible, while seeing the same results
by changing PQI, i would be requiring people to update that across the board to use my thing... which may or may not break functionality of the old thing to get it to a point i would like
other than the fact the only way to update values and stuff is by mouse scroll or reloadui, i haven't seen any glaring issues
I suppose you're right. Back to the drawing board! ... And to get out of bed..
Sent from my HTC One using Tapatalk 4
Haha improving PQI on a global scale isn't out of the question, but I'll give diesel until 5.4 is released before I start playing around and tweaking thingsI am still a fan of cvars... they update instantly and are ready to use
Getting out of bed is for pansies and normal people
Sent from my SCH-I535 using Tapatalk 4
What i tried to solve is to have only one profile for PQI and non PQI users. I am still paranoid about the PQI addon itself (it takes like 30 seconds to implement a code to check for it and ban users on Blizz side) but i stepped over it in the past months because i came to the conclusion that without PQR i would not play at all. I know that there are users who prefer to use the old method aka set the binds in the profile to get rid of the mentioned addon so this is a problem at the moment.
On the other hand i do not want to wait for a possibble PQI update what could fix this. (also i had to modify PQI already to use mouse buttons) but it redirects us to my original post about the need of an open PQR librabry :P Yeah i still believe that this is the way to go instead of separate profile writer's datafile.
Edit: Fixing PQI would not help because the addon is not loaded
Do you have a working solution for this? It annoys me that i type in the value just to get ignored unless i scroll through the values. ReloadUI is simply bad :P
Last edited by Maxitor; 08-28-2013 at 03:22 AM.
Maxitor, I think you're missing the point about how add-ons operate and what PQInterface actually does. The add-on will not get you banned simply because it's only reading and writing data injected into WoW by the PQR program. When you load PQR and initiate a profile, PQRs state and injected variables is picked up by the add-on and "written" as sa ed variables, then fed back to the client and again read by PQR
It's only operating under the extreme tight parameters already set by Blizzard that all add-ons use. You'd find yourself as likely to be banned by using PQInterface as you would using BigWigs or DeadlyBossMods.
I'd go into further analysis and explanations of how add-ons operate, their restrictions and what's going on behind the scenes, but I fear that it would only cause confusions. (I'm a Computional and Systems Biology major at UCLA, I've also read both the UELA and ToS amongst several Lua programming books and books directly aimed towards developing add-ons for World of Warcraft.)
I'm as paranoid about losing my account as anyone, especially my old account which has all my progress from Vanilla. D:
But I do understand where you're coming from in regards to the absurdly long variable names. When I'm done with updating my profiles I'll write up a function translator that short-hands PQIs variables to something of the users choosing and sets default values to those variables in case PQI is undesired. =)
Sent from my HTC One using Tapatalk 4
Ok guys, here is a coding challenge for you:
I want to be able to pass a list of unit ids to the rotation via a macro, parse the ids and use them to cast a specific spell at the desired units (depending on if they exist) while maintaining the order of the units provided.
For example:
/fear focus/fear mouseover, focus/fear arena2, focus, mouseover, target
It should also work with a default set of targets if you cast just /fear.
This must be done without tainting the execution path (i.e. assigning nothing other than static primitive values like 1, 0, true, false etc.)
Any ideas?
That's pretty easy vitalic, and can be simplified to shit with a simple macro:
Otherwise I could write up a regex to capture desired UnitID's and parse them induvidually, I'm not exactly sure if RunMacroText is limited to that of a regular macro in-game, though!Code:RunMacroText("/cast [@mouseover,exists,nodead][@focus,exists,nodead][] Fear")
PM me for further info I suppose.
Also to go along with what mentally said, if Blizz really care to catch PQR users they would just implement the means to detect PQR itself and not even worry about the addon.
Sent from my Galaxy S4 using Tapatalk 2
@mentally @crystal_tech This might be a simplistic way of doing it, ideally I was hoping to store the list of targets and then in a rotation ability perform some logic on each target like LoS checks, immunity checks etc. In other words more than just a normal /cast macro.
The main objective is just to prevent the need to spam a macro/keybind, so it works like a toggle which pauses the rest of the rotation until that spell has been cast.