Share Your RimWorld Modding Knowledge
Do you have practical experience with RimPy, RimWorld mods, load-order management, compatibility testing, or heavily modded playthroughs?
RimPy welcomes original contributions from RimWorld players, mod developers, technical writers, Linux users, modpack creators, and experienced members of the modding community.
We publish practical guides that help players install RimPy, organize their mods, resolve conflicts, improve game stability, and maintain reliable mod lists.
Your article should solve a real problem, explain a useful feature, or provide carefully tested advice that readers can apply to their own RimWorld setup.
Why Write for RimPy.site?
Contributing to RimPy.site allows you to share your knowledge with players who want a smoother and more organized modding experience.
As a contributor, you can:
- Share tested RimPy solutions
- Help beginners understand mod management
- Support players with large mod collections
- Showcase your RimWorld expertise
- Build authority in the gaming community
- Explain technical problems in simple language
- Credit and support mod developers
- Contribute to a growing RimWorld resource
We value honest testing, clear explanations, responsible modding, and practical information.
Topics We Accept
We accept original content related to RimPy, RimWorld modding, Steam Workshop mods, load orders, compatibility, performance, backups, and troubleshooting.
RimPy Beginner Guides
We welcome beginner-friendly articles covering:
- What RimPy Mod Manager is
- How RimPy works with RimWorld
- Understanding the RimPy interface
- Setting up RimPy for the first time
- Finding active and inactive mods
- Understanding mod dependencies
- Organizing a basic mod list
- Applying a mod list to RimWorld
- Launching the game after sorting
- Removing RimPy safely
Beginner guides should explain technical terms clearly and avoid assuming that every reader has previous modding experience.
RimPy Installation
Writers may submit detailed installation guides for supported operating systems.
Suitable topics include:
- Installing RimPy on Windows
- Installing RimPy on Linux
- Choosing the correct release package
- Extracting RimPy files
- Running RimPy from a dedicated folder
- Making RimPy executable on Linux
- Updating an existing installation
- Reinstalling without losing settings
- Removing outdated files
- Troubleshooting installation failures
Installation articles should mention the tested RimPy version, operating system, RimWorld version, and relevant folder paths.
Readers should be directed toward legitimate developer-controlled or trusted project sources.
RimWorld Directory Setup
We welcome practical guides about configuring game and mod paths.
Topics may include:
- Locating the RimWorld installation folder
- Finding the local Mods directory
- Locating Steam Workshop mods
- Adding multiple Steam libraries
- Fixing an incorrect game path
- Troubleshooting missing folders
- Managing RimWorld installations on another drive
- Configuring paths on Linux
- Moving RimWorld without breaking RimPy
- Verifying that RimPy detects the game
File-path examples should use placeholders rather than exposing a writer’s personal username or private folder structure.
Mod Load Orders
Load-order content is especially useful to RimWorld players.
Contributors may write about:
- Why mod load order matters
- Understanding framework mods
- Placing dependencies correctly
- Sorting large mod lists
- Reviewing automatic sorting results
- Fixing mods loaded in the wrong order
- Identifying outdated sorting rules
- Managing patches and compatibility mods
- Testing manual load-order changes
- Restoring a previously stable order
Do not claim that automatic sorting can guarantee compatibility between every possible combination of mods.
Automatic Mod Sorting
We accept articles explaining RimPy’s sorting features and community database.
Possible topics include:
- How automatic sorting works
- Using the RimPy Mod Manager Database
- Understanding community sorting rules
- Updating sorting information
- Fixing a mod that remains unsorted
- Reviewing warnings after sorting
- Adding manual adjustments
- Handling newly released mods
- Troubleshooting incorrect sort results
- Knowing when manual sorting is required
Writers should clearly distinguish the RimPy application from the separate RimPy Mod Manager Database.
Steam Workshop Mods
Contributors may submit practical guides covering Steam Workshop integration.
Suitable topics include:
- Finding the RimWorld Workshop folder
- Detecting subscribed mods
- Refreshing missing Workshop items
- Managing mods across Steam libraries
- Fixing incomplete Workshop downloads
- Identifying duplicate local and Workshop mods
- Updating subscribed mods
- Troubleshooting removed Workshop items
- Moving Workshop content
- Managing mods for offline use where permitted
Articles should respect mod licenses and should not instruct readers to redistribute Workshop files without permission.
Local RimWorld Mods
We welcome articles about manually installed and locally maintained mods.
Topics may include:
- Installing a local RimWorld mod
- Organizing the local Mods folder
- Creating a local copy for testing
- Updating manually installed mods
- Identifying duplicate mod folders
- Managing development versions
- Fixing invalid package IDs
- Removing outdated local copies
- Separating local and Workshop mods
- Backing up private mod configurations
When discussing local copies, writers should respect the original developer’s license and distribution rules.
Mod Dependencies
Writers may contribute articles that help players understand and resolve dependencies.
Possible subjects include:
- What mod dependencies are
- Identifying missing framework mods
- Resolving dependency warnings
- Installing required libraries
- Understanding load-before and load-after rules
- Troubleshooting version requirements
- Fixing circular dependencies
- Managing optional dependencies
- Reading a mod’s requirements
- Testing after dependency updates
Dependency information should be verified against the mod developer’s documentation whenever possible.
Mod Conflicts
We accept troubleshooting guides related to conflicting mods.
Relevant topics include:
- Recognizing mod conflicts
- Finding the mod causing an error
- Testing mods in smaller groups
- Using a minimal mod list
- Reading RimWorld logs
- Comparing two conflicting mods
- Disabling recent additions
- Checking compatibility patches
- Restoring a stable mod list
- Reporting conflicts responsibly
Avoid blaming a specific mod developer without clear evidence.
Duplicate Mods
Contributors may write about duplicate-package and duplicate-folder issues.
Suitable topics include:
- Finding duplicate mods
- Local versus Workshop duplicates
- Understanding duplicate package IDs
- Removing an outdated copy
- Handling development versions
- Avoiding accidental duplicate folders
- Understanding
_copypackage-name behavior - Fixing conflicting versions
- Checking which copy RimWorld loads
- Backing up before deleting duplicates
Any instruction involving deletion should include a clear backup warning.
Mod Lists and Profiles
We welcome content about maintaining separate mod configurations.
Potential topics include:
- Creating different mod lists
- Saving a stable setup
- Maintaining separate playthrough profiles
- Organizing testing and production lists
- Sharing a mod list with friends
- Backing up mod configurations
- Moving lists to another computer
- Restoring a lost configuration
- Comparing lightweight and heavily modded setups
- Documenting version information
Multiplayer articles should explain that all players may need compatible game, mod, and configuration versions.
RimPy Database Guides
Contributors may submit guides specifically about the RimPy sorting database.
Topics may include:
- What the database does
- Installing or updating the database
- Placing database files correctly
- Keeping the database inactive in RimWorld
- Troubleshooting missing sorting rules
- Understanding community-maintained data
- Reporting incorrect rules
- Refreshing outdated information
- Separating the database from gameplay mods
- Verifying that RimPy detects it
Do not present community sorting data as guaranteed to solve every compatibility issue.
RimWorld Modpacks
We accept articles about building and maintaining responsible mod collections.
Possible topics include:
- Planning a RimWorld modpack
- Choosing compatible mods
- Avoiding unnecessary overlap
- Building a lightweight mod list
- Creating a themed playthrough
- Documenting required dependencies
- Testing a modpack before sharing
- Managing updates
- Providing installation instructions
- Maintaining changelogs
Writers must respect mod permissions and should not redistribute another creator’s files without authorization.
Performance Optimization
Writers may share tested advice for improving heavily modded RimWorld performance.
Suitable topics include:
- Reducing startup time
- Identifying performance-heavy mods
- Removing unnecessary content
- Managing texture-heavy mods
- Reducing excessive log errors
- Testing large mod lists
- Improving memory usage
- Choosing performance-focused mods
- Checking hardware limitations
- Comparing clean and modded performance
Performance claims should include the tested computer, RimWorld version, mod list size, and relevant settings.
Avoid promising a specific FPS increase for every player.
RimWorld Startup Problems
We welcome troubleshooting articles covering launch and loading issues.
Topics may include:
- RimWorld not launching after changing mods
- The game freezing during initialization
- An excessively long loading screen
- Missing dependency errors
- Red text in the developer console
- Crashes during mod loading
- A corrupted mod configuration
- Incorrect load-order problems
- Steam Workshop downloads not completing
- Recovering with a minimal mod list
Troubleshooting guides should include the exact symptom, likely causes, tested solutions, and a rollback method.
RimPy Troubleshooting
Detailed RimPy troubleshooting articles are especially valuable.
You may write about issues such as:
- RimPy not opening
- RimPy crashing at startup
- RimWorld not being detected
- Workshop mods not appearing
- Local mods missing
- Automatic sorting not working
- The database not being detected
- Settings not saving
- Incorrect paths
- Non-ASCII character problems
- Mod stripping errors
- Linux permission problems
- An unsupported operating-system package
- Duplicate entries
- Failed configuration updates
A strong troubleshooting article should include:
- The exact error or symptom
- RimPy version
- RimWorld version
- Operating system
- Relevant folder paths
- Likely causes
- Tested fixes
- Backup precautions
- A recovery or rollback option
Do not present an untested suggestion as a guaranteed solution.
Windows Guides
We accept platform-specific content for Windows users.
Potential topics include:
- Installing RimPy on Windows
- Extracting the Windows archive
- Fixing antivirus warnings
- Managing Steam library folders
- Resolving permission errors
- Fixing path problems
- Running RimPy from another drive
- Troubleshooting configuration files
- Performing a clean reinstall
- Backing up RimPy settings
Security software should not be disabled permanently. Writers should recommend verifying legitimate files and using the safest available solution.
Linux Guides
Linux-focused RimPy articles are welcome.
Suitable subjects include:
- Installing RimPy on Linux
- Choosing the Linux release
- Extracting the archive
- Making the application executable
- Fixing launch permissions
- Locating Steam Workshop folders
- Managing Flatpak Steam paths
- Configuring multiple libraries
- Troubleshooting missing dependencies
- Running RimPy on different distributions
Linux guides should identify the tested distribution, desktop environment, and RimPy version.
RimWorld Updates and Mod Compatibility
Contributors may write about maintaining a mod list after game updates.
Topics may include:
- Preparing before a RimWorld update
- Backing up a stable setup
- Checking mod-version compatibility
- Identifying outdated mods
- Waiting for framework updates
- Testing a new game version
- Maintaining a previous RimWorld version
- Updating mods in stages
- Restoring a working load order
- Avoiding automatic-update surprises
Do not assume that every mod will immediately support a newly released RimWorld version.
Save-File Safety
We welcome guides that help players protect their colonies and configurations.
Possible topics include:
- Backing up RimWorld saves
- Protecting saves before changing mods
- Creating a test copy
- Removing mods safely from a save
- Recognizing save incompatibility
- Restoring a previous save
- Moving saves to another computer
- Backing up configuration files
- Separating important and experimental playthroughs
- Maintaining several recovery copies
Any process that may damage or invalidate a save should include a clear warning.
RimWorld Mod Development
Mod developers may submit technical and educational content.
Suitable topics include:
- Structuring a RimWorld mod
- Creating an
About.xmlfile - Setting package IDs
- Declaring dependencies
- Adding load-order rules
- Supporting multiple RimWorld versions
- Testing compatibility
- Reading error logs
- Publishing documentation
- Preparing Workshop releases
- Maintaining changelogs
- Working with community databases
Code examples must serve legitimate development, accessibility, debugging, preservation, or educational purposes.
Comparisons and Alternatives
We accept fair comparisons between RimPy and other legitimate RimWorld mod-management workflows.
A comparison may evaluate:
- RimPy
- RimSort
- RimWorld’s built-in mod manager
- Manual load-order management
- Steam Workshop collections
- Other community-supported tools
Useful comparison factors include:
- Installation
- Operating-system support
- Automatic sorting
- Conflict detection
- Profile management
- User interface
- Database support
- Performance
- Advantages and limitations
- Ideal users
Comparisons should remain factual, balanced, and respectful.
Contributor Guidelines
Submit Original Content
Every article must be original and unpublished.
We do not accept:
- Plagiarized articles
- Copied tutorials
- Scraped content
- Spun or lightly rewritten guides
- Previously published submissions
- Duplicate guest posts
- Poorly reviewed automated content
Submissions may be checked for originality before publication.
Use Accurate and Tested Information
Technical articles should be based on practical testing, developer documentation, reliable community sources, or genuine experience.
When relevant, include:
- RimPy version
- RimWorld version
- Operating system
- Mod versions
- Database version
- Exact error message
- Folder paths
- Mod-list size
- Steps already tested
Never invent errors, compatibility results, performance improvements, download details, or test outcomes.
Write Clearly
Use simple, professional, and natural English.
Explain modding terminology for beginners. Break long paragraphs into smaller sections and use numbered steps for installation and troubleshooting guides.
Avoid unnecessary filler, repeated information, unsupported claims, and exaggerated promises.
Recommended Article Length
Most guest articles should contain between 1,000 and 2,000 words.
Detailed troubleshooting, performance, and mod-list guides may be longer when the additional information genuinely helps readers.
Quality and accuracy are more important than reaching a specific word count.
Recommended Structure
A complete submission should normally include:
- A clear article title
- A short introduction
- Relevant H2 and H3 headings
- Prerequisites
- Numbered steps where needed
- Original screenshots
- Version and testing information
- Backup warnings
- A practical conclusion
- A short author biography
Troubleshooting articles should provide a brief explanation of the likely problem and fix near the beginning.
Responsible Modding Policy
RimPy.site supports lawful, respectful, and community-friendly modding.
Contributors should encourage readers to:
- Own a legitimate copy of RimWorld
- Download RimPy from trusted sources
- Respect mod licenses
- Credit mod developers
- Back up saves and configurations
- Test changes carefully
- Read mod documentation
- Avoid suspicious executables
- Report compatibility issues respectfully
- Support open-source and community projects
We do not publish content that promotes:
- Game piracy
- Cracked copies of RimWorld
- Stolen mod files
- Reuploaded paid content
- Malware
- Credential theft
- Account abuse
- Unauthorized access
- Harassment of mod developers
- Destructive scripts
- Copyright infringement
- Bypassing paid content
Copyright and Ownership
RimWorld, its artwork, code, logos, and trademarks belong to their respective owners.
RimPy, RimWorld mods, database rules, images, documentation, and related projects may have separate developers and licenses.
Contributors must not submit:
- Pirated game files
- Stolen mod packages
- Copyrighted artwork without permission
- Paid mods distributed without authorization
- Reuploaded developer releases
- Private source code
- Misleading download buttons
- Another author’s documentation presented as original work
When discussing a mod or tool, credit the original developer and link to an authorized source whenever possible.
Independent Website Disclosure
RimPy.site is an independent informational website.
Contributors must not describe the website as:
- The official RimPy project website
- The official RimWorld website
- An official Ludeon Studios resource
- The original RimPy developer
- An authorized representative of Steam or a mod developer
Articles should clearly distinguish independent educational content from official project documentation.
Screenshots and Media
Original screenshots can make technical and troubleshooting guides easier to understand.
Submitted images should be:
- Clear and relevant
- Created by you or licensed for reuse
- Free from private information
- Properly credited when required
- Readable on desktop and mobile devices
Before submitting screenshots, hide:
- Usernames
- Email addresses
- Personal file paths
- Steam account details
- Private messages
- Authentication information
- Unreleased mod content
- Private development files
Do not copy screenshots or graphics from another website without permission.
Linking Policy
Relevant links may be included when they support a technical claim, credit a developer, or help readers locate legitimate documentation.
Preferred destinations include:
- Original project repositories
- Developer-controlled release pages
- Steam Workshop mod pages
- Official RimWorld resources
- Trusted community documentation
- Original mod-author pages
A contributor may request a relevant link to a:
- Personal website
- Mod-development page
- Technical portfolio
- GitHub profile
- YouTube channel
- Professional profile
Every link is reviewed before publication.
We may remove links that are:
- Unrelated
- Excessively promotional
- Misleading
- Keyword-stuffed
- Unsafe
- Connected to piracy
- Associated with suspicious downloads
- Added mainly to manipulate search rankings
Submitting an article does not guarantee backlink approval.
Content We Will Reject
RimPy.site does not publish:
- Plagiarized articles
- Previously published submissions
- Pirated RimWorld downloads
- Stolen mod files
- Malicious tools
- Fake download buttons
- Suspicious installers
- Fabricated compatibility results
- Invented performance tests
- Harassment toward developers
- Articles written only for backlinks
- Excessively promotional content
- Irrelevant gaming articles
- Content falsely presented as official
- Destructive instructions without clear warnings
Sponsored Posts and Partnerships
We may consider relevant sponsored articles, gaming-hardware reviews, modding-tool comparisons, hosting resources, performance software, and community partnerships.
Sponsored content must remain:
- Accurate
- Transparent
- Relevant to RimWorld or PC gaming
- Useful to readers
- Safe
- Compliant with our editorial standards
A commercial proposal should include:
- Your full name
- Company or project name
- Website address
- Proposed topic
- Product or service details
- Requested link
- Content requirements
- Preferred publication date
Each proposal is reviewed individually.
How to Submit Your Article
Send your completed draft, detailed outline, or topic proposal to our editorial team.
Please include:
- Proposed article title
- Short article summary
- Complete draft or outline
- Target keyword, when relevant
- Author’s full name
- Short author biography
- Website or professional profile
- Previous writing samples
- Requested backlink details
- Original screenshots
- Testing and version information
Google Docs is preferred. Make sure the sharing permissions allow our editorial team to view and comment.
Contact Details
Email: cloudcorex4@gmail.com
Phone: +971 55 912 8238
Use this subject line for guest-post submissions:
Guest Post Submission – RimPy.site
For sponsored-content proposals, use:
Sponsored Post Inquiry – RimPy.site
Editorial Review Process
Every submission is reviewed for originality, technical accuracy, relevance, readability, copyright compliance, and practical value.
Our editorial team may:
- Correct grammar and spelling
- Improve titles and headings
- Restructure unclear sections
- Update outdated details
- Add internal links
- Remove unsuitable external links
- Add safety or backup notices
- Request screenshots
- Ask for testing information
- Request revisions
- Reject the submission
- Update published content later
Submitting an article does not guarantee publication.
Become a RimPy.site Contributor
Have a useful RimPy tutorial, a RimWorld load-order guide, a conflict fix, a Linux setup, a performance tip, a modpack strategy, or a tested troubleshooting solution?
Send your proposal or completed draft to cloudcorex4@gmail.com.
Use “Guest Post Submission – RimPy.site” as the email subject line.
We look forward to reviewing your contribution.
