by
RudgerWolvram
» 07 Mar 2015, 08:17
The first thing to remember about how LiF works is server-client communication.
The client "tests" first, then if it agrees, it sends the data to the server for verification.
What this means is on the client side, I change wardrobes to hold 1000 stone, but when i put that 501+ stone into it, the client says "yes that's allowed" then sends that data to the server. The server config says, no, wardrobes can only contain 500 stone, and you get a kickback on the client saying it's not possible.
And what all this means is for containers, the server and client must agree on the size of a container. So change the size serverside, then any client that connects must also have their objects xml file updated to reflect the serverside size change.
This is one of the many things that must be set serverside and clientside.
Serverside only example:
Can change the time to perform actions.
And very few others
Server and client side must agree examples.
Container size
Skill needed to perform action (i.e. uproot with only 0 forestry)
What buildings can be claimed
what terrain can be built upon
whether or not unflattened terrain is allowed for a construction
whether or not building can be constructed on paved roads (terrain type)
etc.