---------------------General Operation--------------------------

	1) Overview
Pick a floodgate or a valve and rename it (yes, now you can!) if u make its name start by "eaf_" (like EzAutoFloodgate) then it will be taking into account by this mod.
The next step is to bind some Automation element to it. 
These Automation elements will define the value of height or amount of liquid for the floodgate or valve they are bound to.


	2) The binding
The binding is done simply by using the name of the involved elements.
First you must choose a unique group name.
Then you will rename the element you want to control (which must be a floodgate or a valve) with the prefix "eaf_" followed by the group name.
To bind an automation element to that controlled element just name it with the "eaf_" prefix followed by the group name and finish by the suffix "_" followed by the desired value multiplied by 100.

When the state of one of one of these automation elements changes (i.e. it switches from on to off or vice versa) the mod will use the first automation element of the group which it found to be on and will set the height/flow limit of the controlled floodgate/fill valve/throttling valve   


example : 
if you name the floodgate "eaf_something" then any automation element named "eaf_something_25" will set its height to 0.25 (considering no other automation element of the eaf_something group is on or that eaf_something_25 was the first found on in the group).

Please note u shouldn't use invalid values (for example u can see in the UI the height of the floodgates have a step of 0.05 so u must only use multiple of 5 as value for the automation elements which control it : if for example u have a group named "example" controlling floodgates then avoid having having an automation element named eaf_example_37 choose either eaf_example_30 or eaf_example_35 to respect the values allowed by the UI)





---------------------Control multiple at once--------------------------

You can have multiple controlled elements in a group but they must all be the same type (i.e. you have to keep floodgate in a group containing only floodgates (and automation elements), and the same thing is true for "throttling valves" and for "fill valves" : they all must be seperated from each other).
As each name prefixed with eaf_ must be unique, another prefix is used : @ . After that arobase (that the french name for "at sign", I will use it here as it's a single word so it's more handy) you can add anything you want as long as the resulting name is unique. Note though that the arobase part itself doesn't have to be unique : no issue with having an element named eaf_group1@another and another element named eaf_group2@another.

So with the previous example, you can have a second floodgate which will follow the same "memory" made of multiple automation elements, you just have to name it "eaf_something@another" and you can add as many as you want by changing the arobase part (eaf_something@hello or eaf_something@world...)
