OK, I just saw in my plugins where I’m testing this to update from .11 to .15, and did that, looked in changelog which said you fixed some things with dynamic price calc. So I just regressed the above bug and the dynamic price calc issue is fixed. No extra discounts are used up when recalc is done.

However the related item I mentioned at end is still true. Number of per seat discounts used does not match number of seats booked.
I submit two seats (or 3 or more) with ‘firstfive’ discount but only one discount is used up. I am assuming “fixed per seat” means one discount should be used up for each seat – “per seat” – is that correct, or am I misunderstanding that discount?

OK, thanks.
It seems contrary to the description of “per-seat discount.” If I book three seats at a per-seat discount, that should use up three discounts, whether in one booking or two bookings or three separate bookings. That is my use case anyhow:

A fixed discount is given per seat booked, and, one discount is used up per seat booked.

for example there are five of 20 total seats available at a fixed discount, and each seat booked with that discount must reduce the available discounts by one.

Otherwise I cannot actually control that only five seats are available at that “per-seat” discount price. If someone books 2 in one booking I want only 3 left, but there will be 4 left.

Is there any way I have not tried yet that your plugin would do that?

If not would you consider this as a feature request?
It is a common use case in my experience. First X number of registrations (of some larger total registrations available) get a specific discount; after that one must pay the “regular” price.
I might even be able to contribute code – if the data/code model you have established so far can include this use case.

thanks,
John

Away for holidays, checking back…thanks for response.
It would seem like you already need to be handling some of the cases you identify above, like 4 are used, someone tries to book 2 more…? A booking that was not available because someone booked seconds before the next person would have to be handled with an appropriate message.
Maybe you handle that for seats, but not for discounts, is that what you mean?

Anyhow I understand this is not something you want to work on at this time.
I will do my best to find a workaround for my situation.

The plugin I previously used was unfortunately abandoned – and, not as good as yours overall, just better for this type of discounting. It had a different model – seats were set up by quantity available and price, within an event, with total seats for the event a separate entry, and each booking deducted from the total seats for the event as well as the seats at that price. Discounts were integral with seats, not counted separately (there was also a “coupon code” option but I never used it).

In any case your plugin is well done overall and very versatile in terms of templates and fields and so on. I just happen to have a use case that doesn’t fit well.

regards,
John S.