Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
3-30-2012 @ 7:59PM
Jyotai said...
An example of this:
The most controversial patch in the history of Guild Wars back when people would "raid" in that game (before you could bring 7 NPCs and solo it), was to the AI.
They made the AI adjust its tactics based on what the players did - mobs would switch up what moves they would use, in what order, and would try to 'kite' players by playing positioning games in order to get at healers (its a game with a difference concept of threat, and no tanks).
- Controversial because it proved to be smarter than 50% of the players, and had no lag time so faster than 90%...
- But also controversial because people were thrilled with what it hinted at: encounters you could no longer put on a timer.
An addon like Deadly Boss Mods is great in WoW. It counts down the fight. But it should not be possible...
It should not be the case, that every time you fight 'Boss X', he does Y at z% health, and does 'A' 3 minutes in, then B 30 seconds later...
- Sometimes, the boss should just say... "lets try something else."
Not as extreme as Guild Wars did - where the game became suddenly unbeatable to the point that full max sized groups (8 in that game) in top gear, could not beat world mid-level trash mobs... (until they hot-fixed their AI down and gave it built in lag).
- But at least something... some level of 'not predictable'.
Even just a 5% chance of 'random order to my next move'... would be an improvement...
In other words;
- Raid Bosses should have a priority list, not a rotation.