Elesarr
Jittery Beta Tester
Arcane Dawn of Khadgar - Guild Leader
Posts: 312
|
Post by Elesarr on Mar 10, 2008 13:49:54 GMT -5
Actually, if it isn't too much trouble, could you re-do that code fix and let me know the error message? I'm wondering if it is a "compare with nil" error. If it is, I might need to add "or 0" to the end of that line of code... like so: I think it was, but I'll check now for you to be sure and try the new code you posted. I'll also let you know if you can make the gem at 68 Ele
|
|
Elesarr
Jittery Beta Tester
Arcane Dawn of Khadgar - Guild Leader
Posts: 312
|
Post by Elesarr on Mar 10, 2008 16:43:48 GMT -5
hmm ok couldn't reproduce the error I got before..leads me to believe I copied it wrong the first time to casue the error. far as the gem charge updating it seemed to work fine for me...there was a delay between the update; however it updated before the cooldown was complete. Not sure what the level is for Mana Emerald...I think 68 sounds right though. Let me know if I can be of further help Moon. Ele
|
|
|
Post by Moongaze on Mar 10, 2008 16:55:38 GMT -5
... the cooldown is a few minutes? Or 15-30 seconds? I imagine the update delay might be in the ballpark of 2-5 seconds, but it could also be due to combat. Were you in combat when you tried the stone? Thanks for the help
|
|
Elesarr
Jittery Beta Tester
Arcane Dawn of Khadgar - Guild Leader
Posts: 312
|
Post by Elesarr on Mar 10, 2008 20:59:46 GMT -5
cooldown is 2 mins like for pots and stuff, no was not in combat, seemed to update at the 1 min mark for me at least.
Ele
|
|
yoduki
Junior Beta Tester
Posts: 20
|
Post by yoduki on Mar 11, 2008 12:37:57 GMT -5
|
|
|
Post by Exuro on Mar 12, 2008 13:08:30 GMT -5
I'm on vacation atm skiing in Utah, but i'll try this fix when I get home tomorrow if no one else has and let you know what happens.
|
|
|
Post by Elf on Mar 12, 2008 16:25:53 GMT -5
Great work Moongraze - been waiting for such an all encompassing mod for ages - thanks for all your hard work. I wonder how general this problem is but the most recent version of LunarSphere is coming up with the 'button settings" dialogue every time I left/middle/right click onto a sphere - this was tested on a pally and a hunter. Not an error (well not one that bugsack picks up) and I had no other addons loaded at the time.
Hope this is useful. All the best
|
|
Elesarr
Jittery Beta Tester
Arcane Dawn of Khadgar - Guild Leader
Posts: 312
|
Post by Elesarr on Mar 12, 2008 18:36:16 GMT -5
Great work Moongraze - been waiting for such an all encompassing mod for ages - thanks for all your hard work. I wonder how general this problem is but the most recent version of LunarSphere is coming up with the 'button settings" dialogue every time I left/middle/right click onto a sphere - this was tested on a pally and a hunter. Not an error (well not one that bugsack picks up) and I had no other addons loaded at the time. Hope this is useful. All the best make sure after setting up the sphere how you want that you uncheck "edit buttons" on the sphere tab. That should solve your issue. Ele
|
|
|
Post by Moongaze on Mar 12, 2008 18:44:15 GMT -5
Yeah, when you start up LS for the first time, the sphere is in "edit button" mode. After you set the sphere buttons up the way you want them (either by drag and drop, clicking on a button with something attached to the cursor, or using the button settings window), hover over the sphere and you'll see the shortcut on how to bring up the LunarSphere settings window (where you will uncheck "edit buttons" in the sphere tab) or uncheck "edit buttons" from the dropdown menu that comes out of the sphere. Then, your actions will be locked to the buttons and you'll actually be able to move them Edit: Guess Elessar got to you first ;D
|
|
|
Post by Exuro on Mar 13, 2008 1:27:43 GMT -5
Tried both mana gem changes and neither worked. It still updates when you move it in your inventory. And I didn't get any errors.
|
|
kutai
Newbie Beta Tester
Posts: 5
|
Post by kutai on Mar 14, 2008 0:54:30 GMT -5
v612
Hey Moon just wanted to let you know that the healthstone issue was fixed for me when I checked off that box in the options. Although this was just after 1 night of raid testing so I will have to test it a little more next week. Also, wanted to let you know that the previous version I was using (v610) had no issues with the mana emerald charge for me, but this one does. Later I will try with and without the healthstone option checked off, see if it makes any difference.
|
|
|
Post by Moongaze on Mar 14, 2008 2:40:46 GMT -5
Sounds good, thanks I'll make the healthstone fix a part of the core files of LunarSphere and remove the debug option in the next version.
|
|
|
Post by Exuro on Mar 15, 2008 11:29:14 GMT -5
Wouldn't it be possible to now rempve all the old backwards compatably from the code? Correct me if i'm wrong, but the code should have kept users up to date with how all the buttons are stored and such. So if you removed the code, the only people who would be affected would be people who have not updated their LS in quite some time correct? Just a thought of how to save some more memory.
|
|
|
Post by lothaer on Mar 15, 2008 11:33:17 GMT -5
wait wait wait wait, just hold up a minute Exuro, just whoa..................... people dont update LS?
|
|
|
Post by Moongaze on Mar 15, 2008 11:45:45 GMT -5
The update code doesn't take up any memory while LS is running. It loads it up at start-up, runs it, then wipes it from memory after the user finished logging in. It does take up file size though I will be wiping a lot of the backwards compatability code soon to make my life easier. I kinda left it in there to prove to myself that the concept works, it works REALLY well, and it will be very helpful for all users when the public version releases. When the public version pops out, I'll have some of the Stage 6 stuff and Stage 7 stuff in there for a couple versions, but after version 1.1 or 1.2 of LunarSphere, all beta references will be removed and if someone is upgrading from an old version that is no longer supported, they will be notified that their settings had been reset due to that issue. Although I don't see the need to use it much in the future. It's mainly to help the beta testers since I keep changing database formats and fixing horrible bugs that appeared due to some changes I made that broke parts of LS and the user's settings Thanks for the concern though! I'll be looking into parts of it to remove in the near future.
|
|
|
Post by Chaos on Mar 16, 2008 14:22:41 GMT -5
What kind of nonsense is this? To think people don't update LS.... *shudder*
Don't spread such nasty rumours, I almost wet myself. I'm going to need to seek the comfort of strawberry malts and chili cheese dogs to help me get through this....
|
|
|
Post by Moongaze on Mar 16, 2008 15:02:16 GMT -5
I can imagine people using stage 4 and stage 5 stuff, if they didn't want to take the plunge and get the speech tab and a few other button enhancements. Probably because they didn't want the stuff in stage 5 or 6 and wanted to keep their memory usage down. Of course, over the past few months, the CPU usage in LS went down and naturally, the memory usage went up with all the new features. But when stage 7 pops with its memory management tab, memory won't be an issue anymore. The speech module section is quite large ... probably the 3rd largest part with the buttons being #1 and the sphere being #2.
|
|
|
Post by Moongaze on Mar 16, 2008 15:56:41 GMT -5
Version 613 is now live. I decided to leave the healthstone fix as a debug option for further testing. I'm sure it works fine and will be removed with the next version. It is recommended to have this option turned ON. Mana gems with charges were NOT fixed yet, so that is an on-going bug. I finally added the multi-spell support to the speech tab, so portal makers rejoice. As usual, let me know of any error messages that appear Please check the newest post in the "Stage 6 Changelog" thread for details on what I have added/changed/fixed. Thanks again!
|
|
|
Post by Exuro on Mar 16, 2008 21:44:26 GMT -5
version 613, got this when auro repairing w/ the new guild bank feature
|
|
|
Post by Moongaze on Mar 16, 2008 23:01:22 GMT -5
Thanks. It was a typo that I will fix and upload in an hour or so. For now, go to the moduleAPI.lua file and do a search for:
_GUILD_FUNDS_TAG
You will notice the the line it found has:
formattedReceipt = formattedReceipt .. " " .. Lunar.Locale("_GUILD_FUNDS_TAG");
Those parathesis need to be changed into brackets
formattedReceipt = formattedReceipt .. " " .. Lunar.Locale["_GUILD_FUNDS_TAG"];
Sorry about that =( Looks like the guild repair was going to work properly until it tried to create a formatted text string for the log. Whoops!
|
|