@tragedyjones said:
@Chime is an amazing (and amazingly busy) person who provides awesome and stable hosting for these games to live on.
Thanks! Just had a major change of things at work so maybe stuff will get better. I'm hoping, at least.
@Thenomain said:
I really don't want to be singled out for helping code things.
Preach!
I code WoD, which is one of the most convoluted, intricate, and annoying system I've ever coded. 7th Sea was a hundred times easier to code, and I imagine D&D is likewise. I want people to rely more on simple systems and creativity than this kind of thing, but here we are.
Preach!
I rather hate that people rely this heavily on code to make a game. It makes the barrier of entry so damn high, and I promised @Chime that if she made her Modernized Moo, I would code all over it. I think she's calling it Squidcat. Or Squishy. I don't know, but I want it.
Squids are THUGS of the SEA. I prefer octopodes. Or cuttlefish-- they are pretty cute too. I like nautiluses in theory, but the simpler eye kinda weirds me out. The fantastically bizarre vision capabilities of octopuses and cuttlefish are half the attraction.
And no; I've had various stabs at it codenamed various things over the years. Initially, I'd been looking for something short, simple, and starting with MU. I discovered fairly quickly that TinyMuff might be interpreted somewhat differently by other people.
If I finish up the Lua-based prototype I have, it'll be called TinyMoon. I don't forsee myself finishing a js-based solution, though I made some work down that direction; had a C++ prototype using V8 back before nodejs was really a thing; it had a fair bit of thought spent on scalable high-performance attributed strings (e.g. color specifications and other markup, but generalized in the way that only bored compsci people can...). It was called TinyMuut, but I don't think I'll be continuing it.
I have a fork of MOO somewhere that adds a variety of functional-programming concepts for stacked list processing functions and essentially most of the good stuff that a proper lambda form would offer. Awkwardly, the MOO VM makes it a bit difficult to really do that right, as functions aren't first class objects and specifying anonymous closures as tiny moo-forks tacked onto the end gets messy. Really messy, considering MOO needs to decompile the bytecode back into sourcecode to show it.
I also want a hot librarian nerd girlfriend.
...I can see the appeal.
My baseline for code legibility is @Cobaltasaurus. For everyone who says, "I don't understand code," I point to her. She was still saying it when she coded +events. When I was coding WoD stuff, I would point her to things and say, "Does this make sense?" If it did, I was on the right track.
That's reasonable. I gave up on making things understandable a long time ago, though. Instead, I aim to make the code understandable by me when I look at it in the future. Toward that end, code should be clean, concise, and move like poetry. These are sometimes often conflicting goals.