AnimatedArchitecture

# AnimatedArchitecture (https://jitpack.io/v/PimvanderLoos/AnimatedArchitecture.svg)](https://jitpack.io/#PimvanderLoos/AnimatedArchitecture) AnimatedArchitecture is a plugin for the Minecraft server mod (https://spigotmc.org). Its aim is to enhance your server with animated blocks that can be used to create many kinds of animated architectural structures. AnimatedArchitecture is a rewrite of the old BigDoors plugin. You can find the legacy BigDoors plugin (https://github.com/PimvanderLoos/BigDoors/). ## Preview (https://img.youtube.com/vi/45TwFLBv8yY/0.jpg)](https://www.youtube.com/watch?v=45TwFLBv8yY)<br> (Click the image to go to YouTube and watch the video) ## Supported structure types The following structure types are currently supported: - Big Doors - Clocks that display the in-game time - Drawbridges - Flags - Garage Doors - Portcullises - Revolving Doors - Sliding Doors - Windmills ## Using AnimatedArchitecture ### Requirements: * Java 21+ * A Spigot server (or a fork of Spigot) for Minecraft 1.20+ * Vault ### Installation: * Grab the files of the latest (https://github.com/PimvanderLoos/AnimatedArchitecture/releases). You will need to grab the `AnimatedArchitecture-Spigot.jar` file. * Place the `AnimatedArchitecture-Spigot.jar` in the plugins directory of your server. * (Re)start your server. * Optionally, configure the plugin to your liking by editing the config files in the newly generated `AnimatedArchitecture` folder. ### Importing BigDoors' Database As of (https://github.com/PimvanderLoos/BigDoors/releases) Alpha 0.1.8.44, BigDoors has a command that allows you to export the old database to the new format. Newer versions may contain additional improvements to the export process, so it is recommended to use the latest version of BigDoors to export your database. While running a supported version, you can run the `BigDoors PrepareDatabaseForV2` command <b>in the console</b> to export the database. Read the output in the console to see if everything was exported correctly. Running this command does not affect the existing database for BigDoors. After the export process has completed, you can copy the new `structures.db` file out of the `BigDoors` folder into the `AnimatedArchitecture` folder. You will now be able to use the structures you created in BigDoors! Please note that the export process may not always produce a perfect conversion, potentially leading to minor inconsistencies, such as incorrect opening directions under certain circumstances. Despite these occasional discrepancies, the majority of exported structures should function properly. Any errors can be easily rectified in-game using available commands or the menu. ## Add-ons - (https://modrinth.com/plugin/animatedphysics) (Created by bonn2) It adds collisions to the animated blocks! ## Translations ### Official translations Official translations are managed through (https://hosted.weblate.org/projects/AnimatedArchitecture/): <a href="https://hosted.weblate.org/engage/AnimatedArchitecture/"> <img src="https://hosted.weblate.org/widgets/AnimatedArchitecture/-/multi-auto.svg" alt="Translation status" /> </a> ### Custom translations By default, the plugin will use the messages from `localization/translations.bundle`. This file is regenerated every time the plugin restart, so please do not edit this file manually. All translation keys used by the plugin are also written to a `localization/translations.properties` file.</br> When you provide one or more keys with a value, the plugin will create a new file the next time it restarts: `localization/translations_patched.properties`. This file contains the same data as the 'base' bundle, except for any lines you changed in the properties file.</br> To put it simply, you can override any of the official translations using the properties file. One thing to keep in mind when trying to override translations is that it respects the locale entry. This means that the `translations.properties` file only overrides the base localization messages. The way the localization system works, is that it first tries to get the translated message from the locale defined in the config, and, if that does not exist, from the base localization file. For example, if you set the locale to `nl_NL` (Dutch) in the config, the plugin will try to retrieve messages from `translations_nl_NL.properties` first. If no value is provided for the key the plugin is looking for, it will try the `translations.properties` file next. So, if you have set your locale to `nl_NL` in the config and want to override the default translations, follow these steps: 1) Copy `translations.properties` to `translations_nl_NL.properties`. 2) Apply the changes you wish to make. * You can check the files in `localization/translations.bundle` to see the current translations. 3) Restart either the server or the plugin. * Y