Mentioned it in the portal, but I know things can get hidden there. Assembler Assay's mod portal link in the OP of this thread is broken, but the main thing I wanted to report, don't know if a solution is possible: Assembler Assay conflicts with Production Scrap 2. "data_final_fixes.lua: 179: a...

It definitely appears to be 'fixed'. After updating Rampant, I was soon swarmed by biters in my current game. Looks like I'll be rolling back to an earlier save(I think about six hours earlier) to avoid being overextended to the point where I prematurely poked the bear. It was rather amusing watchin...

Thanks for the absurdly fast response! Always a good idea to update drivers. Turns out Windows Update was misbehaving. I was stuck in an 'update and restart' loop which took a while to get through. Once it finally properly installed the update, everything was hunky dory again.

I've been playing a heavily modded setup with no problems until Windows 10(64-bit Pro) decided to update today. Now it crashes while going through the bootup screen. Initially that was on 0.16.50, I did a 0.16.36 install as well. Don't know how to disable mods without getting to the main menu or I w...

using underground belts to compress belts was not intuitive but to eliminate that and side loading and then go on a rant about how bots were OP and everyone was using them? Ridiculous. If I can't compress a belt using inserters or side loading, then there is no point in using them. This breaks so m...

Sorry for the duplicate post, edited wrongly.

Updated for 0.16 compatibility. Only very limited testing done but it at least survives a brief bit of gameplay with 0.16.16 both by itself and as part of a larger mod package. If any further errors are found please let me know and I'll attempt to resolve them. I make no claims, implied or otherwhis...

Resolved this particular issue in a rather dumb way: progress in the form of Factorio actually trying to load now after processing the mods. I'll add on to this thread if I find any more issues I can't resolve. Anyway, turns out that my mistake was trusting the error message that called it 'Trival s...

Thanks for the reply. If I'm understanding correctly though, "vented smoke" is the prototype name. "smoke" is the prototype type . Either way, changing from "Trivial smoke"(as the error message itself suggested) to "Trivial-smoke" made not the slightest bit of...

Full disclosure: I am attempting to make an existing mod(Wear and Tear) usable with 0.16; the author has not been around for some while and I am not attempting any changes to the features, just making it functional with the new version. I have managed to deal with a number of errors, but the latest ...

Thanks for Bot Servicing, I'm also a fan of Global Warming. Sensible stuff like that which adds to the things the player must contend with is great for Factorio.

Seconded. I'd like to add this to a long game I'm planning for when 0.16 becomes stable. Would be a great, appreciated addition.

I do believe it, and I think it's clearly just a difference of degree. Any tweak to long-standing features is going to make people not be able to play the way they've been playing. Research Revolution invalidated significant parts of long-standing research setups. I think Factorio is much better off...

Any change will potentially drive people away. That by itself is not a good argument in favor of not changing it. Any creative process that has this is a primary concern is going to become stagnant, and how many people the game attracts in the future is going to be based largely on how good the game...

They are. Also FWIW, I tried changing the version number listed in the mod and got the following on game loadup with it enabled: "Error while loading entity prototype 'belt-overflow-indicator'(simple-entity): Key 'icon_size' not found in property tree at ROOT.simple-entity.belt-overflow-indicat...

Just wanted to say that I've love this idea(tried and wasn't able to implement, coding skills not good enough) and would love to see it in 0.16 if you are willing to update it(if it even is something that needs updating?)

You get the satisfaction of having completed the challenge. People play games for different reasons. Some people like 'challenges' or 'house rules' to spice things up and not make every playthrough the same.

By default, they will expand and attack eventually. Pollution makes it happen a lot faster, but it isn't required. I've literally just let the game run after startup, and it took hours but eventually they killed me without me doing anything(didn't move, mine, build, nothing).

It seems to me that people who suggest this do so to increase realism- without ever considering the crippling impact this would have on gameplay. Alternatively, perhaps they have considered in the impact on gameplay and don't think it's crippling. In terms of, as you put it, 'logistical nightmare' ...

It seems to me that for this kind of thing it would be a lot easier to just not do it than to code it that way. I.e., if you don't want to be able to build anything on ore ... don't build it there .