Post by Heap on Mar 18, 2019 5:37:32 GMT
The problem with the chat window not working if the line is too long is because there are two line settings. One is the line width setting you set in Mudlet and the other is the line width setting you set in game. If you set the line width setting to 0 in your coffeeMUD session (using LINEWRAP DISABLE), it means that the data that is sent to your client comes as one line and then Mudlet will wrap it based on the display settings.
When LINEWRAP DISABLE is set, that means that the chat triggers will function correctly and get the entire line of text to show up in chat, like this: Screen Shot 2019-03-17 at 9.36.08 PM.png (61.29 KB)
The problem that it causes is that it looks like some of the tables in game were formatted with the "150" character limit in mind, like the WHO ALL list and the inventory lists for banks/vendors. I don't know how difficult it would be to fix, but is there a way to make it so those tables work with both the LINEWRAP 150 setting and the LINEWRAP DISABLE setting? Because it seems like the ideal setting is LINEWRAP DISABLE that way people can set the line line wrap settings in Mudlet however they want, but the triggers will all function correctly.
When LINEWRAP DISABLE is set, that means that the chat triggers will function correctly and get the entire line of text to show up in chat, like this: Screen Shot 2019-03-17 at 9.36.08 PM.png (61.29 KB)
The problem that it causes is that it looks like some of the tables in game were formatted with the "150" character limit in mind, like the WHO ALL list and the inventory lists for banks/vendors. I don't know how difficult it would be to fix, but is there a way to make it so those tables work with both the LINEWRAP 150 setting and the LINEWRAP DISABLE setting? Because it seems like the ideal setting is LINEWRAP DISABLE that way people can set the line line wrap settings in Mudlet however they want, but the triggers will all function correctly.