FAF Modifications Vault Rules

[armacham01]

"There is no way to enforce that rule so there is no point in making it a rule."

Would it be possible for the client to check the UI mods that are installed against the UI mods that are saved in the vault? For example, check hashes? Unless someone is going to hack the client it should be effective.

[PhilipJFry]

sure we could check but just cause a mod is not in the vault doesn't mean it's not ok to use

and even in such a case you could just edit a mod to have the name+UID of an existing mod in the vault so checking for that doesn't really help us

checking the hash doesn't really solve this either since users may edit mods to their liking as well

[Morax]

Anihilnine nailed it in that, just because we don't have the ability to detect it, it does not mean it's okay.

The point of the rule is to deter thinking it's alright to make something that gives an advantage.

It's better then saying nothing on the matter, right? What harm does it bring us to rule that ?

[armacham01]

PhilipJFry points out that right now we have the right to tweak existing UI mods.

If we uploaded the tweaked versions to the mod vault, everyone could use them. BUT we might not have permission to upload tweaked versions.

So in practice, we would be able to tweak the existing UI mods, but unless we got permission from the original creator, we could only use them for our own personal use in NON-ranked games only.

So we have two imperfect alternatives: nobody gets to use tweaked UI mods, reducing creativity, OR people get to use their own secret UI mods and get an advantage over others.

[Morax]

Why can't you test a mod before uploading to the vault?

You can create a test environment and tweak things without vault upload.

[nine2]

It is common for players to customize ui mods by editing script files.

If we made a rule saying you cant play with something unless it's on the vault, then people are not allowed to customize any more, which wouldn't be great.

Philip was saying in theory we could use file hashes to enforce ui mods to not be allowed unless on vault. However this would ban all tweaks so we dont like this idea. I dont think anyone has said it yet but rogue clients can sidestep this check anyway so you would only be policing 'the good guys'.

So. You could make a rule saying 'no ui mods allowed unless on vault. tweaking is ok unless you add an automated function that is not on the vault. in which case you must submit a new mod that overrides and upgrades the original mod.'. we wouldn't enforce with code because that would ban tweaks.

Doesn't seem great

[nine2]

Why can't you test a mod before uploading to the vault?

You can create a test environment and tweak things without vault upload.

I can test ui party vs AI offline. However I play ladder with upcoming versions to Really test them before I release them. Otherwise I will break players games with uncaught bugs. Therefore I want to be able to play with ui mods that aren't on the vault, for a little while.

It's not easy to make rules he

[Morax]

Hmmm, I really can't stress enough that people need to ask folks to help them test maps, mods, units, etc. etc. rather have this belief it's ineffective beforehand.

I realize that it's been okay in the past and up until now, but it just simply is not true.

I don't understand why a custom, unranked game will not expose bugs in modifications. Can someone explain why a live, ranked game is required?

[nine2]

because I dont have time for that

[Morax]

That's not a good excuse. I trust you, but for the integrity of rulings I ask you don't make that appear as a legitimate reasoning.