Matchu 03c76fe882 Update missing body ID prediction to handle, say, the Maraquan Mynci. ... It turns out that some pets for seemingly nonstandard colors have the standard body type anyway, and vice-versa. This implies that we should stop relying on a color's standardness, but, for the time being, we've just revised the prediction model: Old model: * If I see a body_id, I find the corresponding color_ids, and it's wearable by all pet types with those color_ids. New model: * If I see a body_id, * If it also belongs to a basic pet type, it's a standard body ID. * It therefore fits all pet types of standard color (if there's more than one body ID modeled already). (Not really, because of weird exceptions like Orange Chia. Should that be standard or not?) * If it doesn't also belong to a basic pet type, it's a nonstandard body ID. * It therefore only belongs to one color, and therefore the item fits all pet types of the same color.		2014-01-20 15:29:01 -06:00
..
assets	ugh, add react.js manually :(	2014-01-20 14:35:28 -06:00
controllers	closet hangers index uses neopets connections dropdown	2014-01-18 22:50:14 -06:00
flex	Use item proxies for JSON caching	2013-06-26 23:01:12 -07:00
helpers	modeling i18n	2014-01-20 13:56:19 -06:00
models	Update missing body ID prediction to handle, say, the Maraquan Mynci.	2014-01-20 15:29:01 -06:00
views	Update missing body ID prediction to handle, say, the Maraquan Mynci.	2014-01-20 15:29:01 -06:00