(183Kb)

Compatible with Retail, Classic & TBC

Updated: 04-22-23 01:36 PM

Addon for:
OmniCC.

Add Favorite

Install Help

Portal

Bugs

Features

Pictures

File Info

Compatibility:	Embers of Neltharion (10.1.0) WOTLK Patch (3.4.1) Classic (1.14.3) TBC Patch (2.5.4)
Updated:	04-22-23 01:36 PM
Created:	07-07-10 07:20 PM
Downloads:	22,225
Favorites:	127
MD5:

OmniCC Beta

Version: 10.1.0-beta1

by: Tuller [More]

This is the beta version of OmniCC. Odds are, there will be bugs
The latest stable version of OmniCC can be found here.

Confused? Check the Wiki!

Changes since Waffles

Extracted the timer scheduling code from the timer code.
Created two scheduling engines for the timer: One based on the Animation system, and one based on the classic OnUpdate methods, with the animation system used by default. If you're experiencing crashes when using OmniCC, try switching to the OnUpdate engine.
To switch to the OnUpdate engine, use
Code:
```
/omnicc setengine classic
```
To switch back to the Animation engine, use
Code:
```
/omnicc setengine animation
```

GitHub:

OmniCC development has moved from GogleCode to GitHub. The intention is to make it easier for people to fork/contribute to OmniCC development (and also for me to learn about git). Writing code for me typically gets your request implemented faster than asking me to write it myself :P

Submitting bugs & feature requests:

In order of preference, here's where you should submit bug reports and feature requests:

GitHub
Here on WoWI

I read/have RSS feeds for everywhere, so don't think too much about it

OmniCC Changelog

10.1.0

Update TOCs for 10.1.0

10.0.5

Update TOCs for 10.0.7

10.0.4

Update TOCs for 10.0.5

10.0.3

Update TOCs for 3.4.1

10.0.2

Update TOCs for 10.0.2
NOTE: OmniCC's options menu is now no longer a part of the main options menu, to avoid issues introduced with Dragonflight's UI changes. To bring up the options menu, use either the /omnicc or /occ slash commands.

10.0.1

Tagging as release

10.0.0

Update TOCs for 10.0.0

9.2.1

Updated TOCs for 9.2.5, 3.4.0, 2.5.4, and 1.14.3.

9.2.0

Updated TOCs for 9.2.0, 2.5.3, and 1.14.2

9.1.6

Whoops, I forgot that 9.1.5 introduced a new Maximum Cooldown Duration setting (thanks Lyrex)
Setting the maximum duration slider to 0 will enable cooldowns of any duration
Adjusted default for max duration to be 0 instead of 600

9.1.5

TOC updates for 1.14.1 and 9.1.5

9.1.0

TOC updates for WoW 9.1.0

9.0.10

Update TOCs for Burning Crusade Classic

9.0.9

Update TOCs for 1.13.7

9.0.8

The cooldown opacity setting is now only applied when set at an opacity value under 100%
Update TOCs values for 9.0.5

9.0.7

Updated Korean translation (thanks, WetU)
Updated Russian translation (thanks mone-ennen)
Fixed an issue when upgrading from OmniCC versions prior to 8.1 or so
Added a setting to disable auto disabling of blizzard cooldown text /run OmniCC.db.global.disableBlizzardCooldownText = false; ReloadUI()

9.0.6

Replaced the Draw Cooldown Swipes with a Cooldown Opacity slider
Updated Russian Localization (thanks, Artur91425)

9.0.5

Update TOCs for 1.13.6
Add a nil check when deciding to hide cooldown spirals or not
Build process updates

9.0.4

Updated TOCs for 9.0.2

9.0.3

Fix cases where cooldowns may not properly refresh

9.0.2

Fixed an error for when OmniCC attempts to display configuration for rules with missing id values

9.0.1

Apply default rulesets only when a profile is first created. This fixes an issue with deleting the defaults.

9.0.0

Finish effects will now trigger immediately for cooldowns that are soon to complete, but were overridden by the GCD.
Added a new setting, Timer Offset, to adjust the end point for timers to account for things like spell queue windows and latency.
Added predefined rules for Action Bars, nameplates, and auras
Updated TOCs for the Shadowlands pre-patch

8.3.6

Deferred loading of OmniCC_Config until you either use /omnicc or click on it in interface options
Updated Ace3 packages for compatibility with World of Warcraft Shadowlands

Comment Options

Page 2 of 9

Last »

11-07-10, 04:35 PM

Mikari

A Deviate Faerie Dragon

Forum posts: 17

File comments: 102

Uploads: 3

Originally posted by Necrophgst
Finish effects do seem a tad bit more dodgy in beta9 than they have been in previous betas. I set the minimum time to 1 second and had no problem with cooldown effects (besides the resulting cooldown effect spam). I have it set right now at 4 seconds which catches most things I care about anyway.

The other nil value errors appear to be gone though I'm happy to report. Thank you!.

I have and have always had my finish effect minimum time as 4 seconds, like I said most of the time they play fine, but sometimes I just get the normal WoW finish effect, the tiny sparkle.

11-07-10, 03:37 PM

Necrophgst

A Deviate Faerie Dragon

Forum posts: 17

File comments: 35

Uploads: 0

Originally posted by Mikari
I think I've found another bug, but I can't find a way to reproduce it 100% of the time, it's quite random. Sometimes a finish effect isn't shown, most of the time they work fine though.

Finish effects do seem a tad bit more dodgy in beta9 than they have been in previous betas. I set the minimum time to 1 second and had no problem with cooldown effects (besides the resulting cooldown effect spam). I have it set right now at 4 seconds which catches most things I care about anyway.

The other nil value errors appear to be gone though I'm happy to report. Thank you!.

__________________
The beat goes, Boom Badda Bing

11-07-10, 06:53 AM
Mikari A Deviate Faerie Dragon Forum posts: 17 File comments: 102 Uploads: 3	I think I've found another bug, but I can't find a way to reproduce it 100% of the time, it's quite random. Sometimes a finish effect isn't shown, most of the time they work fine though.

11-07-10, 01:08 AM

Kodewulf

Premium Member

Forum posts: 114

File comments: 104

Uploads: 18

BugSack grabbed these for OmniCC Beta9

Code:

2x OmniCC-4.0.beta9\timer.lua:42: attempt to index local 'OmniCC' (a boolean value)

Locals:

  ---
  
2x OmniCC-4.0.beta9\effects\pulse.lua:111: attempt to index global 'OmniCC' (a boolean value)

Locals:

  ---
  
2x OmniCC-4.0.beta9\effects\shine.lua:103: attempt to index global 'OmniCC' (a boolean value)

Locals:

  ---
 
1x OmniCC_Config\mainPanel.lua:109: attempt to index global 'OmniCC' (a boolean value)
OmniCC_Config\mainPanel.lua:143: in function `initFunction'
Interface\FrameXML\UIDropDownMenu.lua:69: in function `UIDropDownMenu_Initialize':
OmniCC_Config\mainPanel.lua:140: in function <OmniCC_Config\mainPanel.lua:86>
OmniCC_Config\mainPanel.lua:300: in function `optionsPanel_Create'
OmniCC_Config\mainPanel.lua:360: in main chunk
<in C code>: in function `LoadAddOn'
OmniCC-4.0.beta9\OmniCC.lua:65: in function <OmniCC\OmniCC.lua:63>
<in C code>: in function `Show'
Interface\FrameXML\InterfaceOptionsFrame.lua:204: in function `InterfaceOptionsFrame_Show':
Interface\FrameXML\InterfaceOptionsFrame.lua:484: in function <Interface\FrameXML\InterfaceOptionsFrame.lua:426>:
<in C code>: in function `InterfaceOptionsFrame_OpenToCategory'
Broker_HitCrit-2.20.1-release\Broker_HitCrit.lua:2036: in function `ShowConfig'
Broker_HitCrit-2.20.1-release\Broker_HitCrit.lua:965: in function `OnClick'
Bazooka-Bazooka-r167\Bazooka.lua:1267: in function <Bazooka\Bazooka.lua:1264>

Locals:
self = OmniCCOptionsPanelGroupSelector {
 0 = <userdata>
 GetSavedValue = <function> @ OmniCC_Config\mainPanel.lua:93:
 SetSavedValue = <function> @ OmniCC_Config\mainPanel.lua:89:
 initialize = <function> @ OmniCC_Config\mainPanel.lua:140:
}
level = 1
init_levelOne = <function> @ OmniCC_Config\mainPanel.lua:108:
init_levelTwo = <function> @ OmniCC_Config\mainPanel.lua:98:

  ---

1x OmniCC_Config\panels\general.lua:7: attempt to index local 'OmniCC' (a boolean value)
<in C code>: in function `LoadAddOn'
OmniCC-4.0.beta9\OmniCC.lua:65: in function <OmniCC\OmniCC.lua:63>
<in C code>: in function `Show'
Interface\FrameXML\InterfaceOptionsFrame.lua:204: in function `InterfaceOptionsFrame_Show':
Interface\FrameXML\InterfaceOptionsFrame.lua:484: in function <Interface\FrameXML\InterfaceOptionsFrame.lua:426>:
<in C code>: in function `InterfaceOptionsFrame_OpenToCategory'
Broker_HitCrit-2.20.1-release\Broker_HitCrit.lua:2036: in function `ShowConfig'
Broker_HitCrit-2.20.1-release\Broker_HitCrit.lua:965: in function `OnClick'
Bazooka-Bazooka-r167\Bazooka.lua:1267: in function <Bazooka\Bazooka.lua:1264>

Locals:
(*temporary) = "OmniCC_Config"
(*temporary) = <table> {
}
(*temporary) = <function> defined =[C]:-1

  ---

__________________
I will never forget. I will never regret. I will live my life.

11-06-10, 10:29 PM
Tuller A Warpwood Thunder Caller Forum posts: 91 File comments: 1740 Uploads: 17	Guide is up: http://code.google.com/p/tullamods/wiki/OmniCC4 I still need to read over it, and add in a few more screenshots.

11-06-10, 08:11 PM
Tuller A Warpwood Thunder Caller Forum posts: 91 File comments: 1740 Uploads: 17	Oh, that bug :P That bug results from the following: Use a spell with a fairly long cooldown. Log out of WoW, and restart your computer. Log back into WoW. Poof: You have a 50d cooldown timer. This is actually a Blizzard bug, and a longstanding one at that. Basically, for some reason the cooldown information gets corrupted at that point (the start time becomes something approximately X number of seconds since the wow anniversary date, though not exactly). In OmniCC 2, I actually implemented some functionality to handle this, but I dropped it with 3, hoping that Blizzard had finally fixed the issue. Looks like they have not. Last edited by Tuller : 11-06-10 at 08:14 PM.

11-06-10, 05:29 PM

berdan

A Kobold Labourer

Forum posts: 0

File comments: 24

Uploads: 0

The fix for the previous problem appears to have worked fine. Got another LUA error now though. I used Elune's Lantern, which has a 24h CD. The lantern is stowed away in my bank, and now whenever I open my bankframe I get this:

Code:

Message: Interface\AddOns\OmniCC\timer.lua:121: Usage: <unnamed>:SetDuration(durationSec)
Time: 11/07/10 00:25:20
Count: 1
Stack: [C]: in function `SetDuration'
Interface\AddOns\OmniCC\timer.lua:121: in function `ScheduleUpdate'
Interface\AddOns\OmniCC\timer.lua:154: in function `UpdateText'
Interface\AddOns\OmniCC\timer.lua:198: in function `UpdateShown'
Interface\AddOns\OmniCC\timer.lua:346: in function <Interface\AddOns\OmniCC\timer.lua:342>
[C]: in function `Show'
Interface\AddOns\Bagnon\components\frame.lua:77: in function `action'
Interface\AddOns\Bagnon\utility\ears.lua:29: in function `SendMessage'
Interface\AddOns\Bagnon\components\frameSettings.lua:51: in function `SendMessage'
Interface\AddOns\Bagnon\components\frameSettings.lua:69: in function `Show'
Interface\AddOns\Bagnon\main.lua:111: in function `ShowFrame'
Interface\AddOns\Bagnon\main.lua:282: in function `action'
Interface\AddOns\Bagnon\utility\ears.lua:29: in function `SendMessage'
Interface\AddOns\Bagnon\utility\itemEvents.lua:255: in function `?'
Interface\AddOns\Bagnon\utility\itemEvents.lua:70: in function <Interface\AddOns\Bagnon\utility\itemEvents.lua:68>

Locals: (*temporary) = <unnamed> {
 0 = <userdata>
}
(*temporary) = nil

I noticed with earlier betas that the time on this item was off sometimes. It displayed 50+ days, not the 10 or 2 hrs the tooltip stated.

11-06-10, 03:05 PM
Tuller A Warpwood Thunder Caller Forum posts: 91 File comments: 1740 Uploads: 17	Its a good thing that the compact party frames are on even when they're off. It helped me track down that bug :P If that bug is fixed, and I've manged to fix Mikari's other issue, I guess the next thing for me to do is probably write a settings importer thingy/write some documentation of sorts on what the hell groups are. Last edited by Tuller : 11-06-10 at 03:05 PM.

11-05-10, 11:06 AM

berdan

A Kobold Labourer

Forum posts: 0

File comments: 24

Uploads: 0

It still goes bonkers on a nil value :/

We seem to get stuck on different places though, me and Necrophgst.

Edit: It happens when I'm not in combat myself too. I was watching a fight outside Stormwind and got this error while having an enemy player targeted. No cooldowns were ticking for me.

Code:

Message: Interface\AddOns\OmniCC\timer.lua:129: attempt to perform arithmetic on field 'start' (a nil value)
Time: 11/05/10 18:03:51
Count: 3
Stack: Interface\AddOns\OmniCC\timer.lua:129: in function `UpdateText'
Interface\AddOns\OmniCC\timer.lua:88: in function `Start'
Interface\AddOns\OmniCC\timer.lua:415: in function <Interface\AddOns\OmniCC\timer.lua:393>
[C]: in function `SetCooldown'
Interface\FrameXML\Cooldown.lua:4: in function `CooldownFrame_SetTimer'
Interface\FrameXML\UIParent.lua:3335: in function `RefreshDebuffs'
Interface\FrameXML\TargetFrame.lua:777: in function <Interface\FrameXML\TargetFrame.lua:753>

Locals: self = <unnamed> {
 abRatio = 0.33333333333333
 text = <unnamed> {
 }
 0 = <userdata>
 updater = <unnamed> {
 }
 cooldown = TargetFrameToTDebuff1Cooldown {
 }
}
forceStyleUpdate = nil
(*temporary) = nil
(*temporary) = 22371.089
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to perform arithmetic on field 'start' (a nil value)"
GetTime = <function> defined =[C]:-1
OmniCC = OmniCC {
 0 = <userdata>
 PLAYER_LOGIN = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:51
 RegisterEffect = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:292
 GetGroupSettings = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:238
 db = <table> {
 }
 GetDB = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:81
 PLAYER_LOGOUT = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:69
 RemoveGroup = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:258
 CreateNewDB = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:116
 ForEachEffect = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:309
 TriggerEffect = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:285
 GetBaseDefaults = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:126
 GetEffect = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:299
 InitDB = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:85
 effects = <table> {
 }
 AddGroup = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:247
 GetGroupIndex = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:270
 CDToGroup = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:210
 UpgradeDB = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:166
 Timer = <unnamed> {
 }
 RemoveDefaults = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:106
 RecalculateCachedGroups = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:222
 GetAddOnVersion = <function> defined @Interface\AddOns\OmniCC\OmniCC.lua:180
}

Last edited by berdan : 11-05-10 at 02:45 PM.

11-05-10, 01:07 AM
Mikari A Deviate Faerie Dragon Forum posts: 17 File comments: 102 Uploads: 3	The first of my bugs appears to be fixed with beta 8, the 2nd still seems to be there though, the show cooldown text in the default group seems to affect the actions group regardless of if I have show cooldown text enabled in the actions group.

11-04-10, 11:21 PM

Necrophgst

A Deviate Faerie Dragon

Forum posts: 17

File comments: 35

Uploads: 0

Originally posted by Tuller
I'm still not sure of the exact cause, especially since the latest versions have included nil checks for start + duration. Hopefully whatever I did in the latest version will fix it, though :P

Nope, not fixed for me

Got 4 of these on one mob testing the new code out (don't know if frequency of the error helps you any tracking it down).

Code:

1x OmniCC-4.0.beta8\timer.lua:129: attempt to perform arithmetic on field 'start' (a nil value)
OmniCC-4.0.beta8\timer.lua:88: in function `Start'
OmniCC-4.0.beta8\timer.lua:415: in function <OmniCC\timer.lua:393>
<in C code>: in function `SetCooldown'
Interface\FrameXML\Cooldown.lua:4: in function `CooldownFrame_SetTimer':
TellMeWhen-1.5.3\TellMeWhen.lua:1290: in function <TellMeWhen\TellMeWhen.lua:1236>

Locals:
self = <unnamed> {
 abRatio = 0.83333333333333
 text = <unnamed> {}
 0 = <userdata>
 updater = <unnamed> {}
 cooldown = TellMeWhen_Group4_Icon2Cooldown {}
}
start = 1679981.17
duration = 10

  ---

__________________
The beat goes, Boom Badda Bing

11-04-10, 07:34 PM
Tuller A Warpwood Thunder Caller Forum posts: 91 File comments: 1740 Uploads: 17	I'm still not sure of the exact cause, especially since the latest versions have included nil checks for start + duration. Hopefully whatever I did in the latest version will fix it, though :P Last edited by Tuller : 11-04-10 at 07:35 PM.

11-04-10, 03:03 PM

blaugznis

A Kobold Labourer

Forum posts: 0

File comments: 17

Uploads: 0

getting same error as others:

Code:

1x OmniCC-4.0.beta7\timer.lua:129: attempt to perform arithmetic on field 'start' (a nil value)
OmniCC-4.0.beta7\timer.lua:88: in function `Start'
OmniCC-4.0.beta7\timer.lua:415: in function <OmniCC\timer.lua:395>
<in C code>: in function `SetCooldown'
Interface\FrameXML\CompactUnitFrame.lua:705: in function `CompactUnitFrame_UtilSetDebuff':
Interface\FrameXML\CompactUnitFrame.lua:573: in function `CompactUnitFrame_UpdateDebuffs':
Interface\FrameXML\CompactUnitFrame.lua:347: in function `CompactUnitFrame_UpdateAuras':
Interface\FrameXML\CompactUnitFrame.lua:85: in function <Interface\FrameXML\CompactUnitFrame.lua:46>:

Locals:
self = <unnamed> {
 abRatio = 0.30555555555556
 text = <unnamed> {}
 0 = <userdata>
 updater = <unnamed> {}
 cooldown = CompactRaidFrame10Debuff2Cooldown {}
}
start = 36950.564
duration = 30

  ---

11-03-10, 02:15 PM
Mikari A Deviate Faerie Dragon Forum posts: 17 File comments: 102 Uploads: 3	There's some odd things going on with B7, not sure what's intended and what isn't. First bug. With enable cooldown text disabled for pet actions and show cooldown models enabled for pet actions, on the first log in the first time I use a pet ability, in this case prowl for my cat it doesn't show the cooldown model, the 2nd usage of the ability causes the cooldown model to show as it should. If I log out and in again this bug doesn't happen, it's only on the first log in. Second bug, if I have the default group set to not show cooldown text, but have the actions group set to show cooldown text I still don't get the cooldown text. Related to this if I have actions set to not show cooldown text but default set to show it, I get cooldown text. Last edited by Mikari : 11-03-10 at 02:16 PM.

11-03-10, 12:42 PM

Necrophgst

A Deviate Faerie Dragon

Forum posts: 17

File comments: 35

Uploads: 0

I don't know if this is helpful it's out of BugSack.. But I got around 300 of these last night in a 25 man raid with beta6 and they continue to be the same (as far as I can tell) with beta7.

Code:

1x OmniCC-4.0.beta7\timer.lua:129: attempt to perform arithmetic on field 'start' (a nil value)
OmniCC-4.0.beta7\timer.lua:88: in function `Start'
OmniCC-4.0.beta7\timer.lua:415: in function <OmniCC\timer.lua:395>
<in C code>: in function `SetCooldown'
Interface\FrameXML\Cooldown.lua:4: in function `CooldownFrame_SetTimer':
TellMeWhen-1.5.1\TellMeWhen.lua:1321: in function <TellMeWhen\TellMeWhen.lua:1261>

Locals:
self = <unnamed> {
 abRatio = 0.83333333333333
 text = <unnamed> {}
 0 = <userdata>
 updater = <unnamed> {}
 cooldown = TellMeWhen_Group1_Icon4Cooldown {}
}
start = 1554259.694
duration = 15

__________________
The beat goes, Boom Badda Bing

Last edited by Necrophgst : 11-03-10 at 12:42 PM.

Page 2 of 9

Last »

Report this File

Category Jump: