Posts made by Ashen-Shugar

@skew said in Mux Logger Objects:

@Thenomain Okay, so, again, I do not have any pose logger code. I have +repose, and while that could be tweaked to be a logger (and frankly I'm intending to do so), in it's present state it is not.

@Derp On Fate's Harvest, we have code that essentially allows you, the player, to @create an object and then use the Pose Logger command to turn it into a Pose Logger. You turn it on, it listens to the room, when you're done, you turn it off, then it can output the code in WikiMedia template format.

For a non-penn game, make sure that the logger re-uses the same attribute names, otherwise over a period of time you can get some serious db bloat from hashed attribute names.

All mushes (except PennMUSH) uses hash entries for attributes, so its something to keep in mind.

Though MUX and Rhost have a @dbclean that will clean out unused attributes which can greatly save db space and memory use.

Old Social games that I keep up since they have history:

Rhostshyl (Based on the Silverglass series)- rhostmush.com 4201 (founded 1989)
The Underground (A Labyrinth based mush) - rhostmush.com 7000 (founded 1996)

And for those who want contact with RhostMUSH itself:
RhostMUSH Development Hangout - iweb.localecho.net 4201

@thenomain said in Mux Logger Objects:

Yes.

Don't you mean maybe to the 99.9999999999999999999999999% of yes?

@ixokai said in Mux Logger Objects:

@ashen-shugar No that wouldn't work at all. I use @include extensively for code-reuse purposes.

Ie, like:

&I.FIND-LOGGER lp=@assert setr(logger,locate(...))
&cmd.log-view lp=$+log/view *:@include me/I.FIND-LOGGER;@pemit %#=something with %q<logger>
&cmd.log-undo lp=$+log/undo =:@include me/I.FIND-LOGGER;

'trigger()' can't halt the queue of the calling command like @include can

Yea, I thought trigger() would work in-line but you're right, it works just like @trigger does.

Makes you wonder wtf it's even useful for.

Sorry about that. So yea, with MUX you're pretty much SOL without recoding it all to be in-line

@ixokai said in Mux Logger Objects:

Mine actually doesn't work on MUX (the Rhost version heavily uses @include), though I'm going to make it work for HorrorMU soon. When I do I'll post an update to my logger thread and ping you to see if you haven't found something you like yet.

Ixokai, MUX has trigger() so hypothetically you could recode to use trigger() instead of @include and it should, kinda sorta, work the same with minimal impact.

@admiral said in Random Oddness or 'Is This Normal?':

Apnea? I know people with that and I breathe just fine when I sleep. My breathing is, as a certain politician might say, 'The best. The biggest. Yuge. Stable genius breathing.'

I am gonna look into that though, I was unaware that might be a potential thing.

Part of the sleep study is a full neurological and EKG test throughout the sleep period. They put a crap-ton of wires on you and on your head to study brain-waves as well, so even if it's not apnea, they likely will find something if it's neurological in nature.

Regardless, the waking up every night needs to be resolved, as it interrupts your alpha waves in sleep and that's no bueno.

Seriously sounds like a form of Sleep Apnea.

Definitely see a doctor and see if you need to get a sleep study done.

@arkandel

I picked Ashen-Shugar because back in the day with player name character limits having the name 'That Asshole Over There that I hate' just was too long.

So I settled...

@faraday said in A new platform?:

@grapenut I've already seen several people having serious issues playing via websockets because of browser or firewall issues, so it is absolutely not as reliable as telnet even in a low-impact environment like a MUSH.

Anyway, I never said it was impossible to build a web portal in PennMUSH, I said it was not the soundest technical approach and false to equate it with a robust and dedicated JSON API. But best of luck to you regardless.

Not to be a parade rainer, but just like Python, Ruby, and Perl have modules for full, robust, and dedicated JSON API's, so does C.

It's just a matter of including the library class and a quick modify to use it as a built in function handler. If I could get my lazy arse interested I could probably do it in a few hours, but meh. Not on my high list of important tasks in this point of time.

The thing though is it's very possible to do it.

As for importing and exporting existing softcode in JSON?

Assume we have json_encode() and json_decode() on a Rhost.

@wipe me/json;@pipe/on json;+pretty FS3 command here;@pipe/off;think [json_encode(v(json),args-go-here)]

And do that via an external liburl call and you have a full web based JSON handler for the arguments. Since all the output of the command is stored in an attribute, any and all transformation can be done on the fly, anyway you want, before, after, or during json transformation.

I honestly don't see the difficulty? Am I missing something?

How about setting up a full oWoD game where every player in the oWoD game is an NPC, a full fledged world fully running fully grided oWoD game.

Players who connect are NOT part of the WoD game.

Instead, they play characters from anything BUT a WoD game.

Pokemon? Good to go.
D&D? Also great to have you.
Matrix? Sure, why not.
Shadowrun? Welcome aboard!
Amber? We welcome those of the pattern!

Essentially, the entire purpose for players is to go on and absolutely DESTROY the world in every possible way for the WoD NPC's.

Wipe them out, make them cry, ruin their tea breaks, whatever you want to do.

Ergo, a crackfic of a MUSH.

That's a WoD game I would love to play

@faraday said in A new platform?:

@thatguythere said in A new platform?:

@faraday
I fail to see how those being split into two different windows would be better? All that does is make me flip between windows to see things.

Then there's nothing I can say to convince you. Continue enjoying the old systems.

This is one of the big problems. With the avent of graphical front ends and all the ooo shiney out there, people have in their heads how they want things.

People hate Penn's @mail system.
People love Penn's @mail system.
People hate MUX/TM3's @mail system.
People love MUX/TM3's @mail system.
People love the very old Brandy +mail system.
People hate the very old Brandy +mail system.

I could go on, and include Thunderbird, GMail, Outlook, Mutt, Pine, Elm, Mailx/Nail, and any number of profesional grade mail systems out there, as well as the hundreds of clients.

And you'll always get a large number of people who hate and love them.

So the correct answer is giving tools for people to be able to make their own.

Then of course, you get people bitching that they don't have the skill to make it.

Then you suggest they get someone else to make it.

Then they say it's too expensive, or the other person isn't doing it the way they want.

End of the day, people bitch for bitching's sake. Likely they will never be happy. So here's an idea. STOP TRYING TO MAKE THEM HAPPY.

Give them everything they need to find their own happiness, if they can't find it, their problem, not ours. Period.

With Rhost, it had a very unique but powerful mail system.

People disliked it as it wasn't compatible with MUX. We made it so.
People disliked it as it wasn't compatible with Penn. We made it so.
People disliked it as it wasn't compatible with Brandy +mail. We made it so.
People disliked it as it couldn't be used with other clients. We made it so.

We even made it so you can download your mail and use it in a client of your choice from an MBOX standard format.

There's going to be a point where you have to stop say 'you know, I did all I can' and people are going to have to meet you half way.

Some learning of new things is expected. So how about we lay that expectation on others and not trying to dumb it down so much it becomes repulsive to everyone else?

@golgoth said in A new platform?:

So, like @faraday mentions, AresMUSH (and Evennia), while they don't have all the answers yet, have a lot of them. Did you know that it is relatively easy to implement an @mail system where all of this @mail dude=<title>/<Stuff> or whatever is hidden behind a simple popup where you fill in the fields and vwoosh, @mail sent?

Same with the +bb system. Make it clickable. Pueblo Enhancements have been around for ages. Speaking of the +bb system. It's just a blog or forum post. Why not export/link all of that to an actual forum or blog? Can be done, has been done.

Shit, I don't know Ruby / Ruby on Rails and now I'm sitting here thinking how hard it might be to implement all of this stuff for AresMUSH.

--- ANYWAY, what I'm saying is that: Let's start putting brains together and start collaborating on implementing methods to abstract all of the scary code and put in its place easy to use interfaces that are more or less intuitive? I'm down.

Edit: I should read the entire thread instead of jumping in at like 25.

With some work you can do this today with AresMUSH, Evennia, and RhostMUSH through the use of extensible API or language backends.

The only thing you, as the end user admin, will have to do is write the web interface to hook into those api's.

A fully featured graphical front-end is just as hard as a fully-featured chargen or skill system is.

It differs by game to game, by player by player, and by interest to interest.

So what we, as game developers tend to do, is give you the tools so you can fairly easily design it how you want yourselves.

A fully turnkey 'run with this config and I have everything' like a MMPORG isn't going to work, especially since we don't have teams of 20-40 people building the backend world for years to make it work, nor are we paid for it so don't have the inclination or time to dedicate fully to it.

Meet us half way

At the end of my post on what to do when your mush is attacked is several dozen links on how to code, create, and start a mush based on the flavor you want to use. Including MUSH (Penn, Rhost, TM3, MUX2), AresMUSH, and Evennia.

http://www.musoapbox.net/topic/1947/what-to-do-when-your-mush-is-attacked/9

@thenomain said in Dies Irae: Paid Positions for Coder:

@ashen-shugar said in Dies Irae: Paid Positions for Coder:

@ominous said in Dies Irae: Paid Positions for Coder:

@thenomain The stock market is not hard to game-ify. Many board games have done it. It's just a really big auction house. People are selling X at Y price and other people are buying A at B price. Once these people meet and agree to Z price, that sets the new value of the stock. That is a very simplified version, but a MU* only needs a simplified version.

And for all that's holy, try to code it so that a group of people can't nerf the system by cornering the market in attempts to sell 'a common rock' for like 10k a pop?

Are you telling me what Enron did was wrong? Because it was legal, and that’s all that was important.

@ominous said in Dies Irae: Paid Positions for Coder:

@thenomain The stock market is not hard to game-ify. Many board games have done it. It's just a really big auction house. People are selling X at Y price and other people are buying A at B price. Once these people meet and agree to Z price, that sets the new value of the stock. That is a very simplified version, but a MU* only needs a simplified version.

And for all that's holy, try to code it so that a group of people can't nerf the system by cornering the market in attempts to sell 'a common rock' for like 10k a pop?

I've been on MMPORGS that had markets that didn't protect against this which absolutely ruined the game because the people who played the system essentially owned the game.

@zombiegenesis

I remember an Armageddon MUSH I played on years and years ago with Ambrosia. If this is the same environment, I can talk to the original owner and see if they wouldn't mind some of that code for you to use if you'd be interested.

The DB for it is still around.

Add some clients for Linux, even command line ones for power-users who like that choice (ergo tinyfugue).

You may also want to cover colors that mushes tend to use.

Whlie some of them stick to the basic 16 colors, some do use (and ask for you to be able to handle) 256 colors.

Some of the older clients never got around to adding support for 256 (XTERM) colors.

I'd also cover the fact that just like facebook, twitter, and internet blogs, on mushes there will likely be an international presence with people from all around the world, so to keep that in mind when communicating.

A lot of the poo-fling fests I've found on mushes tended to start by miscommunication or a lack of background on something that may have initially been considered a joke or was said with understanding that only a local national (to the one talking) would be able to comprehend.

I'd also ask for this to be sticky. Great document.

@admiral said in My first cellphone:

@ganymede said in My first cellphone:

iPhone 7 explodes

Fixed that for you.

Fixed that better...

Wait for the Samsung S9 to become more widespread then get the Samsung S8.

It's a nice phone, fully waterproof, and has the headphone jack and accepts a microsd card for expansion.

You will want a case with it however as both front and back is glass, so you want the extra protection.

@kay said in Let's talk about TS.:

@ganymede said in Let's talk about TS.:

@theonceler

Jake the One-Eyed Trouser Snake.
The Flesh Spear of Destiny.
Russell the Milk-Spitting Muscle.
Misplaced Baby Fist.
Squirtle.

I can keep going, I guess.

I feel you should! Extra points if it could also be the name for a D&D weapon or artifact.

+7 Barbed Phallicer of Lord Fisto

You could even sing it to music