Why don't you have all of your player.pl's reference a plugin/sub routine for each player.pl subroutine so you don't have to go back through all of those files to make any global changes like that again.

Not to derail the thread too much, but:

Yeah, that would be a decent solution for that type of thing. I could have done that easy enough with plugins or using require(). I just don't like the idea of having to have special player.pl stuff global in every zone. If something needs to be global like that, I normally try to find a better solution for it. In the case of the custom aug pool stuff I made, I only added it to a few key zones as a temporary solution until I had a better one. If something has to go in every zone's player.pl, that would mean I would really need to do it in every single current and future zone in the quests folder. I am sure I could get away with just doing it for our own custom zones, but again, I don't want to have to manage all player.pls like that in any way. There is always another solution!

Anyway, I am hoping to get this running on Storm Haven today and will leave it in for testing so it can be committed maybe tonight.

Don't worry about it in the slightest. You took the time to review, found a few issues, and suggested a better way that works perfectly.

Appreciate the help Trevius.

Appears to be a small defect here - as we are using the same path as the augmentation container, we are first pushing the item to the client then deleting the item (in the container) from the client.

This can cause issues if you have a lag spike and both updates do not happen almost simultaneously.

Looks like it is limited to just deleting one of the lore items and making the other invisible until the client logs off or zones - an annoyance but does not appear to cause any item deletion. Posting a fix for this now.