There's a lot of truth in a lot of these posts. It's refreshing to read posts that are both insightful and polite (well, mostly polite). Props to Subutai and Durvayas especially.
I do want to address something from an earlier page in this thread.
Dr. B wrote: ↑Tue Oct 15, 2019 9:09 pm
I'm currently writing a long post on this issue. The way Arelith has always been run is that, ultimately, authority to decide what happens to the server resides in one person.
I think that's insane and that it's time to reevaluate it. It might have made sense 15 years ago when Jjjerm created and hosted the server. Now it has existed for 15 years and has become, in a sense, a living artifact to which many have contributed. It's not clear that it belongs to one single person, even if the computer that hosts it does. It's also not clear that the current leadership model is in the best interest of the server.
There needs to be a conversation about whom Arelith belongs to. My answer, in brief, is that it belongs to the Arelith community, and that the decision-making structure needs to reflect that in some practicable way.
I want to distinguish between the 'module' and the 'server' in this preamble. The 'module' covers all the assets that comprise Arelith. The 'server' is the community. When somebody thinks about the mechanics, the dungeons, or the loot, they are thinking about the module.
If somebody took the module and hosted a splinter copy of Arelith under new leadership, they would be creating a new server using the existing module. If they brought the vault and database with them, and they had majority community support, I would argue that it was the same server.
As you've correctly highlighted here, the Arelith module is a product of many years of development by a large team of volunteers. It isn't clear who owns the module.
Is it the person who pays the bills? What about the bill-payers of ye olden days? And how do community donations factor into this? Do community donations cover module development or server maintenance?
Is it the person who drives development (the 'dev lead,' as used here)? Again, what about the previous dev leads? How much of the module does Mithreas own, if any? How much do I own, if any?
Is it the coders, without whom the server would have no custom mechanics or systems?
Is it the artists, without whom the server would have no areas?
Is it the designers, without whom the server would have no content?
How much ownership does the balance team have over the content produced under their guidance, given that many implementation details would be different without them?
Do players who post suggestions on the forums, which are later implemented by a developer, have ownership over the original idea?
I won't open the can of worms that is ownership of the module from a legal perspective. From a moral one, I think it's sanest to consider ownership of the module split between the developers who have contributed to it over the years.
This is consistent with the internal policy that Irongron holds: core members of the team who discover irreconcilable creative differences are free to take components of the module and create their own server using them. Irongron offered this to me, and Peppermint, and probably others. Mithreas uses the core engine code from Arelith on his server. We've shared our code with many servers. Even Sinfar!
ETA: Irongron informs me there is even an open-source version of the code available for everyone to use, updated last in 2017: https://neverwintervault.org/project/nw ... -pw-engine
The community has very little entitlement to ownership over the module and its creative direction. One could argue that recent donations by the community have funded module development and so they should have a say in how to spend that money. If you were to analyze Arelith's financials, I suspect you would find that donations barely cover the hosting cost. Irongron is probably paying out of his pocket for module development costs.
The role of the community is incredibly important to the success of the server - but it does not convey ownership over the module. Without the community, the server would not be where it is today, but the module might well be.
Dr. B wrote: ↑Tue Oct 15, 2019 10:32 pm
They're obligated in much the same way that curators are obligated to care for and protect works of art. Great works of art have intrinsic value for many people and ought to be preserved and protected. If the board of trustees in the Louvre decided to vandalize the Mona Lisa, they would have done something wrong. The Louvre is entrusted with something, something valuable--something that they did not create, though that they have taken it upon themselves to maintain. They stand in a fiduciary relationship, and I think this is the sort of relationship standard to which Arelith's host should be held.
Arelith is a more complicated affair than the Mona Lisa. Its function is to promote excellent and enjoyable roleplay, which is fostered by a diverse environment in which characters of many faiths, alignments, and professions exist. The server is better to the extent that this goal is met. Aodh Lazuli explained this very well in a previous post. The updates up until now have done a lot to promote that. There is a clear sense in which this latest update stands to make Arelith worse. This is not how a caretaker should treat the thing in its care. Of course, I understand the caretaker thinks the server is better this way. But the feedback overwhelmingly says otherwise. The caretaker, in this instance, should defer to the feedback.
But more important, my argument for this is ameliorative: it would be better for Arelith and the community at large if it were understood that this were the host's role. If it isn't, it ought to be, because it stands to benefit Arelith. And I also think the server host should be honored by that role. It's an honorable thing to do, as would be deferring to the feedback in this instance.
This example made me think about the duty of the 'dev lead' more deeply than I have in the past.
Is the Mona Lisa the module or the server? From a like-by-like perspective, the Mona Lisa is the module. But it is quite different to the Mona Lisa, which was painted by one artist who is now deceased. The module has been created by many contributors over the years, most of which are still alive and kicking. A painting is a one-and-done. A video game evolves.
The curators of the Mona Lisa are almost certainly paid a salary and given the objective to "preserve this painting in its current state." It is their job for which they receive a salary. Contrast this with the Arelith development team, who do not receive a salary. On this point alone, I think the model of development you propose is unsustainable.
Additionally, the Mona Lisa most likely belongs to the Louvre, or the French government. Either way, the painting is their property, so they should be able to with it as they please. Just like how the French government owns the Mona Lisa, Irongron owns the module. He was given ownership of the module by Mithreas, who was, in turn, granted ownership of the module by the owner preceding him.
The Louvre or the French government has made the decision that they wish to preserve the Mona Lisa in its current state, which makes sense. It is a real, physical piece of art painted by a deceased artist. Arelith is and has always been an ever-changing module. It is not complete, and it never will be. Irongron has not decided to preserve it, but to change it, and improve it – at least, improve it in his view – which is his right, because he owns it.
You could argue that once ownership passed from the original owner to the second owner, the module was 'completed' and, therefore, the owner must preserve it in that state. Do you want that? I doubt it. Some people do, but you value mechanical balance and variety like I do. You don't want a broken and terrible Arelith like it was ten years ago. You want Arelith like it was 6-12 months ago.
But you can't have it both ways. You want to freeze the module at a state that suits your subjective view on its quality. Why should the module forever reflect the values that you consider essential? Others disagree with you. Historically, the module has always been poorly balanced. Mechanics at the forefront is a recent event in the timeline of Arelith.
Let me be clear here – I agree with your view on quality. A big part of why the module improved from a mechanical perspective after Mithreas' reign is because Peppermint and I pushed hard for that. I don't approve of the new direction. I do, however, support the development team's right to set it, and I encourage them to do what they feel is best for the server.
Arelith is not a work of art in the same way the Mona Lisa is a work of art. It is a video game that has, since its inception, undergone consistent, rapid, yet often contradictory change at the whim of the individual who ran it at the time.
Your argument is like barging into Leonardo da Vinci's house while he is still painting the Mona Lisa, and declaring that he must never finish his painting! It is perfect just the way it is, and now it belongs to the French people. Good old Leonardo is an abject moral failure if he doesn't abide by your request.
You do not have the right to demand this. The module does not belong to you – you have no say in its direction, and to imply otherwise is, in my view, meritless.
Irongron should have the right to do as he pleases with the module, and if the contributors don't like its direction, they should take their work and apply it elsewhere. This is the status quo, and I don't believe it should change.
Your argument does have merit when applied to the server, which was built by the community and is therefore owned by it. I think Irongron does have the moral responsibility to preserve it to the best of his ability.
But make no mistake, that doesn't restrict his ability to push change on the module. If he must shut down the server for any reason, he should publish the vault, database, and anything else required for the next generation to carry the torch. He should adhere to the community values that are long-established on the server, like the server's age rating and established style of administration.