Open Modular Turrets

Added

• Holding a turret next to a turret base where it cannot be placed shows a short reason next to the red outline (block in the way, wrong side, base tier too low, base full, too many of this turret), as on 1.20.1+
• Config option turrets.dropTurretsOverMaxSimultaneous (default false): attached turrets over their type's maxSimultaneous drop, e.g. after the limit was lowered (as on 1.20.1+)
• Turret bases, their turrets and OMPD's hardened blocks/walls/fences without an owner sparkle green, and WAILA/HWYLA and The One Probe show "Owner: nobody (right-click to claim)"; right-click claims them (OMLib), as on 1.20.1+
• The owner of a turret base can disown it ("Disown" in its configure screen, after a confirmation, as on 1.20.1+); the trust list is cleared and anyone can claim it
• While you hold OMLib's Ownership Wand, turrets still target and fire at you, but their shots, explosions and effects do not affect you (as on 1.20.1+)

Changed

• A broken turret base scatters its items like a chest
• Only admins of a turret base can attach turrets to it (the placement label says why otherwise), as on 1.20.1+
• Hoppers and pipes can no longer take ammo out of a turret base, so nobody can disarm someone else's base with them (as on 1.20.1+)
• The jar files are named openmodularturrets-<version>-mc1.12.2-forge.jar (Minecraft version with mc, as on 1.20.1+)
• The server sends its config values (openmodularturrets.cfg and openmodularturrets_addon_turrets.cfg) to clients when they join, so tooltips, the ammo slots and the turret placement outline follow the server's rules; after leaving, the client uses its own config again
• Turret bases without an owner (e.g. placed by a machine or a structure) no longer drop themselves; they stay inert until claimed, unless bases.unownedBasesActive is set (as on 1.20.1+)
• Turrets can be attached to a turret base without an owner only by players who may use command blocks (operators in creative mode, mapmakers)
• Requires OMLib 4.0.0-beta.2 or newer

Fixed

• A turret base placed without saved data (e.g. by /setblock or a structure) with turrets already attached no longer starts with range 0; it starts at the range of its shortest reaching turret (as on 1.20.1+)
• Turrets added by other mods could not fire slower than every 20 ticks (their config clamped baseFireRate to 20)
• Decimal settings of turrets added by other mods (damage amp, upgrades, recycler chances, accuracy deviation) were not limited to their range
• The config ranges of baseFireRate (now 1–200 ticks) and baseAccuracyDeviation (0–100 %) did not include the turrets' default values
• Boxes in the turret logic compared 0.0 and -0.0 as equal while hashing them differently
• Computers (ComputerCraft, OpenComputers) could not change access levels: changeAccessLevel / changeTrustedPlayerAccess and addTrustedPlayer with a level reported success but changed nothing
• OpenComputers: setTurretYawPitch rejected valid angles and used the side as yaw, forceShootTurret did not check the side, side 6 counted as the bottom, addTrustedPlayer without an access level failed, getTrustedPlayer returned nothing for unknown players
• Turret base GUI actions (range, mode, targeting, dropping) were handled for unloaded or far-away bases, which could load chunks; they now need the base loaded and the player within reach
• Tooltips and the turret placement outline used the client's own config instead of the server's
• Other mods asking a turret without base (or with its base in an unloaded chunk) for its stats crashed; such a turret now reports its configured values and targets nothing
• The maximum range shown in the turret base GUI also counted turrets mounted on a neighbouring base
• Turret bases could create their tile entity on the chunk render thread (camouflage light settings), which can crash or corrupt the world
• Cranks and generators did not turn with rotated or mirrored structures