Just Cause 3: Multiplayer mod

Hey guys and girls,

We are very excited that our mod is finally available on Steam.

Let's start with a quick list of things that changed from the last beta to the this very first Steam release.

• New Client UI
  • We entirely redesigned the UI for a nicer look and added functionality to integrate better with Steam
    • You can change game settings in our UI now
    • The native JC3 menu has been disabled
• Steam Integration
  • You can join and invite friends directly via Steam
  • The masterlist was changed to use the Steam services
    • The masterlist package is no longer needed or used anymore
• Improved File Transfer Performance
• Added ShowHud, HideHud and IsHudVisible to scripting API
• Added client side vehicle scripting (see docs for more information)
• Added functions to interact with a specific WebUIWindow
• Updated CEF to version 3029
• SetOccupant now teleports the player if the vehicle is not in streaming range
• Fixed mouse leave event not working properly
• Fixed DrawRect not working in 2d render mode
• Fixed player health getting restored on teleport

• Fixed player getting invulnerable on teleport
• Fixed issues in Crash Dialog, address is now displayed correctly
• Fixed audio files not playing properly in a WebUIWindow
• Fixed the linux server requiring LD_LIBRARY_PATH=lib to launch
• Fixed custom properties of player object not getting reset properly on disconnect and getting reused for the next player
• Fixed several server crashes
• We have changed the detection of the Just Cause 3 installation to work more reliable. This should help a lot of people, who were not able to find their local Just Cause 3 folder.

So what are we going to do next?

The first thing that we want to tackle with 1.1.0 is, that we want to rebuild the foundation of our client, just as we did with the 0.9.9 release for the server. This way we can ensure that we can deliver future updates faster, but still keep our code base ready for upcoming features. It also allows us to improve stability even further, as we can reduce crashes and bugs by cleaning up several parts of our client code.

If you want to follow our development plans, feel free to take a look at our public GitLab issue tracking: Gitlab.nanos.io. We are always trying to be as transparent with our development as possible and the best way to follow our development is to just take a look at GitLab from time to time.

If you think there’s a feature missing in the mod our you’ve encountered a bug, please report it on our issue tracker: Gitlab.nanos.io.