-And with this design decision people realize the only way to win anything is with grind. The only way to combat the negative affect of grind on a single player is to spread the pain over a larger, concerted, group. Anything that will accomplish bringing people together in larger numbers SHOULD be a major focus of the devs. This does not necessarily mean that 'ownership provides exclusivity'* though. Think of Guild Halls in the original Guild Wars. They were a private instance that, over time, had added functionality (market reps, outfitting reps, etc.). The same could easily be done here...a guild owned outpost on planet 3 in system y...that the group can upgrade to full service over time...and that no one else can visit or use.
I see no issue in this type of guild housing. It does not affect the game at large since no one else will see it or use it.
*Exclusivity meaning some sort of negative outcome to PvE players over PvP blocking. Obviously, the 'private ownership' IS exclusive to the guild...but has no 'negative' PvP outcomes that can occur from it.
Fleshing out that plan could be interesting / challenging depending on your perspective. If the guild hangout started off as an outpost for cost purposes, it would obviously exclude large ships. To upgrade to full station would be orders of magnitudes higher. Then to have facilities there... Would the guild need to provide hydrogen for refuelling, metals for repairs, industrials for outfitting? Would these be "complete once" guild goals, or require constant updates? Would it be unbalancing for a guild to have access to a 100% outfitter offering all modules up to size 8 and all weapons? Would the availability be limited to match the existing system economy?
-
As with most things where changes are proposed, the devil is in the detail.
-
Also would the exclusivity use something like the guild membership as a chirpsounder? Or would it require a CMDR watchman to sound the general alarm? Would player hideouts be armed to the defense level of an existing Orbis? Could they be attacked and damaged or destroyed?
-
So many questions to try and define the scope of the implementation