Bukkit

@ursak

It's all based on the API, it should work decently well without any updates. As far as breakages go, purpur stairs will become normal steps when used in a press, but they should revert to the correct stair material. To be honest, I don't even remember adding support for red sandstone stairs, so I should probably revisit that anyway. In the 1.9 announcement md_5 said that Player#getItemInHand will still be present, though deprecated, and will return Player#getItemInMainHand. That means all the in-world components will still function, ideally. There's still no word on a book generation API, so unfortunately all copies made with the plugin will continue to be the same as whatever they are copied from (original, copy, copy of copy, etc.) until that is written.

I actually did upload a new release today, but I believe the Curse staff has already finished approving files for the day.

I know I said I'd be updating back in February, but I hit some snags, got busy, and forgot. I'm still here, still alive, and actually (somewhat) back. While I don't plan on adding more new features any more, I will be cleaning up the code and fixing all the things I broke the last time I touched it. You can see my progress over on the GitHub.

When 4.0.0 is done, this project will be complete. I'll update it when needed, but I'll no longer be accepting feature requests.

Progress update 11/19:
I think I may have a release-ready version. I need to test it more, but I've cleaned up the code to the best of my abilities.

@Melonking

Very cool! I'll add that to my recommended section if you don't mind.

A general announcement: With 1.8, written books will be copiable in vanilla.
My vision for BookSuite was originally to offer players vanilla-style mechanics to make up for the lack of book-related features, however, it's become more and more apparent that the majority of users only are interested in the admin functions -- command based book alterations. This policy change will be reflected in any version released whenever 1.8 is actually available.
The one feature I do plan on removing is book stacking - in 1.8, copied books can be stacked. As it is, stacking requires several very costly checks that can cause severe lag for large copy operations.

I apologize for my lack of updates, I'm afraid that the combination of classes, a side project with a friend, and the enormity of my planned changes have had me overwhelmed.
I hope to have a release out within the next month, but I can make no guarantees.

Thank you for bearing with me.

Edit: Tl;dr: with 1.8 I will be changing the focus of this project towards admin commands.

More edit: It's been a month, and a lot of progress has been made! I'll have a release as soon as I finally manage to work out faking an author properly on at Book and Quill.

@Camaroz1

I've been planning on it, but it does come with a few difficulties, the largest being that rules change - I would have to keep a backlog of old rulebooks to check against. Beyond that, it's not bad; it shouldn't be hard to stop dropping/selling to villagers/placing in chests. I also wanted multiple rulebook support because short books are far more likely to be read.

@JacobCZ

My guess would be the lack of newlines after page denotations in the text file generated. When I tried it before, it made a page

<page>This is a page.</page>

when it actually has to be

<page>
This is a page.
</page>

@JacobCZ

Line breaking as in putting line breaks in before and after <page> and </page>? It does need that, all pages will be blank otherwise >.< I've been debating changing it, but currently if a line contains <page> the following lines start to be added to the page string. </page> causes the page string to be saved, then wipes it in preparation for another <page>. Any text on the same line as a <page> or </page> is ignored.

@JacobCZ

Added a line about it being indev, look good? Tmathmeyer's the one responsible for the initial importing and BML (Book Markup Language, totally stealing that abbreviation from jkcclemens) and I do most everything else :p It was thiiiis close to being just another plugin that saves in yaml

@JacobCZ

That looks really cool, quite handy :o