eNeRGy

look at accounts table in realmd database. there is field 'expansion', it must be set to 2 in order to get wotlk expansion works

AFAIK, Tiny abomination in a Jar is not choosing targets and weapon random. According to ElitistJerks, you'll strike with weapon, which gain first of 8(7) motes of anger to target, which gives you last (7/7 or 8/8) mote of anger

Just no.

All multi-passenger mounts needs Vehicle system for work. Vehicle system is NOT implemented yet.

pets trying to find path in most cases. in example, platform jump before Anomalus in Nexus. My imp always goes around and finds right path, coming to me with couple of mobs on the tail %)

on retail servers that bug appears after disconnect. When naked player swaps some gear, all items begins to display.

what should that column do? remove items when player not have required rating anymore?

think? or tested?

may be custom patches/not a master branch ?

Client bug, afaik. Sometimes some characters appearind naked with weapons.

Did you see this all time or for some single characters ?

afaik only way to checkout achievements for player is Map() class used in instance scripts. Every other functions handling achievements are protected and must be used in propper places in MaNGOS core.

i think OP want some command to give achievements by id.

I found that combat log bugs for everyone when there is "Unknown" pet nearby. Not only in raid. Unknown pet happens when a player with active pet logouts or ends game by Alt+F4 and then log again. Maybe another cases...

This also happens on retail servers, so maybe this is client bug.

Consecration should stack from different paladins, without any rank or damage changes.

if you try to use voice chat on retail servers, you'll see that quality is far from vent.

i think it's not a bug, but a feature

combatlog information about caster.

i.e. replaces:

Replenishment fades from You.

with:

He's Replenishment fades from You.

Shouldn't be there some chance? May be better to implement it in *_loot_template way?

Nope... You have some item, and it will be replaced with another when duration ends. With 100% chance. But what you'll loot from new item is another story, so finally there is some chance that you'll get protodrake from FHs.

Example: Frenzyheart's jar will be replaced with another one, which contains loot, defined in _loot_template

Frenzyheart Tribe === > http://www.wowhead.com/?item=44717 ===> 1 week ===> http://www.wowhead.com/?item=44718 ===MAYBE===> http://www.wowhead.com/?item=44719

Oracles ===> http://www.wowhead.com/?item=39878 ===> 1 week ===> http://www.wowhead.com/?item=39883 ===MAYBE===> http://www.wowhead.com/?item=44707

Anyway, there is only 2 items atm, so IMHO new script event on destroy will be the best solution.

Hmmm.. Correct me if i'm wrong, but Vladimir said some time ago, that best way to implement it - is item scripts. So, you need to implement event like onItemDestroy, which will call relative script function when item expires. At now, separate DB table only for 2 items is wrong solution IMO.

MaNGOS is educational project. Our goals is learn to code, not to own 'emulator community'. Also, learn to setup servers... MaNGOS can hold thousands of players.

There is no level limitations on offy for Northrend(as for Outland too, except Dark Portal limitations). You can set areatrigger limitation however(areatrigger_teleport in DB).

But you can't restrict peoples from traveling to Northrend with ships or mage portals.

I do understand perfectly, Ceris. Thing is, eNeRGy original patch check for a mob giving vanguard + horde expedition reputation. The version I did from his doesn't care about the reputation type. Thus allowing without any support some special case like the violet hold where the default reputation you gain here on offi is kirin tor.

The counterpart of this more blizzlike version is that without the dungeons level+map restrictions, those tabards work anywhere, even non wotlk areas.

And if you want it to be integrated into mangos main code, it needs to be blizzlike.

Blizzlike. And no hacky...

Sorry, i forgot Violet Hold.

I think we can add new column in creature_onkill_reputation, which will contain tabard aura ID. If player with that aura(57818 in wotlk) kills that creature, then we should replace faction with tabard's faction. It will be more generic - if in Cataclysm we'll see same system(i think we will), we just can fill table with new mobs and new championing aura ID, without code editing. There is only one question - will Cataclysm championing be released with tabard? i think yes. Well, i'll take some time in next couple of days, and may be post new version.

I think eNeRGy means something like this:

In DB, fill reputation gain of all related cretures (in heroics and 80 lvl dungeons) to alliance vanguard/horde expedition factions.

Then on creature kill, check if creture has reputation setted to those two factions.

If no, then add reputation normally to setted fraction as it is on database.

If yes, then check if player has tabard equipped.

If he hasnt, then add reputation to aliance vanguard/horde expedition factions.

If he has, then add reputation to faction represented by tabard.

Yep. We have implemented reputation gain system, and we know it's right, because there is some exceptions - some mobs shouldn't give rep, some should give more rep, so there is no need in re-implementing it in formulas.

Why we ever need to check expansion, map, or level? Just fill db with right values (reputation without tabard), and add aura check with faction replace... Just like in first post

-% of physical damage taken. in 3.2(or early) Blizzard decided to replace +armor buffs with -% physical damage.

in 3.3 this should work only with Infusion of Light(deep holy talent) %)

Simply answer: nope.

Wee need a cluster solution for mangos.

This topic was meant as discussion, not an announcement. I wanted to hear your opinions on that idea, both from patch developers and testers.

If, however, there's noone interested, it shall fall into the "maybe someday" category.

Good idea, musthave i think. So many bugs appearing after major core modifications in master tree..