Archived

This topic is now archived and is closed to further replies.

MysticalOS

Upcoming custom timer work

3 posts in this topic



This stuff is in alpha now. Or will be in next general release.

New timer features
1. Countdown text/audio can now be added to timers, both personal and broadcasted
2. Timers can now be looped indefinitely or until canceled. They also auto terminate when EndCombat fires for any active boss mod as well so any loops started mid fight will only last until fight end.

Old commands which have not changed

Starts a one time timer for self no one else sees
/dbm timer <sec> <text>

Starts a one time timer that is sent to whole raid if you have promoted status. Note: This will be disabled in LFR.

/dbm broadcast timer <sec> <text>

New commands

Starts a one time timer for self no one else sees that now also includes countdown audio/text

/dbm ctimer <sec> <text>

Starts a one time timer for whole raid if you have promoted status that now also includes countdown audio/text. Note: This will be disabled in LFR.

/dbm broadcast ctimer <sec> <text>

Starts an infinite loop timer for self that no one else sees.

/dbm ltimer <sec> <text>

Starts an infinite loop timer for whole raid if you have promoted status. Terminated by sender or when fight ends. Note: This will be disabled in LFR.

/dbm broadcast ltimer <sec> <text>

Starts an infinite loop timer for self that no one else sees that also includes countdown audio/text

/dbm cltimer <sec> <text>

Starts an infinite loop timer for whole raid if you have promoted status that also includes countdown audio/text. Note: This will be disabled in LFR.

/dbm broadcast cltimer <sec> <text>

Terminates ANY timer loop created by ltimer or cltimer

/dbm timer endloop

Additional Notes:

1. Like any former custom timers, any sender can be ignored to prevent harassment with feature.

2. As noted above, loop functions are disabled in LFR because there is no good reason to use them there. The loop functions are intended for the personal use or organized raid use and not trolling people in LFR.

3. If you don't like either the countdown audio or countdown text, these new additions honor your pull/combat timer settings. This way, if a raid leader prefers to broadcast ones with countdowns, you can disable the counts so incoming "ctimer" act like "timer"

4. You can disable the "x sent you a timer" message in General Message options. Note, you won't be able to ignore that sender unless you re-enable this message since that's where ignore button is.

5. Loops are controlled by sender. The SENDER must terminate loop. Also, only one loop per sender, however you can have two different senders do two different loops.

poleos likes this

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Similar Content

    • 7.0 Progress Report
      By MysticalOS
      Things have appeared quiet around here on DBM end but this is because work is well under way for Legion 7.0 content.
      Currently DBM already has full support for all dungeons and raids for pull/wipe/kill detection and basic features like range finder and other manual commands. 
      For raid mod support, most tested bosses so far (11/12 raid bosses so far) have full and functional mods. 3 raid bosses have drycoded mods. 1 Raid boss is ALMOST fully functional but just needs to see longer pulls (Dragons of NIghtmare). Very few were able to do this during testing. For dungeon mod support, 9 dungeons are fully supported right now. The 10th dungeon (violet hold) is only partially supported do to nature of RNG involved in seeing all the bosses. I will start publishing test videos and then linking to the threads in this sticky so you can see my testing first hand and development process for many of raid test bosses. I'll also update this thread when I do updates and add more bosses/dungeon support.
    • READ FIRST: Known Issues in 6.2.21 (Updated 03/23/16)
      By MysticalOS
      DBM Core
      DBM can't always accurately skip cinematics for you within Siege of Orgrimmar if you are on any of the timeless isle visions of time quests. This is because blizzards CINEMATIC_START api lacks movieIDs to properly tell quest scene from annoying raid scenes you've seen 100x DBM may skip second cinematic in Auchindoun even if it's first time reaching that point. This is because there is no distinction in CINEMATIC_START event on movieID within api to allow us to know one movie from another within the SAME zone, so dbm thinks the second movie is same as first movie and skips it. Hellfire Citadel:
      None Emerald Nightmare:
      Any timers/warnings for Emerald Nightmare were coded using alpha/beta data and mods are subject to inaccuracies if blizzard makes changes before final Legion version ships. The Nighthold:
      Any timers/warnings for Nighthold were coded using alpha/beta data and mods are subject to inaccuracies if blizzard makes changes before final Legion version ships. Broken Isles:
      Any timers/warnings for Broken Isles were coded using alpha/beta data and mods are subject to inaccuracies if blizzard makes changes before final Legion version ships. 5 man dungeons:
      Any timers/warnings for legion dungeons were coded using alpha/beta data and mods are subject to inaccuracies if blizzard makes changes before final Legion version ships. Brawlers Guild:
      None World Events:
      None
  • Recently Browsing   0 members

    No registered users viewing this page.