Factorio Forums

• Changes
  • The following settings are now settable only in server-settings:
    • allow_commands - default is "admins-only"
    • autosave_interval - default is 10
    • autosave_slots - default is 5
    • afk_autokick_interval - default is 0
    • auto_pause - default is true
  • Added /toggle-heavy-mode command. It can be used to generate files that help us to investigate server in a state where all new players get a desync loop.
  • Desync reports are now much bigger, but have bigger chance of being useful.
• Bugfixes
  • Fixed trains slowly moving forward when stopped on a signal (32733).
  • Hopefully fixed Lua desyncs caused by string formatting functions behaving differently on different platforms.

Use the automatic updater if you can (check experimental updates in other settings) or download full installation at http://www.factorio.com/download/experimental.

Hopefully fixed Lua desyncs caused by string formatting functions behaving differently on different platforms.

Awesome! This means we can use `%f` in `string.format()`?

the new lines for server-settings.json [edit] max_upload_in_kilobytes_per_second is broken. (map download stalls)

aubergine18 wrote:

Hopefully fixed Lua desyncs caused by string formatting functions behaving differently on different platforms.

Awesome! This means we can use `%f` in `string.format()`?

Depends on how they fixed it. The default lua implementation seems to use sprintf, which can use localization settings in certain cases. Dunno if factorio does the same, but there are all kinds of odds and ends with this on linux.

aubergine18 wrote:

Hopefully fixed Lua desyncs caused by string formatting functions behaving differently on different platforms.

Awesome! This means we can use `%f` in `string.format()`?

That's the idea.

The fact that you amazing people are able to get an update out on an almost daily basis is truly stunning.

I_LOVE_WAFFLES wrote:The fact that you amazing people are able to get an update out on an almost daily basis is truly stunning.

I really hate to tell you, but there is nothing stunning about - using standard regular modern software devleopment practices.

In modern software development, a build is fully automated. Check in - tests run. Want a deployment, trigger it - the rest happens automatically. Uploading it to a website is the trivial part - I know companies deploying software on dozens of servers automatically when the development teams want it.

Asking for password for the version checK?

Can you fix that? Up to .14.10 it did not happen. NOw I have to reenter the password every time I start - which is not nice.

TheTom wrote:

I_LOVE_WAFFLES wrote:The fact that you amazing people are able to get an update out on an almost daily basis is truly stunning.

I really hate to tell you, but there is nothing stunning about - using standard regular modern software devleopment practices.

In modern software development, a build is fully automated. Check in - tests run. Want a deployment, trigger it - the rest happens automatically. Uploading it to a website is the trivial part - I know companies deploying software on dozens of servers automatically when the development teams want it.

All we have left is to automate the bug fixing and feature development

TheTom wrote:I really hate to tell you, but there is nothing stunning about - using standard regular modern software devleopment practices.

In modern software development, a build is fully automated. Check in - tests run. Want a deployment, trigger it - the rest happens automatically. Uploading it to a website is the trivial part - I know companies deploying software on dozens of servers automatically when the development teams want it.

Can you share the blueprint for automated programming please?

TheTom wrote:

I_LOVE_WAFFLES wrote:The fact that you amazing people are able to get an update out on an almost daily basis is truly stunning.

I really hate to tell you, but there is nothing stunning about - using standard regular modern software devleopment practices.

In modern software development, a build is fully automated. Check in - tests run. Want a deployment, trigger it - the rest happens automatically. Uploading it to a website is the trivial part - I know companies deploying software on dozens of servers automatically when the development teams want it.

If only it were 'standard, regular'. The reality is that it's a massive undertaking to get existing projects working with a proper build and deployment system.

It's quite possibly the best time investment you can make, along with automated testing (unit/integration/whatever, anything is better than nothing). But don't pretend it's simple, easy, or fast. The vast majority of software is old, crufty, and not designed with 'modern' practices in mind. It's difficult to convince the bean counters that spending hundreds of man hours fixing parts a customer doesn't see is a good idea. It's very typical to just want more features, because features are easy to sell. Rarely is 'performance' a feature.

I'm not real happy with my current workplace, as it falls far to the terrible side of software development. If I knew before I started that they not only don't have source control, but don't even know that it exists, I wouldn't have taken the job. It's ridiculous. I've pushed them into using Git, but automated testing/deployment is gonna be a while... We only have one 'developer', and a couple business analysts that also look at the odd code related item. As that one developer it's also my job to: man the help desk phone for 300 users, update content on our websites, and fix all the SQL that the business analysts write. So I do helpdesk stuff for about two hours a day, website content for another two, and the rest I try to make progress on our hopelessly outdated software stack.

starholme wrote:

TheTom wrote:

I_LOVE_WAFFLES wrote:The fact that you amazing people are able to get an update out on an almost daily basis is truly stunning.

I really hate to tell you, but there is nothing stunning about - using standard regular modern software devleopment practices.

In modern software development, a build is fully automated. Check in - tests run. Want a deployment, trigger it - the rest happens automatically. Uploading it to a website is the trivial part - I know companies deploying software on dozens of servers automatically when the development teams want it.

If only it were 'standard, regular'. The reality is that it's a massive undertaking to get existing projects working with a proper build and deployment system.

It's quite possibly the best time investment you can make, along with automated testing (unit/integration/whatever, anything is better than nothing). But don't pretend it's simple, easy, or fast. The vast majority of software is old, crufty, and not designed with 'modern' practices in mind. It's difficult to convince the bean counters that spending hundreds of man hours fixing parts a customer doesn't see is a good idea. It's very typical to just want more features, because features are easy to sell. Rarely is 'performance' a feature.

I'm not real happy with my current workplace, as it falls far to the terrible side of software development. If I knew before I started that they not only don't have source control, but don't even know that it exists, I wouldn't have taken the job. It's ridiculous. I've pushed them into using Git, but automated testing/deployment is gonna be a while... We only have one 'developer', and a couple business analysts that also look at the odd code related item. As that one developer it's also my job to: man the help desk phone for 300 users, update content on our websites, and fix all the SQL that the business analysts write. So I do helpdesk stuff for about two hours a day, website content for another two, and the rest I try to make progress on our hopelessly outdated software stack.

Sounds like hell, you should have quit the job long time ago!

kovarex wrote:

starholme wrote:

TheTom wrote:

I_LOVE_WAFFLES wrote:The fact that you amazing people are able to get an update out on an almost daily basis is truly stunning.

I really hate to tell you, but there is nothing stunning about - using standard regular modern software devleopment practices.

In modern software development, a build is fully automated. Check in - tests run. Want a deployment, trigger it - the rest happens automatically. Uploading it to a website is the trivial part - I know companies deploying software on dozens of servers automatically when the development teams want it.

If only it were 'standard, regular'. The reality is that it's a massive undertaking to get existing projects working with a proper build and deployment system.

It's quite possibly the best time investment you can make, along with automated testing (unit/integration/whatever, anything is better than nothing). But don't pretend it's simple, easy, or fast. The vast majority of software is old, crufty, and not designed with 'modern' practices in mind. It's difficult to convince the bean counters that spending hundreds of man hours fixing parts a customer doesn't see is a good idea. It's very typical to just want more features, because features are easy to sell. Rarely is 'performance' a feature.

I'm not real happy with my current workplace, as it falls far to the terrible side of software development. If I knew before I started that they not only don't have source control, but don't even know that it exists, I wouldn't have taken the job. It's ridiculous. I've pushed them into using Git, but automated testing/deployment is gonna be a while... We only have one 'developer', and a couple business analysts that also look at the odd code related item. As that one developer it's also my job to: man the help desk phone for 300 users, update content on our websites, and fix all the SQL that the business analysts write. So I do helpdesk stuff for about two hours a day, website content for another two, and the rest I try to make progress on our hopelessly outdated software stack.

Sounds like hell, you should have quit the job long time ago and join us!

Fixed.

starholme wrote:It's difficult to convince the bean counters that spending hundreds of man hours fixing parts a customer doesn't see is a good idea.

Judging from a couple other games I play, it is also difficult to convince them about fixing parts that are glaringly obvious for the player to see, as well.

-- Smoov

starholme wrote:It's difficult to convince the bean counters

Ah yes - the ones who know the price of everything and the value of nothing!

Mooncat wrote:

kovarex wrote:

starholme wrote:

TheTom wrote:

I_LOVE_WAFFLES wrote:The fact that you amazing people are able to get an update out on an almost daily basis is truly stunning.

I really hate to tell you, but there is nothing stunning about - using standard regular modern software devleopment practices.

In modern software development, a build is fully automated. Check in - tests run. Want a deployment, trigger it - the rest happens automatically. Uploading it to a website is the trivial part - I know companies deploying software on dozens of servers automatically when the development teams want it.

If only it were 'standard, regular'. The reality is that it's a massive undertaking to get existing projects working with a proper build and deployment system.

It's quite possibly the best time investment you can make, along with automated testing (unit/integration/whatever, anything is better than nothing). But don't pretend it's simple, easy, or fast. The vast majority of software is old, crufty, and not designed with 'modern' practices in mind. It's difficult to convince the bean counters that spending hundreds of man hours fixing parts a customer doesn't see is a good idea. It's very typical to just want more features, because features are easy to sell. Rarely is 'performance' a feature.

I'm not real happy with my current workplace, as it falls far to the terrible side of software development. If I knew before I started that they not only don't have source control, but don't even know that it exists, I wouldn't have taken the job. It's ridiculous. I've pushed them into using Git, but automated testing/deployment is gonna be a while... We only have one 'developer', and a couple business analysts that also look at the odd code related item. As that one developer it's also my job to: man the help desk phone for 300 users, update content on our websites, and fix all the SQL that the business analysts write. So I do helpdesk stuff for about two hours a day, website content for another two, and the rest I try to make progress on our hopelessly outdated software stack.

Sounds like hell, you should have quit the job long time ago and join us!

Fixed.

Honest to god, if I was any good at c++ I would be applying. It's like a dream job. I'm a decent developer but all my skill lie elsewhere: Javascript and c#