v0.3.8

Features:

• New "Always Cloaked" option for multiplayer games.
• projdata.txt files - files that can be used to tweak the balance of the game - can now be loaded for multiplayer games. Put any file starting with "projdata-" and ending with ".txt" in the same directory as olmod, and when you start a multiplayer game you can load that projdata into your game without other players needing the projdata file themselves.
• For single player and challenge mode, map authors can now put projdata.txt files and robotdata.txt files - files that can be used to tweak the balance of the robots - inside their level .zip files, and they will be honored.
• The preset for public anarchy games will now have the default setting for picture-in-picture rear view to be on. You can still turn this setting off in advanced settings.
• TODO: Last feature

Bug fixes:

• Internationalization fix for controller users who don't use decimal points to represent floating point numbers.
• Double the allotted time for a player to enter a map at the beginning of the match from 30s to 60s (should help slow-loading maps on slow computers with synchronized starting)
• Further improvements to lag compensation on bad connections. (Thanks, derhass!)
• Server-side input accelleration is no longer held back when a variable gets desynced. You'll no longer see ships flying a full second behind where they're firing from.

v0.3.7

Bug fixes:

• Fixed disconnected pilots leaving behind "ghost ships" that appeared to be eating shots. (Thanks, Tobias!)
• Fixed a number of CTF flag duplication issues.
• Fix to prevent powerups from being picked up by 2 players simultaneously.
• Fixed minor bug with lag compensation implementation. (Thanks, derhass!)

v0.3.6

Features:

• New lag compensation mods. In short, on default settings, you should be able to more clearly hit ships and more clearly dodge incoming fire at the expense of ships jumping around somewhat when they change trajectories. Settings to fine tune your experience - or turn this off - are found in Options > Multiplayer Options.
• Automap in multiplayer. This uses the quick save key bind from single player as opposed to the existing automap key to avoid confusing with the automap key's purpose in multiplayer.
• Additional autoselect options exist to determine what to do when you pick up a weapon higher than what you're holding but you are holding the fire button down.
• Parts of the player snapshot have been uncompressed to fix ship position quantization in maps that don't stay near the origin.
• Controller Axis Settings are now numerical sliders for more fine tuning.
• You will now clearly see if you are MODDED on the main menu.

Bug fixes:

• Potentially seizure-inducing flashing in VR fixed. (I'm not kidding, it really was THAT bad.)
• Swapping to a higher primary won't eat your thunderbolt charge, you'll get to fire it first.
• CTF flag pickup text should make more sense.
• CTF Boost and Classic Spawn are now correctly implemented for match preset JSON files.
• Team anarchy no longer uses the 3*K+A formula to sort players, it now sorts on kills, breaking ties with assists first, then least deaths.
• Minor tweak to new primary spawns to help ensure extra weapons do not unexpectedly spawn.
• Exceptions with creeper sync have been resolved.
• Crusher/Lancer anti-cheat was relaxed somewhat to address issues from players that keep the button held down, then quick released and re-pressed the button, which would falsely trigger the anti-cheat code.
• .sh files pulled from the repo on Windows and then ported to Linux will now have proper LF line endings. You may need to remove and reset your .sh files for this to take effect.

v0.3.5

Modding (using DLLs that start with Mod-) is now disabled by default. To enable modding, you must pass the "-modded" command line switch to olmod. You will know this works and your mod is enabled by seeing the word **MODDED** as part of your version number. Works for servers as well, modded servers can be seen in the multiplayer lobby (the width of the text for the server version has been expanded for this purpose).

The default method of primary weapon spawning in multiplayer maps has been changed. For players, all you need to know is that you will see more consistent primary loadouts in levels, and that the Lancer will start spawning in JIP games when certain player thresholds are met (this threshold varies by level, which is 5 for Backfire and maps that don't set these values such as Burning Indika v1.1). For map designers, here is what you need to know about the multiplayer mode file:

• The "percent" field - which wasn't really a "percent" - on fields such as $weapon;IMPULSE;2.0 is now a weight. This means that something like giving Imuplse a weight of 2.0 and Driller a weight of 1.0 is no different from giving the Impulse 50 and Driller 25, or Impulse 0.2 and Driller 0.1. Previously, the higher the number, the more of that weapon would spawn, and numbers too high would potentially put a primary's spawn rate at 100%.

• Previously, the game capped the number of available primary spawns at whatever was in the weapon count 8 field, regardless if there were more players than 8 in the game. This cap has been lifted. For instance, if you have $weapon_count2;2 and $weapon_count8;8, today 10 players would give you a maximum of 8 primaries spawned in at once. Now, you will get 10.

• Whether or not the Lancer spawn is controlled by three things. First, if you set $weapon;LANCER;0, you will never see a Lancer. Second, if you set the new command $lancer_players;4, you will not get a Lancer until there are 4 players in the game. The number 4 is adjustable, if you want there to be 8 players before a Lancer is spawned, you set $lancer_players;8. Lastly, if you do not specify $lancer_players, olmod will fallback on old behavior. I'm not going to go into the formula to what this behavior here is, because it's complex and isn't exactly the greatest piece of code in Overload. Generally, the lower the weight of the Lancer is ranked among the other primaries, the more players that will be required for it to spawn.

• Finally, the max number of players is re-evaluated every time a weapon spawn happens. That means as more players join via Join in Progress, more primaries may be available if the map maker allows for it. This also means that if you fall below the player threshold for the Lancer to spawn, it will stop spawning until the player threshold is met.

Autoselect is now available for multiplayer games. To enable, you must go to Control Options -> Advanced Options and set Primary Auto-Select to Never. You modify autoselect settings on the same screen you modify your loadout, ship graphics, and modifiers, the Multiplayer -> Customize menu. Order the weapons you wish starting with the weapon you want to select always on top. You can "X" out a weapon to make sure it never gets selected. Also, never miss a devastator autoselect with the alert option. Autoselect can be enabled for primaries, secondaries, both, or neither. For Classic Spawns mode, Impulse+ (dual Impulse) is treated as being below everything in the list. If you don't want a weapon to be selected above Impulse+, simply "X" it out. Note that this will affect what weapon is selected in your loadouts. For instance, if you have a loadout with Impulse, Thunderbolt, and Hunters, and you have Thunderbolt higher than Impulse in autoselect, you will now start with Thunderbolt selected, and NOT Impulse. Works for missiles, too.

New advanced settings are available for multiplayer games:

• Allow Rear View Camera (defaults off). This option allows players to use the rear view camera. Note the cheat code has been removed. You can now turn on rear view in Cockpit & HUD options.

• Scale Respawn To Team Size (defaults off, only available in team games). This option will scale a player's respawn time after death to be equal to the number of players on their team.

• Classic Spawns (defaults to off). In this mode, you do not get loadouts, but rather you start with Impulse+ (dual Impulse) and Falcons, and must collect the primaries you wish to use. When you pick up an Impulse, you will be rewarded with the Impulse++ Q upgrade which gives quad Impulse. Further, you are unable to pick up copies of weapons you already have, and spewed primaries from destroyed ships will disappear after 30 seconds if not collected to prevent level clutter.

• CTF Carrier Boosting (defaults to off, only available in CTF). This option will prevent flag carriers from using boost in CTF. It will be shown in the UI by your boost always being in an overheat state. Note that this is a change in defaults. In 0.3.4 and prior it was always on.

• Loadout Settings -> Allowed Modifiers (defaults to all modifiers allowed) - Allows you to fine tune which modifiers are allowed in the game. If a player comes in with modifiers that are not allowed, they will be prevented from readying up, and will have to select one of the allowed modifiers before playing. They will be forcefully removed from the game when it starts up, and will not be allowed in a join in progress game with the wrong modifiers.

An attempt has been made to work around the known issue of ships being invisible when you join a multiplayer game in progress.

The multiplayer level selection screen now properly shows map descriptions.

entity_trigger_box_lava_alien and entity_trigger_box_lava_normal entities from the editor are now enabled in game.

Shenanigans, methinks.

v0.3.4

Fixed a bug with silent thunderbolt.

v0.3.3

• VSync options no longer assume 60 Hz, and the left arrow now works for it.
• Sniper packet projectiles are now seen correctly by other clients for all primaries except thunderbolt. Thunderbolt and all secondaries were already being seen correctly by all clients. This should make receiving damage from most primaries feel more consistent.
• Major JIP fixes, including preserving player scores, making players inactive until they spawn, and correctly-synchronized weapons.
• Creeper sync has been expanded to include time bombs.
• Projectiles are no longer able to be seen coming through walls on maps with multiple chunks. These projectiles would not cause damage, but were confusing to players.
• Thunderbolt charge and cyclone fire rate will no longer hold over after a death if you're holding the primary button down when you die and when you spawn.
• CTF flag duplication should no longer occur.
• 10 FPS floor for client-side ticks removed from multiplayer games.
• Race mode times are now displayed in m:ss.fff format.
• Servers should no longer crash when maps have missing resources, it should just bounce clients back to the lobby and continue functioning normally.
• Console now accepts left key input.
• Attempt to make GSync dnSpy fix more consistent.

v0.3.2

• Client-side handling of games that use maps with missing resources. Clients will now be booted to the lobby in this case. Servers still crash, and is being tracked in issue #33.
• Match Presets left arrow now works.
• Sniper packets mod is now on by default, and no longer has an option to be turned off. The only time a v0.3.2 server should start a game without the sniper packets mod is when the client that starts it does not have the sniper packets mod.
• Clients without the sniper packets mod can now join games with the sniper packets mod, but won't have the benefit of sniper packets enabled for them.
• Devastators will still exhibit some strange client-side behavior, and is being tracked in issue #29.

v0.3.2-beta.2

• Potential bug fix to other players' devastators remaining in the game as a broken physics object after being manually detonated.
• olmod.sh can now be ran from any directory if you provide the -gamedir argument for the path to the Overload executable.

Note: v0.3.1.3 and earlier clients will still be able to start and play games on v0.3.2-beta.2 servers. However, if a v0.3.2-beta.2 client starts a game with sniper packets, v0.3.1.3 and earlier clients will not be able to join.

v0.3.2-beta.1

• Replaces default networking model with a sniper packets style, resulting in more consistent network play.

• Better synchronizes energy, ammo, weapon choice, missile counts, and devastator firing/triggering when using sniper packets.

Note: v0.3.1.3 and earlier clients will still be able to start and play games on v0.3.2-beta.1 servers. However, if a v0.3.2-beta.1 client starts a game with sniper packets, v0.3.1.3 and earlier clients will not be able to join.

v0.3.1.3

• Fix for observer first person view