☺
Account Details | |
---|---|
SteamID64 | |
SteamID3 | |
SteamID32 | |
Country | Pirate |
Signed Up | June 18, 2012 |
Last Posted | May 12, 2022 at 12:36 PM |
Posts | 1367 (0.3 per day) |
Game Settings | |
---|---|
In-game Sensitivity | 2.85 |
Windows Sensitivity | 6/11 |
Raw Input | 1 |
DPI |
450 |
Resolution |
1920x1080 |
Refresh Rate |
144 Hz |
Hardware Peripherals | |
---|---|
Mouse | ZOWIE FK |
Keyboard | Noppoo Choc Mini |
Mousepad | Steelseries QcK Heavy |
Headphones | Xiaomi Pistons 2.0 MK301 |
Monitor | BenQ XL2410T |
quick PSA: I reworked the forum subscription system and in the process reset the saved preferences from before.
sorry for the trouble.
did this and merged some forums:
- highlander discussion > general
- deals > hardware
- sports > off topic
KAMOWhatever was done, broke the site in Safari (on desktop)
http://i.imgur.com/ityCItc.png
good now?
enigmathe problem seems to be limited to mobile so i'll work to serve a very strict set of networks (amazon + trimmed-down adsense) when accessing the site from a mobile device
changes should be live. any problems?
awweealong with this, trident based browsers tend to end up like this, so browsing from ie / a windows phone has been broken for a bit
should be fixed; can you confirm?
the problem seems to be limited to mobile so i'll work to serve a very strict set of networks (amazon + trimmed-down adsense) when accessing the site from a mobile device
i'll let you guys know when the change is live so you can all give me feedback as to whether or not the change fixes this
aim-when the fuck was this scheduled lol
when you signed up for the tournament
we're casting this instead:
https://arena.razerzone.com/matches/lobby/2389
place your bets:
https://saloon.tf/match/724/
upload the following so we can diagnose this without back-and-forthing 100x
- your custom folder @ tf/custom
- your config folder @ tf/cfg
AN could have just cleanly won two teamfights in a row if he'd just fucking autoattacked to clean up kills rather than wasting time channeling jinx ult
it's not like he was doing it out of necessity -- he was already in range actively autoattacking with zero threats in both instances