Auto Shout Out Neo

Chat & Communication Login to Add Favorites
  • 0 Likes
  • World of Warcraft
  • 95 Monthly Downloads
  • Supports: 4.0.3a
  • 4,268 Total Downloads
  • Updated 12/11/2010 8:19:53 PM
  • Created 11/28/2010 7:19:43 PM
  • 9 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: All Rights Reserved
  • Newest File: Auto Shout Out Neo v1.0.0
or
Support development! **
Click here to lend your support and make a donation at www.pledgie.com !

About Auto Shout Out Neo

Automatically notifies (via vocal emotes and/or chat messages) when your life, health or mana drops below a certain percentage. Also notifies when your pet's health drops below a certain percentage, as well as if the player loses a "Soulstone Resurrection" buff, or gets Sapped, or cannot cast a helpful spell on a party/raid member.

'Auto Shout Out Neo' is a separate add-on from 'Auto Shout Out', but its meant to replace it. You technically don't need to uninstall 'Auto Shout Out' when' installing 'Auto Shout Out Neo', but you should, as they duplicate the purpose of having them, to notify of events.

'Auto Shout Out Neo' was written using Ace3, while its predecessor was not. Because of this, 'Auto Shout Out Neo' was rewritten from scratch, but not only contains the same functionality, but adds a few new features (Battlegrounds, etc.).

Translations done by translate.google.com, so apologies if they are horrible. Please feel free to contact me with corrections to the translations.

Finally, I was unable to find the coding time to import your old settings into this new add-on. Apologies for this, but real life > WoW.

- Added message notifying user that emote could not be done because of spell channeling.

Addon Packs Containing This...

Comments

  • #11
    It is now doing 30 seconds just fine.

    However, I'm a disc priest so I channel a lot. Instead of the debug message, it would better for it to silently fail and silently retry once per second until it is able to successfully complete the emote and then reset timer at 30 seconds.
  • #12
    My main is a disc priest too! /salute

    That message isn't meant for debugging purposes, but for warning purposes. Some were asking me why they were not seeing their shoutout being done.

    I'll take another look at it, and if it ends up being too spammy, do something about it. But to be honest, I haven't noticed it being much of a problem, not as notification times are usually not that short.
  • #2
    My timestamp says that it is doing it more than every 30 seconds.

    7:49:55
    7:50:13
    7:50:24

    That's more than every 30 seconds. 30 seconds should be a minimum by the way, it's in the ToS that doing something more than every 30 seconds (even an emote) is grounds for spamming and you can get temp banned or worse for it.
  • #3
    Can you expand on what you mean by "it"? Which configuration/event are you speaking about? There may be a bug going on, but notifications are supposed to only happen as often as they are set to.

    I think the TOS is talking about public like General/1 and Trade/2. I have no problem changing the minimum values if that's not correct. But at the end of the day, the user is free to change the default timing values to values they are comfortable with.

    In fact, I'd be happy to take any suggestions from any of the users as to what the default values should be. They were arbitrary values made up at the time I was coding the add-on.

    Thanks for the feedback.
  • #5
    I once used a whisper spam addon in order to try to look for groups, it would whisper each individual person within a certain class/level combination ONCE, in the effort to find people to make a group with. (No longer necessary thanks to the Dungeon tool.) However, people reported me for spam because of it.

    When a GM looked into the issue, he realized that I wasn't harassing people, my message was to try to find a group and not sell gold so the message itself was fine, but since he was looking at my chat log anyway, he noticed that I had done 'healme' emote several times a couple hours ago while fighting some elite that I had spent a couple minutes at very low health while fighting it. So I got banned for 3 hours because I had 'spammed' the 'healme' emote in a zone where I was leveling by myself and absolutely nobody was around to hear it in the first place anyway.

    After research the ToS it's basically 4 times per 2 minutes and/or 30 seconds, whichever way you look at it. I later confirmed this with a GM. Saying the same thing more than once per 30 seconds, 4 times, is the line. Past that line you're spamming. Even if what you're 'saying' is an emote.

    To answer your question, my settings are currently on Auto switch off, using solo configuration since I only need one configuration per character.

    The emote in question is 'life' which is at 50%, notify via emote, and the emote is HELPME. As I'm a healer I prefer using this over 'healme' because obviously I can heal myself if I want to. (My characters that can't heal have healme at 50% and helpme at 25%. Characters that have mana are set at 5%. My default settings are 'helpme' is in combat only and 'healme' and 'oom' are out of combat too.)

    It would be really cool if I could say 'Get %t off me!' where %t is my target and only if that target is an enemy and has me targeted and I'm in my trigger health (below 50%), and of course once per 30 seconds only and only in combat. I kinda think it's outside the scope of this addon though which is why I didn't suggest it before, but if you're looking for things to do, my healer would definitely appreciate it.
  • #8
    I forgot to mention, now that ASON uses Ace3, you have the 'Profiles' support of Ace3 available to you. So, as you mentioned in your post, if you don't use multiple configurations (which seems strange to me as I notify differently in a Party vs. while in a Battleground, but to each their own), you can have in essence meta configurations, by loading/unloading different profiles based on your needs. So you can have one profile where you don't auto switch, and other where you do, etc. etc.
  • #7
    First off, thank you for that info, interesting story. Seemed kind of mean to me that the GM banned you for doing emotes out in the wild by themselves. By that measure, people doing /silly in BGs before a match (or spamming AOE spells) should all get banned too. /shrug

    The latest version has the default time set to 30 seconds (from 10 seconds).

    As far as timing goes, is it just the emotes that are off timed, or the messages? I did some testing with messaging, and the timing was spot on right, but I didn't check emotes (though they use the same single lua function for timing checks).

    In fact, emotes can be bypassed if the user is in the middle of a cast, since in the past emotes would break casting, so you should be seeing less emotes than messages in theory.

    Finally, my original intent was for the Health event to signal to the tank that the healer was being attacked, and the Life event to signal to the whole group that they were about to lose the healer. In essence though, Health and Life are both just hit point checks, so you're welcome to ignore one and just use the other if you want, but personally, I like to annoy the tank if he/she is not holding aggro over my heals. :)

    So work with your 'really cool' suggestion, set Health to 49%, and set Life to any value lower than that. The default time for those events are already 30 seconds, and the 'In Combat Only' should already be checked for those (if not, check them). That'll get you what you need. The current wildcards are are '$HEALTHPERCENT', '$HEALTHMAX', '$HEALTH', '$MANAPERCENT', '$MANAMAX', '$MANA', and '$NAME'. I'll see about adding a '$TARGET' to the mix, but WoW is kind of weird about how and when it wants to give you targeting info. I had to do a little dancing just to get the Spell Cast Failure event to work, as by default when WoW tells you that it doesn't tell you who/what was the target.
  • #10
    Yeah, I figured it would be beyond the scope of the addon to include that, but I'd only want the %t to work when I was targeting something that was targeting me. Usually I don't actually have something targeted that's targeting me unless I have aggro, so to randomly shout out my target when my health is below 50%, when I'm probably targeting a teammate at the time, wouldn't be quite so helpful. =P

    If I see the 'more than once per 30 seconds' happen again I'll let you know.
  • #6
    Anyway, long and short of it is, I set helpme to trigger only per 30 seconds and as you can see by timestamps, it's triggering a lot more often than that.
  • #9
    Well, I just tried testing this with b13, and couldn't reproduce a problem.

    I set my Mana event to 99% and 5 seconds, then did a bunch of spell casting, and had my WoW client display time in H:M:S, and it was displaying every six seconds (I guess the extra second is due to server round trip time or lua processing, etc.).

    All events go through the same single lua function, so I can't imagine it would be any different for Life events. Unfortunately I'm guildless and don't think a PUG would be too kind to me if I start testing this during a run, but I'll try to find a way to test the Life event too, just in case I'm wrong.

    Interesting note. The /oom emote won't actually emote if you are not grouped. I had to switch to another emote (/cry in this case) to do the testing. Must be like /silly, where only a party can see the emote.
  • #4
    One additional comment. Combat is usually finished, one way or the other, in under thirty seconds, so I'd hate to set an arbitrary minimum limit of thirty seconds for notifications that need to be done during a single combat that itself can be done in under thirty seconds.
  • #1
    Auto Shout Out Neo is up to beta 11 now (just submitted it; hasn't been approved yet so not visible to you yet), and I haven't heard back from any one. Are there any outstanding bugs that you know about that haven't been reported yet? If so, please do report them.

    If I don't hear back from anyone in the next few days, I'll make beta 11 the non-beta v1.0 release candidate.
  • To post a comment, please login or register a new account.
Learn how to disable ads
Learn how to disable ads
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Diablo III Giveaway

Enter Now!