Deliberate thread necro time…[SUP]I’m not ashamed to admit that I’m angry.[/SUP]
This has been an outstanding issue for some time now. As a developer I’m mindful of how easy it is to judge a thing “easy” from the outside but this is well beyond that now, I dont normally throw around this kind of language… but whoever is responsible for the resolution of this problem deserves to be fired (as does the person originally responsible).
For 2 years you have had a known issue that prevents your most prolific customers from spending money without tediously involving themselves with your support team performing manual interventions on their accounts. How is this kind of treatment acceptable for your most valuable customers?
Yes I’m aware the big money for Epic as a whole is in studio licences (and Fortnight) and the marketplace is probably lower priority, but if you are going to bother having it at all, you should never under any circumstances consider it acceptable to punish the customers who are spending the most money… Thats just bad business!
This issue predates the launch of the Epic Game Store… thats how long there has been a hard limit to the number of items in an account’s vault. This might look like a bug, but I wonder if its actually a case of “we f****d up the database design and now theres $$$$$$ on top of it so … um can we kick the can further down the road?”… The fact that the new wishlist feature is only 50 items and your “hoping” to be able to increase it to 100 makes me deeply suspicious of the quality of database design that must go on inside Epic. I’ve used both Relational/SQL and Schemaless/NoSQL Databases, I had database design drilled into me back in university/college, and I’ve written plenty of web backends over the years… and the only two answers for these kinds of “arbitrary limits” that I can think of are “bad design” or “extremely weird requirements” (and having a lot of customers does not count as weird.)
Can anyone at Epic please comment on what has happened regarding this issue in the last 2 years with regards to “working with our developers for a long-term solution”?