Skip to content

Environment variable to update mods downloading Mods with mismatched base dependency. #553

Open
@earthserpent89

Description

@earthserpent89
docker run -d \
        -p 34197:34197/udp \
        -p 27015:27015/tcp \
        -e  UPDATE_MODS_ON_START=true \
        -v /home/factorio:/factorio \
        --name factorio \
        --restart=unless-stopped \
        factoriotools/factorio:stable

Stable server on version 2.0.15 is downloading mods with base dependency of >=2.0.18 when using UPDATE_MODS_ON_START=true environment variable. This causes a version mismatch preventing the server from starting.

0.078 Error Util.cpp:81: Failed to load mod "mining-patch-planner":
• mining-patch-planner
    • Dependency base >= 2.0.18 is not satisfied (active: base 2.0.15)

I discussed with one of the mod authors whose mod has the mismatch, and they claim the server should be able to differentiate which version of the mod to download from the mod portal based on the Dependency Base. What is happening behind the UPDATE_MODS_ON_START=true flag and can it be fixed to make sure stable base servers don't accidentally download mods with a mismatched base dependency?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions