Download the latest dev-build HERE. If you decide to use it, there are a few things you'll have to keep in mind:

• Dev builds will always notify you of the latest stable release as soon as it's available regardless of your settings.
• These builds might not be tested as thoroughly as the release builds.
• Dev builds may not always be backward compatible with the latest release build. This can occur if the database schema is changed in a dev-build for example (then the old version can no longer read the data). So be sure to make backups!

An updated list of the changelog can be found HERE.

When opening doors from the console/command block, NAMES DO NOT WORK! You need to use DoorUIDs there. Why? Because names are not unique, while DoorUIDs are. This constraint means that your command blocks won't break when someone creates a new door with the same name as the one you used.

bigdoors.own.<numberOfDoors>
Sets the maximum number of doors this group can own. Replace <numberOfDoors> by the actual number of doors. e.g. "bigdoors.own.4".

bigdoors.user.gui
/BigDoors, /BDM
Allows you to access the BigDoors GUI.

bigdoors.user.createdoor.<type>
Supported types: "door", "drawbridge", "portcullis", "slidingdoor", "flag".
/NewDoor [-BD || - PC || -DB] <DoorName>
Initiate door/drawbridge creation process. Use "-BD" to initiate the big door creation process, "-PC" for portcullis, and "-DB" for drawbridge. Defaults to big door.
/NewPortcullis <PortcullisName>
Initiate the portcullis creation process.
/NewDrawbridge <DrawbridgeName>
Initiate the drawbridge creation process.

bigdoors.user.base
/SetBlocksToMove <doorUID> <blocksToMove>
Sets the number of blocks this door will try to move. Only applies to doors such as portcullises and sliding doors.
/SetDoorRotation <doorUID> <direction>
Changes the direction a door will try to move.
/NameDoor <doorName>
Sets the name of the door when you're in a door creation process.
/BDCancel
Cancel object creation process.

bigdoors.user.deletedoor
/DelDoor <DoorName>
Allows you to delete a Big Door.

bigdoors.user.toggledoor
/OpenDoor <DoorName> [DoorName2] ... [DoorNameX]
Allows you to open a Big Door (of any type). Also allows opening more than 1 door at a time.
/CloseDoor <DoorName> [DoorName2] ... [DoorNameX]
Allows you to close a Big Door (of any type).
/ToggleDoor <DoorName> [DoorName2] ... [DoorNameX]
Allows you to open a Big Door (of any type) when it is closed or close it when it's open.

bigdoors.user.listdoors
/ListDoors [Name]
List all doors owned by you, with a specific name if provided.
Console: /ListDoors <DoorName || PlayerName || PlayerUUID>
List all doors with a given name (and who owns them) or all doors owned by a player (PlayerName can only be used for online players!).

bigdoors.user.doorinfo
/DoorInfo <DoorName>
Allows you to get information about a given door.

bigdoors.user.relocatepowerblock
/ChangePowerBlockLoc <DoorName>
Allows you to change the location of the powerblock of a given door.

bigdoors.user.inspectpowerblock
/InspectPowerBlockLoc
Gives you a tool that gives you the door info of any powerblock you hit with it.

bigdoors.user.addowner
/BigDoors AddOwner <doorUID> <playerName>
Adds another user as an owner of the given door.

bigdoors.user.removeowner
/BigDoors RemoveOwner <doorUID> <playerName>
Removes another user as an owner of the given door.

bigdoors.user.setclosetime
/SetAutoCloseTime <doorUID> <autoCloseTime>
Sets the amount of time after which a door will try to close itself after it was opened. Negative values mean the door will not try to automatically close (you can still use redstone, of course).


bigdoors.admin.pausedoors
/PauseDoors
Allows an admin to pause all doors. (toggle)

bigdoors.admin.stopdoors
/StopDoors
Forcefully finishes all doors currently in the process of being opened.

bigdoors.admin.unlockdoor
/UnlockDoor <DoorName>
Forcefully unlocks a door not owned by you.

bigdoors.admin.killbigdoorsentities
/KillBigDoorsEntities
Kills all entities that may have been left behind by BigDoors for one reason or another. Should not be necessary to use, but useful just in case.

bigdoors.admin.fillDoor
/FillDoor <doorName || doorUID>
Fills in a door with stone blocks, regardless of whether the user who issues the command is allowed to build there or not or if there are already blocks there.

bigdoors.admin.version
/BigDoors Version
Gets the version of the plugin. If it's a dev-build, it'll also show you the build number.

bigdoors.admin.restart
/BigDoors Restart
Restarts the plugin. Almost everything will be reinitialized (config, translation, etc).

bigdoors.admin.bypass.<attribute>
Gives you access to all doors via commands, even if they don't own them.
The attributes are: "lock", "toggle", "info", "delete", "relocatepowerblock", "changetime", "blockstomove", "direction", "addowner", and "removeowner". Note that when accessing a door you're not an owner of, you'll have to use its UID!


DoorName can also be substituted by the ID of the door, which can be useful when you have multiple doors of the same name. You can get the ID of a door using the "/DoorInfo" command or the "/DoorInfo" button in the BigDoor Menu. When listing all doors (with a given name, if provided), you also get the IDs of those doors. Note that as a consequence, you cannot give doors numerical names.

• (0.1.8.35+) German, provided by ZockerStation.
• (0.1.8.16) German, provided by @Lord_Junes.
• (0.1.8.15) Spanish, provided by @Link_1213.
• (0.1.8.18) Norwegian, provided by @Themarwik.
• (0.1.8.27) Japanese, provided by @keiichi.
• (0.1.8.30) Chinese, provided by @sheip9.
• (0.1.8.32) Italian, provided by @MiniMoro.

Got your own translation? Let me know!
Note that translations created for older versions may still work. If there are any missing translations you'll be notified in the log.

Making a big door:
When you want to create an animated object of any type, don't worry. There's an in-game guide to help you with it!
When you have built a door that you would like to open, you start the door creation process using "/NewDoor <DoorName>", where you substitute <DoorName> for any (non-numerical) name you'd like to give it. Alternatively, you can open the BigDoor Menu using "/BigDoorMenu" (or "/BDM" for short) and use the "New Door" button in the GUI and choose a name using "/NameDoor <DoorName|| DoorUID>", as the instructions will tell you.
Next, you will need to define the region of the door*. Just select two points on the door as far away from each other as possible, e.g. top-left and bottom right. You then need to define where the rotation point (or: hinge) is, so the plugin not only knows where the door is but also how to open it. This is done by selecting a column of blocks on the side you want the door to rotate around.
And that's it! You can now start using the door using "/OpenDoor <DoorName || DoorUID>" or find the door in the list shown in this plugin's GUI (sorted by door ID, i.e. creation date, for now) and use the switch there.
If you want to use redstone to open a door, you can do that too! Simply place the "power block" (as set in the config file)** under the rotation point/hinge as shown here:

*: Note that in the current version of this plugin, doors can only be 1 block deep!
**: I would recommend choosing a rare block (such as a gold block) to avoid lots of checks to the DB, which could cause slowdowns depending on how much redstone is used on your server (you don't have to worry about that when you use a rare block). This is only temporary.

Making a drawbridge:
Making a drawbridge is very similar to making a big door. For drawbridges, however, you can select a flat area as well. After selecting the area of the drawbridge, select one of the 4 sides of the rectangle to define the rotation point/hinge. If you select a corner, you'll have to select another point on the desired axis to avoid ambiguity.

The location of the power block is in the middle, under the rotation point. If it's still unclear, you can use the "/DoorInfo <DoorName || DoorUID>" command or the GUI to see its exact coordinates. Of course, you can also just move the power block to a location of your choice using "/ChangePowerBlockLoc <DoorName || DoorUID>" or the GUI.


Making a portcullis:
Again, a very similar process as before. The only difference from making a big door is that you use a different command (or GUI option) to initiate the creation process and that you don't have to select a rotation point (it only goes up and down, after all). The power block works the same as it does for drawbridges: By default, it's 1 block under the portcullis, in the middle and it can be moved just like it can for any of the other door-types.
The portcullis door-type will look at how many blocks it can move up and how many blocks it can move down. If it can move further down than up or if the number of blocks is equal in both directions (it never goes further than its total height), it will move down for as many blocks as it can. Otherwise, it will go up.

Very useful tutorial showing how to create all door types, created by the fantastic @Achaius: