Skip to content

Services request: Patch client against target server #273

Description

@Kheartz

(Just so this is tracked)

Client patcher is great! Though I was wondering--given a server version, provide the most compatible client patch. This should hopefully prevent server owners from having to constantly keep up their servers up-to-date when FW is updated and make sure they're not hit with regressions that are out of their control.

Activity

  1. zpl-zak commented on Sep 2, 2026

    @zpl-zak
    Member

    Thank you. Yeah, we definitely also need to figure out server patching as well.

  2. Segfaultd commented on Sep 3, 2026

    @Segfaultd
    Member

    I have modified the versioning system to allow for minor patches to still work. Now, only the major patches will generate incompatibility.
    We will think about server auto updater yes

  3. Kheartz commented on Sep 3, 2026

    @Kheartz
    CollaboratorAuthor

    Thanks. Unless I misunderstand, I think this might not be sufficient?

    Server owners might want/need to stay on a specific server version for a long period, and during this period several major bumps could be released? If Framework or mods bumps major versions (to support new wire formats or even API breaking changes), they'd need to address the fixes immediately--since all of this happens outside of a timeline they control.

  4. Segfaultd commented on Sep 3, 2026

    @Segfaultd
    Member

    Latest changes cover exactly that usecase. They will break compat on wire mismatch.

  5. Kheartz commented on Sep 3, 2026

    @Kheartz
    CollaboratorAuthor

    But are users/clients still forced to latest version (even if it includes a wire mismatch)? If that's still true, that's the point I'm trying to make.

    1. Server has FW version 18 and 100 resources to maintain (or mod has version 2.0)
    2. Server releases FW version 19
    3. All clients update to FW 19
    4. Clients can't connect to server
    5. Server owners have to scramble to update their server and update potentially 100 resources with breaking changes so that users can jump back in the server

    is the main scenario I'm thinking of avoiding

  6. Segfaultd commented on Sep 3, 2026

    @Segfaultd
    Member

    Per your scenario, if everyone update to FW 19, then there is no mismatch anymore and everyone can connect.

  7. Kheartz commented on Sep 3, 2026

    @Kheartz
    CollaboratorAuthor

    Updating and fixing breaking changes could take time, people need to test their resources against the new versions, etc...All while their server is meant to be "in-production". If this happens at like the middle of the night, their server is forced to shut until they address all of these issues.

  8. Segfaultd commented on Sep 3, 2026

    @Segfaultd
    Member

    This is why most of the releases should go the "minor" patch way.
    We will later offer options to deny an automated update tho.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions