Posts made by Thenomain

I have less to say about this but to add some comments, and shorten it. My additions in bold.

@Corruption said:

1. Pick Setting, Theme (Write the Newsfiles)

2. Decide what Spheres will be allowed. (1a. Pick which WoD.)

3. Find staffers for the appropriate Spheres.

This one is vaguely contentious. Find experts. Find people who want to buy into this game. Sphere staff have a horrible tendency to form their own Kingdoms. Do not let them. Tell them they can quit if they don't want to share their position.

Do not hesitate to fire a staffer who is not going along with the game's theme or culture. To leave this person in power is to tacitly approve their actions and authority.

4. Hire Coder. Give coder all needed "We need this common code, we need this customized code."

Be careful about asking a coder if it's okay that their code gets shared. Tell them that the code is for the game, regardless what happens later, even if you won't share it. Staffers are contractors; build and code staff doubly so.

5. Get everyone to write a substantial amount of News and help files. Make sure everyone understands the Theme and Setting. Get people planning initial plots. Make sure everyone's down with the staff structure and the basic rules of operation that will be used. Buildwizard(s) Can begin writing grid and planning layout.

Builders are just as important to your RP staffers as setting is important to your theme. Some of us coders don't get along with the theme, but a coder with buy-in is a dedicated coder.

6. Aquire site. Three people need the PW for this: Coder, Sitewiz, Owner. No one else ever will need access.

The lead coder does not, at any time, need access to the shell. Only give access to the shell to people who need to set up things that can only be set up at that level, and whom you trust implicitly. Do not give anyone else access to your shell.

If you trust your lead coder that much then sure, but do not lump them in this list. Only one person needs access: You. (Your site host already has access.)

7. Open game. Finalize code, finalize wiki.

Nothing else needs said here. Do not give wizbits to anyone who doesn't need them. Not because of paranoia, but because of what can be broken.

Don't trust just anyone to do shortcuts available to wizbits.

8. Once the +news. +help, Grid, code, Wiki and all that jazz is assembled, test the fuck out of everything.

This should be before 6.

9. Ads go up. You are open. Wait a week or two before introducing heavy plots. Otherwise, go, go, go!

Hope that helps.

Fung Shui is being redone.

Just saying.

If you're going to put that annoying first letter ansi thing for staff names, put it on the entire name. Best thing I've seen, and I thank Reno for it.

Funny. In DA:O, the key points always end the same and make no lasting effect on the game, but still manage to reflect your decisions.

Still one of the best RPGs I've ever played.

@Alzie said:

Well, that's our other difference. You code in pre-requisites, I don't. You think the system should handle that, I think the staffers should. I imagine that we do many small things different in this way.

Yeah, I looked at your system and then looked again for a, you know, a system. Anyone can offer a list of traits. You made character sheets into an inventory list!

I made them into art.

https://github.com/thenomain/GMCCG/tree/master/1 - Data Dictionary/Demon

Still working out how to do Interlocks and Ciphers, which are Mux unfriendly. No suggestions needed, just time and caution.

Cobs, this is one of the cooler additions to the system:

&class.demonic_form.? DD=flag

Class for the entire stat category may be set this way, with exceptions made per stat. The code overhead should be very slight. I haven't finished coding in what the 'flag' stat class means, but it will mean that it doesn't need or even get a value. Conditions, Keys, etc.

@alzie, Part of the problem is that each new WoD game seems to introduce a new stat concept. Once I get that concept coded, it's good for staffers to add the stats. I often have to explain how to make a prerequisite, which doesn't help matters either. Some are simple, others need to know not only what the stat currently is but what it's being set to. This means teaching some staffers some code, or eventually creating a token system for it.

I am wildly unhappy how I'm doing list stats such as Gifts, too.

I can't code ALL GMC all at once. Demon is almost done. Maybe @Cobaltasaurus Will help me out. Wink wink.

I'm on iOS 8 and neither Safari nor Chrome seem to be working out for me, for various reasons of either the submit code not firing or something's the edit window being too small to see. So list here what works and what mobile platform. Thanks!

DA:I is a simplified Skyrim with the writing of Mass Effect.

I ran up to wail upon the dragon (I was also Level 6 when I first encountered it) and it flew away.

Granted: still a lot harder then the high dragons in DAO, but that's at least partly because DAI's tactical view is utterly worthless.

It is, but the dragon at the Andraste's Ashes quest in DA:O was hard as a mofo. I wanted to stab my eyes out in the two cases where you must use tactical view in order to solve some puzzles, tho.

Huh. Between @Chime, @Glitch and I, we don't really know TinyMUSH, which explains why our answers are in such disjunction with what you were expecting.

If we can't get you a good answer, Lydia might be on the Amber game, Road To Amber, and there is a support mailing list as well.

If it's not working correctly, then the best action is to check for an existing bug report here, and adding one if it's not there.

I still can't find the room_attr_defaults help file.

(edit: that is, please provide etc.)

@Rainbow-Bright said:

Interesingly enough, room_parent isn't quite what I wanted and after thinking on it last night, I realized I could just toss a switch that checks to see if there is a preexisting exitformat or conformat on the room and utilize that instead.

Nnnnhhh, no, this is horrible coding. The point of parenting rooms is that the most immediate parent will give the information that you need.

As room_attr_defaults doesn't seem to be a config parameter, it's not going to do anything. Instead, what @Glitch and @Chime said are correct; you want to override the main room parent's @conformat by using a different parent room, or see if you're having config issues by trying: @conformat here=blah

If that doesn't work, you have a larger problem.

Way too many to remember. Will edit as ancient history comes back.

Under the player name "Zoë Kincaid"

• Tilia @ TwoMoons
• Someone @ Shadowed Isles
• Zoe Kincaid @ LarryGhost's Game
• Vera @ Haunted Memories
• June (Medusa Changeling) @ The Reach

Under the "Thenomain" banner

• Thenomain/Th'main @ PernMUSH (Norcon)
• Can't Remember @ Masquerade MUSH
• Sywin Billard @ Some old and wonderful end of the world game many years ago.
• Rad @ DarkMetal

Staff & Coding

• Masquerade MUSH (WoD, from the beginning)
• Amaranth MUSH (WoD; New Hope, Maine)
• Aether MUX (original fantasy)
• DarkMetal (WoD; gutter-game)
• DarkWater (nWoD;, Somewhere, Washington)
• The Reach (nWoD; Aleswich Maine)
• Coding help for four nWoD games that have not yet been announced

@Ganymede said:

Raptor,

I don't put out shitty product even if I'm arguing before a small claims court.

This is closer to: You're representing a number of clients in a class-action. If a single person complains how you're doing things, or a CEO who is funding most of your effort complains how you're doing things, who do you put priority to?

Both metaphors are way off-base, but I think this one is better.

I would, to be honest, like to make sure that someone knows where the line is and to say "this is the line". The line being: Spamming, too much beating of a dead horse, when the chance of any productivity concerning a topic has gone well beyond the pale.

All of these things are roughly the same thing: Keep things moving. Be hateful, be nice, but if you're repeating yourself then you're probably done. If people complain that you're repeating yourself, that's bordering on the spam.

That's my view of things.

Emma,

I'm pretty sure Jaded started Wora as his playground of trolling PHB staffers on WoD games. Everything else was an accident.

History!

For the record: I like Sera based upon my character's personality. I like all of them but Vivienne, so far, based on same, meaning they are, in my book, well-rounded and fantastically written.

Vivienne is kinder to you right off the bat if you're a human noble. Many opening conversations are smoother if you're human, the racists.

@Chime said:

In particular, people that are comfortable with shells and setting up MUX games could be very useful in getting the mechanipus fork of MUX into a more end-user usable state, if people are still interested in that. If not, well; it'll keep. It's all on github, but no I won't build it for you and set everything up.

@Chime:

I would like to make a "Darkwater nWoD" bare-bones game database, complete with your quiet room that's ready to run.

Hell yes I'm interested.

@Cobaltasaurus said:

Oh! My +Events code is there! AWESOME! Thank you for finding that!

@Cobaltasaurus, I've been maintaining and improving your +Events code for a while now, you dork.

No, I'm Sparticus!

What Happened to WORA: It's around, somewhere, on a server we're still trying to reach. The site host went incommunicado for a long period of time and has since resurfaced. This puts our chances of recovering the information much better than it did several weeks ago.

Peverel has not been involved in WORA for quite some time, and I doubt he cares whether or not someone else makes a clone. WORA technically belongs to Lolth, but I doubt she cares if there a hundred WORAs out there.

I don't. When I overheard @Glitch and @EmmahSue mention "The Soapbox" as a name, it hit the right note.

WORA is vitrol, anger, sputum, like angry sex, so having a place, a more constructive kind of place without WORA's history of bang-on vile accuracies and just banging on would be a good idea. I approve.