Fan Content

matthornb · **Posted:** Wed Oct 03, 2012 12:20 am

I've already agreed to model & texture this... And am hoping that someone will step up to implement the scripting.

As for the plugin you mentioned, thanks, I'll take a look at it.

I want you to know that while 'builders and coders equal implementation', those builders and coders often use ideas from the community... Those ideas do influence my design and though not all of them will be included, many of them will be.

Calumon · **Joined:** Wed Aug 22, 2007 9:38 pm **Posts:** 1673

Paradise wrote:

In the past, UU and URU attracted a number of brilliant people; programmers, artists etc, sadly they have gone. And I ask all of you why.

Bringing it over the next page, 'cause it needs to be repeated.

matthornb wrote:

I've already agreed to model & texture this... And am hoping that someone will step up to implement the scripting.

Adding that to the list of things to remind people:

"We have a modeler. We need a programmer."

Echoing Karkadann's repeated question now: Is there anyone out there willing to program a nexus?

---

Penny in the air....

AdamJohnso · **Posted:** Wed Oct 03, 2012 1:21 am

Program a completely new nexus, no. I thought that distasteful idea had been abandoned. However, I would be willing to offer some time* up to assisting with: adding a new panel to the existing nexus or helping wire a library age. Those are the two compromises (that I've read! I might have missed some.) that I find acceptable, given that no one seems interested in what I have described as being the "easy way."

* NOTE: This awkward phrasing means that I have a lot of other stuff going on that isn't Uru related.

Calumon · **Joined:** Wed Aug 22, 2007 9:38 pm **Posts:** 1673

AdamJohnso wrote:

Program a completely new nexus, no. I thought that distasteful idea had been abandoned. However, I would be willing to offer some time* up to assisting with: adding a new panel to the existing nexus or helping wire a library age. Those are the two compromises (that I've read! I might have missed some.) that I find acceptable, given that no one seems interested in what I have described as being the "easy way."

By "program a nexus" I meant to work on *Any* part of any kind of Nexus, be it a brand new one or a modification of the current. :)

---

So then, if most people are in favor of a Library, but if there are those that *also* want the quick access of a Nexus for 'speed'...

My suggested course of action is this: we should make a new tab in the nexus that is tied to Sevkor's library- when explorers use a book in the Library for the first time, the link is added to the nexus as is done with all of the current ages. This can weed out the pesky instancing issues that would come up with sharing the library book age with other people.

For now, however, I think we should work on getting Sevkor modeled and wired, and worry about implementing the Nexus functionality later on, once we have a need for such speed.

All in favor? All opposed?

HarveyMidnight · **Joined:** Sat Apr 14, 2012 2:59 pm **Posts:** 432

AdamJohnso wrote:

... or helping wire a library age.

Okay... I was thinking the objection to a 'fan-nexus' was how someone else claimed, that it was in some way discriminatory toward fan-content as being separate from Cyan. Which I never believed... but that's beside the point...

My original 'doghouse' idea always WAS a so-called "library age" --- I considered it a fan-nexus ONLY in the sense that it was the place to access fan-created ages-- a 'nexus' as in a central source of them being collected together.

Are you talking specifically about a nexus, as in THE Nexus, something that works the exact same way, with a screen we click on? Sorry, but that IS counterproductive. If the fan-content is supposed to be entirely fan-created and maintained... seems like a "library age" would be a lot easier for fans alone to create & maintain. So why would anybody insist on it working JUST like the nexus we have, and be a LOT harder to create & maintain?

If you don't have any kind of objection to a "library age" full of books that are fan-content--- well, THAT in mind, what we've come up with is a "fan nexus" in name only-- I think this IS a 'library age' that others are envisioning, and we're just CALLING it a fan-nexus.

AdamJohnso · **Posted:** Wed Oct 03, 2012 2:08 am

Calumon wrote:

For now, however, I think we should work on getting Sevkor modeled and wired, and worry about implementing the Nexus functionality later on, once we have a need for such speed.

I think that it would be wise to decide on one single way to access fan ages before anything happens. The game is really confusing enough as it is (think ambiguous instancing), and I don't think adding multiple ways of accessing fan ages would help in that regard. That means we need to know if people want Sevkor or whatever other option(s) there are. I would suggest putting up a poll with the appropriate options and a closing date. Then, real work can get started... Unless I missed the decision on this point and am just wasting my time typing

Emor D'ni Lap · **Joined:** Sun Aug 12, 2007 6:15 am **Posts:** 587

HarveyMidnight wrote:

... seems like a "library age" would be a lot easier for fans alone to create & maintain. So why would anybody insist on it working JUST like the nexus we have, and be a LOT harder to create & maintain?

The present Nexus displays text information in a similar way to a database, reflecting the current data in the vault.
A physical Library would require the creation and placement of textured book meshes in-game, with client updates for each addition.

Why do you believe a Nexus would be harder to maintain?
And who has insisted on a new fan Nexus "working JUST like the nexus we have"???

Calumon · **Joined:** Wed Aug 22, 2007 9:38 pm **Posts:** 1673

AdamJohnso wrote:

Calumon wrote:

For now, however, I think we should work on getting Sevkor modeled and wired, and worry about implementing the Nexus functionality later on, once we have a need for such speed.

I think that it would be wise to decide on one single way to access fan ages before anything happens. The game is really confusing enough as it is (think ambiguous instancing), and I don't think adding multiple ways of accessing fan ages would help in that regard. That means we need to know if people want Sevkor or whatever other option(s) there are. I would suggest putting up a poll with the appropriate options and a closing date. Then, real work can get started... Unless I missed the decision on this point and am just wasting my time typing 8)

A Poll is a great idea. EDIT: And here it is! :)

AdamJohnso · **Posted:** Wed Oct 03, 2012 2:59 am

Emor D'ni Lap wrote:

A physical Library would require the creation and placement of textured book meshes in-game, with client updates for each addition.

Heh, I'm glad you said that. It gave me the idea for a script that can place/remove linking books in a library with trivial vault updates (read: no content changes nesecary).

JWPlatt · **Posted:** Wed Oct 03, 2012 3:01 am

Adam,

Let me see if I can summarize the thread so far, in a sort of specification format, about what would make an acceptable compromise. Then only if I have it right, see if it's possible to do something about it.

Use the current Nexus model to meet your terms - no second Nexus. It becomes fan supported.
Add an easel to the Nexus - "There be dragons here!" to meet Cyan's terms.
Add a GoW-designed and/or -approved seal to every fan book - and the easel - to clue people in on what it means.
Add an "Explorer Library" to hold books leading to more new fan content.
Add an "Explorer Ages" tab to the Nexus UI.
Prepopulate the Nexus "Explorer Ages" tab with a link to "Explorer Library."

AdamJohnso · **Posted:** Wed Oct 03, 2012 3:04 am

I think you've got the idea except I would prefer that the nexus and library options be mutually exclusive. That is, we have a nexus page OR a library, not both*.

* That doesn't mean a link to the library age itself cannot appear in Cyan's nexus.

JWPlatt · **Posted:** Wed Oct 03, 2012 3:18 am

AdamJohnso wrote:

nexus page OR a library, not both.

Can you explain the Nexus page more? Between "Fan Nexus" (copy of existing Nexus), "Fan Nexus" (Library), "Nexus" (the existing Nexus), and the Nexus book (in Relto and other ages), the word has grown ambiguous.

HarveyMidnight · **Joined:** Sat Apr 14, 2012 2:59 pm **Posts:** 432

Emor D'ni Lap wrote:

Why do you believe a Nexus would be harder to maintain?

Uhh. cuz I don't know that much about it... :oops:

80's college dropout, here.. I know zip from programming. Sorry.. I withdraw the comment.

AdamJohnso · **Posted:** Wed Oct 03, 2012 3:34 am

Heh, good idea.

I mean that we add another tab to Cyan's existing nexus that says something to the effect of "fan ages." This tab would hold links to any fan ages added to MOULa. To accomplish this, we would need for Cyan to add a new GUI button with the same styling underneath "Personal Links" and, perhaps, a dynamic layer for displaying the linking panel (the current panels are all hardwired). Then, some magic would have to happen in the existing nexus python.

JWPlatt · **Posted:** Wed Oct 03, 2012 4:19 am

Understood, thanks.

I prefer "Explorer Ages" because it's IC and "Fan Ages" is OOC.

The tab is already stipulated. But there has been canon objection to having ages just seem to appear in the Nexus with no external gameplay cause. This was resolved by using the books in the Explorer Library - or elsewhere - first before the ages appear on the Nexus list.

Also note I am proposing fan possession and support of the Nexus model, UI, and code.

Fan Content

Who is online