MODGuard Projects

MODGuard Ecosystem

New systems should expand the game without getting in each other’s way.

MODGuard proposes a shared technical foundation for ATS and ETS2 developers: coordinate game integrations, reuse resources and reduce conflicts between systems built by different creators.

ATS & ETS2 Shared infrastructure Open to free mods

For players, the aim is more features working together, with less need to choose which mod to remove.

Proposed ecosystem: your ideas, shared infrastructure.

The challenge

Working alone is only part of the challenge.

A system can work well on its own and still interfere with another project when both are installed. This can happen when plugins access or modify the same parts of the game without coordinating their integrations.

For players

A new feature can mean disabling another mod to keep the game working.

For modders

Separate integrations mean repeated work and conflicts that may only appear when projects are used together.

For the community

Established projects and new ideas both need room to coexist. Coordination is a shared responsibility.

The platform

Share the integration. Keep the freedom to create.

When different projects need the same game resource, the proposed approach is a shared integration with documented interfaces and responsibilities. Each creator keeps building their own ideas, while collaborating on the infrastructure those projects need to share.

Independent access Separate integrations

Different systems, overlapping access

Each project maintains its own integration. Changes to the same parts of the game can affect other systems.

Proposed coordination Shared integration

Shared access, individual projects

A common layer could coordinate game access and reduce duplicated work, while each project develops its own features.

Illustrative example

Two systems need vehicle data. Instead of maintaining separate integrations for the same information, both could use a shared interface when that resource becomes available.

Coordinated integrations and shared interfaces are the direction we want to build. The goal is to reduce conflicts and simplify maintenance; it does not guarantee compatibility with every external plugin or combination of mods.

Current projects

Current projects and their roles

Reusable game features, protection and web services play different roles. These are the projects available today or in beta.

Follow on Discord
In-game feature Available · Free

Smoke System

Realistic exhaust smoke driven by engine load and turbo pressure, on AI traffic and in Convoy multiplayer, powered by the free MODGuard plugin.

Reusable technology

Built on MODGuard and released for free. Modders can add it to their own trucks using the published guides.

Storefront Beta

Web Guardian

A storefront in development for selling and delivering mods, with each file uniquely encrypted for its customer.

Smoke demonstrates reusable game technology. MODGuardian and Web Guardian support how creators protect, distribute and deliver their work.

Experience & continuity

Experience to build. Continuity to maintain.

Our aim is to document, maintain and evolve a shared infrastructure as the games and the needs of creators change.

2017

Building software since 2017

Years of development, research and hands-on experience solving real problems.

2023

MODGuard active since 2023

Since day one, the project has been continuously developed, updated and adapted to changes in the game and to what modders need.

Access

Free mod creators too

Free mods and commercial projects both belong in this vision. The Smoke System is already free; access and use conditions for other resources are discussed for each integration.

For developers

Already building your own system?

Creating a DLL, a game integration or a new feature for ATS or ETS2? Let’s discuss shared needs, possible conflicts and opportunities to make different projects work better together.

Tell us what your system does, which game resources it needs and where integration could help. We can then discuss available resources, the scope of a collaboration and the conditions for using each resource.

Built by Toni Volma