Community Nexus

[D'nial]

If I may vomit forth my opinion, I would say that my favourite solution is to change the GUI of the existing Nexus.

Changing the GUI of the existing Nexus would require a rewrite of cyan's python file for the nexus. It would also require an entirely new GUI for the Nexus itself to create the neceassary buttons and animations required for a rewrite. Not impossible, but all it would do is simply reorganize the mess that the Nexus currently is in. Which still doesn't help the solution of the Nexus, well being a mess.

EDIT: It also requires us to address the issue of wether or not we should tamper with a resource of Cyan's to suit our own needs. In the past, changes to the KI, and Nexus have been superficial and done entirely in Python, in order to not have to resort to changing the existing PRPS too much. A completely new GUI would mean discarding the one made by Cyan, creating a new one. It'd be akin IMO, to going in and making major changes to someone elses age without their approval. Granted in the past I have done so to Cyan's ages, however these were superficial changes like adding books in new prps that could be removed easily by anyone who didn't want them. The former is a bit different then the latter.

Would that also preclude major re-structuring of the way the KI interface works?

[nathan2055]

If I may vomit forth my opinion, I would say that my favourite solution is to change the GUI of the existing Nexus.

Changing the GUI of the existing Nexus would require a rewrite of cyan's python file for the nexus. It would also require an entirely new GUI for the Nexus itself to create the neceassary buttons and animations required for a rewrite. Not impossible, but all it would do is simply reorganize the mess that the Nexus currently is in. Which still doesn't help the solution of the Nexus, well being a mess.

EDIT: It also requires us to address the issue of wether or not we should tamper with a resource of Cyan's to suit our own needs. In the past, changes to the KI, and Nexus have been superficial and done entirely in Python, in order to not have to resort to changing the existing PRPS too much. A completely new GUI would mean discarding the one made by Cyan, creating a new one. It'd be akin IMO, to going in and making major changes to someone elses age without their approval. Granted in the past I have done so to Cyan's ages, however these were superficial changes like adding books in new prps that could be removed easily by anyone who didn't want them. The former is a bit different then the latter.

Would that also preclude major re-structuring of the way the KI interface works?

Actually, yes, but that's also something that eventually needs to get done.

[Luna]

Speaking as messenger, I would advise you to also think of the way the separation of content would appear to the fans who know nothing of this separation, maybe aren't even aware that there was only one nexus once(if it is implemented and all) . They won't think "they made two nexuses (nexusi, whatever) because they didn't want to edit Cyan's". They are likely to reach other ( less positive) conclusions depending on their feelings about the writers and fan content. It can be seen as arrogant, bragging, a way of saying "*** you Cyan".

[diafero]

Actually, I think you are right in the fact we shouldn't edit or delete Cyan's content. Exactly the reason I want Fan D'ni Locations in the WNexus ( ).

But that does not require any age editing. It just requires changes in the Python code, which works on a totally different level. We are editing Cyan's Python code all the time, otherwise neither Alcugs Shards nor the Offline KI could even remotely work.

Would that also preclude major re-structuring of the way the KI interface works?

The KI is independent, please, one issue at a time.

They won't think "they made two nexuses (nexusi, whatever) because they didn't want to edit Cyan's". They are likely to reach other ( less positive) conclusions depending on their feelings about the writers and fan content. It can be seen as arrogant, bragging, a way of saying "*** you Cyan".

...?!?? How that? Not only are we respecting Cyan's work and want to leave it, but in addition we also make sure it fits with the lore *they are breaking continuously* and have a good explanation for why an age is here, and another is there. I really can't see how that can trigger these feelings, quite the opposite - I'd much less surprised if people would feel bad about us ripping out an existing age, or parts of it (which mostly boils down to the same, in this case, as the Nexus is nut much more than the GUI).

[Luna]

@ diafero

I was commenting on how it would seem if we separated it on base of maker(fan age nexus, cyan nexus), not on location (D'ni locations nexus, other ages' nexus).
The way the community is going to react is arguable, but considering the "A bot/Hax! Uru is gonna die!" reaction of some people, I do not consider (a part of ) the community either rational or logical.

[Whilyam]

Yeah Chloe sort of has... no ground to stand on when it comes to changing Cyan Ages so that argument needs to stop. Thanks. Moreover, I don't think it's an issue. Cyan has shown recently that they are open to fans modifying the game when it's presented in the right way. Instead of neutering an idea before it gets started, perhaps we should just do the work and see where things go from there. Show it to Rand and see if maybe, just maybe, you start the next "Fun House" style project.

What we don't need more of is the "no we can't" attitude.

[diafero]

I was commenting on how it would seem if we separated it on base of maker(fan age nexus, cyan nexus), not on location (D'ni locations nexus, other ages' nexus).

But this was never seriously discussed - nathan was the only one voting for a creator-based organization. The alternative to editing Cyan's Nexus is separating ages located in D'ni/Earth from ages located elsewhere. However, the "elsewhere" Nexus would contain no Cyan Nexus as they all already have their access.

[nathan2055]

Yeah Chloe sort of has... no ground to stand on when it comes to changing Cyan Ages so that argument needs to stop. Thanks. Moreover, I don't think it's an issue. Cyan has shown recently that they are open to fans modifying the game when it's presented in the right way. Instead of neutering an idea before it gets started, perhaps we should just do the work and see where things go from there. Show it to Rand and see if maybe, just maybe, you start the next "Fun House" style project.

What we don't need more of is the "no we can't" attitude.

Well, I now believe definitely that it would be better if we made the WNexus the only Nexus.

[Egon]

So finally I have sit down and make first draft of assigning ages do categories.
There are over 110 ages to assign, I wasn't able to visit all of them, most of them I made from memory so some assignments might be "strange".
Any fixes and changes are welcome.

As for categories:
I didn't assign categories "Large/Medium/Small", and "Indoor/Outdoor/In-and-outdoor", although I think that they most definitely should be assign.

It turns out that we might not need category "Other", since in the worst case scenario, category "Explorable" might be assign (since every age is, duh, explorable). At first I wanted use "Explorable" category only for ages which are huge, "labyrinth-like", and put emphasis on exploration aspect of gameplay, but such definition was to much subjective to be any useful.
With that in mind I tried to put "Explorable" only for those ages for which I wasn't able to came up with better categories.

[kaelisebonrai]

re: The "Guild" category... that tag, I feel, should only be for guild endorsed locations. Endorsed specifically by the leadership of that guild.

So, your Age Maps Gallery and Jamey's Writer's Niche would have to be endorsed by the leadership of the Cartographers and the Writers respectively, after all, the guild tag does imply that they are representative of the guild, and that they /are/ endorsed by that guild. =P

if no one wants to endorse or have things endorsed - drop the guild tag entirely.

Also, as mentioned, drop the "D'ni" tag, as none of the D'ni locations will be in the Writer's Nexus. None of them. At all. The standard nexus will have the D'ni locations. =P