Skip to content

min_mta_version 'server' is not working as expected #3852

@Fernando-A-Rocha

Description

@Fernando-A-Rocha

Describe the bug

You can start a resource that has a minimal server version that is higher than your server's. This should not be possible. The server should not be able to start a resource that clearly states that it was designed for a more recent server version.

Steps to reproduce

  1. Launch MTA server version 1.6.0-9.22746.0 for example
  2. Create a resource and set its minimum server version to a higher build
<meta>
    <min_mta_version server="1.6.0-9.22789.0"/>
</meta>
  1. Start it: notice that resource starts normally; it shouldnt!

Version

Tested on 1.6.0-9.22746.0. Likely has been like this for years.

Additional context

Developers create resources that are meant to be used in servers that are a certain version or higher. This feature is what they use, it seems broken.

On the other hand, min_mta_version "client" seems to be working correctly. It updates the server's minclientversion to the highest min_mta_version "client" provided by resources. It only lets players join with that minclientversion version or higher.
Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions