- Home
- Downloads
-
Addons & Mods
Featured
World of Warcraft
4,840 Addons
-
Popular Downloads
- Top World of Warcraft Addons
- Top Rift Addons
- Top Skyrim Mods
- Top Minecraft Server Mods
- Top Terraria Maps
- Top Starcraft II Maps
- Top Runes of Magic Addons
- Top Warhammer Online Addons
- Top Age of Conan Addons
-
- Curse Client
- Premium
- News
- Giveaways
- Forums
InstanceTime
Login to Add Favorites
- 2 Likes
- World of Warcraft
- 41,408 Downloads
- Supports: 4.3
- 10 Average Daily Downloads
- Comments
- Created 5/27/2007 5:34:24 PM
- Updated 11/30/2011 2:54:31 PM
- 431 Favorites
- Project Site
- License: All Rights Reserved
- Release Type: Release
- Newest File: InstanceTime_v4.3
About InstanceTime
About 'InstanceTime'
This AddOn records how long it took to complete an instance. The timer will not be interrupted by dying (and running back to the instance) oder by beeing reanimated. It will stop the timer and add an entry to the list, if you are alive and leave an instance or if you are using the "ghosthealer". By entering an instance, the timer will automatically start. By leaving the instance, the timer will automatically stop. There's nothing to be done by the player.
This AddOn is not intended to be used as stopwatch. Every zone-change resets the timer.
LibDataBroker (LDB)-Support
This AddOn has LDB support.
Dependencies
- no dependencies
Release Version 4.3 (11/30/2011)
—————————————————————————————-
- small bugfix
- changed toc 40300
| File Name | Release Type | Game Version | Downloads | Date |
|---|---|---|---|---|
| InstanceTime_v4.3 | Release | 4.3 | 254 | 11/30/2011 2:54:31 PM |
| InstanceTime_v4.22 | Release | 4.2 | 103 | 11/9/2011 1:40:02 AM |
| InstanceTime_v4.21 | Release | 4.2 | 71 | 10/29/2011 4:49:56 AM |
| InstanceTime FuBarPlugin_forV3.61+ | Release | 3.0.3 | 320 | 11/27/2008 3:22:16 PM |
Comments
InstanceTime v4.3 is still very unreliable when selecting the "Let InstanceTime handle start/stop (of the timer) automatically" option, as it was when I first reported it months ago.
Checkmark that option and uncheck "Timer starts with first pull" & "Timer stops after end boss was killed" options. For "Time Period:" choose the default 30.
Enter the LFD finder and choose a specific dungeon (in this case, the new for WoW 4.3 Well of Eternity). Start from the beginning and finish it, then leave the party as is standard procedure. The timer appears to stop in the LDB display.
Then choose a "random dungeon" in the LFD finder and wait. About 7 minutes after finishing the last one, the queue comes up. Enter the new dungeon through the LFD finder -- which is again Well of Eternity -- but with a different group. Enter it at a point after the first two bosses have been killed.
Improperly, the timer restarts at "28:12..." as though I had not finished and left the last dungeon. It incorrectly seemed to be "on hold" waiting for the same dungeon to appear again. This despite leaving the finished last dungeon by leaving the party.
I then CTRL-leftclicked the LDB feed to stop the timer, then started it again doing the same thing. The LDB feed showed "1 sec", etc. properly. But then after a few seconds the timer reverted to "29:12...". Did this a few times and the timer never reset.
Here's hoping you can get the "Let InstanceTime handle start/stop (of the timer) automatically" option to work properly some day.
The russian translation is broken! I was think that localisation file saved not as UTF-8, but it really worst.
INSTANCETIME_LOADED_TEXT = "загружен уÑпешно"; this is not russian words.
Hi^^
Yes, I know. But I can't "undo" it. I need someone to translate these strings. Nevertheless: There are several more strings which need to be translated anyway. :-(
*whew* great
For some reason, I still can't see the time/xp/rep on my shaman.
Tried the new /it resetxxx commands, but it didn't help.
The addon seems to work fine otherwise and I can see the options and instance list dialogues. It's only the time/xp/rep info that wont show.
Hmmm...
You can try this: Go to your "\World of Warcraft\WTF\Account\<YourAccountName>\<YourServer>\<YourCharacter>" and edit the file called "layout-local.txt". There you will find "Frame: InstanceTimeFrame" and set the following:
Anchor: CENTER
X: 0
Y: 0
I tried it and this resets my InstanceTime dialogue to the center of the screen. Hope this helps.
Yeah, that did the trick. The dialogues are now in the center of the screen.
Is it possible to hide the instance time movable windows altogether? I use the LDB option, and i cant seem to get rid of the additional movable window that shows the actual instance time, rep and xp were easy to turn off, but i cant find the option for time.
To hide just type:
/it
type
/it
again and the dialogue will be shown again
On some chars, I simply can't move the time/xp/rep bars that are stuck in the middle of the screen.
On other chars, the bars must be stuck somewhere outside the screen area, because no matter what I do, I can't get them to show.
What is the correct way to move the bars?
Can you reset position for all the bars?
You should be able to mouse-right-click on the writing "InstanceTime". If you do so, a menu will show up (either right or left of the writing). Now you can mouse-left-click- on the writing "InstanceTime". Hold the left mouse button and drag the dialogue.
I'm currently still fixing a few bugs and I will add a function to reset the dialogue to top or center of the screen. So I hope this then will get your dialoge back to your screen.
Open up "Options", "Output" tab. In the "Chat output after an instance:" dropdown list, try to change it from the default "no channel" to "self". An error is thrown and it does not change:
\n",
["type"] = "error",
["locals"] = "self = DropDownList1Button5 {\n 0 = \n func = defined @Interface\\AddOns\\FreierGeist_InstanceTime\\FreierGeist_InstanceTime.lua:5315\n value = \"self\"\n}\n",
["session"] = 4232,
["counter"] = 2,
}, -- [1000]
I will look into it.
Thanks Zidomo!
Will be fixed in the next version.
After a relog, all the dialogs are shown again even though the option is still checked/enabled.
When clicking disable/enable again, I get a LUA error.