J'Kla wrote:Lets just clear the reason it is the easiest to answer.
I want to run a small shared shard maybe as few as three users on a local network in a place that is NOT on the internet so I was looking to do exactly what Destiny does but without an internet connection.
I also want to be able to include fan built worlds.
That's pretty great!
I've been hoping for a long time that people would be more interested in doing this sort of project.
J'Kla wrote:To do that I need to be able understand every step so that if something does not work we have a chance of finding where the method breaks because of say some Linux update has moved the goalposts.
I'm not sure how much you will understand at this stage. Getting things accomplished is usually the first step in understanding, not the last.
If there's one thing I've learned it's that I always have more to learn!
J'Kla wrote:One advantage is I have fully documented every step and when it is complete there's every chance you will have your new wiki page as a bonus.
I look forward to your updates to the wiki. I'd suggest keeping the changes to a minimum, adding steps and explanations where necessary to the existing instructions. Be sure to post here when you do, so I and some of the other technical people can go over it for factual errors (you made a few crucial ones in your recent post outlining the steps you've taken). Hopefully by the end we can have some really stellar instructions that are more helpful.
J'Kla wrote:There is a good possibility that by the end of the year I will have access to a venue with three screens each one 3 meters wide by 2.5 meters tall where I could be running an Avatar on each screen in a shared world.
But will you have enough hands?!
J'Kla wrote:Nowhere near as complex once you know how.
That's always the main pitfall when trying to write about something you know how to do.
J'Kla wrote:Have you ever considered there were so few Admins and people building their own shards simply because there were no concise instructions?
Sure have. I've been a part of this community long enough to know that's not nearly the biggest barrier. Also, these instructions belong to the community. There's an ouroboros-like assumption here: if there were sufficient interest, the instructions would be better, because someone would be improving upon them. And here you are, proving
that point!
J'Kla wrote:From an idiots point of view (and here I am qualified) this does not really need automating just a decent set of instructions.
I dunno. An installer script that would download the required libraries, walk you through setting up the server, and building a client dataset would be a big time-saver in my opinion.
More people want to make Ages than run their own server, or else we'd see more like Deep Island, ToC, and OpenUru's Minkata. There are still semi-frequent Age releases from a small number of prolific creators. That's why we've been focusing on Korman for the last several years. Unfortunately there aren't many technical people left in the community (at least, actively contributing) and those of us still here are increasingly busy elsewhere, so we rely heavily on users to file bug reports and contribute even small additions to all of the projects we maintain. If you find something insufficient in the README, you're welcome to submit an
Issue, or even make the changes yourself and submit them as a
Pull Request at which point you'll receive some feedback and at the end if it's accepted it will be merged into the primary document. To be honest, I'm not sure having the information semi-duplicated on the wiki is ever a good idea, as it's extremely likely to get out of sync with the code itself, unlike the README which is hosted and tracked along with the server code.