Feature Request: Add flag to prevent spawn from being sent to client.

[jdestefx]

I am using various spawn2 entries that act as location markers for quest mechanics. In this case, when a mob dies, I randomly pick one of the chest anchors and spawn a chest. I have many anchors, so it clutters up the MacroQuest map. These spawns are invisible and serve no use to the client. It would be nice if there was some flag (maybe on npc_type?) that would indicate to the server to omit sending any information about it's existence at all (think like some kind of GM-hide status or flag on the spawn).

This would also be very useful for anyone wanting to implement scavenger-hunt type events, where a trigger needs to be 100% hidden from the client.

Thanks

[joligario]

Perhaps use a zone global or an encounter to spawn from an array of locations on npc death?

[fryguy503]

Yea, can use an array of AABoxes or if you need to enter an area can have an array checks of enter areas

[jdestefx]

I'm avoiding using hard-coded coords in the script. It's much easier and more manageable in my ecosystem to use spawngroups and spawn2s. It also allows me perl/lua access to convenient functions. This isn't an "on enter" mechanic, either. They are simply a collection of possible places where I can spawn a chest when a mob in proximity is killed.