roncli.com blog
The blog of roncli
roncli.com blog
roncli.com
blog
Profile
roncli
Houston, Texas, United States
Labels
Coding
CTG Music
Editorials
Games
Miscellaneous
Music
Servers
Silliness
Software
Sports
Trax in Space Beta
Weather
Recent Posts
WTF did Revival Productions just do?
A Tale of Two Communities
The Final Stretch
A Two Tiered, Untiered OTL
Secretly, you wish you could've done what I did
What have I done since roncli.com v2?
It's Done. It's Finally Done.
The Big Picture is Starting to Wear on Me
A Low Bang to Buck Ratio
win-acme
Archives
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
June 2008
July 2008
September 2008
December 2008
February 2009
July 2009
August 2009
September 2009
October 2009
November 2009
February 2010
March 2010
April 2010
June 2010
July 2010
August 2010
September 2010
October 2010
November 2010
December 2010
March 2011
June 2011
July 2011
August 2011
September 2011
October 2011
December 2011
January 2012
February 2012
April 2012
July 2012
November 2012
July 2013
April 2014
July 2014
August 2014
November 2014
December 2014
March 2015
April 2015
May 2015
June 2015
July 2015
September 2015
January 2016
February 2016
May 2016
July 2016
November 2016
March 2017
January 2018
May 2018
June 2018
January 2019
January 2021
February 2021
March 2021
August 2021
October 2021
December 2021
August 2022
November 2022
October 2023
February 2024
April 2024
Current Posts
Thursday, March 25, 2021
Overload has truth; next it needs balance
Posted: 6:31:00 PM 0 comments
Overload multiplayer was put together in around a month, went through another month of testing, and ended up being rather underwhelming to play. Ranked multiplayer queues died out after the first couple weeks, those that remained were either gaming the system or late to the party. Mercifully, ranked multiplayer did not survive very long.

However, multiplayer soon began to thrive in the form of the Overload Teams League. I founded the OTL in 2019 for pilots who wanted to play team games. It caught on pretty quick with 6 teams by its second month. At first, we dealt with the frustrating limitations of poor server choices, shoddy networking, and always demanding to Bammer "RESTART YOUR SERVERS!!!". But shortly after Revival Productions folded in February of 2019, a glimmer of hope appeared in the form of olproxy, a piece of software that allowed Overload LAN servers to act as Internet servers. For the first time, Internet games were playable without official servers.

Over time, this expanded to olproxy being incorporated into olmod, a collection of mods for Overload with the aim to improve multiplayer game play. A large number of improvements have been included in olmod since then, including larger game sizes, reporting to a tracker, sniper packets, lag compensation, and more. What hasn't been addressed is weapon balance.

Multiplayer weapon balance has not been great since Overload launched. Ammo weapons have been shown to dominate, and the energy weapons are a mixed bag with cyclone being dominant and reflex being weak. Hunters used to be super strong until an early nerf was added to olmod. Creepers and time bombs used to be excessively out of sync between client and server. Despite this, people still played, but bigger issues existed because people couldn't understand what they were seeing. Ship positions were not consistent. People were saying that 50ms in Overload felt worse than 100ms in Descent 3. (While seemingly unbelievable, this was learned to be a true statement since Overload intentally adds a minimum of 83ms of lag to game play; 33ms for processing controls smoothly and 50ms to be able to interpolate ships smoothly.) Slowly over time, the net code was deciphered and unravelled, and we learned some shocking things about how the net code was implemented. In addition to the intentionally added lag, your entire controls are sent to the server every frame for processing server-side. Every button press, mouse movement, or swing of the joystick would be part of that send. But because client and server frames don't match up one to one, this would cause errors in position and rotation, and weapon firing that was often out of phase, meaning what you saw on your screen wasn't what was happening on the server.

First, we fixed the weapons. Sniper packets made it so that every time you fire something client-side, that is what was seen server-side. This also eliminated some super bad parts of the game, such as disagreements as to how many missiles you have, what weapon you're using, what side of the ship you're firing a missile out of, and more.

Second, we fixed most of the intentional lag and made it so that it would try to compensate for lag, predicting where ships will be in the future, making them easy to hit. Then we revisited weapons, also compensating them for lag so that they'd be easier to dodge.

I say "we" because this is a team of developers doing this. Arne de Brujin created olproxy and olmod and showed us what is possible. I've contributed a bunch of code, and Tobias, Whollycow, and derhass have been instrumental in keeping things on track. We even have occasional contributors like terminal, luponix, and D.Cent provide extra quality of life for both players and developers.

And now we're ready to tackle balance.

Players are now seeing the game closer to the truth than ever before, and as a result they have honed in their skills better than ever, showing us that, yeah, there are serious balance problems with the game. It's not like we didn't already know this. However, now that we are seeing closer to the truth, we can begin to understand exactly what these balance problems are, and hopefully start finding common ground in regards to what needs to be balanced.

Labels: , , ,