ProjectX

Hello Shadez, Ive found a few theme related bugs. Dunno if you are going to fix theme bugs because there is a lot of work needed on system files. But for future. int.css line 65 ( .int .search-bar .module a {color:#fed500} ) - if you change color to something else, it will change also color of "Log In" text on search page ( not the front one ) int.css line 66 ( .int .search-bar .module a:hover {color:white} ) - if you change color to something else, it wont work and hover is still white ( also not on the front one ) I will try to find out where is the problem but I dont have much time right now so maybe u will be faster than me Anyway very good job. Keep going

1. posting client screenshots is forbiden or Im wromg ? 2. nothing usefull in the screenshot, just that DKs and Palas do somehow bigger damage than others It would be better to find out what does this uber damage ( ability, spell, etc ) and then report bug with more information. I think this problem is connected with spell damage/power calculation changes ... so try to PM this screen to Laise.

I dont think this spell should revive player. It should only proc ( and this patch allows proc of it ) spawn of http://www.wowhead.com/npc=28534 and this npc have to cast http://www.wowhead.com/spell=51918 on dead player to revive him

MangAdmin still working ( even on 3.3.3a ) but u have to do "unbugs", like /reload everytime on login, or if u cant click on hyperlinks, theres a way how to activate them. But anyway thank you for the link. Im going to try this MangMod. I will let you know if it is or isnt working.

hmm i think it should give u error message because .go is not .gobject but something different and has different subcommands, if u want to use .gobject near its better to write .gob near ( and same for all .gobject subcommands like .gobject target etc. )

Just one question. In the video "tutorial" ( not sure if it is the right word, cuz it was little bit chaotic but nevermind ) you tell that users have to replace orig Launcher.exe and thats forbiden or im wrong ? ( i know users dont have to used it, but shouldnt be better make your Launcher standalone without need to replace orig Launcher.exe ? ) Anyway nice work, in the end it will look very nice, just keep going.

make a macro 1st one .gm on .gm chat on 2nd one .gm off .gm chat off so simple ... EDIT: or try to experiment and copypaste code from .gm chat command to .gm code ... ( Im sure it wont work but i can try it )

1000 players but on the same place ?

Yup confirmed, 3 raids in instancies and 6Mbit/s upload. It always hapens when a lot of people are in the same place. I think it is something with Raid related ( maybe not, didnt try to do it without raid ).Tried to turn off LoS and Addon Channel and it didnt worked. Dunno why so much data is send to players ...

FreeBSD 7.2

Im 100% sure this hapenss when the new global reset time for the instance is calculated and it depends on type of dungeon heroic dungeons are recalculated after 1 day, 3-day dungeons are recalculated after 3 days and etc, normal dungeons has own reset time so they are ok our global reset time is set on 4:00 AM ( btw i was watching it minute after minute , 3:59:00 AM - 1 minute left to reset, 4:00:00 AM - all ok, 4:00:01 AM - new reset time is calculated and is set to 49k days and etc )

please can someone confirm this or not because Im little bit confused right now and dont know if it is just my problem or it is global bug

Any ideas ? Someone with same problem ?

More details so... for example http://www.wowhead.com/?search=nature+resist+totem Now if you have 2 shamans on raid, and 1st one will summons Rank 6 and the 2nd one summons Rank 5 of this totem, they will give you 130+85 nature resist, but i think they shouldnt stack. More shamans, more totems. And I'm not sure about hunters aspects and paladins auras. I havent tested it yet, but i think when 2 hunters with http://www.wowhead.com/?search=aspect+of+the+wild ( low level hunter and high level hunter, for example hunter level 56 with rank 2 and hunter level 68 with rank 3 ) they will stack but again i think they shouldnt. I hope I explained it better now.

Mangos: 7502 SD2: 921 UDB: 369 Problem: When instnace reset time is calcuted for 2nd time after the last server restart, the timer says that instance will be reseted after about 49700 days and some hours. But if you restart server it will be recalculated as it should be. The best examples are Heroic instances, we have reset time set at 04:00 AM, when the new reset time is calculated it will be set on 49k days and etc. But all instaces behave same. ( 7-day instances get mad after 7th day , 3-day instances after 3rd day and etc ). Very strange bug but I havn't found any report about this. Any ideas ? EDIT: added some screenshots Server Uptime Heroic Magister Terrace Reset Time after 1. boss killed