EVE General Discussion

I am an incursion runner and I have 50 fittings already filling up.
100 please!

The 8000 people who have max fitting, and I am one of them, are the few that actually probably use it the least. Think about it... If it's full, you can't import, you can't save, you can't do anything with the tool. It totally blocks you out from ACTIVELY using it. They probably logged in the day of the update, ran the updater and haven't touched it since because they are frustrated and can't deal with having to deal with importing and exporting. I love the fitting manager, but I hate the current implementation from a user stand point.

Anyone who ACTIVELY uses the fitting tool is going to leave some space to "work" in there to save and modify their fittings saved. So, looking and saying "well, only 8000 people have maxed fittings" is the 8000 people who gave up on it. You're looking at the people in the 30-45 mark that are actively using it and are probably "cleaning it up" regularly to use it with space. But all you're doing is giving these same people a headache in user interface.


My issue is that there's no reason to have a cap if you allow both server side AND client side saved fittings. Then I can work and play with my fittings on my client, and then those same fittings can be saved on the client when I want them there. Same way that you can save corporation fittings, etc.


I don't think you need more than 50 fittings, you just need to permit us to save them on our client for "Workspace" for fittings. Saving friends fittings, work fittings, corp fittings, and then when we really want to save them on the server, we get the space for it.

I train a lot of PVP pilots and I tend to save a lot of different fittings from races and ships I don't even fly to help them out and throw them a fit that they can use in a jiffy. Although many people will have and save "junk" fittings - I bet you most of the people that have more than 35-40 fittings are actually serious PVP pilots that keep up to date and on top of the newest combat styles. They probably clean up the old trash fittings on their own just to not clutter THEIR space.

I don't want to clog your servers with tons of junk fittings - I DON'T want to have to keep shuffling fittings around with a poor fitting manager.


User Interface Test

GO fill your fittings full of 50 fittings (I have 45 unique ships sitting in just one of my main bases, and yes, I use them all in different PVP scenarios).

Now, imagine someone gives you a fitting, and you're maxed out, what do you have to do? You have to export one of your 50 fittings. Uncheck all the ones you SPECIFICALLY want. Then delete the fitting. Then save the new fitting. Then go back and max out the current fitting limit you have. Then when you want to import an old fitting, you have to uncheck everything, check the ones you want, and blah blah.

It's poor interface design. IF you allowed us an intermediary client "storage", then we'd gladly use it to store our "junk" fittings, and then be selective and happy with the server side fittings being saved for whenever we need it.

Contradiction in Philosophy and Reality

You state that you're worried about people storing tons of junk fitting on your server with the limitation - and then you state that 1/3 of the people hardly are near the max, the other majority are in the mid-range, and then a small percentage are in the top bracket.

If the reality is most of those people aren't even using their max fitting storage, then you're really telling me that the 50,000 who use it near max storage really have another 100,000+ peoples worth of 50+ fitting that they really should have available to them.

And, are those by account or by character? For 310K Characters, 100,000 could easily be ALTS. So, really you're looking at the majority of the player base using 20+ fittings (Which is probably realistic for the average players number of fittings). Long time veterans, PVP pilots, etc require more fittings to deal with more scenarios.


EDIT To Add thought from below ::

Also, you permit us UNLIMITED storage in the WHOLE GALAXY. You permit us a gregarious amount of E-Mail Storage. You permit us UNLIMITED Bookmarks stored. You permit us pretty much UNLIMITED usage of data storage for the rest of our EVE Junk. Yet, the Ship DNA code, which is essentially 1 very predictable line of fitting information, you're worried about data storage on?

Ship DNA:




____________________________________________________________________


Also, can you give us a number of how many of those numbers represent High Sec, Low Sec and 0.0? I bet you most of the people who have near-max fittings are between low sec and 0.0 dwellers.

Thanks for responding on this thread....

DBAs never want to store data unless they see a real reason for it to be there. more data in the DB = slower db.

*sigh* More misleading data from CCP. Its misleading because you look at the numbers and you give absolutely no context. Honestly, before the fitting nerf I never saved my fittings to Eve. The reason was I just didn't use a lot. But, now, i'm into PVP. I'm training for different ships, different capabilities. Often times I will research a ship fitting before I have the ability to fit it and then save that fitting for future reference when I get around to being able to use it.

Since the nerf, I don't even bother saving my fittings in Eve. Why? Well, maybe because I don't want you guys deleting my saved fits? Maybe I don't like the idea that 50 might become 25. I do believe some people had fits go missing when the limit was put in place. So, I save all my stuff in EFT so I can keep it "safe" from CCP. I have several dozen fits, not just for myself, but for up and coming noobs I accept into my corp since I can't be arsed to remember tens of thousands of possible permutation of ship fits. Sorry.

Regardless, there are those players who have amassed a "resource" of good ship fits for all purposes. These people are resources and the go to guy for people in the know.

Also, the "there has to be a limit" argument is rather weak. You want to sell back a function we previously had. Interesting that it wasn't a problem until you could affix a dollar sign to the paltry limit of 50. Obviously whatever limit there was did not put undue stress on your hardware. And if so few people are saving large numbers of fits, then a higher limit shouldn't be a problem. But, I suppose, you could blame null lag on ship fittings if you want.

Edit: I don't even know why I bother replying to a dev with his head that far up his wormhole.

That's a very, very minuscule amount of data storage that you're saving with this cap. That argument is weak.

What was the technical argument in favor of removing the local storage when you implemented the server-side storage?


I don't mean to be confrontational. We know that the change was with an eye toward charging Aurum for the service. You know what? That's fine. But what should have been done is left the local storage option as-is, and rolled out the server-side storage option as an Aurum enhancement from the get go. That way, you would have avoided the (correct) impression that you eliminated an existing option only to sell it back to us.

There is value in server-side storage options.
It's OK to sell us value-add services that don't impact competitive gameplay.
Just don't take away the inferior alternative in the process.

That just pisses people off.

additionaly fittings help new players.

If a corp member asks for a decent hirican fit I may have one and can help out or use it as an example of what to aim for in his fit...with limited fittings that is no longer possible.

I agree that having the ability to store them both server-side and client side would be best. When saving a fitting, add the option to store it remotely or locally

8k unhappy people, because ccp dont like to spend 20 MB in a Database.

100-150 fits please. Seems reasonable if there needs to be a balance between storage and utility.

If you have to use EFT for most of your fits, you might as well use it for all of them.