Topics created by BlackDahlia

I can't do it this year. I signed up for it and then remembered i won't be able to do much writing, if any, for four days which would put me woefully behind. So am going to need to hold off until next year. Makes me sad as I think I had a pretty good idea, but it'll keep for next time.

---> previous builder. I am happy to vouch that the other staffers on this game have been super pleasant to deal with. If I had had the time and energy I'd still be descing. Also the exits get all the messages automatically set up, so no need to dig into @succ etc unless you wanna.

What is this goo-ey you speak of?

@blackdahlia Did it anyways...

https://github.com/skewskewskew/MUSHCode/blob/master/+watch

Thanks to Annapurna/Rainbow!

@skew said in Quiet Room:

If you're using TinyMUX (which I know you are), there's no way to squelch the connect/disconnect (and the leave/arrive?) messages unless you have @Chime's fork. Which a certain cephalopod has just recently informed me has had a very minor update to handle some SSL something something something.

MUX 2.12 seems to already have arrive/leave handled by blind (on target player or location).

So to add this functionality to connect/disconnect, you need to edit netcommon.cpp in three locations.

One to handle connect/reconnect
One to handle disconnect
One to handle partial disconnect

You look for this section:

if ( loc != NOTHING && !( Hidden(player) && Can_Hide(player)))

And modify it to this:

if ( loc != NOTHING && !( Hidden(player) && Can_Hide(player)) && !(Blind(loc) || Blind(player)))

You should then be good to go.

I didn't see it here, but automated/self-service xp spending is good stuff.

Happy Little Update: We need a werewolf lead, we have an admin/st. We also need a mortal TL, and an admin/ST. Eventually we will need a mage staffer and an Admin/ST. Are you interested in any of these things? Speak with Death over on our discord.

We are also nearly finished with Cgen and probably going to get some alpha testing done within the next week.

Descs are nearly done on the grid, we are working on a map.

I've made a list of things people want from the post over here and we're also beginning to start on those things.

@skew

It was @Chime who created it. I broke it and fixed it a few times.

Unlike multi page, which I broke once and never fixed.

She still reminds me sometimes.

In the spirit of 'getting #@#$! done, I've decided to make little posts here to let everyone know that we're still very much alive and moving ever closer to opening.

I just cleared staff to start using the wiki, the theme is finally stable enough for content (until I'm done with my extensions later!). Things are starting to move over. I predict we'll be ready for our first small beta really soon, so keep an eye out! I'll also post a link to the Wiki as soon as there's something to look at.

Feel free to join us on Discord for more frequent updates, ask questions, plot, plan and hang out! https://discord.gg/F7ZZT8p

It's the mysql.h, probably.

The 'do the secure installation' step that is now recommended does something that changes the standard permissions that tinymux expects when it comes time to configure it.

I know I managed to fix it once. I do not for the life of me remember how, but it wasn't any of the things recommended on the thread to fix the mysql.h issue, because none of those worked for me at all.

It may have been some kind of worst practice hail mary I yanked out of my ass, so I don't recall, unfortunately, what it was. It was a permissions issue, that much I do remember. Whether it involved changing the permissions on the directory where the file was housed or the file itself, and what I ended up changing them to, unfortunately, I do not remember. 😕

I know that isn't much help, but maybe with that information some of the people who actually know what they're doing can help narrow it down.

ETA: For the tech people: If this is a digitalocean install, mysql.h is there, and it is installed. The permissions are just locked down in such a way that tinymux can't access it to use it to do anything -- which may be only after the 'mysql_secure_installation' step, but even if you did this after setting up tinymux you'd run into the same issue later -- so tinymux acts like it isn't there because it can't see or use it.

ETA2: Mediawiki 1.30.0, the current version, is fussy and different in some new and interesting ways. Be advised if you're using code from an earlier iteration or planning to import. Apparently a lot of stuff deprecated between versions 29 and 30 and you will probably need to tweak your stuff. Depending on how much you fuss with things, this may be no big deal.

(I know I found the stuff they're starting to add in so egregiously annoying I gave up on using Vector entirely and started building a new skin during the time I can't really do anything else productive (while this comp is on its last teetering legs and we settle in for the long wait for its replacement).)

I'll second my experience that Mudconnector is dodgy at best. I'm not sure of the algorithm that the site uses but the cached activity reports for games seems to be highly delayed. But its still possible to find some interesting places if you have the patience for sorting through things.