Dyaxler
Player-
Content count
60 -
Joined
-
Last visited
Community Reputation
9 NeutralAbout Dyaxler
-
Rank
Savvy
Recent Profile Visitors
1329 profile views
-
Elysium went down for maintenance one evening so I logged into another project to test some stuff and Questie wasn't working quite right... I was getting similar nil errors that others have said was occurring. I forgot to clear my WDB folder. I really need to hear more details about that is going on. Sounds like an "edge case" issue. If it was a bigger problem we'd have a lot more complaints flooding GitHub. Saying that it doesn't work doesn't help. :(
-
A little update... we've been hard at work adding some new features for the 3.70 release. Just a couple highlights... * Improved Starter/Finisher/Objective icon clustering. (only on the Worldmap - minimap remains untouched as a source for a more precise location of map markers) * Quest Chat Links! Questie will now support Shagu's implementation and you'll be able to view Quest Links sent to chat by either AddOn. Questie pulls quest info directly from it's own database instead of the Quest Log so it won't matter if you're on the quest or not. You'll see all the quest info. I have plans to improve the output for CTRL + Click (quest progress) but I'm not sure if it'll make it into the next release. I might just dress up the text and make it more readable. * Improved Tooltips! Better info. Better stacking. Just plain better. * We've made significant strides in improving the Questing system. Some of the Quest object types that start quests were broken. We're hoping this will reduce the number of complaints about missing quests. * TONS of bug fixes...
-
Just fixed a bug and updated the zip file... this is what I get for making code changes before my first cup of coffee. *sigh* Sorry if you tried it and it failed. Should work now. Works for me again. :D
-
https://github.com/Dyaxler/BlizzMo_Vanilla/releases/latest BlizzMo for Vanilla WoW 1.12 There isn't much to say other than this mod will move any Blizzard Frame and all your Bags. There is code to handle just about any situation including keeping the frames visible and to not allow them to be dragged off screen. There are no slash commands as none are needed. There are a few user options that you can take advantage of. First is the ability to toggle the save frame locations between game sessions. Just CTRL + Click any frame and you'll see a message in chat telling you which mode you're in. SHIFT + Mousewheel will scale the individual frames. NOTE: your mouse cursor must remain over the desired frame that you're making changes to. If for some reason you get yourself snarled into a bizzare situation and your frames are all foobar'd, just go into your game menu and you'll see a reset button for BlizzMo. A confirmation popup will occure and your UI will be reloaded after confirming reset. Here is a list of Frames that are in the SAVE state by default: AuctionFrame CharacterFrame ClassTrainerFrame FriendsFrame QuestLogFrame SpellBookFrame TalentFrame GossipFrame MailFrame MerchantFrame TradeSkillFrame DressUpFrame LootFrame TaxiFrame TradeFrame Backpack Bag1 Bag2 Bag3 Bag4 You can even add your own custom mods to a table (requires some knowledge of LUA) and is fairly straight forward. Just follow the examples that I've already added support for. For your convience the section of code is at the very bottom of BlizzMo.lua and it looks like this: These are some of the mods that I use. Feel free to add or remove support for them. If you're not using it, don't worry it won't cause any issues.
-
Sorry, I know what's causing that now. *smacks head* @all Sorry guys. There are going to be some little issues like this. You all have faster computers than I do so your functions fire faster than mine. It's all about timing. I just have to nail down the correct flow in order to keep the functions firing in the right order.
-
That function has been in Questie for months and has never changed... something is definitely up with your install.
-
I was trying to engineer a solution for Quest linking in chat. It requires a custom Hyper link to be made and hooked before the text will show up as yellow otherwise you get kicked off the server.... can't colorize text being sent to chat. I was speaking with Shagu the other day (he said his mod is open source and to feel free to "borrow" code) and his mod does kind of a Sudo quest linking but it gets the info from the users Quest log so if someone links a quest in chat, if you have that quest in your log it'll show you the description otherwise it says that you're not on the quest. I was planning on using the exact same method and Hyperlink name he used so if one user is using Shagu Quest and links a quest in chat, the hyperlink will work for both Questie users and Shagu users. I was going to go a step further though. Instead of looking in a players quest log for the quest, and telling you that you're not on a quest if you click on a hyperlink that isn't in your quest log, I'm going to do the look up in the Questie database for the description instead. ...but not everyone is using a mod that adds the little [50] or [+60] in the quest titles. So it was striped out when it sends the text to chat. Otherwise the internal DB look ups fail. *NOTE* If you don't use either Shagu or Questie and you click the Hyperlink you will NOT get kicked off the server. You'll just get an error saying that the Hyperlink reference can't be found.
-
Yeah, either use the Questie Toggle button on the World map or reload your UI tends to fix these occasional glitches. Earlier to night in my testing I some how locked up my QuestTrackers saved variables. It wasn't registering that I had removed all the quests from the tracker causing a whole slew of functions to fire constantly. I was scratching my head for a good hour thinking I introduced a new bug some how and was searching back through changes to find it. I had to NUKE my config to fix it. :D
-
New release - well a Hotfix update to be honest. https://github.com/AeroScripts/QuestieDev/releases/latest
-
I caught that one and I have a bunch of hot fixes ready to go to fix some other small issues. Just finishing up with a round of testing and I should have it up soon.
-
It's a 2001 Ducati 748 actually. Can't tell the difference between these bikes. Same chassis. I was looking for a 996 engine to do a straight swap last summer then decided against it now that I have an R1. Only difference really are the injectors and the control chip in the ECU.
-
@zaphon That issue is on my list to fix... if you get a chance can you open a quick bug on GitHub to remind me? :D In other news... latest release: https://github.com/AeroScripts/QuestieDev/releases/latest
-
You'll need SuperMacro for this but here is mine - the 12 is the Hotkey assignment. Just change it to what ever key your macro is sitting in. -- Mashable Wand Cast /script UIErrorsFrame:Hide() /script if (UnitName('target')==nil) then TargetNearestEnemy() else if not IsAutoRepeatAction(12) then CastSpellByName("Shoot") end;end @Mitchymoo Did you move your macro to a key? That would have broken it. According to your macro you're using button #1.
-
What was it? Pass on the knowledge brother!
-
You've got some seriously wonky stuff going on then. I don't have a clue. I've never seen this issue before. Weird stuff like this is usually caused from cached data that came from another server - I.E. not from Elysium. I would try and clear your WDB folder out and go from there.
