| Author |
Message |
 Topic: Prompt trigger triggering "too soon" |
Securis
Replies: 6
Views: 7847
|
 Forum: CMUD General Discussion Posted: Mon Jan 18, 2016 4:47 pm Subject: Prompt trigger triggering "too soon" |
Well, I've seemed to work around it reliably.
Sorry that this has turned out into a monologue, but I'll post my solution here in the hope that it might be useful for someone else in the future.
... |
| Topic: Prompt trigger triggering "too soon" |
Securis
Replies: 6
Views: 7847
|
Forum: CMUD General Discussion Posted: Mon Jan 18, 2016 3:45 pm Subject: Prompt trigger triggering "too soon" |
As a follow up: I've confirmed that it's due to the trigger adhering to network packet boundaries.
When I capture some MUD traffic in Wireshark, I see that the network packet boundary coincides with ... |
| Topic: Prompt trigger triggering "too soon" |
Securis
Replies: 6
Views: 7847
|
Forum: CMUD General Discussion Posted: Mon Jan 18, 2016 6:37 am Subject: Prompt trigger triggering "too soon" |
The capture regex:
#K\%(?:@MIP/mipcode)(\d{3})(\a{3})(.*) |
| Topic: Prompt trigger triggering "too soon" |
Securis
Replies: 6
Views: 7847
|
Forum: CMUD General Discussion Posted: Sun Jan 17, 2016 11:18 pm Subject: Prompt trigger triggering "too soon" |
| Edited the post with raw session input/output data. I think that's where the problem lies. |
| Topic: Prompt trigger triggering "too soon" |
Securis
Replies: 6
Views: 7847
|
Forum: CMUD General Discussion Posted: Sun Jan 17, 2016 10:59 pm Subject: Prompt trigger triggering "too soon" |
For my MIP trigger (which I used on 3Kingdoms), in certain cases my prompt trigger triggers "too soon".
Perhaps this is best illustrated by this debug logging (newlines added for clarity):
c 3Kin ... |
| |
