More Quality Scaling

by sh4dow

Extends quality scaling to locomotives, wagons, storage tanks, rocket silos, roboports and more.

Content
a month ago
2.0
4.49K
Transportation Logistics Trains Fluids Logistic network Storage

b Crash on_robot_built_entity

8 days ago
(updated 8 days ago)

https://mods.factorio.com/mod/quality-heat-pipes/discussion/68abc678be902c893e4b93c0
The mod More Quality Scaling (1.4.5) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event more-quality-scaling::on_robot_built_entity (ID 17)
The mod More Quality Scaling (1.4.5) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event more-quality-scaling::script_raised_built (ID 90)
The mod Quality Heat Pipes (1.1.2) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event quality-heat-pipes::script_raised_built (ID 90)
Unknown entity name: epic-epic-epic-heat-pipe
stack traceback:
[C]: in function 'create_entity'
quality-heat-pipes/control.lua:15: in function <quality-heat-pipes/control.lua:1>
stack traceback:
[C]: in function 'create_entity'
more-quality-scaling/control.lua:347: in function <more-quality-scaling/control.lua:275>
stack traceback:
[C]: in function 'create_entity'
more-quality-scaling/control.lua:347: in function <more-quality-scaling/control.lua:275>

7 days ago

This mod already has an option to increase heat pipe range, so using another mod with the same feature should be unnecessary.

The crash itself seems to demonstrate some interesting behavior when entities with multiple quality prefixes are available - namely, that my mod tries to place the entity with the most prefixes of the correct quality.
In general, this may be a good compatibility feature (albeit not implemented intentionally), since it applies all installed quality tweaks that use this prefix format independently of the load order - though only if the other mod does sanity checks before doing their replacement.
On the other hand, this invalidates the assumption that prefix entity generation and prefix entity replacement work consistently - so perhaps it would be safer to limit replacements to once per entity (could be cached per tick; though in the case of delayed replacement of belts with identical prefix formats, this crash would be significantly harder to fix)...

7 days ago

i did see some Reporting that over at that mod page. also saw your had that feature so that mod was deleted to us this mod instead anyway.

7 days ago

Still Thanks.

New response