AtomYcX
Shadowfire Enterprises Rura-Penthe
0
|
Posted - 2012.11.14 18:55:00 -
[1] - Quote
It's clear to anyone reading the thread that the thing that matters most to everyone is granularity of access control within hangars, the suggestions of using containers and such is quite frankly rediculous. You're planning to release something that you full well know the EVE players - your customers - not only do not want, but will be negatively affected by.
As has been said earlier in the thread, the separation of hangar access from corporation roles is a much needed move, nobody's arguing that fact. You really do need to consider taking the feedback on this thread seriously though - nobody wants what you're offering so far. We don't want to mess around with cans, we don't want on/off access for the entire hangar, we want to be able to control access like we can currently, but better.
Being a developer myself I understand the issues around having to deal with legacy code but in this case it sounds like most of the legacy code around hangars is being removed - why isn't this opportunity being taken to provide the players with a system that would actually make their lives easier? Is there a real and honest technical limitation that means you can't provide a better solution than "use cans", or are you just trying to rush a release?
I think I speak for pretty much everyone who's replied to this thread so far in saying that in an ideal world this is what the replacement for the current system would look like:
A "Configure Hangar/Bay" interface where divisions/folders/sub-hangars - whatever you want to call them - can be specified on a per-ship basis. While we're here, why not let the user create as many divisions as they want (within reason), the number shouldn't matter - the ship's overall hangar capacity would govern the total space available. Each division could then be configured independently, to allow fleet/corp/alliance give and take permission.
I obviously don't know anything about how EVE is coded, and forgive me if I'm missing something, but why couldn't it be implemented like this:
- Player accesses the public hangar on another players ship
- List of user configured divisions for the ship are pulled from the database, along with their access permissions. Something like this if it was in XML:
Dream World Hangar Permissions wrote: GǦDIVISIONSGǦ -á-á-áGǦDIVISIONGǦ -á-á-á-á-á-áGǦDIVISION_INDEXGǦ0GǦ/DIVISION_INDEXGǦ -á-á-á-á-á-áGǦDIVISION_NAMEGǦFleet ModsGǦ/DIVISION_NAMEGǦ -á-á-á-á-á-áGǦACCESS_PERMISSIONSGǦ Where 0 = No Access, 1 = Give Access, 2 = Take Access -á-á-á-á-á-á-á-á-áGǦFLEETGǦ2GǦ/FLEETGǦ -á-á-á-á-á-á-á-á-áGǦCORPORATIONGǦ2GǦ/CORPORATIONGǦ -á-á-á-á-á-á-á-á-áGǦALLIANCEGǦ0GǦ/ALLIANCEGǦ -á-á-á-á-á-áGǦ/ACCESS_PERMISSIONSGǦ -á-á-áGǦ/DIVISIONGǦ -á-á-áGǦDIVISIONGǦ -á-á-á-á-á-áGǦDIVISION_INDEXGǦ1GǦ/DIVISION_INDEXGǦ -á-á-á-á-á-áGǦDIVISION_NAMEGǦSekret StuffGǦ/DIVISION_NAMEGǦ -á-á-á-á-á-áGǦACCESS_PERMISSIONSGǦ -á-á-á-á-á-á-á-á-áGǦFLEETGǦ0GǦ/FLEETGǦ -á-á-á-á-á-á-á-á-áGǦCORPORATIONGǦ0GǦ/CORPORATIONGǦ -á-á-á-á-á-á-á-á-áGǦALLIANCEGǦ0GǦ/ALLIANCEGǦ -á-á-á-á-á-áGǦ/ACCESS_PERMISSIONSGǦ -á-á-áGǦ/DIVISIONGǦ GǦ/DIVISIONSGǦ
- For each user configured division, compare the access privileges to the player accessing the hangar's relationship to the ship owner (fleet/corp/alliance) and apply the relevant UI updates to each division - greying out divisions with no access, not displaying the contents of give only divisions etc.
Just my thoughts on how I'd approach the issue from a design point of view, surely something like this would be possible with a bit of time and effort. You seem to under estimate how much love you'd get from the player base for listening to them and providing a truely well thought out improvement to the current hangar system. Bonus points if you could implement something like the above on a per-hangar basis in POS's too - perhaps with a "Copy access configuration from (list of hangars in POS)" option too |