Answers over a certain length get cut off and are not resumed in a second message
Steps to Reproduce
Ask !ai a question, if the answer is long enough, it will be truncated.
Expected Behavior
Answer should come back in 2 messages
Actual Behavior
Answer is truncated
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
### Description
Answers over a certain length get cut off and are not resumed in a second message
### Steps to Reproduce
Ask !ai a question, if the answer is long enough, it will be truncated.
### Expected Behavior
Answer should come back in 2 messages
### Actual Behavior
Answer is truncated
### Archipelago Version
1.7.99-alpha
### Hardware
x86_64 (Intel/AMD)
### Relevant Logs
_No response_
### Screenshots
_No response_
Fixed: mesh assistant replies are now split into ordered 160-character AssistResponse chunks (core/archipelago/src/mesh/listener/assist.rs — CHUNK_CHARS + send_typed_chunks), so a long answer arrives as several messages instead of one cut-off text. There is still an overall length cap with an explicit “(truncated)” marker — LoRa airtime is scarce — but the “never resumed in a second message” defect is gone.
Fixed: mesh assistant replies are now split into ordered 160-character `AssistResponse` chunks (`core/archipelago/src/mesh/listener/assist.rs` — `CHUNK_CHARS` + `send_typed_chunks`), so a long answer arrives as several messages instead of one cut-off text. There is still an overall length cap with an explicit “(truncated)” marker — LoRa airtime is scarce — but the “never resumed in a second message” defect is gone.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
Answers over a certain length get cut off and are not resumed in a second message
Steps to Reproduce
Ask !ai a question, if the answer is long enough, it will be truncated.
Expected Behavior
Answer should come back in 2 messages
Actual Behavior
Answer is truncated
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
Fixed: mesh assistant replies are now split into ordered 160-character
AssistResponsechunks (core/archipelago/src/mesh/listener/assist.rs—CHUNK_CHARS+send_typed_chunks), so a long answer arrives as several messages instead of one cut-off text. There is still an overall length cap with an explicit “(truncated)” marker — LoRa airtime is scarce — but the “never resumed in a second message” defect is gone.