Platform Rules

Version 1.2.0 · Effective 2026-06-28

Platform Rules

Effective Date: 28 June 2026 Last Reviewed: 28 June 2026

These Platform Rules apply to everyone who uses TrucklineMP services. They sit alongside the Code of Conduct, which defines behavioral standards. Where both documents cover the same topic, both apply. Violations may result in warnings, restrictions, suspensions, permanent bans, VTC dissolution, OAuth revocation, or Discord server action, depending on severity and history.

1. Scope

These Rules cover:

  • the TrucklineMP website and its subdomains (trucklinemp.com, beta.trucklinemp.com, forum.trucklinemp.com, and others we operate);
  • the identity service (id.trucklinemp.com, id-dev.trucklinemp.com);
  • the recruitment portal (recruitment.trucklinemp.com);
  • the TrucklineMP mobile application;
  • the official TrucklineMP Discord server and Discord bots we operate there;
  • the developer API, OAuth applications, and webhooks;
  • TrucklineMP-organized in-game events and convoys.

They do not govern third-party Discord servers, VTC-owned Discord servers, or the Euro Truck Simulator 2 game client itself, except where a VTC has verified a Discord guild to TrucklineMP (see section 5).

2. Accounts and Identity

2.1 Eligibility

  • You must be at least 13 years old. If you are under 18 (or the age of majority where you live), you need a parent or guardian's permission.
  • Registration is Steam-first. You authenticate through our identity service and may link additional providers (Discord, Google, YouTube, Twitch) afterward.

2.2 One account per person

  • You may hold one active TrucklineMP account.
  • Creating additional accounts to evade bans, manipulate recruitment, abuse VTC systems, bypass forum restrictions, or circumvent alt-detection is prohibited and may result in all linked accounts being restricted or banned.

2.3 Alt and ban-evasion detection

  • We run automated checks at registration and login that compare your account against active ban records using Discord ID, email address, and login IP address.
  • When a high-confidence match is found, your account may be automatically restricted (altRestricted) until staff review the case.
  • Attempting to circumvent alt detection — including using VPNs solely to evade IP matching after a ban — is a violation.

2.4 Accurate information

  • Your display name, @handle, profile fields, and linked accounts must not impersonate staff, other users, real people, brands, or other VTCs.
  • Handles and display names are subject to availability, reserved-name lists, and staff moderation.
  • You are responsible for all activity under your account. Do not share your account, session tokens, API tokens, or OAuth credentials.

2.5 Profile pictures and banners

  • Uploaded profile pictures are stored in our object storage and published on upload. There is no automated image moderation — staff act on reports.
  • Profile pictures, banners, and signatures must comply with the Code of Conduct. Staff may remove, replace, or lock them.

2.6 Security

  • Two-factor authentication is strongly encouraged for all users and required for staff and certain elevated permissions.
  • Do not attempt to access accounts that are not yours, harvest tokens, or phish credentials.

2.7 Legal acceptance

  • When we update the Terms of Service, Privacy Policy, Rules, or other mandatory legal documents, you may be required to accept the new version before continuing to use the platform. We record which document version you accepted and when.

3. Forum and Community

3.1 General posting

  • Forum posts, threads, reactions, reputation, polls, profile wall posts, direct messages, and bookmarks must comply with the Code of Conduct.
  • Do not spam, bump threads excessively, post off-topic content in the wrong board, or use the forum for unauthorized advertising.

3.2 Content moderation

  • Forum posts and replies are checked against our self-hosted content moderation service (cm.trucklinemp.com). Text is sent to that service for matching against configured rules; the service does not permanently store your message text.
  • Posts that match severe rules (slurs, hate speech, etc.) are held for staff review before publication. You will see a notice that your post is pending.
  • New accounts and boards with approval requirements may also hold posts for manual review regardless of content-mod results.

3.3 Direct messages

  • Private conversations between users are stored on our servers. Staff may access them for moderation and safety purposes. Do not use DMs for harassment, scams, or sharing illegal content.

3.4 Presence and activity

  • The forum tracks your online status, last-seen time, and current page for community features ("who's viewing this thread"). You may hide your activity from your public profile in forum settings.

3.5 Reports

  • Use the in-forum report system for rule violations. Retaliation against good-faith reporters is itself a violation.

4. VTCs and Events

4.1 VTC ownership

  • VTC owners are responsible for their VTC's name, branding, member roster, internal notes, recruitment listings, news, and member behavior in official VTC spaces.
  • VTC names, tags, descriptions, and avatars must not be offensive, misleading, or impersonating.

4.2 Discord guild verification

  • A VTC may link a Discord guild by verifying ownership. The guild owner must approve the link. Rules in section 7 apply to verified guilds insofar as they represent the VTC on TrucklineMP.

4.3 Member management

  • VTC managers may maintain internal member notes, role assignments, blacklists, and audit logs. These are visible to VTC management and staff — not to ordinary members.
  • Using VTC blacklists or rosters to harass users outside the VTC context is prohibited.

4.4 Events

  • Events published on TrucklineMP are subject to staff moderation. False, misleading, or rule-breaking events may be unpublished or modified.
  • Event attendance, slot assignments, check-ins, and event bans are recorded. Do not falsify attendance or abuse the check-in system.

4.5 VTC verification applications

  • VTCs may apply for verified, official, partnered, or featured status. Application answers are reviewed by staff and retained as described in the Privacy Policy.

4.6 Dissolution

  • VTCs used for ban evasion, harassment, or systematic rule-breaking may be dissolved. Member rosters and audit history may be retained for moderation purposes.

5. Recruitment

  • Applying for a staff or platform role is voluntary. Answers are reviewed by authorized staff and reviewers.
  • You must answer truthfully. Misrepresentation of identity, experience, age, or availability is grounds for rejection, offer withdrawal, or role removal.
  • Position-specific NDAs may apply. You must agree before your application is processed where required.
  • Accepted candidates may receive Discord onboarding through our recruitment bot (invite links, role assignments). Do not share invite links publicly.
  • Reviewers must recuse themselves from applications where they have a conflict of interest.

6. Support, Appeals, and Moderation

6.1 Support tickets

  • Use the in-platform support system (/support) for help. Do not abuse the system with spam, threats, or bad-faith tickets.
  • Internal staff notes on tickets are not visible to you. Ticket content, attachments, lifecycle events, and CSAT responses are stored as described in the Privacy Policy.

6.2 Ban scopes

  • Bans may apply to one or more scopes: website, game, event, VTC, and Discord (official server). Scope is stated in the ban record.
  • Public ban listings may show your username, reason, and expiry depending on ban configuration.

6.3 Appeals

  • You may appeal moderation actions through the support/appeals system within the configured appeal window (currently 7 days from issuance, subject to change in admin settings).
  • Appeal messages, staff responses, and decisions are retained. One active appeal per ban at a time.
  • Appeal outcomes are final once communicated, subject to new evidence or procedural error.

6.4 Discord tickets

  • On our official Discord server, support tickets opened through the ticket bot are logged. When a ticket closes, a transcript (including message content, edits, attachments metadata, and internal staff notes) is stored in our platform database and linked to your Discord ID where resolvable to a TrucklineMP account.

7. Discord

7.1 Official server

  • Rules on our official Discord server align with this document and the Code of Conduct. Discord's own Terms of Service and Community Guidelines also apply.
  • Our modbot enforces automod rules (including content-mod checks on messages), manages ticket panels, persists role assignments across rejoins, and syncs ban state with the platform database.
  • Our community bot links Discord accounts to TrucklineMP accounts, logs moderation actions, and delivers in-app notifications to Discord where configured.

7.2 Discord bans

  • Discord bans on our official server are synced to the platform discord_bans table and may be linked to your TrucklineMP account when your Discord is connected. Discord-scope website bans may reference these records.

7.3 Bot abuse

  • Do not spam bot commands, flood ticket creation, abuse automod exemptions, or attempt to manipulate bot logs or role persistence.

8. Developer API, OAuth, and Webhooks

  • The official API is the only supported automation surface. Scraping, headless browsing, and cookie replay are not permitted.
  • API tokens, OAuth applications, and webhooks are bound to your account and your permissions.
  • Do not exceed rate limits, bulk-export data beyond authorized scopes, or build competing user/VTC/event directories without written permission.
  • OAuth applications must honestly represent themselves at the consent screen and protect user data at least as well as we do.

See Terms of Service section 8 for full developer terms.

9. Beta, Pre-Release, and NDA-Gated Features

  • Pre-release NDA acceptance (including Discord ID, username, avatar, IP, and user agent at signing) is recorded and retained for legal defense.
  • Recruitment positions may require NDA agreement on acceptance. Beta Discord roles are assigned through automated onboarding flows.
  • Leaks, screenshots, or descriptions of NDA-gated features published outside permitted channels are a violation.
  • Reporting bugs through official channels is encouraged and is not a leak.

10. In-Game Conduct

  • At TrucklineMP-organized events and convoys: follow staff instructions, do not intentionally ram or block, drive responsibly, and report violations through the reports system rather than retaliating in-game.
  • Launcher configuration files you upload are stored under your account. Do not upload configs containing credentials or personal data of others.

11. Prohibited Platform-Wide

Regardless of which feature you are using, the following are always prohibited:

  • violations of applicable law;
  • harassment, hate speech, slurs, doxing, or coordinated brigading;
  • sexual content involving minors (zero tolerance — permanent ban and reporting to authorities);
  • impersonation of staff, users, or organizations;
  • ban evasion and alt accounts;
  • cheating, exploit abuse, or unauthorized automation;
  • spam, unauthorized advertising, or metric manipulation (votes, queue position, analytics);
  • sharing OAuth tokens, API tokens, or session credentials;
  • circumventing rate limits, CAPTCHA, queue protection, or maintenance restrictions.

See the Code of Conduct for the full behavioral standard.

12. Enforcement

Moderation actions include, in escalating order where appropriate:

  1. Verbal or informal warning
  2. Formal warning or soft warning
  3. Forum restriction or mute
  4. Temporary suspension (website, game, event, VTC, and/or Discord scope)
  5. Permanent ban
  6. VTC dissolution
  7. OAuth application or API token revocation
  8. Credential blacklisting (preventing re-registration with the same Steam, Discord, or other identifier)

Serious violations may skip directly to permanent action. We may report potentially illegal activity to authorities.

Your moderation standing (a computed score based on warnings, bans, and appeals) may affect automated enforcement thresholds. Staff may override standing tiers.

13. Reporting

14. Changes

We may update these Rules as the platform evolves. Material changes will be communicated in-product and may require re-acceptance. The Effective Date at the top is updated when changes are published.

Changes in This Version (28 June 2026)

  • Published full Platform Rules (replacing pre-launch placeholder).
  • Documented alt-account detection, content moderation holds, Discord ticket transcripts, modbot/community bot behavior, ban scopes including Discord, legal re-acceptance, and moderation standing.