I have a question, regarding the plugin::SendToInstance, but I'll explain the situation, so we're all on the same page here.

I was doing some instance testing and ran across something with the instance plugin, that I wasn't aware of before. I logged on 4 seperate (non-gm) accounts and grouped two of them together, leaving the other 2 as singles. I had the SendToInstance npc script set to "group", and it successfully gave the two grouped toons their own group instance, no problem. Of course, inviting another toon into the group, let it join the instance as well.
But, while those two grouped toons were in their instance, the third (non-grouped) toon hailed the same npc, and was given a "public" instance by default. This allowed the fourth single toon to join that public instance too. So I assume, no matter what the instance is setup for, (group or guild), anyone can use the same npc to (unintentionally) start a public instance.
It's an awesome plugin for instances, it really simplifies the process. I'm sure there might be people out there that may have some use for a "public" instance, but it would be pointless for my preferences. Is there an altercation I can do to prevent public instances from being created ? (permanently) ? lol
This is the script I have been testing with. (npc is flagged for qglobal)
Code:
sub EVENT_SAY {
if (($text =~/hail/i) && ($ulevel > 35)) {
quest::say("Greetings $name, Are you interested in a [group] adventure ?");
}
elsif ($text =~/group/i && ($ulevel > 35)) {
plugin::SendToInstance("group", "dulak", 1, 438, 548, 4, "GRP", 64800);
}
}