Updated the script... need to clean up how I am handling the data (storing and manipulating.) But its currently creating items and by volume selected and placing them in one state array with owner's name. As you can see the parting has been investing heavily in "transportation" items (for no real reason.) Each item has its own "key" so it can be traded, destroyed, sold, or updated (i.e. a "Sword Long" could later be found to be a "Sword Long +1") {description:"Lance Heavy Horse", cost:"15", costunit:"gp", costgp:"15", weight:"15", size:"L", type:"P", speedfactor:"8", damagesm:"1d8+1", damagel:"3d6", note:"This weapon inflicts double damage when used from the back of a charging mount.", family:"weapon", combat:"Melee", rof:"", s:"", m:"", l:"", ac:"", armortype:""}, And.... when an item is created all information about that weapon is captured. Riley D. said: The navigation macros thing is...interesting :-). I never would have thought of that, myself. It does use quite a bit of server resources (since you're "re-sending" the entire HTML content of the window pane to every player every time someone presses one of the arrow buttons), but I suppose it's not too bad? Haha. Yea... sorry about that.... I am sure a better UI for API is on the way (or the new record sheets will be flexible enough to be leveraged.) Ability to make hyperlink API commands with "/direct" would be really nice... especially if you could "/wdirect" we could do a lot with just that!