heck just 28

rip

# of healing xbows

https://www.last.fm/user/oblaa

Confirmed livelogs produces the overhealing component of the log.

https://github.com/ozfortress/tf2-livelogs

I'm the server administrator for both logs in question. Neither server runs TFTrue. Does that mean `medicstats_logbuffs 1` removes overhealing or the opposite. As of yesterday, ozfortress servers now use that cvar set to 1, while PugChamp uses '0'. I'm looking through logs to see the difference.

That seems to be the case in that log. Yet, take this for example: http://logs.tf/1956398

L 02/13/2018 - 23:04:51: "ozfortress obla<6><[U:1:101203767]><Red>" triggered "healed" against "ozfortress obla<6><[U:1:101203767]><Red>" (healing "3")
L 02/13/2018 - 23:04:38: "ozfortress obla<6><STEAM_0:1:50601883><Red>" triggered "overhealed" against "sf.wig<8><STEAM_0:1:22838924><Red>" (overhealing "35")

Overhealing clearly distinguished from healing. I can't seem to find why one has it but not the other? I looked on both servers, both utilise F2's Supplemental Stats v2 and Medic Stats

I strongly agree with the above recommendation. If it doesn't clutter up the page too much and doesn't take too much of zoob's time, I would like to request this also.

We've been planning the new format for about half a year now. In light of the rapid increase in new teams forming over the past two seasons, especially in the lower bracket, we wanted to revitalise the league with a new and exciting format. Highlander was obviously a possibility, having the meta and rules already established, as well as having run ozfortress Highlander in the past. However, due to the poor state of Highlander in the region, it wasn't going to be effective having another Highlander league and fighting over the same player base.

So we decided to look at newly established formats, such as the highly debated 7v7. We're excited to give this a shot and see what the concensus is on the future of ozfortress.

https://i.imgur.com/aqJGVUI.png

New status thing is pretty neat

THEY FIXED PYRO

Flamethrowers
Flamethrowers were able to do full damage regardless of the spread of their flames, rewarding maximizing flame spread over focusing on a target. We've made changes geared toward preserving the current damage range of flamethrowers, but requiring better aim to do so.
- Flame damage per second now ramps up based on density of flame encountered, up to 200%
- Initial flame damage per second reduced by 50%, resulting in the max damage being unchanged

H U G S

Less than a day to go.

K E E N

Thanks for the fixes.

Conquer #4 DM in AU can be removed. Also the AsiaFortress Jump servers that have been offline for 60 days seem dead.

Signups close tomorrow, signups are looking good! We have some top teams in Premier, should be an exciting season.