Developer Nexus

[nathan2055]

Split from Community Nexus discussion

Something that should be considered as we build the new Community Nexus and pedestals is a Nexus for GoW Developers, GoMa Testers, and GoCartographers Map Makers. This Nexus will list only Ages under testing, and will somehow allow people to choose whether a certain Age is stored in the Cyan Nexus, Community Nexus, or the Developer Nexus. It may also include an imager or journal if necessary. It will also most likely NOT need it's own pedestal, as quick access for reward Ages will be necessary when testing a set of Ages connected by storyline. Please post your thoughts.

[nathan2055]

Copying posts from old thread:

Just a little bit off topic

What about a Nexus devoted to ages that have not as of yet been completed. Ages too dangerous for the normal explorer, Ages where one of the two Maintainer Suits must be used. Ages that are under development and open to those who are assisting in finding problems and discrepancies. In other words a Maintainers Nexus. This would also include the exterior worlds of the Pod Ages...

Just a little bit off topic

What about a Nexus devoted to ages that have not as of yet been completed. Ages too dangerous for the normal explorer, Ages where one of the two Maintainer Suits must be used. Ages that are under development and open to those who are assisting in finding problems and discrepancies. In other words a Maintainers Nexus. This would also include the exterior worlds of the Pod Ages...

That's kind of what I meant by a Maintainer's Library. It would store Ages like that, include a Maintainer's suit vending machine, and be used for testing by the GoMa and by a writer of an Age that they need to test.

Then we'll need a Cartographers Nexus that will contain the Age that haven't been/are being mapped out.

Then we'll need a Cartographers Nexus that will contain the Age that haven't been/are being mapped out.

Does Cartographers even exist outside of the small group on URU Obsession? Even so, a section in the Maintainers/Developers Nexus will work.

EDIT: I suggest splitting discussion of the Developer Nexus off to it's own thread. I'll make it and reedit with a link.
REEDIT: The topic is up and the link is http://forum.guildofwriters.com/viewtopic.php?f=7&t=5181.

[Sirius]

With all the good ideas everyone gave, I wonder if we should really keep the Nexus concept. Well, of course we should keep the idea of books sorted by some kind of machine, but if we want to use new categories, new design and all that, it won't have a lot in common with the original Nexus anymore...

[Aloys]

I don't want to be rude; but I don't really see the point of having a 'developper' nexus.
We have the offline Ki that's all we need; why add a nexus for Ages in development? Is it to make the development process more IC?

[nathan2055]

With all the good ideas everyone gave, I wonder if we should really keep the Nexus concept. Well, of course we should keep the idea of books sorted by some kind of machine, but if we want to use new categories, new design and all that, it won't have a lot in common with the original Nexus anymore...

Are you referring to this Nexus in particular or both of them?

Anyway, both me and Tweek suggested updating the GUI in Cyan's Nexus, which was heavily turned down. Some people want a library-type system for each guild, others want a three Nexus system like I support, still others want to support Cyan's Nexus and an additional Writer's Library.

I don't want to be rude; but I don't really see the point of having a 'developper' nexus.
We have the offline Ki that's all we need; why add a nexus for Ages in development? Is it to make the development process more IC?

Not just IC. It would function basically as a storage point for Ages still in testing, or ones being mapped out by the Cartographers Guild. Although one could just use /link, it could also function on shards (which don't support /link) to allow players to download and link to beta or alpha versions of new or updated Ages.

[Wamduskasapa]

I don't want to be rude; but I don't really see the point of having a 'developper' nexus.
We have the offline Ki that's all we need; why add a nexus for Ages in development? Is it to make the development process more IC?

OK I will stomp on some toes...

Yes this would be more IC but the KI has also gotten way too fancy I see no problem for an Admin to have the type of KI that we now poccess, but the regular explorer should only have the original Cyan KI...

[nathan2055]

I don't want to be rude; but I don't really see the point of having a 'developper' nexus.
We have the offline Ki that's all we need; why add a nexus for Ages in development? Is it to make the development process more IC?

OK I will stomp on some toes...

Yes this would be more IC but the KI has also gotten way too fancy I see no problem for an Admin to have the type of KI that we now poccess, but the regular explorer should only have the original Cyan KI...

Although the "story access" requirement helps with this, I kind of understand. Which is why I bring up every Age having a Nexus book in the first place.

EDIT: While we work on the way the Nexus will work, discussion will seem odd on the two threads. They will most likely separate once we reach a design consensus.

[Aloys]

The Age development process is an OOC thing, that's why it needs fancy OOC tools like the Offline Ki, it just needs to be restricted to developpers, not regular explorers. (I certainly hated some of the stuff that happened in UU with the special KIs). I don't understand why we need an IC Nexus here.

[nathan2055]

The Age development process is an OOC thing, that's why it needs fancy OOC tools like the Offline Ki, it just needs to be restricted to developpers, not regular explorers. (I certainly hated some of the stuff that happened in UU with the special KIs). I don't understand why we need an IC Nexus here.

We don't need a OOC reason. This is most likely going to be used to allow the Guild and explorers access to beta Ages not in the general Nexus.

[Lontahv]

People testing beta content don't really need a separate Nexus. If you want a restricted testing group, you could always just send out age invites to the testers and keep the unreleased age off the general user-created-content list in the Nexus.