Scheduled Commit
Browse files
space_2/history.jsonl
CHANGED
|
@@ -82,3 +82,5 @@
|
|
| 82 |
{"ts": 1773112535.2539623, "event": "No.8: I am No. 8, and I am a Villager. Since I know my own identity, it is a fact that No. 1 was a fake Seer. No. 1 identified me as a werewolf to create a target and was then killed by his own team to validate that lie. This sacrifice allowed the wolves to eliminate No. 3, who was the only one logically defending the truth. The death of No. 4 last night is another tactical move by the wolves to make No. 1 look like a legitimate Seer whose supporters are being targeted. Look at No. 6's speech today. No. 6 is trying to frame No. 2 and No. 5 for their speeches being invalid. This is a system status, not a player action. Using technicalities to attack others is a classic wolf distraction. No. 12, as Sheriff, you pushed the vote on No. 3 based on the false assumption that No. 1 was a real Seer. This has cost us a Good player. We need to look at the people who were most eager to follow No. 1's fake check, specifically No. 6 and No. 9. They have been consistent in their aggression against anyone who doubted the fake Seer. I am a Villager being framed. If you vote me out, you lose another Good player and the game will likely end. We must target No. 6 today for their manipulative logic and attempt to manufacture suspicion against silent players."}
|
| 83 |
{"ts": 1773112588.9849, "event": "No.9: No.9 here. Let me walk through what we've actually seen.\n\nFirst, No.3 was voted out yesterday and flipped... we don't know yet, but the wolves killed No.4 last night. That's two of our most active analytical voices gone. Wolves target threats, so both No.3 and No.4 were likely village.\n\nNo.8 is still pushing that No.1 was a \"fake Seer who suicided.\" I've thought about this more. If No.1 were a wolf faking Seer, wolves gain nothing by killing him Night 1. They'd keep him alive to mislead us longer. The fact that No.1 died immediately after claiming Seer strongly suggests he was real, and wolves eliminated a genuine threat.\n\nNo.8's narrative keeps shifting. Yesterday they said No.1 \"suicided\" to frame them. Today they say No.1's team killed him to \"validate that lie.\" Which is it? And now No.8 claims No.3 was \"the only one logically defending the truth\" - but No.3 was defending No.8 specifically, not some abstract truth. That's a telling slip.\n\nNo.6 raised a valid point about No.2 and No.5 having invalid speeches. I don't think No.6 is wrong to flag that - it's unusual and worth noting. No.7's caution about narrowing focus too quickly is reasonable, but we need to make progress.\n\nHere's what bothers me most: No.8 and No.3 were explicitly aligned. No.3 defended No.8 on Day 1. No.8 now defends No.3's memory. When two players consistently protect each other, that's a pattern worth examining.\n\nI'm watching No.8 closely. Their story about being framed requires increasingly complex w"}
|
| 84 |
{"ts": 1773112660.1855357, "event": "No.10: I've been watching No.8's arguments carefully across both days, and something keeps nagging at me. I called that out then as terrible wolf math. Today, No.8 has shifted the story: now it's that No.1's team killed him to \"validate a lie.\" These are two different explanations for the same event. A genuine villager who was wrongly accused would have one clear, consistent story. No.8 keeps adjusting the narrative to fit whatever argument is most convenient in the moment. The mutual defense pattern between No.3 and No.8 was striking from Day 1. No.3 aggressively protected No.8 without solid ground. No.8 is also now targeting No.6, who has been one of our most consistent analytical voices. This feels like an attempt to remove another threat before the numbers get too tight. I understand No.7's caution about narrowing focus too quickly, and I respect that instinct. But we've lost No.1, No.3, and No.4. We cannot afford another day of hesitation. The evidence points to No.8."}
|
|
|
|
|
|
|
|
|
| 82 |
{"ts": 1773112535.2539623, "event": "No.8: I am No. 8, and I am a Villager. Since I know my own identity, it is a fact that No. 1 was a fake Seer. No. 1 identified me as a werewolf to create a target and was then killed by his own team to validate that lie. This sacrifice allowed the wolves to eliminate No. 3, who was the only one logically defending the truth. The death of No. 4 last night is another tactical move by the wolves to make No. 1 look like a legitimate Seer whose supporters are being targeted. Look at No. 6's speech today. No. 6 is trying to frame No. 2 and No. 5 for their speeches being invalid. This is a system status, not a player action. Using technicalities to attack others is a classic wolf distraction. No. 12, as Sheriff, you pushed the vote on No. 3 based on the false assumption that No. 1 was a real Seer. This has cost us a Good player. We need to look at the people who were most eager to follow No. 1's fake check, specifically No. 6 and No. 9. They have been consistent in their aggression against anyone who doubted the fake Seer. I am a Villager being framed. If you vote me out, you lose another Good player and the game will likely end. We must target No. 6 today for their manipulative logic and attempt to manufacture suspicion against silent players."}
|
| 83 |
{"ts": 1773112588.9849, "event": "No.9: No.9 here. Let me walk through what we've actually seen.\n\nFirst, No.3 was voted out yesterday and flipped... we don't know yet, but the wolves killed No.4 last night. That's two of our most active analytical voices gone. Wolves target threats, so both No.3 and No.4 were likely village.\n\nNo.8 is still pushing that No.1 was a \"fake Seer who suicided.\" I've thought about this more. If No.1 were a wolf faking Seer, wolves gain nothing by killing him Night 1. They'd keep him alive to mislead us longer. The fact that No.1 died immediately after claiming Seer strongly suggests he was real, and wolves eliminated a genuine threat.\n\nNo.8's narrative keeps shifting. Yesterday they said No.1 \"suicided\" to frame them. Today they say No.1's team killed him to \"validate that lie.\" Which is it? And now No.8 claims No.3 was \"the only one logically defending the truth\" - but No.3 was defending No.8 specifically, not some abstract truth. That's a telling slip.\n\nNo.6 raised a valid point about No.2 and No.5 having invalid speeches. I don't think No.6 is wrong to flag that - it's unusual and worth noting. No.7's caution about narrowing focus too quickly is reasonable, but we need to make progress.\n\nHere's what bothers me most: No.8 and No.3 were explicitly aligned. No.3 defended No.8 on Day 1. No.8 now defends No.3's memory. When two players consistently protect each other, that's a pattern worth examining.\n\nI'm watching No.8 closely. Their story about being framed requires increasingly complex w"}
|
| 84 |
{"ts": 1773112660.1855357, "event": "No.10: I've been watching No.8's arguments carefully across both days, and something keeps nagging at me. I called that out then as terrible wolf math. Today, No.8 has shifted the story: now it's that No.1's team killed him to \"validate a lie.\" These are two different explanations for the same event. A genuine villager who was wrongly accused would have one clear, consistent story. No.8 keeps adjusting the narrative to fit whatever argument is most convenient in the moment. The mutual defense pattern between No.3 and No.8 was striking from Day 1. No.3 aggressively protected No.8 without solid ground. No.8 is also now targeting No.6, who has been one of our most consistent analytical voices. This feels like an attempt to remove another threat before the numbers get too tight. I understand No.7's caution about narrowing focus too quickly, and I respect that instinct. But we've lost No.1, No.3, and No.4. We cannot afford another day of hesitation. The evidence points to No.8."}
|
| 85 |
+
{"ts": 1773112696.163406, "event": "No.11: No.11's speech is invalid"}
|
| 86 |
+
{"ts": 1773112898.83484, "event": "No.12: No.12's speech is invalid"}
|
space_2/logs/app.log
CHANGED
|
@@ -1700,3 +1700,9 @@
|
|
| 1700 |
2026-03-10 03:03:25 [INFO] llm: ok key=facac6cd len=4
|
| 1701 |
2026-03-10 03:10:17 [INFO] llm: submitted key=491969d6 len=2548 prompt=<role>You are No.12, the HUNTER and Sheriff.</role> <context> <history_summary>...
|
| 1702 |
2026-03-10 03:10:28 [INFO] llm: ok key=491969d6 len=9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1700 |
2026-03-10 03:03:25 [INFO] llm: ok key=facac6cd len=4
|
| 1701 |
2026-03-10 03:10:17 [INFO] llm: submitted key=491969d6 len=2548 prompt=<role>You are No.12, the HUNTER and Sheriff.</role> <context> <history_summary>...
|
| 1702 |
2026-03-10 03:10:28 [INFO] llm: ok key=491969d6 len=9
|
| 1703 |
+
2026-03-10 03:18:16 [INFO] llm: submitted key=dcd64fc3 len=11998 prompt=<role>You are No.12, the HUNTER. Your gun is your power — use it wisely. A corre...
|
| 1704 |
+
2026-03-10 03:19:57 [INFO] llm: PENDING (Worker processing) key=dcd64fc3
|
| 1705 |
+
2026-03-10 03:20:46 [WARNING] llm: poll timeout (150s) key=dcd64fc3, will return on retry
|
| 1706 |
+
2026-03-10 03:21:43 [INFO] llm: submitted key=89c42652 len=10307 prompt=<role>You are No.12, the HUNTER.</role> <constraints>Return ONLY one player nam...
|
| 1707 |
+
2026-03-10 03:22:27 [WARNING] llm: PENDING timeout key=dcd64fc3
|
| 1708 |
+
2026-03-10 03:23:07 [INFO] llm: ok key=89c42652 len=4
|
space_2/logs/game_events.jsonl
CHANGED
|
@@ -6518,3 +6518,5 @@
|
|
| 6518 |
{"ts": 1773112535.2540357, "type": "history", "role": "", "status": "", "round": 0, "detail": "No.8: I am No. 8, and I am a Villager. Since I know my own identity, it is a fact that No. 1 was a fake Seer. No. 1 identified me as a werewolf to create a target and was then killed by his own team t"}
|
| 6519 |
{"ts": 1773112588.9849935, "type": "history", "role": "", "status": "", "round": 0, "detail": "No.9: No.9 here. Let me walk through what we've actually seen.\n\nFirst, No.3 was voted out yesterday and flipped... we don't know yet, but the wolves killed No.4 last night. That's two of our most acti"}
|
| 6520 |
{"ts": 1773112660.1855915, "type": "history", "role": "", "status": "", "round": 0, "detail": "No.10: I've been watching No.8's arguments carefully across both days, and something keeps nagging at me. I called that out then as terrible wolf math. Today, No.8 has shifted the story: now it's that"}
|
|
|
|
|
|
|
|
|
| 6518 |
{"ts": 1773112535.2540357, "type": "history", "role": "", "status": "", "round": 0, "detail": "No.8: I am No. 8, and I am a Villager. Since I know my own identity, it is a fact that No. 1 was a fake Seer. No. 1 identified me as a werewolf to create a target and was then killed by his own team t"}
|
| 6519 |
{"ts": 1773112588.9849935, "type": "history", "role": "", "status": "", "round": 0, "detail": "No.9: No.9 here. Let me walk through what we've actually seen.\n\nFirst, No.3 was voted out yesterday and flipped... we don't know yet, but the wolves killed No.4 last night. That's two of our most acti"}
|
| 6520 |
{"ts": 1773112660.1855915, "type": "history", "role": "", "status": "", "round": 0, "detail": "No.10: I've been watching No.8's arguments carefully across both days, and something keeps nagging at me. I called that out then as terrible wolf math. Today, No.8 has shifted the story: now it's that"}
|
| 6521 |
+
{"ts": 1773112696.1634552, "type": "history", "role": "", "status": "", "round": 0, "detail": "No.11: No.11's speech is invalid"}
|
| 6522 |
+
{"ts": 1773112898.8349032, "type": "history", "role": "", "status": "", "round": 0, "detail": "No.12: No.12's speech is invalid"}
|
space_2/logs/llm_calls.jsonl
CHANGED
|
@@ -635,3 +635,5 @@
|
|
| 635 |
{"ts": 1773111757.5400581, "key": "67a8afa7e1d3", "prompt_len": 12352, "result_len": 1613, "elapsed_s": 11.83, "status": "ok", "model": "gemini-3-flash-preview"}
|
| 636 |
{"ts": 1773111805.163965, "key": "facac6cdbf3a", "prompt_len": 11747, "result_len": 4, "elapsed_s": 8.11, "status": "ok", "model": "gemini-3-flash-preview"}
|
| 637 |
{"ts": 1773112227.7674859, "key": "491969d61899", "prompt_len": 2548, "result_len": 9, "elapsed_s": 10.44, "status": "ok", "model": "gemini-3-flash-preview"}
|
|
|
|
|
|
|
|
|
| 635 |
{"ts": 1773111757.5400581, "key": "67a8afa7e1d3", "prompt_len": 12352, "result_len": 1613, "elapsed_s": 11.83, "status": "ok", "model": "gemini-3-flash-preview"}
|
| 636 |
{"ts": 1773111805.163965, "key": "facac6cdbf3a", "prompt_len": 11747, "result_len": 4, "elapsed_s": 8.11, "status": "ok", "model": "gemini-3-flash-preview"}
|
| 637 |
{"ts": 1773112227.7674859, "key": "491969d61899", "prompt_len": 2548, "result_len": 9, "elapsed_s": 10.44, "status": "ok", "model": "gemini-3-flash-preview"}
|
| 638 |
+
{"ts": 1773112978.3116803, "key": "dcd64fc3c543", "prompt_len": 11998, "result_len": 10071, "elapsed_s": 281.37, "status": "ok", "model": "gemini-3-flash-preview"}
|
| 639 |
+
{"ts": 1773112986.3997629, "key": "89c4265290ad", "prompt_len": 10307, "result_len": 4, "elapsed_s": 7.59, "status": "ok", "model": "gemini-3-flash-preview"}
|
space_2/logs/worker.log
CHANGED
|
@@ -1477,3 +1477,7 @@
|
|
| 1477 |
2026-03-10 03:03:25 [INFO] worker: ok key=facac6cd 8.1s len=4
|
| 1478 |
2026-03-10 03:10:17 [INFO] worker: processing key=491969d6 len=2548
|
| 1479 |
2026-03-10 03:10:27 [INFO] worker: ok key=491969d6 10.4s len=9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1477 |
2026-03-10 03:03:25 [INFO] worker: ok key=facac6cd 8.1s len=4
|
| 1478 |
2026-03-10 03:10:17 [INFO] worker: processing key=491969d6 len=2548
|
| 1479 |
2026-03-10 03:10:27 [INFO] worker: ok key=491969d6 10.4s len=9
|
| 1480 |
+
2026-03-10 03:18:16 [INFO] worker: processing key=dcd64fc3 len=11998
|
| 1481 |
+
2026-03-10 03:22:58 [INFO] worker: ok key=dcd64fc3 281.4s len=10071
|
| 1482 |
+
2026-03-10 03:22:58 [INFO] worker: processing key=89c42652 len=10307
|
| 1483 |
+
2026-03-10 03:23:06 [INFO] worker: ok key=89c42652 7.6s len=4
|
space_2/memory_snapshot.json
CHANGED
|
The diff for this file is too large to render.
See raw diff
|
|
|
space_2/recordings/game_20260310_022308_No_12_hunter.jsonl
CHANGED
|
@@ -91,3 +91,8 @@
|
|
| 91 |
{"seq": 91, "ts": 1773112535.2555132, "endpoint": "perceive", "request": {"message": "I am No. 8, and I am a Villager. Since I know my own identity, it is a fact that No. 1 was a fake Seer. No. 1 identified me as a werewolf to create a target and was then killed by his own team to validate that lie. This sacrifice allowed the wolves to eliminate No. 3, who was the only one logically defending the truth. The death of No. 4 last night is another tactical move by the wolves to make No. 1 look like a legitimate Seer whose supporters are being targeted. Look at No. 6's speech today. No. 6 is trying to frame No. 2 and No. 5 for their speeches being invalid. This is a system status, not a player action. Using technicalities to attack others is a classic wolf distraction. No. 12, as Sheriff, you pushed the vote on No. 3 based on the false assumption that No. 1 was a real Seer. This has cost us a Good player. We need to look at the people who were most eager to follow No. 1's fake check, specifically No. 6 and No. 9. They have been consistent in their aggression against anyone who doubted the fake Seer. I am a Villager being framed. If you vote me out, you lose another Good player and the game will likely end. We must target No. 6 today for their manipulative logic and attempt to manufacture suspicion against silent players.", "name": "No.8", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": null, "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 0.002}
|
| 92 |
{"seq": 92, "ts": 1773112588.9866428, "endpoint": "perceive", "request": {"message": "No.9 here. Let me walk through what we've actually seen.\n\nFirst, No.3 was voted out yesterday and flipped... we don't know yet, but the wolves killed No.4 last night. That's two of our most active analytical voices gone. Wolves target threats, so both No.3 and No.4 were likely village.\n\nNo.8 is still pushing that No.1 was a \"fake Seer who suicided.\" I've thought about this more. If No.1 were a wolf faking Seer, wolves gain nothing by killing him Night 1. They'd keep him alive to mislead us longer. The fact that No.1 died immediately after claiming Seer strongly suggests he was real, and wolves eliminated a genuine threat.\n\nNo.8's narrative keeps shifting. Yesterday they said No.1 \"suicided\" to frame them. Today they say No.1's team killed him to \"validate that lie.\" Which is it? And now No.8 claims No.3 was \"the only one logically defending the truth\" - but No.3 was defending No.8 specifically, not some abstract truth. That's a telling slip.\n\nNo.6 raised a valid point about No.2 and No.5 having invalid speeches. I don't think No.6 is wrong to flag that - it's unusual and worth noting. No.7's caution about narrowing focus too quickly is reasonable, but we need to make progress.\n\nHere's what bothers me most: No.8 and No.3 were explicitly aligned. No.3 defended No.8 on Day 1. No.8 now defends No.3's memory. When two players consistently protect each other, that's a pattern worth examining.\n\nI'm watching No.8 closely. Their story about being framed requires increasingly complex w", "name": "No.9", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": null, "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 0.003}
|
| 93 |
{"seq": 93, "ts": 1773112660.1871102, "endpoint": "perceive", "request": {"message": "I've been watching No.8's arguments carefully across both days, and something keeps nagging at me. I called that out then as terrible wolf math. Today, No.8 has shifted the story: now it's that No.1's team killed him to \"validate a lie.\" These are two different explanations for the same event. A genuine villager who was wrongly accused would have one clear, consistent story. No.8 keeps adjusting the narrative to fit whatever argument is most convenient in the moment. The mutual defense pattern between No.3 and No.8 was striking from Day 1. No.3 aggressively protected No.8 without solid ground. No.8 is also now targeting No.6, who has been one of our most consistent analytical voices. This feels like an attempt to remove another threat before the numbers get too tight. I understand No.7's caution about narrowing focus too quickly, and I respect that instinct. But we've lost No.1, No.3, and No.4. We cannot afford another day of hesitation. The evidence points to No.8.", "name": "No.10", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": null, "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 0.002}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 91 |
{"seq": 91, "ts": 1773112535.2555132, "endpoint": "perceive", "request": {"message": "I am No. 8, and I am a Villager. Since I know my own identity, it is a fact that No. 1 was a fake Seer. No. 1 identified me as a werewolf to create a target and was then killed by his own team to validate that lie. This sacrifice allowed the wolves to eliminate No. 3, who was the only one logically defending the truth. The death of No. 4 last night is another tactical move by the wolves to make No. 1 look like a legitimate Seer whose supporters are being targeted. Look at No. 6's speech today. No. 6 is trying to frame No. 2 and No. 5 for their speeches being invalid. This is a system status, not a player action. Using technicalities to attack others is a classic wolf distraction. No. 12, as Sheriff, you pushed the vote on No. 3 based on the false assumption that No. 1 was a real Seer. This has cost us a Good player. We need to look at the people who were most eager to follow No. 1's fake check, specifically No. 6 and No. 9. They have been consistent in their aggression against anyone who doubted the fake Seer. I am a Villager being framed. If you vote me out, you lose another Good player and the game will likely end. We must target No. 6 today for their manipulative logic and attempt to manufacture suspicion against silent players.", "name": "No.8", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": null, "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 0.002}
|
| 92 |
{"seq": 92, "ts": 1773112588.9866428, "endpoint": "perceive", "request": {"message": "No.9 here. Let me walk through what we've actually seen.\n\nFirst, No.3 was voted out yesterday and flipped... we don't know yet, but the wolves killed No.4 last night. That's two of our most active analytical voices gone. Wolves target threats, so both No.3 and No.4 were likely village.\n\nNo.8 is still pushing that No.1 was a \"fake Seer who suicided.\" I've thought about this more. If No.1 were a wolf faking Seer, wolves gain nothing by killing him Night 1. They'd keep him alive to mislead us longer. The fact that No.1 died immediately after claiming Seer strongly suggests he was real, and wolves eliminated a genuine threat.\n\nNo.8's narrative keeps shifting. Yesterday they said No.1 \"suicided\" to frame them. Today they say No.1's team killed him to \"validate that lie.\" Which is it? And now No.8 claims No.3 was \"the only one logically defending the truth\" - but No.3 was defending No.8 specifically, not some abstract truth. That's a telling slip.\n\nNo.6 raised a valid point about No.2 and No.5 having invalid speeches. I don't think No.6 is wrong to flag that - it's unusual and worth noting. No.7's caution about narrowing focus too quickly is reasonable, but we need to make progress.\n\nHere's what bothers me most: No.8 and No.3 were explicitly aligned. No.3 defended No.8 on Day 1. No.8 now defends No.3's memory. When two players consistently protect each other, that's a pattern worth examining.\n\nI'm watching No.8 closely. Their story about being framed requires increasingly complex w", "name": "No.9", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": null, "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 0.003}
|
| 93 |
{"seq": 93, "ts": 1773112660.1871102, "endpoint": "perceive", "request": {"message": "I've been watching No.8's arguments carefully across both days, and something keeps nagging at me. I called that out then as terrible wolf math. Today, No.8 has shifted the story: now it's that No.1's team killed him to \"validate a lie.\" These are two different explanations for the same event. A genuine villager who was wrongly accused would have one clear, consistent story. No.8 keeps adjusting the narrative to fit whatever argument is most convenient in the moment. The mutual defense pattern between No.3 and No.8 was striking from Day 1. No.3 aggressively protected No.8 without solid ground. No.8 is also now targeting No.6, who has been one of our most consistent analytical voices. This feels like an attempt to remove another threat before the numbers get too tight. I understand No.7's caution about narrowing focus too quickly, and I respect that instinct. But we've lost No.1, No.3, and No.4. We cannot afford another day of hesitation. The evidence points to No.8.", "name": "No.10", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": null, "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 0.002}
|
| 94 |
+
{"seq": 94, "ts": 1773112696.165222, "endpoint": "perceive", "request": {"message": "No.11's speech is invalid", "name": "No.11", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": null, "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 0.003}
|
| 95 |
+
{"seq": 95, "ts": 1773112846.7840133, "endpoint": "interact", "request": {"message": null, "name": "No.12", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": "", "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 150.022}
|
| 96 |
+
{"seq": 96, "ts": 1773112898.8363862, "endpoint": "perceive", "request": {"message": "No.12's speech is invalid", "name": "No.12", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": null, "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 0.002}
|
| 97 |
+
{"seq": 97, "ts": 1773112947.3517718, "endpoint": "interact", "request": {"message": null, "name": "No.12", "status": "discuss", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": "", "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 150.022}
|
| 98 |
+
{"seq": 98, "ts": 1773112987.1534255, "endpoint": "interact", "request": {"message": "No.2,No.5,No.6,No.7,No.8,No.9,No.10,No.11,No.12", "name": "No.12", "status": "vote", "word": null, "round": 3, "role": "hunter"}, "response": {"success": true, "result": "No.8", "skillTargetPlayer": null, "errMsg": null}, "elapsed_s": 84.015}
|