Authors CurseForge

That'd be me, hi!

I created Spelling because nothing else really seemed to fit the bill for what I wanted. Here's a quick run-down of what Spelling does...

- Can print to all channels, including emotes.
- Allows more than one entry per spell, thus adding variety.
- The user can specify a chance of firing so that Spelling doesn't spam its entries all the time.
- The SOURCE variable exists so that if a player sets up an item for being the recipient of a buff/debuff/ability/attack, it'll allow them to put the name of the entity responsible in their output.
- The HITNAME variable exists so that the person casting or using an ability can put the name of the focus/target in their output (you don't have to have anything targeted for this to be true, the only condition is that the spell/ability must actually land on a named entity).
- Uses the new COMBAT_LOG_EVENT_UNFILTERED, as most systems for parsing the old chat log or catching auras seem to be partially broken these days.

So to the OP, if this sounds like what you want then check out Spelling. And if you find that Spelling is almost what you want but it's missing a certain something, then let me know and I'll try to implement it. I'm always looking to improve the Spelling experience.

(Oh, I forgot to mention that the reason I created my own instead of using AuraToChat, as an example, was because AuraToChat can't output emotes.)

How about MagusLogue?

Little more than a paronomasia really, but it's got a certain something going for it. I'm not quite sure what that something is though.

Sorry Nirek, I didn't want to put any undue pressure on you. All I was trying to do really was offer some pre-written code so you could have something to drop in (or at least, modify a little and then drop in). I understand that you're going for functionality first, and that's a good thing.

Anyway, I think you're doing a really great job with this King of the Jungle remake!

It's there. The RegisterChatCommand functions do it.

Great to have this back. No problems so far (aside from the aforementioned zoning error), and my pet certainly is feeling a lot happier now that her forgetful friend isn't frequently failing to feed her.

The only suggestion I might have might be using a "select" instead of an "input" for the growth option, you can add TOP/BOTTOM/LEFT/RIGHT as values in that, then. You could also use a slider for the time interval.

Here's an example of both...

	options.args.interval   = {}
	options.args.interval.type = "range"
	options.args.interval.name = L["Warn Interval"]
	options.args.interval.desc = L["Set the amount of time between warnings."]
	options.args.interval.min = 5
	options.args.interval.max = 120
	options.args.interval.step = 5
	options.args.interval.get = function() return intervalVar end
	options.args.interval.set = function(_, set) intervalVar = set end
	options.args.interval.order = ?

---

	options.args.select    = {}
	options.args.select.type = "select"
	options.args.select.name = L["Growth Direction"]
	options.args.select.values= { TOP = L["Up"], BOTTOM = L["Down"], RIGHT = L["Right"], LEFT = L["Left"] }
	options.args.select.get  = function() return positionVar or "RIGHT" end
	options.args.select.set  = function(_, set) positionVar = set end
	options.args.select.order = ?

Entitled

Is that the sort of thing you're after?