Drop Inventory Throttles

heyas;

made a note-card drop box script that's about done, but i worry about people trying to spam it. is there a way to prevent or throttle multi-card drops? like, if i have the change event set allowinventorydrop to false, and somebody selects 200 cards from their inventory and chucks them all at once.... will the first one go in and trigger the event an throttle it, or will all 200 be one event? or will it just cue 200 change events? gah!


barring an input throttle.... it was also suggested to keep accepted cards in another prim in a linkset, so that any new drop could be found and sorted easily. but how does one script a prim giving a notecard to another prim in its own linkset? if i could do this, i could do an after-spam clean-up, at least.



also sorta related... is there a ceiling on how many notecards can be in an object? 255 or so? how about how many objects can be passed on a llgiveinventorylist? i want to add a 'box full' routine, but dont know what would be a reasonable limit.

thanks guys!

I believe you can llGiveInventory to a linked prim's key. If the notecard is no-copy, it should be removed from the giving prim. Or you could check the name and remove it if it still exists, or check the permissions and act accordingly.

Perhaps you've got yourself a use for llMinEventDelay

not really, min event delay, would only change the delay in the script (presumably for the changed event in this case) which would mean more batch processing of the individual drops if they run close together....

the limit for items in an object is huge, but you may want to impose your own, to be able to effectively read even just all the titles of the notecards.