Posts made by Thenomain

@Glitch said:

@Thenomain It shouldn't be a chance. Another reason the lottery is meh.

There's always a chance. The chance that you apply "in time", the chance that you know that it's coming, the chance that your @mail gets through before someone else's. I am in no way trying to be pedantic about the word "chance" here, but to stress what @Coin is also saying: The goal is to minimize shittiness.

I'd say to ignore the fringe cases, but there are so many of them that a different problem-solving philosophy needs to take place, even if just to determine which cases are actually fringe.

I'm currently still leaning toward: 1 or 2 week notice, 2 days application, lotto. I personally want people with no supers to get first pick in a supers sphere, but I have been convinced that this is not a de-facto good thing.

In HM's Changeling, it was largely: Open, accept a few apps, close. That this didn't cause too much headache informs me that we're over-analyzing the problem, but IMO it's a problem worth over-analyzing, in case shaking the tree makes something interesting fall out of it.

@Arkandel said:

The answer seems simple: If that person wants priority for the new sphere they can drop their first alt. It's not a dick move, any more than making someone else wait with no alts is.

Telling someone to drop what they are doing for a chance to do something else seems, yeah, like a dick move.

Players who aren't engaged with a super sphere aren't necessarily not doing anything, either, but the suggestion doesn't affect them at all. Keep in mind the suggestion doesn't affect those without a major template.

@Glitch said:

@Thenomain Then they can be interesting and engaging in their new sphere. It's not punishment. They're getting the character they really wanted.

Maybe I misspoke. If someone makes a Vampire because Geist*[1]* isn't open yet, then Geist comes along, they're at a disadvantage because they're already playing a Vampire. Making them drop the Vampire just for a better chance at playing their preferred sphere seems like kind of a dick move.

The same would be true for a sphere that is closed because it's closed, not because it isn't around yet.

That is, someone with a supernatural slot, someone who is engaged and helping the game but would rather take a different supernatural slot, would be at a disadvantage. This is something to consider while fussing around with ideas.

[1] At least, not until the coder gets the Geist v2 book.

@Sponge thinks of the children.

@silentsophia said,

I do like the idea of giving priority to someone who doesn't have their 1 supernatural alt

I'm going to echo something that came up in conversation about this:

What if someone joined a difference sphere waiting for their preferred sphere to open up? They are being active and engaging the game, so why punish them when the time comes?

I also have the desire to reward people who aren't engaged at all, but is it worth alienating those who are involved? From this perspective, my personal answer is "no, it's not".

Code Object Data Parent

Most of my code objects end up being filled with attributes. I mean, filled. Here's an idea if what I mean:

Thenomain types -=> think attrcnt( #209 )
64

Sixty-four attributes to do what? This is Wiki News and Help <wnh>, and all it does is looks at a database and pulls a file. The nWoD 2 data dictionary has 595 attributes for Core and Demon. I mean it. I like using attributes.

What I don't like is losing track of what's where. Here's an old, old trick that has been used quite a lot:

@desc object=lattr( %! )

Well that's good, but what about sorting them so that all the &cmd attributes are together? Okay, what if you use &cmd and &c? How about sorting them with headers? Why not do this, or that, ot this other, or, or, or ...

:::::::::::::::::::::::::.  WoD Health System <whs>  .::::::::::::::::::::::::::

Desc is null for this code object.

..:  Data  :....................................................................
d.data-dictionary          d.health-types             d.stat-funcs              
..:  Commands  :................................................................
c.hurt                                   c.heal                                 
..:  Functions  :...............................................................
f.conv-type                f.do-some-dmg              f.healhurt-workhorse      
f.min-dmg                  f.do-some-dmg.push         f.healhurt-errorcheck     
f.reverse-max-health       f.do-some-dmg.wrap                                   
..:  Displays  :................................................................
display.health-bar                       display.health-detail                  
display.health-descr                     display.current-health-descr           
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::.  17 attributes  .::

This is the result of the Code Object Data Parent. Muxify. Copy. Paste. @parent. Done.

If I had a "must have for Mux" code, then this is it, an informational blob to help people get up to speed on the code around them. It's not fit for everything; don't use it on a gigantic code system like Anomaly Jobs, but for pretty much every other project I find it almost indispensable.

Request

I'm not the biggest fan of Anomaly Jobs, but I'm just going to have to be in the minority until I can come up with a suitable replacement. Some games use it so heavily that adding to it might feel like a trip down to the local doctor's for your weekly leeching.

These games have come up with a way to sort out player or even other staffer requests, put them in the right bucket, assign them to the right +jgroup, and let the staff figure out what to do with them next.

The Jobs Request System is essentially a complete rewrite of The Reach's +req, in such a way that it should be trivial to add to.

Drop it into Muxify and viola.

My Github grows and I guess I wanted a place to say: This is here, please use it, I think it's pretty awesome.

None of this is what I would consider the absolute must have code of a Mux: Bboard, Mushcron, Anomaly Jobs, @Whence, and Events. If you're not using these five systems, you should.

I have a place for most of my stuff. These systems are small and most of them are not copy/paste and call it done, tho I do get there eventually.

And now, on with the crowing.

@Miss-Demeanor said:

@Thenomain Yes, it does include them as well since even they have nothing they can offer me

...

@tragedyjones
When I get my hands on a copy of the Idagram Chronicles (Idiot Chronicles? I seriously cannot remember any Werewolf pseudo-language nonsense), I will start the long process of converting it to code.

The sooner the better, if anyone wants to help in that regard.

Other concepts in deliberation:

• Announce one week before opening the sphere, allow apps for 2 days, lotto.
• Outright 'first come, first served'. The cgen system can have you done and waiting for that fateful day without staff intervention, so you just hit the "Accept Me!" when staff is ready.

My current opinion about becomings is that they have to wait the same as anyone else. I personally lament that a relatively simple IC action (turning someone into a vampire) has to wait for an OOC condition (staff feeling they can handle it), but this is a natural consequence of sphere caps.

I've been campaigning for these two riders, as well (which I mention because I think we're agreeing at the moment.) First is that deaths through role-play get to re-app immediately, as a thank-you for being cool about playing to the bitter end. The second is that unfreezing also requires space in the sphere. No special treatment, just like how "becoming" wouldn't, and "character death" would.

Exceptions are always allowed, and that's one of the (many) things I like about working with this group. If the exception seems reasonable, such as group-apps stretching the cap and vacation-flags not getting you frozen, they will probably be okay. If we have to spell this out, I will be disappointed.

I'm of two minds of activity monitors. One is: No no no no no no no no no no no no!

The other is: It can be done. Haunted Memories did it, but HM's application had nothing to do with estimating the activity of the sphere and the weight of that on staff. (They instead counted jobs, which was just as bad.) What HM did was use it to force you out and about more often. "Force" was, IMO, the wrong way to do it, but I can't say that it didn't work. They also kept the trains running on time.

Activity monitors can provide useful information, but the idea is a sledge-hammer where a social contract is needed.

@Miss-Demeanor said:

Fuck people that want to tell me how to raise/discipline my kids.

That rules out child psychiatrists of all levels, as well as the chance that normal people who didn't spend tens of thousands of dollars in specialty training and education from coming up with anything worth listening to.

Like: Don't leave your kid in the middle of the running track or they might get hurt.

@Ganymede,

I'm afraid that I'm about to go alarmingly off the path and into my patented Thenothoughts, wherein what I'm thinking may not coincide to reality on a 1:1 basis. I'll try not to, but bare with me.

Thinking about analogies, I see a waiting list more like seating at a busy restaurant. You get your name put down, but you have a vague idea of who's there but not everyone waiting is still waiting, and instead of seeing the lobby you only see the list.

Part of the time-consuming nature of reservation lists is verifying it, and to me, a report that is not accurate is not a very good report.

@Ganymede said:

@Coin

I really hate the NBA and NHL drafts. I prefer the NFL draft.

Please explain for those of us Americans who follow sports less religiously than the release schedule of Korra? Thanks.

@Coin said:

@Thenomain, what if several people have been waiting for two weeks? I prefer sticking to the same method. Of course, if no one has been waiting and a slot opens up, then it's definitely first-come, first-serve.

First on the list. The thought I'm having about this is that there may be a small enough time-frame where a lotto system is the less reasonable option.

To counter my own argument: Even two weeks waiting for a character slot is a long time.

Alternatively, if nobody has been waiting for over a month, it reverts to first-come first-served instead of lotto.

Issue found and fixed. If you used this code already, copy the following to your newshelp object:

&CMD.WIKI.NEWSHELP Wiki News and Help <wnh>=$^(\+?news|\+help)( ([- !(),./;?_A-Za-z0-9]+))?$:@break eq( strlen( %3 ), 0 )={ @pemit %#=u( display.index, trim( %1, l, + ))}; think strcat( qn:%b, setr( n, v( namespace.[trim( %1, l, + )] )), %r, q1:%b, setr( 1, u( f.clean.query, %qn, edit( %3, %b, _ ))), %r, qt:%b, setr( t, edit( first( %q1, ^ ), _, %b )), %r, qm:%b, setr( m, elements( %q1, 2, ^ )), %r, qc:%b, setr( c, elements( %q1, 3, ^ )), %r, wdivider(), %r, ); @assert t( %q1 )={ @pemit %#=u( .msg, lcstr( %1 ), Unknown page. ) }; @pemit %#=[u( .wheader, cat( capstr( lcstr( trim( %1, l, + ))), for %qt ))]%r; @pemit %#=s( iter( trim( translate( s( %qc ), p ), b, lit( %r )), [setq( z, regmatchi( %i0, (.)(.*), z a b ))][setq( b, s( %qb ))][case( %qa, :, translate( u( wiki.block-quote, %qb ), p ), %b, translate( u( wiki.block-quote, trim( %qb )), p ), %;, translate( u( wiki.definition-block, %qb ), p ), *, translate( u( wiki.bullet-point, %qb ), p ), -, if( strmatch( %i0, ---- ), u( wiki.horizontal-rule ), %i0 ), =, if( regmatch( %i0, (=+)(.*?)(=+), z y x w ), strcat( translate( udefault( wiki.h[strlen( %qy )], u( wiki.h5, trim( %qx )), trim( %qx )), p ), %xn )), ', if( regmatch( %i0, (''+)(.*?)(\\1)(.*), z y x w v ), switch( strlen( %qy ), <3, [translate( u( wiki.italics, %qx ), p )]%xn%qv, <5, [translate( u( wiki.bold, %qx ), p )]%xn%qv, <6, [translate( u( wiki.bold-italics, %qx ), p )]%xn%qv, %i0 ), %i0 ), , %%b, %i0 )]%%xn, lit( %r ), lit( %r ))); @pemit %#={%r[u( .wfooter, u( display.footer, %qm ))]}; 

Sorry for the oversight.

A friend of mine is a very good father, yet his tween-aged child still took an entire bottle of medication.

I think the fine we pay is "life is what it is; sometimes you act all entitled and luck out, sometimes you try really hard and still get the bad luck thrust upon you".

That any of us survive until we're old enough to risk our own damn lives is what astounds me.

The only multiplayer games that I know that I have (and know how to play multiplayer) are Portal 2 and Borderlands 2/Borderlands Pre-Sequel.

I think it's a stretch to say that I know how to multiplayer Borderlands well, though.