KiwiHawk wrote: Sun Aug 10, 2025 9:51 pm

1. Recipe localised_name
2. Recipe name
3. Recipe main_product 's localised_name
4. Recipe main_product 's name

This, exactly. +1

+1

This is not "I'm not great at the game and can't work around problems" this is "How about this feature that is somewhat useful in SA but can be very useful in modded runs"

+1

Another +1: Caravans from pYmods. It already has all of the train features implemented, including stop conditions and interrupts, but the sheer UX of making a schedule properly prevents it from being a good scaleable option.

+1

A couple of relevant issues with pYmods have been loosely connected. Circuit signals in 2.0 can act strangely, at least to the uninformed user. Currently, the recipe and item signals are only merged IF they have the same name internally. I don't know if there are other requirements, but that seems ...

For an actually helpful answer,

Energy sources as a separate entity prototype, that then connect to a 'linked energy source' for a specific entity, just like one connects linked belts, containers, and pipes. This energy source then provides power for that entity, with all of the normal restrictions ...

TL;DR
Add minimum temperature as a generator property

What?
As in title. Currently only supports maximum temperature, even though both are supported in the actual fluidbox. The other half of this request, why it's being added as a separate property, is so it can be shown on the tooltip ...

Thanks for the reply, wasn't quite sure what was causing it but that explanation makes sense.

+1

I was working on some TURD scripts for pY when this error ocurred. This error is completely reproduceable on my machine.

Mods were all pYmods from the repos (master branch, not yet on portal), the fork of AlienLife where I was working, FMTK Debug Adapter, Enable all Feature Flags, flib, and Recipe ...

1000% yes, please

I've been wanting to do more with beacons (particularly for nonstandard beacons) but these issues, especially the latter one, have stopped all of my attempts.

Oh nevermind, i just realized why it wasn't working. adjustable_belt_stack wasn't properly enabled.

Apologies, some script had been obstructing my view of the issue.

Using a script to change the value of the override stack size causes an error. That's the issue, not it quasi-working.

Recipes that do not have item ingredients (i.e. only fluid or no ingredients) cannot produce non-normal levels of quality items. This is counterintuitive. I understand that the GUI prevents doing this because it would be immensely powerful, but even when the recipe and quality are set via script ...

As in title. A loader prototype with the flags `wait_for_full_stack` and `adjustable_belt_stack_size` will not throw an error, even though adjusting the stack size is not doable in-game but waiting for the full stack is. This is counterintuitive, as the game accepting these values implies that they ...

+1

Asking for events is much more freeing than asking for a very specific implementation detail that is more likely to be overlooked. +1 to the events.

Osmo wrote: Sun Jul 13, 2025 6:43 pm +1, the latest suggestion would basically function like extents do already, and no one seems to have problems with them this part of their impelmentarion

Actually yeah, I hadn't thought about that. Extents function in exactly the same fashion.