friedmag / bider Goto Github PK

Need to update the regexp

I kind of didn't want the addon permanently listening for whispers, but this seems kind of unavoidable. People keep looking for it. And it would be really easy still, so whatever.

Probably want to be able to purge old raids more easily than editing the SavedVariables. They'd be recorded forever in BidER-data anyways.

Since we're doing resets on new tiers/starting the new system right now, we need a one-time reset for everyone initially.

I could see this particularly on tier tokens, people might want to bid on multiple if the same one dropped more than once.

I think this could be pretty cool, and looks easy. Hell, could record a full list of buffs active, though overall that's not that useful. It could be meaningful metrics, though! Heehee, metrics, how corporate.

Sure seems like DKPSystem.com wants this. I don't like it. Should be based on who was actually there, down to the toon.

Saw this a bunch. 2 people bid 2, one person bids 5. The damn thing bitches that it's a tie! No! Bad addon!

I could swear I added this. Either it's broke or something is blocking it from running (the error was that cancel was invalid, maybe I checked the input earlier than I thought).

just a simple option to announce to say "THIS IS THE LAST ANNOUNCEMENT" or something. a close warning.

Oops.

Right now if there are multiple items being auctioned, somebody can bid for more than their total DKP across items. Shouldn't allow that.

I do NOT want to completely tie BidER into the whole GRSS/DKPSystem.com system. I don't like it anywhere near enough to do that. I want more versatility. However, I think it should not be terribly difficult to detect GRSS-provided DKP and create an internal DKP system based on it.

Should auto-assign DKP when a boss kill is detected from DBM. I've already begun looking at this, and am pretty sure it can be done easily.

Right now the current DKP is called total, which is silly. I'm pretty sure we've discussed using something like a historical DKP count (and maybe loot#) for such cases as ties when there isn't an obvious upgrade gap or something. Either way, it'd be something good and easy to track.

Thankfully it only happened once and worked itself out. But it should from "pick loot" just know. And I even tried it manually and it still fucked up. That ain't right. It showed up as two separate x1's and, ... hmm. You know they might actually be slightly different in the case of tokens. The links might not be identical. Fuck? Need to look into that. I forgot they don't stack. Maybe nonstacking items are different somehow?

This is ridiculous! I probably should lower() everything. Should be easy if everything is properly abstracted. Which it probably isn't entirely right now, but...

Or, since WoW forces the same capitalization on everyone, could easily just correct for it I would think.

Something like [item] 6o or 6m. Or if I wanted to get really fancy, it could register as unspecified by default and ask the user to followup. Maybe that would be best...

"NOTE: You did not specify the item as being main/off spec. To do so, re-submit the bid as [link]{value}m (or o). Loot priority is main, off, and finally unspecified."

I want to be able to erase DKP sets. Right now they grow and grow and the only way to ditch them is to remove them from the SavedVariables (or use the Lua console, which is a much better option I guess).

A lot people would write like "[link] 1 dkp" or other varieties, and it would not work well. It should handle at least that simple a case, getting a 1 is easy.

Problem is the tokens themselves don't actually have an iLvl. Dangit. Going to have to recognize them by name?

Not sure why this didn't occur to me before, but apparently the "Unrecognized bid" message isn't even clear enough to say "no, your bid didn't go through" to some people. Should make it provide help on how to bid.

Seems to assign one loot, then break. I think the index of loot might be shifting - maybe if I iterated through it backward, it would work?

Right now I'm recording all loot won, but I forgot to account for DEs. Those should register differently... they're mostly just to show what has dropped, not for bookkeeping purposes so much.

Realized this the other day, people aren't always on their mains necessarily depending on what a raid needs. Need to account for it.

I think it's actually technically impossible, even directly in Lua since it's all local variables. Should be able to make it a fairly simple option.

Like the title says!

Such as " dkp" or "DKP" etc

DKPSystem.com at least does not like them as input. Don't need them...

I think we can detect a tie and refuse to 'finalize'. Require an edit to set the winner.

I had to open the lua console to fix this in place. Basically, having an invalid channel caused a bunch of errors. Couldn't set it back, either. Possibly corrupted the setting altogether.

This is obviously wrong. I think I just ignored 0 bids originally to avoid pointlessly printing out that DKP didn't change, not thinking about the possibility of a reset.

Like only showing DKP for people in raid by default, probably.

Damn you, Tanner! Bringing along druid and rogue leads to double-DKP granting per kill. This isn't exactly a common case but should be handled.

Think that would be a good thing to see.

WoW really gives us no way of saving or importing data outside of SavedVariables. Well, except one - copy/paste! We could share data with an external application by giving the user a text window they can copy, then paste into the other app. Also, the app could dump stuff to the clipboard to be pasted in.

This would be most useful for attendance taking and tracking DKP over time.

Right now you can only assign relative DKP to the entire raid, and putting a value to a specific user SETS their DKP to that. Relative probably makes a bit more sense in general...

I wasn't entirely clear how to get a listing of party members from the API docs. Can probably figure it out with some work.

In Naxx, alts lost DKP when I switched to do Instructor. Pretty sure it is due to the mechanism I use to alias them... basically, it is a oneshot deal and nothing is done when a "new" DKP system is put in place. Therefore, by creating a new system for the run, he was unaliased until I restarted at which point he was aliased to a 0 since his main did not have points.

Really need a separation of DKP for eg 10/25 mans.

It would be pretty easy to take the DBM pull event and start a raid if in one of our pre-defined raid zones... I keep forgetting to do /ber start before hand, which means I miss stuff.

After finalizing an auction, still need to assign loots. Should be a button equivalent to /ber assign command.

Need to just register attendance in some way. Generate a simple report.

It should properly reflect selections.

Oi. :(

Right now it's hardcoded to 1, and 0 for failed attempts. Both probably might as well be settings.

And be per-player...

Title says it all

Need some sort of system for setting minimum bids on items. Should be easy in theory aside from actually determining/assigning them. I think I should be able to extract the iLvl from the item, though...

Should be able to specify a channel or something to output stuff to. Think this could be good to do for the Print() function which currently just outputs to the local chat window. This would allow sharing of DKP, auction statuses, whatever.