Jun 11th 2009 10:50AM I don't like it. If you're leveling an alt, coming up with the old fees is easy to through your main. If you're new, you shouldn't be leapfrogged over the old world--for reasons of equity, for reasons of quality (your quality, as a player), for reasons of story (will anyone ever do the pally/lock mount quest--or even know about it?)...and so on.
This change should be attached to an account flag that activates server by server when you reach the level cap. Before you do so, you get the old mount requirements.
And use of mounts in BGs should be restricted to the original requirements. The class advantages/disadvantages that revolve around mounts in the lower brackets are part of what makes them interesting.
Jun 9th 2009 8:41AM Take it easy people. Remember when every Tuesday meant at least six hours down across all realms?
Sep 2nd 2008 2:26PM Now what we need is for Routes to accept a list of waypoints assembled from TourGuide (maybe via TomTom), create a new route from them, and optimize it the same way it does for gathering routes. It would be a little limited in that you'd have to create each circuit with one waypoint from each quest--or add them as you went along and re-optimize--unless Routes was also made smart enough to take the requisite order of completion into account, which isn't neeeded for gathering purposes.
But, either way, then the whole route could be displayed in GatherHUD.
My complaint with the current setup (I'm using LightHeaded+TomTom+Routes, and GatherMate) is that I can't generate a route map for anything that isn't resource gathering nodes.
I can get steering from TomTom to whatever waypoint I designate as 'next'--but I can't see an ordered list of the waypoints I've set of have keys for "next waypoint", "previous waypoint," etc.