@Cobaltasaurus said:
Those are the things you want it to do?
Hell no. I want it to die.
@Thenomain said:
There is a way to change how Anomaly Jobs reacts to inputs. I'm looking for it, so I don't have to re-invent this stone wheel. On the whole it acts like this:
Added differently on each mush, which is why I recommend storing UNMODIFIED AJ objects and then override objects that inherit from them; your patches would pop right out and be easy to see.
@Thenomain said:
Try this specimen sheet: http://eldritch.mechanipus.com/w/fonts/berylium/berylium-demo.html
Missing letter drama aside... Theno, that is one ugly-ass font. https://www.google.com/fonts/specimen/IM+Fell+English is much much much nicer, and has clear historical relevance.
@Bobotron said:
@Thenomain
Lots and lots of missing letters.
What browser / os ?
At some point it's fairly reasonable for games to just politely say "lol tough shit sucka."
Missing letters is usually going to mean bad hardware and/or some really strange network filtering. If you can't fix it, just disable CSS support in your browser. MediaWiki is still readable that way.
On the list of much-overlooked things that HM/TheReach did right:
People might not like jobs, but they really are a lot better than every alternative presented thus far. That said,
I'd actually recommend new games consider using a separate, web-based, general purpose issue tracker of some sort, possibly with in-game visibility.
In any case: persistent historical ticket data is essential to running a game of any serious scale.
Side note that is not directly a solution:
Mediawiki has some severe problems. It'd be really nice if some mush found and started using something different-and-better. I'd recommend checking the local node.js experts to see if there are any wikis in that arena. This forum is using a node.js bb, iirc, and it seems like a great way to go.
For those still trapped on mediawiki that "just want it to work like reach" -- I didn't write any of that but iirc Ebla did long, long ago. See:
for the logs, and http://thereachmux.org/w/index.php?title=Template:RP_Logs&action=edit for on-character-page lists.
As far as direct help with MediaWiki template scripting-- no. Just no. That shit is more foul than mushcode!
@purldator Oooh, that's actually got some very nice ones. A nice spread of clearly discernible but heavily desaturated colors is exactly what I'm looking for.
Solarized (dark) is a nice idea. The light one hurts as much as most of the rest. I'm still not a big fan of their color choices, but it does work.
I'm mostly using Emacs in dark-mode with the wombat color theme, as I've probably shared before-- complete with large fonts for reducing eye-strain.
If someone produced a solarized-dark option that I could just click on and enable for this forum, I'd use that. In the absence of it, this is what I have so far.
If it seems a bit too gray, well. Better that than garish (nsfw).
@Sponge: right. The data is still available, but the user pitched a tantrum and won't click the link in the email to actually download it.
For a hypothetical future game with joint/distributed ownership, I suppose the 'committee' or whatever could have backups encrypted with asymmetric keys (standard PKI like x.509 or GPG) so that anyone possessing the private side of the pair could decrypt later. And then splitting THAT private key definition with a redunancy-recovery program so that given X pieces of the secret, Y pieces are able to read it.
This way even years after the fact, if "everyone" had the encrypted backup, it could be opened if some percentage of the trusted parties agreed that it should be done.
In practice, well. Most people are still using bare telnet with no ssl/tls, so good luck.
Hello peoples. One of the more prominent things affecting my life lately has been an increasingly frequent and crippling set of headaches. Strangely enough, bold white backgrounds cause actual physical pain and mean I need to go rest that much sooner.
So. I like gentler, low-ish contrast color-neutral light-on-dark themes for everything whenever and where-ever possible. There are a variety of ways to do this, but I'm on Chrome now and the easiest plugin for doing this programmatically on a site-by-site basis is Stylebot. There might be better ways, but this worked for me and may help others.
It's still very much a work in progress, but this has made the forum much more manageable for me:
.post-bar {
background-color: #555;
border: none;
}
a {
color: #aaf;
}
div.category-body {
background-color: #444;
color: #ddd;
}
div.category-info {
background-color: #444;
}
div.category-text p small {
color: #888;
font-size: 80%;
font-style: italic;
}
div.container-fluid {
background: inherit;
}
div.navbar-collapse.collapse.navbar-ex1-collapse {
background-color: #444;
}
div.panel-body {
background-color: #555;
}
div.post-content blockquote {
border-color: #aaa;
border-left: solid 2px;
}
div.row {
background-color: #333;
}
div.topic-body {
background-color: #333;
border-style: none;
}
h1.navbar-brand.forum-title {
color: #ddd;
border-style: none;
}
html body {
background-color: #333;
color: #ddd;
}
li.category-item {
background-color: #555;
border-left-width: 0;
}
li.category-item.unread {
background-color: #faa;
}
li.post-row {
border: none;
}
ol.breadcrumb {
background-color: #333;
}
button {
color: #ddd;
background-color: #666;
}
textarea.write {
background-color: #333;
color: #ddd;
}
div.preview.well {
background-color: #333;
}
div.composer-container {
background-color: #222;
color: #ddd;
}
i {
color: #ddd;
}
input.title.form-control {
color: #ddd;
background-color: #333;
}
button.navbar-toggle {
border: none;
}
div.navbar {
border: none;
}
.navbar-default {
background-color: #333;
}
Not done yet:
Anyone else interested or have thoughts/recommendations?
@Alzie said:
Oh, so that's why he sent out the giant email to everyone telling us his host had screwed him and the games were down. There were like 7 emails from him that day.
He's very excitable. His data is still safe, though he proved unable to download a file successfully. He tried a few times, then apparently gave up. Not my problem. If he sends me an address I'll mail him a dvd-r or something. Mostly I'm happy he's gone away. Yay for lower stress levels.
@Orange:
Thanks. I wish I could be more patient and helpful but I'm pretty burned out on everything. It hurts seeing people hit the same problems over and over again trying to launch a new game. I wanted that to be something easy to do-- and promote the whole hobby as a modern literary tradition. I ran out of energy, though. It's been very hard just trying to get back into the habit of RP, let alone staffing or managing a hosting quasi-business. Good luck, though. And thanks. Nice people make everything better.
I can only speak from my experience as staff and dealing with staff. Yes, staffers WILL spend SOME time idling. It happens. People have lives. That said, if someone is ALWAYS idle for hours at a time? There's an issue there.
This is often a bad assumption caused by overly-complex code and poor +who implementations.
Consider a typical workflow:
Given that, when only the TF session is running -- detached -- random users on the mush will see that staffer as idle. They might see them as idle for days or weeks, even if they were chatting just seconds ago.
Haunted Memories especially fell victim to this, as lots of us there understood and used this technology in exactly that fashion. End users just could not wrap their head around the concept. Awkwardly enough, a variety of staffers and players in this boat couldn't either.
So. What can we learn from this?
+who, who, +finger, page @mail look SESSIONS and all myriad commands and bits of mushcode that tie into user status info (consider places code for example) will cover all cases of this, you're an idiot.Or perhaps more gracefully:
@Luna Some places have flags for this; on Reach the WantRP flag is (was?) supposed to mean exactly that. (@Arkandel's idea iirc)
Expanding that to more places seems like a good idea.
@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.
Good luck. It takes a great deal of effort, dedication, and skill in a wide range of different things-- organizing people, storytelling, software engineering, etc.
I'm... still kinda burned out on everything, so I probably can't help much on the tutorial front. My best advise is: try things and see what happens. Don't be afraid to experiment, and be damn sure you are self-motivated and confident enough to read documentation, even when it seems inapplicable or partially outdated.
People on my fork (TheReach, DarkSpires, Wildcard, most mechanipus people by default, etc.) will find a very relevant mux patch:
https://github.com/lashtear/tinymux/commit/6b19bbb955921265c7f79195f870f466f37c95b1
Which lets us do the same thing on Muxen instead of RHost, if that's your flavor of choice. (Brazil's fork still has that disabled for reasons of taste, I think).
This is definitely my recommended way of applying patches to mush code: @create new object, @parent it to the old one, override attributes as needed and put the child in the master room (or zone master room, or whatever). Then further updates to the upstream-controlled object can proceed without directly damaging local house-customizations.
Now if only we could find a good way to explain what this all means to the typical mush user...
@Misadventure: I could use one. And we should totally hang out when you get back down here!
I think it was some lingering sense of basic decency. My bad. When he started posting all over unrelated G+ posts (okay, not important stuff, but pictures of cats and things for family that I had semi-public), I think I can safely say that he's not worried about these sorts of boundaries anymore.
I've given him a URI for downloading the tarball. What he does with it is anyone's guess.
This was willm (redacted again at the request of forum staff), owner of a starwars game, gundam seed, and zero. I suspect people could do business with him just fine as long as clear contracts, expectations, and boundaries are set and never crossed. I sure as hell don't want him on any of my systems though.
Again, for those who are vaguely worried about all this: his data is fine and safe, and he has full access to it. He's just been an utter jackass.
http://mudstats.com/World/StarWarsNewJediOrder
http://mudstats.com/World/StarWarsLegacy(NewJediOrder) (same game, duplicate entry)
http://mudstats.com/World/TITAN2100
http://mudstats.com/World/GundamMUSH
edit: removed name at request of staff