Donnachadh
United Allegiance of Undesirables
1246
|
Posted - 2017.05.19 14:11:40 -
[1] - Quote
Linus Gorp wrote:You lost me at "summoning drones". WoW is that way ---> EvE has the reputation for having a very toxic and elitist player base, I was wondering who would volunteer to be the poster child for that, thank you for stepping up to fill that role.
Ideas are important, the words chosen to express them are not as long as those words clearly relate the idea. In this case the words chosen clearly relate the idea so your objection to the term "summon" is .......... well can't say that here the ISD may take offense and I do not want to offend them or suffer their wrath.
There are several 10 year plus EvE veterans in the low sec group I have a character in, I wish I could video tape their reactions when I post up your comments about "summoning" drones, it is likely to get interesting since they have been "summoning" drones since I started playing in late 2009.
Getting back to the changes requested, OP ideas similar to yours appear on a fairly consistent basis and they are usually well received as virtually all drones pilots would like to see some variation of your idea implemented. We have some hope based on the recent changes to how carriers handle fighters so who knows what may come our way.
Oh and all that nonsense from Linus Gorp about this never happening because legacy code, yeah don't worry about that. Over the years CCP has proven repeatedly that they can and will find ways around the legacy code issue, or simply re-write portions of it to allow for a new feature or game change. One of the most recent is the way carriers handle fighters, there are those who said that would never happen because legacy code, they were wrong and there is little doubt in my mind that Linus Gorp is wrong here. Not sure if the problem here is in convincing CCP this a good idea or the devs having time to implement the idea but either way the real problem is CCP not legacy code.
Oh and Linus Gorp, yes I do know a little about programming, based on the published average age of an EvE player I was programming computers before your were born and quite possibly before your parents were old enough to walk and talk. See I learned to program when an entire program had to be entered using puch cards. We did not even have a tape drive system to store data it was stored on wait, yep you guessed it punch cards. I was there when the original basic was released, I was there when D-Base was released. Over the years I have programmed in about a dozen flavors of BASIC not to mention multiple implementations of FORTRAN, COBOL, C, C++, C#, D-Base, R-Base, SQL and even some Python simply because I was interested. You are right none of this makes me an expert on EvE or in computer programming in general. What all of this experience does make me an expert are these. Without access to the actual code it is impossible for you, me or anyone else to determine what is and what is not possible.
In software virtually anything is possible, so virtually all of those legacy code issues can be worked around. The real question becomes this, do the benefits to the game as a whole justify the dev resources needed to make that work around happen. |
Donnachadh
United Allegiance of Undesirables
1248
|
Posted - 2017.05.21 14:15:53 -
[2] - Quote
Krysenth wrote:Donnachadh wrote: In software virtually anything is possible, so virtually all of those legacy code issues can be worked around. The real question becomes this, do the benefits to the game as a whole justify the dev resources needed to make that work around happen.
You are right, but only insofar as the fact that they're working around pos legacy code by systematically butchering out bits and pieces and recoding them as NOT-legacy code (actually adding in appropriate commenting and tags for code blocks as well) as benefits for Upwell structures. And eventually completely removing the pos code from the game. So....it's not exactly "working around" legacy code, it's writing a bypass to legacy code which when completed will excise and assume the role of the legacy code. I understand your point but completely replacing existing code is the ultimate work around when you come up against any form of legacy (old) code issues.
|