Current version: 1.01 LiBro is a new plugin that provides two main features. It allows you to read and write books (which are normally quite useless) to record information. It also provides a secure lock/key system where keys are stored in the inventory and can be used for anything redstone-based. Usage Reading books Reading books is simple. All you need to do is have the book in your hand and right click. Text will be output to the chatbox, page by page. You can also skip to a given page using /lb skip [page]. Writing books Aspiring novelists will only need a blank book - one that's not been "created" yet. Using /lb create [Title] they can set a title and claim the book. The title may be several words. Once a book has your name on it, it can be written using the /lb write and /lb append [Text] commands. Creating keys and locks Locks consist of a sign and 1-2 levers. The sign and the key books both contain a hash of your password - this is used to compare them, but can't be used to figure out what password you used. To create a key, enter /lb key [Name] [Password]. Name and Password are both ONE word. To create a lock, make a sign. The first line must be [LLOCK], the others must be blank. Enter /lb lock [Password] and hit the sign while holding a book. There are two lock layouts - one where the sign is showing, another where it isn't. Sorry about the Paint illustration. I'm lazy. I might make a quick video tutorial. Permissions Uses "regular" permissions API. Code: libro.create - create books (necessary to make them writable) libro.append libro.append.others - add text to the end of books, one line at a time libro.write libro.write.others - "chat mode" for adding large amounts of text libro.info - get info on a book (author, length, title) libro.info.extra - more info (book id) libro.delete libro.delete.others - deletes the contents of a book libro.security.lock - allows creation of LiBro Locks libro.security.key - allows creation of LiBro Keys Note that everybody can use books and keys - I saw no reason to make permissions for these. However, if the demand is there, I will reconsider. Configuration Configuration consists of three nodes currently. Default values should work fine. salt: used for the hashing function used on keys/locks. Default: random/autogenerate page-size: how much text (characters/bytes) fits on one page. Default: 280 (4-5 lines) stack-field: Since stacking destroys data on books, we need to prevent stacking. This is the name of the obfuscated field. Might need adjustment for future versions, but currently, it should be left out. Changelog 1.01: Minor change due to WG tampering with the sign syntax. Syntax was changed from [LOCK] to [LLOCK]. 1.0: Public release. Known issues None at the moment. Download
I've been hunting for a plugin similar to your books. I wanted to create a library that was basically a summary of all my help files. ((I have no issues doing this manually)) But instead of books it would use bookshelves. So for instance if I wanted to create a help file for lilbro, i would create the file much like your book commands, enter all the relevant text (in game or offline--offline preferred) and then i put a sign on the back of the bookshelf [lilbro] and when someone punches the *bookshelf* it out puts all the help data, page by page... Could this be possible with your plugin?
Get Bookworm. Does exactly what you want, and i use it for that exact purpose on my server. http://forums.bukkit.org/threads/fun-mech-bookworm-v1-6-1-read-and-write-books-1000.22159/
amazing plugin, really useful however, 1 complaint: It says i dont have permission to create keys. i have given myself perms for libro.key, libro.* and i am op. i am using permissionsbukkit. I have also tried with superpermbridge. all other perms work fine.
Thanks! That's odd. I'm quite sure it was working when I tested it (I almost religiously test whatever I can ). If you could check your permissions and make sure it's not a problem on your side, I'd be happy to take a look.
these are the admin permissions (i'm part of this group) Admin: permissions: libro.*: true libro.append: true libro.append.others: true libro.create: true libro.delete: true libro.info: true libro.key: true libro.lock: true libro.read: true libro.write: true libro.write.others: true permissions.*: true slappy.canslap: true superpermbridge.citizens.*: true superpermbridge.libro.key: true inheritance: - user
Oops, this is my bad. I accidentally screwed up the documentation. The key and lock permissions both have libro.security in them, I'll fix the top post right away.
