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.

utils/patches/patch_Titanium.conf

@@ -458,7 +458,7 @@ OP_TaskActivityComplete=0x54eb
 OP_CompletedTasks=0x76a2			# ShowEQ 10/27/05
 OP_TaskDescription=0x5ef7			# ShowEQ 10/27/05
 OP_TaskActivity=0x682d			# ShowEQ 10/27/05
-OP_TaskMemberList=0x722f	#not sure
+#OP_TaskMemberList=0x722f	#not sure
 OP_OpenNewTasksWindow=0x5e7c	#combined with OP_AvaliableTask I think
 OP_AvaliableTask=0x0000
 OP_AcceptNewTask=0x207f
@@ -476,6 +476,7 @@ OP_TaskPlayerList=0x3961
 OP_TaskQuit=0x35dd
 OP_TaskRequestTimer=0x6a1d
 OP_AcceptNewSharedTask=0x194d
+OP_SharedTaskMemberList=0x722f
 #task complete related: 0x0000 (24 bytes), 0x0000 (8 bytes), 0x0000 (4 bytes)