Posts made by Glitch

@Rook I don't know if you've heard of this system, but I think the bill fits rather closely here: The Strange

Cypher system is pretty awesome (also the basis of Numenera).

@Coin The answer is: that is not the RP they want to focus on.

Your examples are hyperbolic, but I can see where people just want to bump their gnosis, or make the job rolls for a token or just burn that XP on a new pact and cover.

Whether you agree with that or not, they might prefer to let the pact thing happen in the background so they can instead play with other demons or a particular cover. A mage who doesn't want to go on a spiritual journey PrP and would rather just offscreen it in order to keep playing with their cabal is reasonable to me.

People come to a game for different reasons and one of TR's strengths was allowing you to focus on the content that you found desirable. I think RP'ing out the things you describe would be more fun, but is it really such a hard thing to believe that people don't look for the same thing in their RP?

The only time I've had notifications were when I was @mentioned or if I started the topic. I'm not sure there's anyway to turn either of those off, but are you talking about when you ignore a category?

@Thenomain I think it needs to be a specified category, instead of just page. Like:

notcategory=UncategorizedPages

@Thenomain

Try:

notcategory={page}

?

ETA: It was magic parsing out my {page}

What the .... okay, something is doing some strange shit to my text. I think it's the templating system for nodebb.

notcategory=[page]

But instead of brackets, curly braces.

@Misadventure The one I suggested is made by him.

There's also MUCon.

@HelloRaptor Your distress is a basic qol item for me, but since you're not the only one asking for it, I'll see what I can do.

@Thenomain said:

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.

You are being pedantic, even if it's in service to trying to make a point.

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.

There's really not. Accounting for every fringe case with a variety of philosophies is ten steps too far in over-analyzing. Besides, @Eerie and @Coin continue to stress that no rule is "concrete" and they'll "re-evaluate" decisions after some given time-frame, so all of this conjecture about the possibility of some fringe cases is overmuch.

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.

The impression I'm getting is that these big requests for discussion go up, but they've already hunkered down. They certainly don't need anyone's approval, but it's the impression I'm left with and I think there's too much cart before the horse decision-making in the name of "preparation".

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

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

@Eerie said:

So @Coin had proposed keeping a waiting list of 5 people and filling spots from that as they open up. We could do it so that, when the queue is empty and it’s time to refresh the list, Slot 1 goes to the person who’s been waiting longest, straight up. Slot 2 is a random pull among the 25% of the people who’ve been waiting longest, 3 the 50% of the people who’ve waited longest, 4/75% and the last one among the entire pool. I think this still preserves the chance for new people to get involved, but also shows deference to the people who’ve been there the longest, as people the top 25% are in every draw and the newcomers only one. Then if we email or @mail or whatever you and don’t respond within X days, we’ll redraw I suppose.

This is like a solution in search of a problem. Who is unsatisfied with a first come, first served queue for entry into a sphere? Other policies are going to make this more or less appealing, such as giving priority to people with non-supers, etc, but it seems like an overly complex response to something that has yet to be proven an issue.

@Sunny It is legal for your own children in any state. Only thing that matters is degree: time.com

@Arkandel said:

Two potential solutions:

1. Allow just one (supernatural? overall?) alt. This way at least you are discouraging people who intend to play in your game at all from parking characters in its spheres.

I don't have any problem with this. If you want a slot restricted super, it's your only super.

2. Define then hardcode an activity requirement. It's not so hard, it's just that everyone will define it in a way that makes sense for them, so you'll need to pick one. My personal pitch is something that goes kinda like this (more refinement is needed but just to get an idea):

I think this is an awful idea. Coded checking of activity is never going to do what it needs to do because there will never be a point that its benefits outweigh its annoyances and contrivances.

A sphere leader will have an idea of how much they, and their sphere staffers, can handle based on current activity by however many people they have in the sphere. Staff resources are often unevenly distributed across players due to the general level of attention some need versus others and there is no way to quantify that through automated code.

First come, first served. Easily tracked and understandably fair to most people. As long as the "start" point for waiting is the same, there shouldn't be an issue.

@Creepy said:

You know what I always needed help with? Finding rooms. I know there are search commands and whatnot but sometimes the help files read like a foreign language as I have no coding background.

For example, if I want a list of all room dbrefs, what would I type, exactly?

@search type=room

The rest of these mostly want to find an object of a particular type and then do some check with it. So here are your <thing> + <do> searches:

  EOBJECT   - A combination of TYPE=OBJECT and EVAL=<restriction>.
  ETHING    - An alias for OBJECTS.
  EROOM     - A combination of TYPE=ROOM and EVAL=<restriction>.
  EEXIT     - A combination of TYPE=EXIT and EVAL=<restriction>.
  EPLAYER   - A combination of TYPE=PLAYER and EVAL=<restriction>.
  PARENT    - Restricts to the parent designated by <restriction>.
  ZONE      - Restricts to the zone designated by <restriction>.

If I want a list of all rooms with a certain parent, such as an outdoor parent, what would I type?
To get the outdoor parent's dbref (or find any object with a given name)

@find Outdoor Parent

Then, if the Outdoor Parent's dbref is #25, for example:

@search parent=#25

How about a search for any rooms or exits without some attribute set? Say, desc or odrop? Then I could plow through to see what areas I haven't finished yet.

We'll use eroom and eexit for these:

@search eroom=not(get(##/desc))
@search eexit=not(get(##/odrop))

How can I use basic commands, such as @desc here, without being in the room? @desc dbref#=Text here?

You got it.

ETA: This may have been better as part of a more thorough tutorial. I have a different one lined up right now (part of which @Cobaltasaurus has now kindly already covered for me), but I'll keep this one in mind too.

I liked Silas too!

The Forums went down for a bit. A rogue plugin was at fault. It is entirely @Coin's fault. May be some residual effects with logging in, but should be fine shortly.

@Arkandel I'm actually going to disagree that this always has to be the case. If they want to limit play within their grid to certain areas to encourage that resource competition, I could see it, but just starting small and adding on is not great in my opinion. I played on a game where you could just basically make up an area and history of somewhere you were from and it got tacked on to the game. It ended up with a haphazard mess.

I think having a good sense of location is important, so having the broad strokes already present is my personal ideal. You can always fill in detail later.

FFIX. <.<