Is it possible, code-wise, to make it so that when a herald-scribed manuscript is dropped within the Library, it will begin to repop there? So after every crash and reboot and area repop, this manuscript repops and sits on the floor.

I think this would make the Lyceum extremely easy to update by Heralds, and would require only a little moderation from Imms, to see that the items are acceptable. Unacceptable books and books that are repeat topics can be culled.

Of course, this has nothing to do with the adding submitted works to the shelves, I understand that's an extensive project that has been more or less on the back burner for ages. However, once that's done, this feature would allow it to be easily updated.

Splntrd

A recent publications - room in Lyceum where such unsorted works are neatly arranged in the shelf and some Heralds that are trusted well enough having a command for adding such works. An Imm could have a tool which would transfer accepted works to proper shelves in the current Lyceum rooms. Also, readers could be given a power to review the works in the new publications room and Imms would be able to read such reviews.

I'd rather have it this way that objects that would repop to litter the Lyceum floor.

Using the repop list uses mostly existing code, and allows for the same amount of moderation as your idea does. Plus, they could repop in a container known as a "shelf", rather than on the floor. Maybe call it the New Releases shelf or something. This method stores information in a semi-permanent and accessible way until someone decides to get off their butt and update the Lyceum properly.

It has been explained to me before that a library like the Lyceum is insanely complex and hard to create and update. Lots and lots of manual labor that nobody wants to do. Therefore, the best system is the one that involves the least intervention. As it stands right now, the Imms apparently aren't interested in investing a whole lot of time into the Lyceum, and probably aren't interested in the full-time job of moderating the recent works, accepted works, and player reviews of those works. Of course, I can only speak for myself, but this is definately the impression I get. Other than that, I like your idea too. Maybe it's not too late for the Imms to put some consideration into these ideas for the Lyceum update project.

Splntrd

Using the repop list uses mostly existing code

No, it wouldn't. It's a pet peeve of mine when people who have never seen our code claim something is easy.

It has been explained to me before that a library like the Lyceum is insanely complex and hard to create and update.

It's not complex at all, in my opinion. If the Lyceum isn't being updated, it's a question of priorities and not complexity.

Therefore, the best system is the one that involves the least intervention.

That's the system that will put the most stuff in the Lyceum, not the best stuff. It sacrifices quality control, which is why I wouldn't want to adopt it.

valguarnera@carrionfields.com

>Using the repop list uses mostly existing code
>
>No, it wouldn't. It's a pet peeve of mine when people who
>have never seen our code claim something is easy.

Sorry. I assumed it would use the same functions as traditional repop, plus an additional set of script to add dropped items labeled as herald manuscripts to the list. This is just from my experience seeing coding and working on other MUDs.

Splntrd