The requestor should at least be able to see the new shared task and get

a member list

There are still a few issues that need to be solved this way.
We could try searching for the members in zone (by name ...) or we could
just fire off to world and world will have to send a special full
serialization so the new zone could load the state. Or at this point we
could just assume that we have saved the state to the DB (which hasn't
been coded yet) and any out of zone members will have to depend on
loading it up from the DB.

common/emu_oplist.h

@@ -462,6 +462,7 @@ N(OP_SetServerFilter),
 N(OP_SetStartCity),
 N(OP_SetTitle),
 N(OP_SetTitleReply),
+N(OP_SharedTaskMemberList),
 N(OP_Shielding),
 N(OP_ShopDelItem),
 N(OP_ShopEnd),

common/eq_packet_structs.h

@@ -3698,6 +3698,7 @@ struct TaskMemberList_Struct {
 /*12*/ char	list_pointer[0];
 /*	list is of the form:
 	char member_name[1]	//null terminated string
+	uint32	monster_mission; // class chosen
 	uint8	task_leader	//boolean flag
 */
 };