Exploratory Contribution: MUD Support (MXP/Pueblo) #1288
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't expect this Pull Request to pass as-is. It would definitely need a bit more polish for that. But see the description!
Basically, I'm looking for input on whether this SORT of contribution would be desired, before I commit to going further.
Please let me know if it's not; then I might have to fork. I tried to integrate these features via monkey-patching, but it caused a lot of problems.
Type of changes
Checklist
Description
This patch would add support for MXP (Mud eXtension Protocol) and Pueblo. This required some minor edits to Text, Style, and Console. Because I'm working on a project that relies heavily on Text objects and treating them largely like normal strings, the Text object API was also expanded to handle much more of the Python String API.
Also added the ability to specify BOX type for Traceback printing, because the default one looks terrible in monospace MUD setups.