As it turns out, they're pretty much ordered in the order that I coded them in, unless I'm mistaken.

The problem is, there isn't really anything in the Edge infrastructure to tag a given edge as being general, racial, class, etc. exactly, so much as there's a set of requirements which you either meet or don't... so in addition to the obvious bit of coding there, there's also the grunt work of going through almost 500 entries worth of the Edge Table and marking the whole thing up as appropriate.

It's a lot of not very fun work that I don't especially want to do, but equally I see your point with respect to the unwieldiness of the list. I'll see if we can come up with some kind of clever solution that addresses the problem.

obviously you already have an edge point assigned to each edge somewhere so why not use that to divide the list. make some ranges of edge values and label them like cheap, moderate, expensive and just list out the edges that way.

You kill 2 birds with one stone, you give players a general idea of how expensive an edge is without being too number crunchy. You also have a way of dividing up the list into smaller groups.