Publisher Guidelines

  1. Publishers

    • Publishers help promote custom content to players around the world!

      • Any member can become a publisher by uploading content.
      • You do not need to be a developer or contributor to be a publisher.
      • All published items must be properly credited to avoid disputes.

      Developers and Contributors can claim ownership of published items.

      • You can not claim developer rights if you are only a publisher.
      • Distribution rights can be challenged by the original developer or contributor.
      • Published items may be transferred or outsourced to the original developer or contributor without notice.
  2. Developers

    • Developers are the project owner and/or lead developer.

      • Developers are the original content creators and/or team members.
      • Developers can claim ownership of uncredited and credited published items.
      • Developers have full distribution rights and can challenge published content.
      • Original developers can request the transfer or outsourcing of an existing item.
      • Developers supersede contributors in disputes.
  3. Contributors

    • Contributors modified, fixed, or produced a variant of an existing item.

      • Any member can be a contributor by modding/altering or fixing existing content.
      • All published items must be properly credited to the original developers to avoid disputes.

      Developers can claim ownership of a contributors published content.

      • Distribution rights can be challenged by the original developer.
      • Published items may be transferred or outsourced to the original developer without notice.
  4. Properly crediting content avoids 99% of the disputes!

    • It's good practice to ensure proper credit is given when publishing content; And to contact the original developers (if possible) and inform them about the published item. This will allow the original developer to embrace your marketing efforts, while giving them the opportunity to claim ownership if desired. Ultimately it's in everyones best interest if the original works are maintained and updated by the developer, contributor, or an endorsed publisher.

      • Publishers should embrace transfers to original owners and contributors.
      • Openly offer to transfer the published item to the original developers.
      • Publishers should not be attached to their published items, please respect the distribution rights of the developers.
      • Outsourcing the published item to Steam is a good gesture towards original developers.
      • For best results; Developers, contributors, and publishers should work together to promote their content.
  5. Failure to properly credit content.

    • As a publisher it's your responsibility to ensure content is properly credited. Failure to do so is considered neglect and can result in administrative action.

      • Content and credits may be corrected by GameMaps staff.
      • Your account may receive a notice informing you to update content credits.
      • The content item may become 'disowned' and inaccesible from your account.
      • The item may be transferred to another account, such as a developer or contributor.
      • The content item may be abandoned or removed completely.
      • Repeated offenses can result in an account ban.
  6. Legacy content.

    • Legacy content is content of an unknown origin/publisher.

      • Legacy content can not be verified to an originating source containing credit.
      • Legacy content can exclude developer credits when there is no known developer.
      • Legacy content may be sourced from local, and internet archives.
      • Publishers can not claim developer rights for publishing legacy content.
  7. Transfer content between members.

    • A transfer request can be initiated by members listed in the item credits.

      • Ensure the member you are transferring to is properly credited.
      • Credited developers can send a transfer request to the publisher.
      • Both accounts must confirm the transfer for the process to complete.
      • If further assistance is needed, please create a support ticket.
  8. Disputed content

    • Disputed content requires escalatory measures as follows.

      • You can file a dispute by creating a support ticket.
      • Only the original developer can claim or dispute ownership.
      • Members can not dispute content on behalf of developers and contributors.
      • During a dispute, both parties may be notified to attempt a resolution.
      • Further actions may be taken on a case by case basis by our support team.
  9. Reporting content

    • Reporting content that does not follow the Terms of Use.

      • You can report a member from the profile page.
      • You can report content from the details page.
      • Do not use forums, comments and public discussions to report users.
      • If further assistance is needed, please create a support ticket.