| Updated: | 02-05-12 06:22 PM |
| Created: | 01-24-12 04:11 PM |
| Downloads: | 542 |
| Favorites: | 4 |
| MD5: |
File Name |
Version |
Size |
Author |
Date |
4.3.012 |
50kB |
VagrantEsha |
02-05-12 04:08 PM |
|
4.3.011 (Beta) |
17kB |
VagrantEsha |
02-05-12 11:54 AM |
|
4.3.010 |
17kB |
VagrantEsha |
02-03-12 07:55 PM |
![]() |
Comment Options |
|
|
|
|
Oh, wait. I see what's happened. Gah. Let's see...
Last edited by VagrantEsha : 02-05-12 at 02:20 PM.
|
|
|
|
|
|
|
|
Blargh. That'll teach me to read right after waking up, my reading comprehension is nil. For some reason my mind took those as dungeon names. I have no idea why.
But anyway, the name bug should be fixed now, I hope. Sorry about hat. |
|
|
|
|
|
||
I can be in a capital city or in ANY outside zone, solo or grouped. It has the error no matter what. Thank you.
Last edited by Jaim Sandar : 02-05-12 at 11:53 AM.
|
||
|
|
|
|
|
|
Ah. Thanks! I haven't had a chance to test in instance play. I thought the logic was solid (I kept simplifying it so that I could make it as solid as possible) but apparently not! So, I shall have a look at those errors and get this fixed ASAP.
Even if this means me running off to find a random dungeon to test it in. But that should hopefully not be necessary. I think this is most likely just going to be a stupid oversight. Consider it being worked on! --- The weird thing is that I've been using this in non-instanced play myself, and I've had no issues at all with it. (Honest!) So, what I'm thinking is happening here is that the targeting event is firing weirdly in dungeons. This is a simple fix, though. I hope it just doesn't disable functionality in dungeons. I'll get a new version up ASAP that will give you a reprieve from the errors, but it'll take me a bit to test it.
Last edited by VagrantEsha : 02-05-12 at 11:46 AM.
|
|
|
|
|
|
|
|
I updated to 4.3.010, started WoW, logged on. In Deepholm (solo), took portal to the throne of Therazane, accepted some daily quests, shift to Druid flight form & accidently clicked on a couple of NPC (Therazane & another local one). This error popped up at that point:
Code:
OnMyMark\OnMyMark-4.3.010.lua:18: attempt to concatenate local "name" (a nil value) OnMyMark\OnMyMark-4.3.010.lua:18: in function <OnMyMark\OnMyMark.lua:4> <in C code> <string>:"CAMERAORSELECTORMOVE":4: in function <string>:"CAMERAORSELECTORMOVE":1 Locals: (*temporary) = nil (*temporary) = "PLAYER_TARGET_CHANGED" (*temporary) = "PLAYER_TARGET_CHANGED" (*temporary) = <func> =[C]:-1 A few minutes later, after log off & back on, flew to Crimson Expanse, destroyed a couple of mushrooms, then killed a Verlok Grubthumpter. I'm not sure if it was during the last couple of blows during the combat or after losing the target, this error popped up twice: Code:
OnMyMark\OnMyMark-4.3.010.lua:18: attempt to concatenate local "name" (a nil value) OnMyMark\OnMyMark-4.3.010.lua:18: in function <OnMyMark\OnMyMark.lua:4> Locals: Still solo. The solo mark (X) is applied to new targets and cleared when I click on something else, so the basic functionality appears to be good in spite of the errors. Thank you. Edit 2: I played with my Saturday night group, and On My Mark 4.3.010 does the same thing when in a party as solo. Every time someting is targeted results in the error, as well as releasing the target. To review, what it is doing whether solo or grouped is a constant stream of the same error (2nd code example above) repeating as long as anything is targeted and/or released. I would go back to the previous release to avoid the constant errors, but I deleted it from my disk and I can't find it to download again.
Last edited by Jaim Sandar : 02-05-12 at 11:28 AM.
|
|
|
|
|
|
|
|
So, this is becoming pretty complicated. And in a way it's turning into an all round dungeon/marking mod.
People who aren't me or my friends: Do you fin this difficult to use and would it be easier if it had an options screen? I've been tempted to write one in, but if that's not helpful to anyone else then I won't bother. |
|
|
|
![]() |