Dyaxler

You're running Elkano's QuestLevel AddOn. My understanding of how that works is that it modifies the quests in your quest log to show you the level in which the quest should be done? I could be wrong but any AddOn that makes changes to the Quest Log frame can break Questie since we rely on data in the Quest log to make matches and to draw stuff...

There is a functions.txt in the addons directory. it's a "user guide" of sorts. Here are some of my priest SM functions. In coming wall of txt. -- Cast SWP if it's not already on the target /script UIErrorsFrame:Hide() /script if not buffed("Shadow Word: Pain", 'target') then CastSpellByName("Shadow Word: Pain") end -- Don't double up on Renew /script UIErrorsFrame:Hide() /script if UnitExists("target") and UnitIsFriend("target", "player") then if not buffed("Renew", 'target') then CastSpellByName("Renew") end return end if not buffed("Renew", 'player') then cast("Renew",1) end -- Self-Buffs: /script if not buffed("Power Word: Fortitude", 'player') then CastSpellByName("Power Word: Fortitude",1) end;end -- Rotation: /script UIErrorsFrame:Hide() /script if not buffed("Shadow Word: Pain", 'target') then CastSpellByName("Shadow Word: Pain") end DoOrder("Mind Blast", "Smite") SM_Channel("mind flay") -- Mashable Wand Cast /script UIErrorsFrame:Hide() /script if (UnitName('target')==nil) then TargetNearestEnemy() else if not IsAutoRepeatAction(12) then CastSpellByName("Shoot") end;end -- Instant Casts /script UIErrorsFrame:Hide() /script SpellStopCasting() /script CastSpellByName("Desperate Prayer",1) /script UIErrorsFrame:Hide() /script SpellStopCasting() /script CastSpellByName("Fade",1) /script UIErrorsFrame:Hide() /script SpellStopCasting() /script CastSpellByName("Power Word: Shield",1) -- Self-heal if no target /script UIErrorsFrame:Hide() /script SpellStopCasting() /script if UnitExists("target") and UnitIsFriend("target", "player") then CastSpellByName("Lesser Heal") else CastSpellByName("Lesser Heal",1) end /script UIErrorsFrame:Hide() /script SpellStopCasting() /script if UnitExists("target") and UnitIsFriend("target", "player") then CastSpellByName("Heal") else CastSpellByName("Heal",1) end /script UIErrorsFrame:Hide() /script SpellStopCasting() /script if UnitExists("target") and UnitIsFriend("target", "player") then CastSpellByName("Flash Heal") else CastSpellByName("Flash Heal",1) end -- Buff target based on level (You have to alter the spell name according to the spell you want to cast and change i=6 by the number of ranks you currently have for that spell) /script a="Power Word: Fortitude" b={1,2,14,26,38,50} c="target" d="(Rank " e=CastSpellByName if (UnitLevel(c) ~= nil and UnitIsFriend("player",c)) then for i=3,1,-1 do if (UnitLevel(c) >= b[i]) then e(a..d..i..")") return end end else e(a,1) end /script a="Renew" b={1,2,10,16,22,28,34,40,46} c="target" d="(Rank " e=CastSpellByName if (UnitLevel(c) ~= nil and UnitIsFriend("player",c)) then for i=3,1,-1 do if (UnitLevel(c) >= b[i]) then e(a..d..i..")") return end end else e(a,1) end -- Grind /script --CastSpellByName("Mind Blast") /script UIErrorsFrame:Hide() /script if not buffed("Weakened Soul") then if not buffed("Power Word: Shield", 'player') then CastSpellByName("Power Word: Shield",1) end;end if not UnitExists("target") then return;end if not buffed("Shadow Word: Pain", 'target') then CastSpellByName("Shadow Word: Pain") end DoOrder("Mind Blast", "Smite")

The Supermacro MOD has the ability to do what you're after. It has a function called DoOrder(). It "does" the first entry in the list and skips the rest. Subsequent executions will cast the next entry if the first is unavailable, on cool down or otherwise fails for some reason. You can include match conditions as well like... /script DoOrder( not FindBuff("mark") and "mark of the wild" or "", not FindBuff("thorns") and "thorns" or "" )

I originally shared this on the Nost forums. Providing link for those that are interested in a fully working back port of SpartanUI. https://github.com/Dyaxler/SpartanUI_Vanilla/releases/latest Original post from Nost forums... --------------------------------------------------------------------------------------------- *Current Version: v0.9.6.1* Hey all, When I first started playing on Nostalrius I quickly realized how much I missed my SpartanUI. After some searching here and other sites I quickly realized that nobody had a working version for Vanilla. I thought, how hard could it be to back port it? Ha! After a month of coding in my spare time, fixing, re-writing, debugging... heck with it. No sense in bombarding you all with a stupid wall of text. I've uploaded it onto GitHub where I'll plan to keep track of bugs and future revisions. Feel free to peer review it, critique it... what ever. It's a gift to you all. https://github.com/Dyaxler/SpartanUI/releases/latest I've been running it for the past week or so without any issues so far after I stamped out all the bugs I could find. I'm sure there are some others that I haven't encountered yet as I'm presently only playing a low level Priest and just started a Paladin. My son tested it on his Rogue and Hunter so I know that Stances and Pets work. I'm kind of a MOD junkie and right now I have over 80 sub-directories worth of mods in my AddOns directory so I'm fairly certain that this version of SpartanUI will play nice with most of the mods out there. Unless of course you decide to try and run Bongos or some other bar Addon. It comes with a custom embedded version of Bartender2. Check out the README for more info. If you find a bug, I have one request... try and capture it with some kind of a LUA capture mod like !ImprovedErrorFrame. Please? The default error interface in the WoW client tends to only capture the first error it encounters and ignores the rest. A clue to a bugs issue can sometimes be found in the errors after the initial trigger. If you can provide consistent repro steps - that would help tremendously in tracking down a bugs origin. Thank you! Full UI: Left Panel: Right Panel: Party Frames: (can be turned off using /sui menu) Pet Frame: Rogue Combo-Points:

Added to classicaddons.com site: https://classicaddons.com/index.php?/file/92-spartanui-for-vanilla-wow-112

Wulf is right. You should use EQL3. The default WoW QuestLog sucks. It only allows you to track up to 5 quests and there are certain types of quests you can't put on the tracker. You'll get an error... "No objectives to track..." or some such. The latest version is always found here: https://github.com/AeroScripts/QuestieDev/releases/latest By default, Questie shows all objectives. There is a slash command to turn it off and only show objectives that are on your tracker. This helps reduce the clutter in your maps. Just type '/questie' in game for a list of commands you can run. If you're curious which CVARS are set type '/questie settings'. Oftentimes players play on more than one server. You MUST go into your */WDB folder and delete all your cache files before playing on a new server. I'm still investigating this but sometimes your characters Saved Variables files become corrupt or locked in memory. If shutting down your game client and restarting doesn't clear it up then one way you can verify if it's a Saved Variables issue is to create a new character and try out a couple of quests to see if you experience the same issues. If that fixes your problem then I would suggest disabling Questie and see if you're able to change another addons settings and verify if the changes "stick" between logout/login sessions. If nothing is wrong then delete the !Questie.lua file inside your ..\[realm] \ [character name] \ SavedVariables directory. This will wipe out your finished quests unfortunately but if you know LUA you can edit the file and make a copy of that section. It looks like this... only three quests but I wasn't going to bombard you all with a wall of TXT. :D

Please report these as you find them. The fix for these are fairly simple and quick. I can insert the fixes between releases. Linking the quest from db.vanillagaming.org provides enough info to fix these. EDIT: Fixes were checked in. You'll have to manually install the files until they are incorporated with a release.

I forgot to include a fix in Astrolabe to ignore the fact that while in an instance, coordinates are always returned "0 , 0 ". Right now Questie is removing quests from the tracker because it can't calculate where a Quest Objective is located. This has been fixed in a new Hotfix I just committed. Version: 3.66 https://github.com/AeroScripts/QuestieDev/releases/latest

It is supposed to be automatic. You've got something going on with your game client. Its not saving data to your Saved Variables file. Hold down CTRL + SHIFT and Left Click on your tracker then move it some place on your screen. Then log out and login. Tracker should be in exactly the same place, If it's not, something is corrupted. Make a new character - doesn't matter which kind you can delete it after this test. If Questie works fine then you've got something going on with that one Characters Saved Variables file. You do NOT have to wipe out your entire WTF folder. Just delete any Questie* files from your characters directory and clear out the WDB folder.

/questie minlevel <-- turn on the filter Run the above command... The min level filter is already set to 5 levels. So if you're level 10, you won't see any quests with a Min Level value lower than level 5.

If Questies current database were in this format sure. :) Currently these are the only keys that are available to us... ['name'] ['startedType'] ['finishedType'] ['startedBy'] ['finishedBy'] ['level'] ['questLevel'] ['rq'] --> requiredQuest ['rr'] --> requiredRaces ['rc'] --> requiredClasses ['rs'] --> requiredSkill I've only briefly looked at the new database that Aero designed. He says he has all that stuff figured out for v4.0.

I'm quite surprised that we're not getting more complaints about quests suddenly showing up all over their screen. :D When I moved Questies settings from a per server to a per character format the saved variables makes no reference to [accountname][server] so doing what Aero says should restore Questie. There is no CLEAN way to hide all the holiday quests. Most of them are level 60 quests with a minimum level of 1 in the database. You'll just have to Shift-Click complete them to hide them. :( The new database in Questie 4.0 has Quest Type flags such as, Faction, Profession, Repeatable etc. Should make it a lot easier to hide and show those kinds of quests in the future.

It might be like he said... if one of his SavedVaribles files is corrupted then it would prevent the tracker from moving. If '/questie cleartracker' doesn't move his tracker to the middle of his screen then that is generally an indication of user saved data being locked.

So running '/questie cleartracker' didn't move the tracker to the middle of your screen?

/questie cleartracker This will wipe the position info for the tracker and drop it in the middle of your screen. There might be a hidden UI element that is sitting on top of Questie preventing you from moving it.

There is a Version check in Questie - if the versions are different it runs: /questie clearconfig - clearconfig: Resets all Questie settings and removes stale quest database entries (will not delete completed quests). This would have re-enabled the Quesite QuestTracker... This clean up prevents incompatibilities from older versions polluting new or removed functionality.

@Jebo AWESOME! That was going to be my last and final suggestion. If you're moving around between different servers you should be deleting the contents of your WDB folder anyway. This is the games cache and it caches everything that comes from the server so conflicts happen quite frequently and are the #1 source for reported issues with addons not working correctly. Deleting your WTF folder isn't really ideal since it contains all YOUR personal settings for everything from chat window settings and placement to individual addon settings and cache data that they collect. It's usually OK for you to leave it alone since it creates a separate folder for each server / account / character that is created. For Questie specifically it stores which quests you've completed. Wiping out your WTF folder will make all those quests re-appear and you'd have to spend some time Shift+Clicking each quest you know you've completed. We built in slash commands that will wipe out your Questie settings without wiping out your completed quests. Just type /questie in game to see the list of available commands. That's not entirely true anymore. :) There are some EQL3 CVAR's that are deliberately switched off because they conflict with Questie or cause duplicate info to appear. Most notably, Quest objective tooltips. ;) Here is a list of CVAR's that are forced off when the QuestieTracker is enabled: QuestlogOptions[EQL3_Player].MobTooltip = 0; QuestlogOptions[EQL3_Player].ItemTooltip = 0; QuestlogOptions[EQL3_Player].RemoveCompletedObjectives = 0; QuestlogOptions[EQL3_Player].RemoveFinished = 0; QuestlogOptions[EQL3_Player].MinimizeFinished = 0; The first two are obvious. RemoveCompletedObjectives - Since Questie packages each quest and their objectives into a single "button" that is inserted into the tracker, individual Objectives can't be hidden and for some quests it would cause the entire quest to be hidden even if there are still objectives to be collected/done. RemoveFinished - Prevents the ability to show the Arrow so you can find the Quest Finisher. Most folks like being able to click on a completed quest and know where to turn it in without having to look at the worldmap. MinimizeFinished - This is very similar to RemoveCompletedObjectives. The only way to disable Quest Sorting is to use another tracker. You can use either the Default WoW QuestTracker or EQL3's QuestTracker. Just simply run this command in game and it will switch you over: /questie tracker I don't recall if EQL3's QuestTracker can be disabled like Questies can so if you want to use the WoW QuestTracker (Why?!?! It's ugly) then you might have to fully disable EQL3. NOTE: If you disable the Questie QuestTracker then you'll loose the ability to use the Questie Arrow.

... if none of that works try un-tracking everything then reload your UI. Turn off EQL3 - un-track all your quests, reload your UI, then re-enable EQL3 and then try tracking some quests. Are you running ShaguQuest or EQL3?

I dunno man... you'd be the first in thousands with this issue. Line 44 is this: if GetTime() - QuestieTracker.lastUpdate >= 1 then ...and the error says that QuestieTracker.lastUpdate is nil which means it can't find that value. This value is set Globally to zero at the top of QuestieTracker.lua on line 19. So this value being nil? Impossible. Unless there is another mod messing with this value which I find highly unlikely that another mod would be setting this value for: QuestieTracker.lastUpdate. Where is your client installed? If it's in C:\Program Files*** then that might be your issue. The old Nost client had issues running from that protected directory and Windows might be preventing you from saving session variables. I would install your client on a second hard drive or in the root of your C: drive. Try running the WoW client as an Administrator.

Doesn't anyone read the Readme & FAQ? He probably can't pull the tracker out from under the player frame anyway... use this command. @Jebo - It's not finding the last timestamp. Reload your UI. This is quite common on a fresh install. BTW... since you're starting out, if all else fails try /questie NUKE

The Interface Options setting in the clients config menu "Automatic Quest Tracking" only works with the default WoW tracker. Doesn't work with the Questie Tracker. Unless you're running EQL3 - shift+clicking is the only way to add an objective to the Questie Tracker.

If you're using the default WoW Questlog then functionality is vary limited. Not all quests are trackable and you can only put up to 5 items on the tracker. Try Shift+Clicking a quest from the Questlog to add it to the tracker. Should tell you if there aren't any trackable objectives. If you want the full potential of Questie I'd use EQL3. It will auto add quests to your tracker and you can track the max (20 quests) - doesn't matter if there are objectives that are trackable or not. You can put anything on your tracker.

Questie has been updated to v3.61...

OK, that's better... you can see the slash commands more clearly.