Talk:Trading hut stock reports

It might be possible to whip up a script to strip out this information from the pulldown menu, but for now I'm using view-selection source and replacing the HTML tags. --Lint 19:58, 3 May 2006 (BST)

Same here, I cut and paste to microsoft word and then replace (wild cards) "\<*\>" with "" and "^p" with ", ^p". But a greasemonkey script that automatically shipped the data would be much more stylin. --Tycho44 20:03, 3 May 2006 (BST)

Formatting

I think the most useful way to display this information is to use a table with a row for each trading hut and a column for each item, like this:

Trading hut stock reports
Camp	Updated	Cut	bTb	Bul	Crb	Rif	Man	Blo	Dag	Ban	Gem	Drt	GPS	FAK	ShS	bPb	Mac	bCut	BotWat	bMac	Snk	HH	Rum	Wood	gc	Beer	Gou	Kni
Dalpok	04:25, 28 May 2006 (BST)	x		x	x	x	x	x		x	x	x	x	x		x	x	x	x	x		x	x	x	x	x		x
Derby	04:25, 28 May 2006 (BST)	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x
Durham	04:25, 28 May 2006 (BST)	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x
Raktam	04:25, 28 May 2006 (BST)
Shipwreck	04:25, 28 May 2006 (BST)	x			x	x	x	x			x	x	x	x			x	x	x	x			x	x	x	x
Wiksik	04:25, 28 May 2006 (BST)				x	x	x				x	x	x				x	x	x				x	x	x
York	04:25, 28 May 2006 (BST)	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x	x

(NB: finished column info, modified column titles, modified some table options. Tycho44 21:56, 2 June 2006 (BST))

(An "x" means that hut has that item. Also, I count 28 items in the game, so there are 28 item columns here). This would let people tell at a glance which items were rare, or where to find a certain item. It wouldn't let people track trader inventories over time, but I don't think that would be useful. Also, I would be glad to write a Greasemonkey script which would get a string (like "||x||x|| ||x...") from a trader's <select> tag, to make it easier for people to add to the table. — Elembis (talk) 04:25, 28 May 2006 (BST)

I think that the most useful way would be to have a separate table for each town. The time variation in the trading stock at a particular town is very important, whereas players are less likely to need to directly compare current inventories in different towns. After all, it takes several days to travel to a foreign town: (1) in that time, you could have searched thousands of dollars of equipment in a local hut, (2) if you're about to undertake a trading voyage, you're probably more concerned about whether gems or GPS units might reappear in the next couple days in that foreign town than whether GPS units are there right now, which means that the previous stock history is at least as important as the current stock. --Tycho44 06:07, 28 May 2006 (BST)

You're right, a table for each camp would work just as well. When I have time to visit a trading hut I can get the HTML I need for my script. How do you think items should be sorted? It'd be easiest and fastest to use the order in which they appear in a trader's inventory list, but I don't know whether GPS units or poison darts come first, nor where heavy swords go in the list; the order of everything else I have figured out. — Elembis (talk) 21:31, 28 May 2006 (BST)

Poison Darts before GPS units. Ignore the 28th column; if the Trading Hut ever stocks a Heavy Sword, your greasemonkey script should break and a champagne bottle should ride out on the computer's cd tray. --Tycho44 21:52, 2 June 2006 (BST)

Here's Trading Hut view source from Trader Harry. I removed most of my inventory, and censored a final value="###" that I didn't understand. The next formblock is give-gold or something.

<form class="formblock" method="POST" action="/game.cgi"><input class="txbuttonsubmit" type="submit" value="Trade"> my <select name="uobj"><option value="09">gold coin</option>
<option value="08">gps unit</option>
<option value="06">first aid kit</option>
<option value="0I" selected="selected">bottle of water</option></select> for <select name="tobj"><option value="0R">cutlass</option>
<option value="05">rifle bullet</option>
<option value="0O">crab</option>
<option value="04">rifle</option>
<option value="0F">mango</option>
<option value="02" selected="selected">blowpipe</option>
<option value="0P">dagger</option>
<option value="0E">banana</option>
<option value="0Q">gem</option>
<option value="03">poison dart</option>
<option value="08">gps unit</option>
<option value="06">first aid kit</option>
<option value="0B">sharpening stone</option>
<option value="01">machete</option>
<option value="0I">bottle of water</option>
<option value="0C">blunt machete</option>
<option value="09">gold coin</option>
<option value="0T">knife</option>
<option value="0M">bottle of beer</option>
<option value="0D">gourd of water</option></select><input type="hidden" name="action" value="query"><input type="hidden" name="trader" value="####"></form>
<br/>

--Tycho44 21:52, 2 June 2006 (BST)

Thanks. Here's the script. — Elembis (talk) 07:02, 3 June 2006 (BST)

A couple of minor glitches have been smoothed out. Anyone who downloaded the script before the time of this message's posting should install it again to ensure that they have the correct version. — Elembis (talk) 07:41, 3 June 2006 (BST)

The new world of Trading

Ideally, our stock reports would show the exact quantities in the trader's inventory whenever possible. It is important to know not just what items are in stock, but whether the items are double-short (he'll buy from you at 2x price), short (he'll buy at normal price but only sells at 2x), normal price, long (he'll buy for less but sells at normal), or double-long (he'll buy and sell at reduced price). Although an 'x' in a column is better than nothing, the table should probably easily allow for a quantity notation and/or codes for short and long inventory quantities. For example, most outsider towns have machetes double-long (selling at about $24), whereas the pirate trader machetes are double-short (he buys at $200). --Tycho44 06:07, 28 May 2006 (BST)

Proposed Table Format:

Trading hut stock reports
Camp	Updated	Cut	bTb	Bul	Crb	Rif	Man	Blo	Dag	Ban	Gem	Drt	GPS	FAK	ShS	bPb	Mac	bCut	BotWat	bMac	Snk	HH	Rum	Wood	gc	Beer	Gou	Kni
Camp	Updated	Cut	bTb	Bul	Crb	Rif	Man	Blo	Dag	Ban	Gem	Drt	GPS	FAK	ShS	bPb	Mac	bCut	BotWat	bMac	Snk	HH	Rum	Wood	gc	Beer	Gou	Kni
Dalpok	05:57, 5 June 2006 (BST)	3++	14	0	0	N	N	N	N	N	N	L	0	0	N	S	N	S	0	6++	0	2+	0	0	N	0	S	N

Legend

• x = In Stock, quantities unknown
• N = In Stock, normal stock prices
• L = Long Stock, cheaper prices
• S = Short Stock, twice normal price
• 14 = exactly 14 in stock
• 3++ = at least 3 in stock
• 0 = Out of Stock

Comments

This information is indeed important, but I recommend that we use a style that accomodates the color-free space/x style (which is quite easy to use, since the Greasemonkey script does it all) and can be extended from there. With that in mind, the changes I would make to your style recommendations would be to:

1. Represent empty stocks with empty cells instead of zeros, making it easier to visually differentiate stocked items from unstocked ones.
2. Signify long/short/normal prices with background colors only (which may be your intention): long with #dfd, normal with #ffd, short with #fdd, and unknown with no special background color at all. These colors are easier on the eyes and still easy to tell apart, and they distinguish between "normal prices (I checked)" and "unknown prices (I didn't check)", which the current color scheme doesn't do. Submitters shouldn't be required to check the prices of every item.
3. Use just one plus for "at least x in stock".

Here's what my table would look like (with the "Camp" column removed):

Trading hut stock reports
Updated	Cut	bTb	Bul	Crb	Rif	Man	Blo	Dag	Ban	Gem	Drt	GPS	FAK	ShS	bPb	Mac	bCut	BotWat	bMac	Snk	HH	Rum	Wood	gc	Beer	Gou	Kni
05:57, 5 June 2006 (BST)	3+	14			x	x	x	x	x	x	x			x	x	x	x		6+		2+			x		x	x

— Elembis (talk) 08:05, 5 June 2006 (BST)