Getting the most out of WoW Web Stats - Page 5

Setia · 05/02/07, 7:10 AM

About Combat Log ranges...

I changed the config.wtf file, and it did nothing - even if the file said 200 or 150 yards, it logged only to about 50 yards.

I then tried the combat log range option in Deadly Boss Mods. With that setting at its maximum, I was able to catch things up to 100 yard away, but no farther (tested with a priest friend).

This makes a solo logger barely adequate for Gruul - the room's big diameter is about 100 yards, but if you include the mouth of the tunnel, from the fence to the other end of the room, that's about 120 yards. It will be fine for most encounters, though.

• Praanz · 05/02/07, 7:13 AM

Originally Posted by Setia

About Combat Log ranges...

I changed the config.wtf file, and it did nothing - even if the file said 200 or 150 yards, it logged only to about 50 yards.

I then tried the combat log range option in Deadly Boss Mods. With that setting at its maximum, I was able to catch things up to 100 yard away, but no farther (tested with a priest friend).

This makes a solo logger barely adequate for Gruul - the room's big diameter is about 100 yards, but if you include the mouth of the tunnel, from the fence to the other end of the room, that's about 120 yards. It will be fine for most encounters, though.

You would be pretty viable if you have a position thats somewhere near the center - usually i stand at fireblast range for max dps, but I've logged from the side too.

I don't use any boss mods or any other mod that tweaks the combat log. I'm guessing that DBM will change the range-setting to a new value, maby something lesser than 150-200.

• Arawethion · 05/02/07, 12:35 PM

Yeah, some Ace mods like to mess with your combatlog range themselves. I know Squishy used to--DBM as well?

Swanchr · 05/02/07, 1:58 PM

We have been using it to fine tune our dps for Gruul.

Some notes on using it...

1. If you upload it to the website it will automatically split the attempts on the boss (did not check if this is 100% accurate)
2. For Gruul you need lots of logs. I have my range set to max, got 3 other logs, and one of our hunters still seemed to do minimal damage (yet he always died near last and his per shot damage was similar to other hunters).
3. Some players have a strange clock issue and their logs cannot be merged with others.
4. The website hosting is nice because you can compare your fight with other guilds... although this is limited to the top 50 or so in dps (I think). It would be cool to look at raids more at our level.

Question...

Does WWS save a copy of the merged log before generating the html (I assume so because it is posted to the website).. where is saved locally (thinking about some perl hackery).

bodicea · 05/02/07, 4:23 PM

I believe oTweaks can set all your range options to 200 yards. I don't have to deal with merging any logs that way.

Irise · 05/03/07, 9:00 AM

I am looking for a program which will do this client side, i.e. no need for me to upload any data or log on.

I had been using WoWParser, but the author has not updated the program in over a year (link: http://www.brockjones.com/wowparser/?cat=2 ). WoWParser and WWS seem identical in functionality but WoWParser can be used offline and you can store as many combat logs as you want.

Any help would be appreciated.

ka · 05/03/07, 9:43 AM

Originally Posted by lossendil

Since yesterday 11pm, the WWS server is under attack by one or more hackers. The server systems and software are still in beta, and I must admit that they're not very secure against some types of attacks, yet. The hotfixes and counter-measures I've tried since yesterday were not enough to bring the server back with acceptable response time and reliability. Please note that despite the attacks, no reports were lost and the database is unharmed.

I must now shut down the server and start working on a real securization, sooner than I had expected. I have good hope the work will be done by the end of the week, so the WWS server should be back by next Monday.

Does anyone know the symptoms of WWS withdrawal?

Oh god, my hands are already clammy.

Ewan · 05/03/07, 11:08 AM

Originally Posted by Irise

I am looking for a program which will do this client side, i.e. no need for me to upload any data or log on.

I had been using WoWParser, but the author has not updated the program in over a year (link: http://www.brockjones.com/wowparser/?cat=2 ). WoWParser and WWS seem identical in functionality but WoWParser can be used offline and you can store as many combat logs as you want.

Any help would be appreciated.

WWS has always been able to be used stand alone. The WWS Server is only a recent development and still 100% optional.

• Praanz · 05/03/07, 8:42 PM

Originally Posted by Swanchr

3. Some players have a strange clock issue and their logs cannot be merged with others.

This is usally FPS-related - ask your loggers if they'r playing with ridiculously (read <10) low FPS. If they do you can scrap their logs since it usually gets different time stamps due to the intense hardware lag.

Emeraude · 05/03/07, 11:50 PM

Delete, MT. >_>

Arnath · 05/04/07, 1:42 AM

WWS doesn't seem to differentiate between Life Tap and Dark Pact (or maybe it just ignores Dark Pact completely, I couldn't really tell). Is there some way around this?

Asmo · 05/04/07, 11:04 AM

Originally Posted by Breakerone

I see a lot of people talking about extending the combat log range to 200 yards, so I still felt comfortable about doing it, but now some guy in another forum told me that since 2.0 all of the settings which try to extend the combat log past 30 yards have no effect anymore and he pasted this from the BigWigs readme:

r33241 | rabbit | 2007-04-20 20:42:22 -0400 (Fri, 20 Apr 2007) | 1 line
Changed paths:
M /trunk/BigWigs/BigWigs.toc
M /trunk/BigWigs/Plugins/BigWigs_Plugins.toc
D /trunk/BigWigs/Plugins/Range.lua

BigWigs: Remove the Range plugin, since tweaking these settings have no impact any more.

Do you guys have any idea whats the deal now?

I see the developer of DBM also just posted a comment on Curse-gaming that you cannot increase combatlog range anymore. So was this recently stealthnerfed or something or whats going on? What is the default range now then?

I didn't notice anything when solo logging last weeks Gruul kill so it seems a bit strange but I can't be sure ofcourse. Otoh would seem pretty weird if both these addon developers were misinformed.

Pretty important to know I think since this would make WWS alot more cumbersome to use if you're required to have many logs to get accurate results for alot of fights.

• Arawethion · 05/04/07, 12:49 PM

I generate accurate reports perfectly fine with only my own log:
http://www.sigilguild.net/hamlet/WWS...348/index.html

boomix · 05/09/07, 12:04 AM

I've been looking for an explanation on this error: "no common Event2s" when trying to parse more then 1 log file. I cannot seem to find a solution to this issue.

ka · 05/09/07, 12:10 AM

That would seem to indicate that they are logs from completely different events. Try checking the logs manually to make sure they look ok.

What are these logs supposed to be from?

boomix · 05/09/07, 12:33 AM

Well I recorded log tonight for Gruul's lair and so has the other person(druid) only thing that is different between two of us is time zone. He is 2 hours ahead of me, also buddy of mine can process both logs and I show up with healing touch and steady shot.

Edit: I think my combat log is messed up. I will try this again soon.

Darkmantle · 05/09/07, 5:48 AM

I was able to detect a hunter aura changing from up to 100 yards away. Past 100 yards be disappeared on my screen due to low settings and combat log stopped reading him.

Edit: Cartographer mouse over person info used for range determination.

srg · 05/09/07, 4:39 PM

Can someone tell me what the config.wtf line is to increase combat log detection? If that is even possible to do.

j0ntar · 05/09/07, 4:47 PM

@srg:
Personally adding

/console SET CombatLogRangeParty "150"
/console SET CombatLogRangePartyPet "150"
/console SET CombatLogRangeFriendlyPlayers "150"
/console SET CombatLogRangeFriendlyPlayersPets "150"
/console SET CombatLogRangeHostilePlayers "150"
/console SET CombatLogRangeHostilePlayersPets "150"
/console SET CombatLogRangeCreature "150"

to the config.wtf file does not work for me. I have to run it via macro while in game.

edit: max range is 200.

srg · 05/09/07, 4:59 PM

@j0ntar - Thank you very much. I'll create that macro tonight. Just quick question. Loading it once is all I need to do correct? I don't need to do it each time I enter a instance or something along those lines correct?

j0ntar · 05/09/07, 5:11 PM

Yes just once per loading WoW.
I did tests with a warlock guildie to see if adding to the config.wtf did indeed work. We went to the Elemental Plateau. He would start dot'ing mobs and I would start at 40 yards (information gathered with Cartographer). I would then slowly move back, to my suprise(gasp) 50 yards was the limit.

I then executed the macro at 40 yards. I then slowly moved back and got to around 125 yards clearly reading all his dmg in my combat log. I ran out of room to try the full 200, and was truthfully to in a hurry to restart it all. 125 was a suffice distance to prove that it can work with a macro.

I do not know if others have had luck with adding it to config.wtf or not. This is just my personal experience.

Amerle · 05/14/07, 1:42 PM

Configuring logging range in the WTF file works fine for me. I have the options set to 200 yards, and I've tested parses from WWS both with and without additional raid members' logs. The only fight thus far where adding another person's log actually added a significant amount of data (i.e., I wasn't capturing everything on my own) is Void Reaver.

Just speculation, but I believe the settings in your WTF file are only read once by the game when you start up. So any addons that mess with range could still be altering it when they load, thus explaining why some people have to override it by setting it again with a console command.

◊ Cadfael · 05/15/07, 6:53 AM

Originally Posted by Amerle

Just speculation, but I believe the settings in your WTF file are only read once by the game when you start up. So any addons that mess with range could still be altering it when they load, thus explaining why some people have to override it by setting it again with a console command.

Yes, config.wtf is loaded once on startup. Any change during run time of the game in this file is discarded since WoW overwrites its content on exit. Just edit it when the game is not running and you'll be fine.

When the game is running you have to use the macro command and when you quit afterwards, you will have the entries in your config.wtf.

In short:
- game running: use macro, addons use the SetCVar call.
- game not running: edit config.wtf

I have no idea where the comment in bigwigs comes from that it wouldn't work anymore. I run around with 200 all the time and I get a hell lot of info from afar which I don't get when I turn it down. Works for me I guess *shrug*

• kendra · 05/16/07, 1:49 PM

I just wanted to add to the thread that changing the global variables holding the log strings also change your combat log so it's not seperated and sw_fixlogstrings also affects the combat log.

boomix · 05/16/07, 3:41 PM

Does anyone have newer version of AutoCL or something similar to auto log combatlog?