Only client mod buf for all clients. How can I do it?

[Maris]

For example, I have a mod that fix some bug on clients. It may be a bug of another mod.

So clients should be able to install my mod manually if they want it.

However host should be able to share my mod for all clients.

 

 

This does not work:

all_clients_require_mod = trueclient_only_mod = true

(mod is disabled on clients even if host have it)

 

Upd: mistype in the name of the topic. I mean: Only client mod but for all clients.

Edited January 21, 2015 by Maris

[Maris]

Should I publish 2 versions of my mod? (for server and for client)

[rezecib]

@Maris, The only thing client_only_mod = true does is make it so that if people are only using mods with that set, it doesn't mark their server as modded.

 

But I don't think all_clients_require_mod will do what you want (let it run as client for hosts who don't have it, but also give it to all clients for a host who has it).

 

Publishing 2 versions of the mod would work, but I don't think that's a nice solution... But I guess there aren't any other solutions.

[Maris]

 

The only thing client_only_mod = true does is make it so that if people are only using mods with that set, it doesn't mark their server as modded.

Actually client_only_mod = true prevents disabling a mod by host.

 

let it run as client for hosts who don't have it

I would like two things at the same time:

1) to run for clients if host has the mod.

2) to run for client if client has the mod and host has not (i.e. prevent disabling).

​ 

[Kzisor]

Actually client_only_mod = true prevents disabling a mod by host.

 

 

 

I would like two things at the same time:

1) to run for clients if host has the mod.

2) to run for client if client has the mod and host has not (i.e. prevent disabling).

​ 

 

There is currently no way to do both at the same time without publishing two mods. However I bet PeterA might find this topic interesting if you could give a working example of why you need such a setting.

[PeterA]

This is an interesting topic. I'd definitely be interested in hearing some more use cases for this beyond patching bugs (I'm not discounting the value of that though).

[rezecib]

Actually client_only_mod = true prevents disabling a mod by host.

Are you sure? I thought leaving both to false would still do this, but I guess I haven't made any mods that have neither set to true since the flags were added.

[PeterA]

Are you sure? I thought leaving both to false would still do this, but I guess I haven't made any mods that have neither set to true since the flags were added.

 

Yeah, if client_only_mod is set to true, the temp disabling is bypassed. In theory a mod with both flags set to false would be safe to leave enabled because that mod would be server side only mod and if it was written correctly, would do nothing on a client.

[Maris]

Yeah, if client_only_mod is set to true, the temp disabling is bypassed. In theory a mod with both flags set to false would be safe to leave enabled because that mod would be server side only mod and if it was written correctly, would do nothing on a client.

 

Peter, here I have an existing example of universal mod. Now it is divided on two parts:

1) Server side.

2) Client side.

 

The code is exactly the same. The only difference is:

all_clients_require_mod = trueclient_only_mod = false

​and

all_clients_require_mod = falseclient_only_mod = true

​Is it possible to publish it as one universal mod, without dividing? I'd like to make it permanently active and independent from user state (server/host or client).