You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is simple.
Anyone who knows how it works can change the version and force (if they have the same mods but not the same configs) to enter the server.
By adding a guid to the version that is the same between server and client but which is updated every time by the modpack creator, this problem is prevented since the end user cannot and should not know the guid entered on the server.
Also it is possible to update the mod for 1.19.2 I would need it for my server.
The text was updated successfully, but these errors were encountered:
How exactly would you provide the the guid between the client and server then? Cause if the pack author just puts it in the config file, or in any readable/writable file, what prevents a player from just keeping a list, and just cycling through them as needed. Also, as modpacks aren't necessarily updated too often, the guid might be correct for several months/indefinitely. It would run into the same issue as the version number, just changing it till it works.
While the guid idea is a good idea, I can't think of any good way to implement it without allowing people to get around it trivially, though I don't know everything. Am I missing something?
Feature Description
The problem is simple.
Anyone who knows how it works can change the version and force (if they have the same mods but not the same configs) to enter the server.
By adding a guid to the version that is the same between server and client but which is updated every time by the modpack creator, this problem is prevented since the end user cannot and should not know the guid entered on the server.
Also it is possible to update the mod for 1.19.2 I would need it for my server.
The text was updated successfully, but these errors were encountered: