This leaves MUDs in a weird place since things like MUSHes generally have most of the roleplaying tools without as much weird code for attacks and PVP interactions being involved so I've seen those thrive more recently.
One adjacent project we're exploring for the future is if you took all of the current understanding of game design and mechanics with modern AI functionality, knowledge bases, etc, and built a MUD, what would it look like and would it be enough to bring back players from other games?
Interesting, could you share more info? I couldn't find anything on Google. I played a fair amount of SOI back in the day and it'd be fun to start over on a fresh server.
Maybe limiting npc's to only a certain number of moves that aren't a response to other users per day...
It could be a lot of fun.
If a MUD is going to survive today it's going to be driven by those RP focused players where the freedom to describe actions in text allows a flexibility that's unrealistic in graphical games.
Not to say that what you're describing didn't exist, but I don't think it was defining feature of all MUDs.
Secondly, exactly none of these had a "combat system" of any kind. These were all derived from TinyMUD, written by Jim Aspnes at CMU. https://en.wikipedia.org/wiki/James_Aspnes
TinyMUD was a "social MUD" and its explicit goals were to be a glorified chat room, and a sort of "blank slate" for people interested in building their own extensible worlds, based on a pure textual interface. There was absolutely no "combat system" at all--in stark contrast to the other "MUDs" on the scene in those days, such as AberMUD, DikuMUD, and LPmud, which were arguably way more popular, way more violent, and way more into the "combat" or "PvP" or also PvE type play styles.
There was, of course, a "kill" command to allow one player to kill another. But the results of the kill were quite nerfed: the player was sent to their $HOME, and collected an "insurance policy" of pennies, which was partly based on the killer-determined "cost" to kill them in the first place. This wasn't combat by any means--basically, a way to sort of put an exclamation mark on a conversation.
MOO, though it was not derived from any Tiny* codebase, was also one of those "talkie" muds at its heart: it was an object-oriented, fully-programmable, extensible world-building server, where indeed, any combat system could've been implemented, if the players/programmers of a certain world agreed to include combat. But MOO was unique in giving a "barebones" server to program from first principles. So, no, none of these had combat systems, and that's their chief appeal.
I sure spent a lot of time on Furry. I think the penultimate time I logged on there was something like a decade ago; the last time was to attend Tugrik's wake.
The real truth is they have a 30 second attention span and can't finish a page without daydreaming so in order to stay focussed they need a YouTube video than contains the same information but with constant visual changes.
With modern technology, training in both games is very automatable. But developing and optimizing your training routines is (in my opinion) incredibly fun. Actual roleplaying is less common it was in the 90s, but there are still nightly events where dozens of players will get together to socialize and explore the worlds in-character.
I suspect MUDs may have a bit of a resurgence soon, I've seen more and more interest in them as of late simply because they seem like an excellent pairing with LLMs which easily consume text. Though I think for your needs someone would need to work on the barrier to entry to getting on a MUD as well as the modern UI/UX expected today.
I think this could be solved with bridge bots to make your MUD multiplatform. You could have a dedicated web app, an IRC bridge, a Discord bridge, etc.
Discord-brained users can still use your MUD and contribute to network effects, and you can provide an off-ramp ("I just want to play VarelionScape, maybe I'll just open the dedicated website on my phone instead of going on Discord and digging through the server list").
About 15 years ago, for a while I ran a MUD over AX.25, because MUDs aren't nerdy enough on their own, and amateur radio - even packet radio - isn't nerdy enough on its own.
All three of us that used it found it pretty entertaining.
I started playing on an LP MUD in the late '90s. Over the past 20 years, I tried a few times to implement a similar environment, only with everyone being a "wizard". LPC was also a prototype-based OO language with multiple inheritance, and it supported live development, with code for objects stored in files and dynamically reloadable. I would always hit some kind of blocker, no matter the language I chose for the implementation. It looks like MOOs did (and do) what I wanted, but I just wasn't aware of their existence. :( Maybe if I used MOOs as a model, I'd get better results... but I'm not sure if I want to go all in on DB. I tried looking up how the code is loaded into the DB in the book (https://timbran.org/book), but couldn't find it. Is there an explanation somewhere of how MOOs are bootstrapped from sources, how you can maintain sources in files on disk, and how new definitions are pulled into the DB at runtime?
For one, I think MOO is kind of shite in lots of ways. But I and others spent lots of time 20+ years ago building alternatives and nobody used them. There's intrinsic value to just picking up and then improving on something that has established history. It gathers an audience of users, has name recognition, and most importantly keeps you responsible from an engineering dev POV because you are forced to focus on delivering a thing that works and you have a way to prove it. As Linux has shown, incremental improvement on a somewhat flawed but relatively popular and known foundation has value. mooR cakes over a lot of the ugly parts of MOO and honestly, I'm pretty proud of it.
Secondly, existing "mainstream" languages are not appropriate, mostly. None of them or their runtimes are really based on a properly sandboxed persistent model. I poked at WASM, and I could write a screed about that, but wrong system. MOO (and successors to it) were built with the idea of lots of people jamming on one shared world, and it shows.
Finally, I have all sorts of ideas on what I think is "better" than MOO, and did eventually open the floodgate this spring and start building out the "dream system" here: https://github.com/timbran-project/mica -- but as you can see from relative star count of one vs the other.. my first point has relvance.
There should be an explanation in the book on how loading works. If not, I'll need to clarify. Documentation writing sucks. But the TLDR is that one of the arguments you pass to the system at start is basically a source directory of ("objdef") human readable / editable source files, and that gets compiled into a persistent binary database. Once that's done, restarts load directly from that DB/image, not source. (But the system can periodically export or "dump" objdef files as well).
Note this is a bit different from classic LambdaMOO, which had no such process. It had a primitive text database that was not human editable really, and you started from what people passed around of those.
Hope that helps. Come by the discord if you have questions: https://discord.com/invite/Ec94y5983z
Also I just finally put up a new blog post on dev status https://timbran.org/catching-up-with-moor.html
Right. I kind of forgot that MUDs are supposed to be social. Seeing as the popularity of MUDs plummeted, I also changed my goals over time: I want to build a persistent, text-based (but with rich formatting support, including eventually GUI widgets) live programmable environment with network transparency and multiple concurrent sessions allowed. Since it's personal/local space first, and only allows others to "visit" (and even that is mostly for my own remote sessions), I don't need many users initially. If I was trying to build something that emphasizes the multi-user aspect, the choice of continuing one of the historical lineages would be much harder to avoid.
> Secondly, existing "mainstream" languages are not appropriate, mostly. None of them or their runtimes are really based on a properly sandboxed persistent model.
You're right. And even if you broaden the search so much that "mainstream" is barely visible from the cut-off point, you're left with basically just Smalltalk. My current attempt is based on GToolkit distribution of Pharo Smalltalk - it does check some boxes, but it's class-based (not a big problem given the dynamism) and VERY single-user by design (quite a big problem, and thinking about eventual security/permissions/capabilities handling gives me a headache). Still, from all the prototypes I made over the years, this attempt went the farthest; I think I'll stick with it for a while longer.
> Finally, I have all sorts of ideas on what I think is "better" than MOO
Thank you, I will definitely check it out :)
> But the TLDR is that one of the arguments you pass to the system at start is basically a source directory of ("objdef") human readable / editable source files, and that gets compiled into a persistent binary database.
Thanks. That's exactly how a Smalltalk image is built, too, at least with the tooling I'm using (GT). You start an image, point it to a set of Git repos with Smalltalk code, which is then loaded into the image, classes are created, and methods get compiled. You then dump the new image. When you start it the next time, it already contains all the code, and you can change it inside the image at runtime, as much as you want. At some point, you export the changed code back to Git repos, and regenerate the image. Since the image contains all the live objects as well, you can close it, and all the state is restored when you reopen it.
Thanks for the Discord invite, I just joined. I'll go over the book and try to run mooR and mica first, and will reach out for help if needed.
For mica specifically: I'm not 100% sure, but I seem to remember you describing the idea behind it much earlier (here on HN) than this spring. I think it was in comments under a Python-Prolog bridge or something like that. Good to see you had the time and motivation to implement it :) I'll definitely give it a read!
I don't think I understand your meaning here. I'd much rather use Markdown than BBCode or related.
> telnet playlom.com 4000
Owe my programming skills to it, and also dropping college, only to start a company later.
They aren't as popular as they once were, but they are still out there. One of the hardest-core OG muds, Armageddon Mud (which was based on the Dark Sun world) recently went down, but the founders have been working on a new reboot with a totally new code base. Looks interesting (I played the original but have no connection with the MUD itself). They are aiming to launch BETA in the relatively near future if anyone wants to check it out.
There are also some OG muds still chugging along after 30+ years, like the hardcore PVP mud Duris:Land of Bloodlust. The player base has dwindled mightily over the years but people still play and it is a load of fun to explore, if MUDs are your thing, as it incredibly expansive having been in active development for decades.
I really wish MUDs were still a thing. The text-based roleplaying communities were largely swallowed by Discord, where as before they existed scattered over proboards, jcink, and a few others.
Discord, being the imperfect text platform, limits the text and leaves most interaction limited by awkward formatting. To boot, even when a better ecosystem is invented, players refuse to give it a shot even if directly invited, because they got comfortable with Discord's terribleness.
It's so frustrating, and I don't know how to voice it, or even what can be done.