Elements 3.1 Released – Service Layer Fixes, Secure APIs, and Steam Bug Fix

We’re happy to share that **Elements 3.1** is now live!

This release addresses a major issue introduced in version 3.0 related to service layer scoping. In 3.1, we’ve refactored the way services are accessed and scoped, ensuring consistent lifecycle behavior across the platform. This resolves previous issues where services were incorrectly shared or not instantiated as expected in custom environments.

These changes make it easier to manage dependency lifecycles and improve the developer experience when building custom extensions or services within the Elements platform.

Our new security integration feature enforces full parity with the core Elements authentication system. It’s an easy way to lock down your custom endpoints using Elements’ built-in authentication. Just set:

“`properties

dev.getelements.elements.auth.enabled=true

“`

…and your endpoints will inherit session handling, user authentication, and permission enforcement — no extra work required. This allows developers to extend the backend securely without duplicating or rewriting auth logic.

This version also patches a bug disabling OAuth 2.0 support for Steam APIs. Integrating Steam sign-ins is now more universal. 

You can read the full release notes [here]

As always, Elements is 100% open source and ready for you to deploy. If you’re working on a multiplayer or liveops game and want help getting started, [get in touch]

Follow Us: