SRD talk:Creatures by CR

Test
CR 1 Creatures in the SRD

Okay, so, first off, problems: The SRD shows in the name space. That needs to be gone. The pages without all the categories bump them over into the wrong column. This is bad, obviously. The creatures listed aren't just the CR 1s. Anyone else who want's to toy around with this, give it a shot. --Ganteka Future 22:14, February 25, 2010 (UTC)


 * There's a special template used for outputting monsters that deals with the type and subtype problem -- you can see the template call on 3.5e Monsters. Surgo 22:16, February 25, 2010 (UTC)


 * Ah, starting to look better now. Though, it's probably going to need a new template table row to remove the SRD on the namespace of the articles. I would prefer it as aesthetics, but it isn't important. Still can't get categories and properties to exclude using #ask. I thought we could do that now. Maybe I'm just messing up. Anyhow, it appears that #ask is reading fractional CRs, such as CR of 1/2 as CR 1 and CR /2, they are included in the listing. Starting to come together... --Ganteka Future 23:31, February 25, 2010 (UTC)


 * I'll take a look at this soon. We may need to implement CR as a string or something. I had to go to paleowiki in order to see this page >_<. --Andrew Arnott (talk, email) 17:30, March 12, 2010 (UTC)


 * I think this is actually just an issue of semantic wiki being math stupid. Attempts to run the query to get CR >0.9 and <1.1 return the same results as we have here, so I think it just can't parse the division operator here. You may also have noticed that it's setting CRs to "1 /2" instead of "1/2", which I think is because it's trying to make them numbers and failing. A custom unit setup that equated 1/2 with 0.5 might work to resolve the issue. I'll try plugging it in later. - TarkisFlux 18:07, March 12, 2010 (UTC)


 * Yeah, it's math fail, properties with type number have to be in decimal form (see here) or it will do dumb things with them. Custom units don't work either without a base unit (can't be a simple number), and lead to annoying behavior in the box at bottom anyway. Strings would probably work, and I don't think it'll break anything, but I'll wait for Surgo to weigh in on that in case I'm forgetting something. - TarkisFlux 18:30, March 12, 2010 (UTC)