When Battlefield got 60-120hz Servers
- Tom Belous (The Lanky Soldier)
- Jul 3
- 2 min read
Episode 2: When Battlefield got 60-120hz Servers
Released on July 20, 2015
Length: 48min
HIGHLIGHTS:
Summer Patch & Battlefield 4 Updates
Community Map Patches:
Two new patches released with improved textures, environmental updates (greenery, floor detail, massive cave).
Not all textures complete; still a work in progress.
Reload Bug Fix:
A long-standing reload bug (since Bad Company 2) was finally fixed.
Mixed community reactions: celebration from some, backlash from others calling it a waste of resources.
Tank Turret Changes:
Adjustments made due to 60Hz/120Hz server implementation affecting turret rotation.
Aimed at fixing animation/input delay issues; applies to tanks and wheeled turrets.
Concerns mostly voiced by PC users, while console users largely unaffected.
Community Backlash:
Frustration over knee-jerk complaints to visual/mechanical changes.
Developers constantly adjusting to user feedback, often met with negativity.
2. Battlefield: Hardline Discussion
Mixed Reception:
One host wants it to "die"; other acknowledges its role in attracting infantry-focused players.
Debate on whether it should have been branded as a Battlefield game.
Game Mode Experiments:
Introduction of modes like "King of the Hill" as test beds for new gameplay.
Potential use as a sandbox for experimental features without affecting core titles.
Gameplay Changes:
Increased player health via server-side modifications to slow down time-to-kill.
Some resistance to these backend fixes due to perception of it being a workaround.
Longevity Concerns:
Community still trying to keep Hardline relevant, but seen by hosts as a lost cause due to limited innovation and small player base.
3. Battlefield 5 Speculation
BF4 as a Testbed:
Battlefield 4's long-term updates are viewed as groundwork for Battlefield 5.
Lessons learned: avoid over-the-top gimmicks (e.g., Levolution), focus on solid, tactical gameplay.
Map & Mode Design:
Request for better-designed maps and Rush modes.
Calls for improved GUI, less grinding, and more meaningful gameplay progression.
Phantom Program Praise:
Community enjoyed ARG-style content like the Phantom assignments.
Desire for more hidden content and co-op/squad-based training or horde modes.
4. Star Wars: Battlefront Anticipation
Gameplay Comparisons:
Debate over whether Battlefront is a Battlefield reskin.
Similar UI and mechanics due to shared developers (DICE), but distinct in setting and style (e.g., no ballistics, laser weapons).
Beta Expectations:
Beta predicted to arrive ~1 month before launch.
Expected to include 1–2 game modes and maps, similar to previous EA shooter betas.
Casual Focus Concerns:
Worry that Battlefront may be too casual with jump-in-jump-out mechanics.
Expected to be highly popular but lacking depth for long-term competitive players.
Lack of Content Fears:
Limited planets and maps at launch (10 total).
Speculation that content is being withheld for DLC monetization.
5. Future of Battlefield 4 and CTE
Support Timeline Predictions:
Some predict support will continue until Summer 2016 (around E3), others believe it’ll end by end of 2015.
Community Test Environment (CTE) may continue even if retail support ends, as a testing ground for Battlefield 5.
CTE Role Going Forward:
Seen as a critical platform for experimentation and balancing ahead of the next title.
Suggestion that CTE could evolve into a standalone dev/testbed for future games.
