if enabling or disabling a given mod Dependency management doesn't work in this case anyway. If you disable a dependency the interface won't complain or mark your dependencies as red until you press commit. So "tries to" is a nice description. Citing the change in a feature that that isn't ...

Knowing that you're trying to use SE+bobs, you'll likely have to do a lot of local edits anyway. At which point there's no difference to editing info.json yourself.

IIRC building a powerpole connects it to the global network, so you should be able to connect it to that

Maybe make update_connections or whatever its called work on mining drills? Then just let modders worry about updating miners. I assume its already a problem if you spawn some resources under existing mining drills that have ran out of resources.


For future reference, update_connections works ...

Perhaps you could have a count property like some of the other TechnologyTriggers so there is a maximum to reference to?

That might also be better served by converting LuaTechnology::saved_progress to a uint of the units researched/'used' by script, relative to num-research-units

I was able to edit and update the aforementioned licenses with just the links sent, while logged into my own mod portal account.

Bug report: pybugreports

Yes I have seen the other related issues, even so this is a rather egregious example.

04-26-2026, 22-14-55.png

Tested on v2.0.76 with experimental pYmods. I'm guessing that it's caused by efficiency not being taken into account. It consumes 5.71MW of power, with each ...

Just to confirm, does this still work with the resolution to viewtopic.php?t=128129 ?

Better tile placement rule options, or using them more creatively, would be a better solution than 'just add more collision layer slots'

They're tangentially related ideas, all of this was the result of not being able to make alerts that last longer. I'm working on adding more 'in your face' notifications to the beacon interference mechanic in pY, which necessitates alerts. Short alerts is fine when you're actively building, but for ...

As in title, I'd like to be able to use a LocalisedString instead of a plain string for the label property when adding pins to the player.

I'd like to create a custom alert that is persistent, only disappearing when it's manually removed via script. Similar to how certain alerts, like logistic network notifications, are persistent until fulfilled.

I'd like to be able to have the placement visualization properly support rotating when the entity is rotated in the cursor. It rotates to the correct offset from the entity but the sprite itself does not rotate. For example, if I have an arrow sprite under crafting machines, I want it to rotate to ...

I'd like to be able to use any SpritePath for custom alerts, instead of just a SignalID. It's more convenient to create a sprite for both the in-game rendering and the alert, instead of a virtual signal just for the alert.

+1

That's fine, it just makes things simpler for mod developers.

I would like to be able to create alerts for an entire force, without having to iterate over force.players. This would also solve the issue of players joining late and not having existing alerts. Ideally, it would be a set of methods on LuaForce that mirror the alert-related methods on LuaPlayer ...

As in title, I want to be able to disable the rocket part storage mechanic introduced in 2.0. The prototype property `rocket_part_storage_cap` has a minimum value of whatever `rocket_parts_required` is, meaning you can't allow partial or zero storage. Ideally, setting this to zero would disable the ...

+1

I want to be able to override the built-in system of tech numbering, without having to set localized_name or localized_description on the prototype. Ideally, the default behavior looks for an exact match in the locale, then searches for a non-numbered entry. Ideally, this also applies to both the ...