Check out packet 0xBF and it's subcommand 4:
http://packets.polserver.com/index.php?op=showpacket&packet=0xBF.
What I'm asking for is core function to do the gump-closing trick. You see, when this packet is sent, client closes the gump, but never replies in any way. Thus process that sends the gump using SendGumpDialog() leaves hanging. There is really nothing you can do but .kill() it.
That would be fine, if it weren't the new (5.0.6c, at least) superb clients that remember where the user dragged the gump. Great feature if you happen to have a gump that is used often and a lot. Sadly this feature only works if the gumps id (which is the PID of the process that sends it!) remains the same. So, if process is killed, the actual location of gump gets lost.
While this problem could be solved, like, adding a new parameter to SendDialogGump(), which would of course be 'gump_id', I think that CloseDialogGump() (or CloseGump() if you want to be user friendly) would be more useful addon to core as overall.
So, to summarize the idea:
Add a function CloseDialogGump( character, gump_id ), which would send packet to player AND (this is THE FEATURE!)
tell the process that sent the gump to stop waiting for it!
