The update to 9.4.2 broke the dependency for ATO. I posted on that page as well.

I am unsure what this ATO is referring to?

EDIT: Oh, I'm guessing it's All The Overhauls Modpack? I've heard that one referred to as ATOM, not just ATO, mb.

I do remember getting a report about that on an unrelated thread, and one of the posters there mentioned this:

For the record, you've nailed it on the issue with ATOM. It basically turns the mini assemblers into the electronics assembly machines from Bob's mods (higher speed, smaller footprint, but limited recipe selection), so it depends on not just the old functionality but a fairly specific set of settings within it.

They need to either set the dependency to the previous version of mini machines (v9.3.28), or they're going to have to update the code that references any mini machine recipes or removed settings. Any balancing changes made to the entities themselves are fine (though they might also have to unhide the entities from the factoriopedia, since I have them hidden, to make it easier to check the modified stats)

They need to either set the dependency to the previous version of mini machines (v9.3.28)

We did; OP must still be on an old version.

I've been thinking it might be better for ATOM if we pull the miniaturization code out into a library and depend on that instead of the dependency on this mod. Not because there's anything wrong with this mod, just that you're taking it in a direction that's different from what ATOM is using it for.

And also it will reduce the incidence of posts like this.

Yes. Just began a playthrough with ATOM installed, and have to put it on hold for now. Glad this post was noticed, and in reference to the other topic. KEEP UP THE GOOD WORK!

I've been thinking it might be better for ATOM if we pull the miniaturization code out into a library and depend on that instead of the dependency on this mod. Not because there's anything wrong with this mod, just that you're taking it in a direction that's different from what ATOM is using it for.
And also it will reduce the incidence of posts like this.

I feel kinda bad about this, I didn't realize other mods were depending on the functionality being the way it was (especially since I considered the old recipe requirements as more of a stopgap measure, until figuring out how to implement them properly)

I'm looking at re-implementing the legacy code (which shouldn't be too difficult to trigger based on a setting, and the new runtime functionality can be disabled based on that setting as well)

That should give a safe upgrade path for ATOM to allow newer versions of mini machines (by having a settings-update that forces the legacy setting within mini machines)

<3

Just uploaded a version of mini machines that should work with ATOM again, with some very minor changes from their end (undoing the minimum version requirement, removing the mini-micro-settings incompatibility, and adding one line to settings-updates change_setting("mini-legacy-code", true)))

I've also posted it up on their discord for additional visibility, hopefully they should be perfectly compatible again

EDIT: ATOM v2.2.7 is now compatible with the latest version of Mini Machines (v9.4.3), and theoretically, all future versions

dependency on core mod is still on 2.0.0 while current update is 2.0.3 SORRY I feel like I'm hounding this issue for my selfish desires...

That must have been one of the last things I did, because it was already set that way in my unzipped copy of v9.4.3, but somehow wasn't in the zipped copy on the portal. Anyways, implemented the fix in v9.4.4, now requiring at least v2.0.3