WowAce

tag v3.0
e4b46208bdc9f5c08f314ee588fb2852adcfc127
David Lynch <kemayo@gmail.com>
2012-09-14 21:41:02 -0500

Tagging as v3.0

--------------------

David Lynch:
    - Put some toast in my sink
    - Had Jade Forest mapid as the id for the scenario instead.
    880 vs 806
    - It amuses me to rearrange the default sound this way
    - Tweak the facing of the full-body model
    - Clean up some wording, and change where counts are incremented
    - Encoding
    - Refactor the listing
    - Needs AceConsole
    - Add a "list all mobs" to the config
    - Wrong zone id for Kun-Lai
    - Forgot to move the settings check into the modules
    - Some type concerns. In particular, some rares are vehicles.
    - Keep Blood Seeker from being tameable, for sanity's sake
    - Syncs shouldn't trigger from the fake testing notifies
    - Save synced mobs, and further config tweaks.
    - Loopable sounds. Loopable sounds. Loopable sounds.
    - Special sounds for mounts / bosses
    - Move guess_expansion around
    - First scan should still be everything, though
    - Big config reorganization
    - Middle of the road position on cached tameables
    If someone has alerts for tameable mobs turned off, scan for all
    tameables constantly. Then, if we're outside their zone, suppress
    the notification.
    
    If alerts are on, save the CPU cycles and just show the alert when
    we wind up in their zone.
    - Change first cache scan approach
    Instead of scanning over every single possible rare, go back to
    scanning just the ones we know of in the zone. Avoid the old problem
    of a notification popping up for mobs like hunter pets the instant
    you enter a zone by making the first scan inside every zone be a
    no-notifications scan.
    
    Big benefit: not being ridiculously expensive in terms of CPU. Cache
    scanning 600 mobs every second? Not cheap.
    
    This does give us the potential edge case of a rare *right next to*
    the zone border not triggering a notification. That seems
    significantly less common than a hunter having tamed a rare, though.
    - More terrain phasing
    - Deleting all rares wasn't clearing tameable information
    - Manually put the camel into defaults, for now. Damn it.
    - Run dataminer
    - Let dataminer handle mobs whose location aren't known
    - using nil meant defaults overwrote everything
    - Fun with phased terrain
    - Run the dataminer with Pandaria mobs included
    - Bump sync protocol version, since we're now sending mapids instead of mapnames
    - Abstract out the base URL
    - Remove all translations code from dataminer
    Non-enUS will still work. Only problem they'll see is broker showing
    the enUS version of the name... until they encounter it themselves.
    - Datamine per-expansion as well as per-category, to avoid limits
    - Non-removed Babble-Zone reference. Nil name.
    - New tooltip handling: show on mob tooltip if it's an achievement mob, and give option to show the id in the tooltip (for help with manual alerts)
    - Little more rearranging
    - Little extra name collection
    - Account for forced non-rares in cache
    - More resilient cache scan
    - Always and ignore
    - Further rearranging
    - Delete all issue
    - Missed name import
    - Complete switch to mapids and mobids
    - Rearrange a bit more
    - With disabling, plz
    - Rearrange code a little, so that the core isn't so crowded
    - Small optimization to not check targets when not in group
    - Shouldn't do registerscanner yet