So, by not using dayz_tools to create a secret server_mod, you're not covered by the license—that's obvious to everyone. That's why I'm still here.

Regarding the lawsuit, I'm saying that Bagemia can't do anything to me. Well, again, I'm not hiding. They have lawyers, I've spoken with them, but they understand perfectly well they can't win the lawsuit.

"The DMCA is absolutely applicable to code" - it's obvious that changing a couple of lines disqualifies any claims, as this isn't a 3D model that's very difficult to rework without preserving the original, unlike variable names. And things like a=b+c aren't protected by copyright, especially since I was talking about code written in the Enfusion language, which is essentially based on scripts.

A literary work has a limited number of changes, unlike C++ code, which can be changed beyond recognition simply by changing variables with auto-replacement, so these are completely different things.

"Releasing mods for DayZ" - you're wrong again. The mere fact of creating a mod doesn't impose any obligations on me. The terms of the license agreement apply when using dayz_tools.
Again, what does Steam have to do with this? Steam doesn't prohibit indirect commercial activity on Steam; it prohibits advertising such commercial activity.

3rd, I'm trying to play Batman, ♥♥♥♥ off.

2nd, you asked where “restriction” is prohibited. The DayZ EULA and BI modding rules PROHIBIT selling mods or monetizing mod functionality without explicit BI approval. This includes forcing external DRM, licensing systems, a nd forced 3rd party dependencies. The rules don’t need to say “restrict” bro.. Its on you to understand EFFECT and INTENT.

Forcing a server-side PBO that without, disables functionality or prevents servers from running unless external activation conditions are met is restriction of use rights.

Saying “models can still spawn” is stupid. The issue here is FUNCTIONAL GATING not file existence. A helicopter INTENTIONALLY prevented from operating due to licensing logic is restricted content. Helis not flying is a design choice dude not license enforcement.

And no, tracking alone is not the issue bnut using tracking to enforce licensing and control workshop usage via external systems IS. You're losing the argument.

DMCA absolutely applies to code, including source code and compiled binaries. Software is protected as a literary work, and DMCA takedowns for code happen all the time. You're incorrect here.

Yes might own the original textures and models you created, but that does not override BI's license or Steams ToS. BI doesn't have to “take” your assets to enforce rules. By releasing mods for DayZ, you agreed to restrictions on monetization/distribution/usage rules within their platform. Ownership does not grant permission to violate ToS.

Having a company that can be sued is irrelevant. Steam and BI enforcement is contractual, not civil litigation. Mods are delisted or blocked every year without lawsuits.

You're so far removed from all this that I feel like this is a conversation between a car mechanic and a 3-year-old with a wooden toy car...