--------------------

--------------------

- Create item spec

- Delete item spec

- Edit item spec details

- Edit item spec attributes

- Upload item spec image

- Browse item specs

- Item spec index page

- Create item instances from item spec (for creating one to sell/equip)

- In-page documentation for Item Making

- Revise active items (request name, desc, image, etc., changes)

- View detailed summary of item

- View list of current item uses (total equipped, total in vault, total sold by NPCs, etc.)
- Moderator control panel (for approval/rejection).

- Use item specs on NPC Treasure Lists

- Use item specs on Vendor NPCs (sell stock directly from the item spec, not just instances)

- Add support for new character/item attributes to PvP, PvE, GvG and GvE pages.

- Create new item attributes, integrate into game engine.

It's not quite this simple, but this is the main stuff. As you can see, I'm not doing too badly now. I only really need the "Edit item spec attributes" page finished for beta testing. Most of the stuff in orange is almost finished, with the exception of the NPC Treasure Lists and the Vendor NPC stuff. You'll see Vendor NPCs before the Treasure Lists, as I've finished most of the design on those.

EDIT: I'm updating this list as I go.

The difficult part is that I have to start creating rules for the attributes at each quality level. The lowest quality ratings will be restricted in the number of attributes that they can have,

There is also the issue of a trade-off between Defence and Hit Points (HP). In the way I have it set up now, the two do largely the same thing, but in different ways. The idea is that a player must choose to specialise in being better at cushioning damage (Defence), or being better at enduring the full force of it (HP). Since they work in a similar way, it may be unwise to allow an item to provide both attributes simultaneously. At the very least, the amount of power you give one attribute should reduce the amount available for the other.

The special Exp/hr, Turns/hr and Income/hr attributes will probably be allowed for most quality levels, though the lower ones will have to choose just one of them. for the purpose of keeping the low quality items cheap.

This isn't the say that you'll have to buy the absolute best Unreal quality items to have a decent item. I intend to have most of the quality levels at the higher end of the scale, with only the likes of Poor and Common being noticeably inferior.

From a standard baseline of items, up to an extreme upper limit, with the intervening quality levels being grouped rather closely, to keep them all relevant.

EDIT: A few more screenshots:

---