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_SoF.conf

@@ -500,7 +500,7 @@ OP_TaskHistoryRequest=0x3035		#
 OP_TaskHistoryReply=0x3A60		#
 OP_CancelTask=0x4db6			#Xinu or 0x2c8c or 0x4db6
 OP_DeclineAllTasks=0x0000		#not sure, 12 bytes
-OP_TaskMemberList=0x3713
+#OP_TaskMemberList=0x3713
 OP_TaskMemberInvite=0x3cde
 OP_TaskMemberInviteResponse=0x6cab
 OP_TaskMemberChange=0x354a
@@ -511,6 +511,7 @@ OP_TaskPlayerList=0x0ad6
 OP_TaskQuit=0x2c8c
 OP_TaskRequestTimer=0x0b08
 OP_AcceptNewSharedTask=0x5bed
+OP_SharedTaskMemberList=0x3713
 
 #Title opcodes
 OP_NewTitlesAvailable=0x179c		#