Edit Only another 5957 to go to the Double hehe !
I do not want to disappoint you but "Double" does not come with 2 * 6000
I do not know exactly but to be a "Double", you have to do, much, much more ...
Good luck
Last edited:
Edit Only another 5957 to go to the Double hehe !
Apologies, but where have they said 3.0 is going to be delayed?
Jira is written in Java and certainly the reason why ED is so wonderfully bug free.
sorry couldn't resist :x
Changing mat limit from 1000 to say 4000 and data from 500 to 2000 surely isn't a client update. The OP isn't asking for 3.0 right now, just increased limits.
We don't need per mat storage right now, just increase the existing limits. Give a reason for some to play up to the 3.0 launch.
wait, what? the storage limit per commander is "Code" ?
its not a single number somwhere in a database?
Correct me if I'm wrong but isn't the limit going from - limit of total materials - to - limit of each material?
This would require new code.
why do we have to wait, you know your going to do it, the module storage is just changing some number in a database from 60 to 120 or whatever. i really wish we could get more incremental upgrades than 1 big one every quarter of a year.
sorry, i did reply in context of the opening post, not the threat title:
there is no word of material storage in there
Edit:
Bah, misread your post.
Anywhere, it seems to me that putting the module limit count on the server side means that the client has to ping the server and request the limit value. That would be a ridiculous way to go about it, when you can just store the value on the client. You could do the lookup once on startup, rather than every time, but it's still much more complex than doing it client-side.
they could impliment the easy stuff, like module limits etc, before the harder stuff, and as to a reason, oh i dont know, how about to just be nice to those waiting, how about that as a reason.
Changing mat limit from 1000 to say 4000 and data from 500 to 2000 surely isn't a client update. The OP isn't asking for 3.0 right now, just increased limits.
We don't need per mat storage right now, just increase the existing limits. Give a reason for some to play up to the 3.0 launch.
What makes you think that there are not already such tools?Then you’d have people writing trainers to increase or remove the material cap on the client after the initial lookup.
What makes you think that there are not already such tools?
Jira is only a tool for logging bugs and features requests, it's not the cause of the bugs - they have programmers for that( just like every software house ).
As a programmer ( not in gaming ) I blame the QA team![]()
The curse of a developer is that if they do their job well enough, it looks easy to the customer and they begin to make demands that aren't actually as easy as they appear.
I know it happens to me. I've been told as much as late as last week even.