CircleMUD VS xml-mut

Unfortunately the server has a blocking select until there's a new socket for when there's no open sockets to manage. I either have to change the old logic or write some awkward condvar stuff (like here https://github.com/Yuffster/CircleMUD/commit/94c27cc11fda671ede5316e6aadc170889060f5e). It's really sad, the naive version that busy loops when the server has no connections is very chic and then it gets a lot harder to follow.

Here's the original CircleMUD code. Here's a decent write-up of the origin of "proc" as shorthand for a triggered effect. Here's a TIL of someone from another MMO discovering its actual origin.

CircleMUD code from https://github.com/Yuffster/CircleMUD

That's a backronym. Proc is just short for procedure from ancient MUD code, randomness is not necessary or implied. You'll notice the term "mob" for a monster also comes from there, they used to be called "mobiles".

This is exactly what I needed when implementing xml-mut :D I have used roxmltree instead and manipulated text directly. will try to rewrite it using Xot.

I was developing a game with Bevy some time ago. But sadly have no time to contribute to it at this time. It still uses Bevy 0.9. Also, I have started some "thing (tm)" related to XML transformation. If that would be your jazz you could grab something like this and have a stab at it :).

Hello dear people. So I have been developing this experiment of mine. it is a simple XML mutation definition language resembling SQL with a CLI to invoke it (something instead of unwieldy XSLT). I am not a top Rust dev just yet. So I would appreciate any feedback regarding the code base. Advice welcome! Further, I would like to know if you consider it useful. Should I invent this when again?

If I will find some time to spare will work on xml-mut. A simple XML mutation definition language resembling SQL.