Frontier, since 3.0 is not soon, pls put module, and material limits up now, thx.

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.
 
So tie a bunch of resources to a minor update, hindering the major release. Yes. People will love them for that. :D
(Sorry I don't want to sound dismissive of everything you say, it's just you have to see this through THEIR eyes, not yours)
 
OP's idea is not a bad one.
I guess the idea is so we can start saving up extra materials now ready for whatever upgrades we think we'll want.

From my point of view it would help as I have to keep throwing away stuff I collect. I'm pretty much at my materials limit already.
I'm not near any engineers at the moment and won't be for some time, but I currently am just ignoring any mats I could collect as I've nowhere to put them.
 
As far as I understood the (limited) feedback from fdev the reason for the delay in releasing 3.0 is they are still debating balance and other ramifications of some of the more signoficant changes to crime and punishment. This has been evidenced by sandro posting a proposal for reworking kill warrant scanner after beta had ended.

Assuming they are set on the engineering changes etc they could release 3.0 with crime and punishment changes inhibited? Or simoly tweak the storage capacities for modules to the 120, and materials and data to combined total of equivalent of 100 of each class?
 

Brett C

Frontier
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.

Developer time is better spent to have such code changes contained within a new version with a mass of changes rather forking out a new build of the 2.4 series in addition to ensuring the code works properly in the 3.0 series.

I don't want to sound rash, but there's nothing in our code that allows us to do 'handwavium-coding', or fork out a new build to live whenever we please. Everything is executed as per Jira tickets and overseen by team leads.
 
Developer time is better spent to have such code changes contained within a new version with a mass of changes rather forking out a new build of the 2.4 series in addition to ensuring the code works properly in the 3.0 series.

I don't want to sound rash, but there's nothing in our code that allows us to do 'handwavium-coding', or fork out a new build to live whenever we please. Everything is executed as per Jira tickets and overseen by team leads.

You guys accepting apps for team leads by chance? I might just be crazy enough if you are. ;)
 
Jira is written in Java and certainly the reason why ED is so wonderfully bug free. :p
sorry couldn't resist :x

One more reason to run Open Java... :D

But seriously, my Minecraft has never been better, never mind that I don't update it. There's no one behind the curtain. What are you talking about?
 
Last edited:
Developer time is better spent to have such code changes contained within a new version with a mass of changes rather forking out a new build of the 2.4 series in addition to ensuring the code works properly in the 3.0 series.

I don't want to sound rash, but there's nothing in our code that allows us to do 'handwavium-coding', or fork out a new build to live whenever we please. Everything is executed as per Jira tickets and overseen by team leads.

Not to mention they have to get a pass from MS and Sony to put anything out on console.
 
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.

It's not about easy or complicated or any such nonsense. It's a matter of contracts, signed deals and legal changes to an agreed upon change control process with Sony and Microsoft and probably a few others as well...

FDev don't have exclusive control over content any longer since the console versions were included in the game. So what you are asking for isn't as 'easy' as changing a number somewhere. It's requires a bunch of legal bull to make it happen, with signatures all round.
 
Elite: Dangerous for the Nintendo Switch. Get on my level...

Just kidding. But then again...

I hear one guy at Nintendo reprogrammed Sim City for the SNES from scratch just because he liked it and that's why it runs so well. Hats of to those folks for what they do when they're driven to it.
 
Developer time is better spent to have such code changes contained within a new version with a mass of changes rather forking out a new build of the 2.4 series in addition to ensuring the code works properly in the 3.0 series.

I don't want to sound rash, but there's nothing in our code that allows us to do 'handwavium-coding', or fork out a new build to live whenever we please. Everything is executed as per Jira tickets and overseen by team leads.

Sisyphus And The Rock. :(
 
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.

It would only take extra time. Updating a huge game like this, with all its numerous interacting systems, is not that simple.
 
Back
Top Bottom