Administrators Dazz Posted April 21 Administrators Posted April 21 VPUniverse Remix & Community Continuation System First off, yes, I did indeed use AI to help me think through this process. This is something that I've been thinking really hard about for a really long time. The hobbies current thinking about how mods/remixes of others creations are handled really needs a good modification. The modifying of someone else's creation has always been a controversial topic over the many years in this hobby. Modding is good for the hobby and is usually a gateway into better/bigger contributions. We have never had a standard, or any real attempts to make modding something we openly welcome. This is a live conversation... nothing written below is set in stone and is all up for discussion. Overview This document defines a remix system for VPUniverse that balances: Respect for original creators Long-term preservation of content Continued community-driven development Practical realities of creator inactivity The goal is to enable a healthy ecosystem where creations can evolve over time without becoming locked or abandoned. Core Principles 1. Attribution is permanent All derivative works must retain clear, non-removable attribution to original creators. 2. Creators are respected, not absolute gatekeepers Original authors have control while active, but do not permanently block community progress if they leave. 3. Community continuity is essential If a project is abandoned, the community must be able to continue development. 4. Remixing is a first-class workflow Remixing should be treated as a primary creation path, not an afterthought. 5. Technical complexity is hidden from users Systems like diff/patching (VPURemix) operate behind the scenes and should not burden users. Remix System Model Remix Definition A Remix is a derivative creation that: Is based on an existing VPUniverse creation Maintains a permanent link to the original Stores only differences (diff) when possible Exists as a separate, independently managed creation Remix Workflow Primary Workflow (Recommended) User clicks Remix on an existing creation System creates a new child creation (Draft) User develops the mod over time (weeks/months possible) User uploads versions during development System generates diff against original (if applicable) User publishes when ready Secondary Workflow (Fallback) User builds mod offline Uploads as a new creation Selects “This is a remix of…” System links to original and generates diff where possible Creation States Draft Private to creator Used for long-term development WIP (Work in Progress) Publicly visible Marked as unfinished Can receive feedback Published Final release Listed in main content feeds Remix Permission System Each creation has a Remix Policy set by the original creator: Available Policies No Remixing Allowed Remix Allowed Remix Allowed (Notify Me) Remix Requires Approval Remix Request Flow If Remix is Allowed User can immediately create a remix Original creator is notified (optional based on policy) If Approval is Required User submits a remix request Includes: Planned changes Scope of modification Creator can: Approve Deny Message requester Inactivity & Community Continuation Problem Many creators become inactive, leaving projects abandoned. Without intervention, this blocks progress and harms the ecosystem. Solution: Inactivity-Based Override If a creator is inactive beyond a defined threshold, remixing is allowed under a Community Continuation Policy. Inactivity Criteria A creator is considered inactive if: No login activity for X months (recommended: 6–12 months) No uploads, comments, or interactions No response to notifications Behavior When Inactive Remix requests no longer require approval Users may proceed with remix creation Original creator is still notified (in case they return) Messaging: Original creator appears inactive. Remixing is allowed under community continuation policy. Abandoned Project Indicator Creations should display a visible status when inactive: ⚠️ This project appears inactive (last activity: X time ago) This helps: Encourage community contributions Reduce hesitation to remix Avoid duplicate effort Attribution System Every remix must include: Original creation title Original creator name Link to original creation Automatic attribution (non-editable) Displayed as: Remixed from [Original Title] by [Original Author] Diff-Based Storage (VPURemix Integration) Purpose Reduce file duplication Enforce dependency on original Improve update handling Behavior System generates diff during upload Stores: Original reference Diff file Version metadata User Experience Users do NOT manually handle patches Installer/launcher manages: Required files Version compatibility Patch application Optional: Project Adoption System To further support abandoned projects: “Adopt Project” Feature Allows a user to become the primary maintainer of an inactive project. Effects Marked as “Maintained by [New User]” Original author still credited Clear lineage preserved Moderation & Safeguards Required Protections Attribution cannot be removed Remix must differ meaningfully from original Spam/low-effort remixes can be removed Original creators can report misuse Edge Cases Creator Returns After Inactivity They retain authorship of original Cannot delete existing remixes arbitrarily May publish new versions independently Creator Disallows Remix Enforced only while creator is active May be overridden after long-term inactivity (optional, configurable) System Philosophy Creators are credited and respected, but the community ensures creations can live on. Summary This system enables: Sustainable long-term content evolution Reduced conflict between creators and remixers Better handling of abandoned projects Strong attribution and lineage tracking A modern, structured remix ecosystem By combining permission control, inactivity handling, and diff-based storage, VPUniverse can support both creators and the broader community effectively.
ejvfx Posted April 22 Posted April 22 (edited) Dazz, this is excellent and clearly you’ve put a lot more thought into this than I have. Nonetheless, I’ll share a few thoughts, even at the risk of stating things that are obvious. Here are a few different kinds of tables I’ve encountered: 1) Variant/Remix Tables - Tables where cosmetic elements like graphics or lighting have been changed but the underlying gameplay is more or less unchanged. Re-Skins are generally in this category as well (Same table/New Name). 2) Mod Tables - Changes in physics scripting, adding menu items like LUTs or mod options 3) PupPack or DOF function additions to a table that is otherwise unchanged 4) Significant reworking of a base table, modernizing scripting, graphic or 3D object rebuilds, etc. The table may play noticeably differently. 5) Complete rebuild of a table but perhaps starting with the base playfield or other core elements 6) Tables that have been updated to VPX from VP9, etc but otherwise unchanged. 7) VR Environment additions - Table is unchanged but VR elements added. 8) Reworking an existing table with a new theme but significantly reworking the gameplay, graphics, etc. into an “Original” game. Since many tables are based on some pre-existing, real-world pinball machine, it’s sometimes hard to tell what assets an author starts with and it seems like people generally credit any and every author that ever touched the table - even if most of their work has been replaced by someone else in the relay race. I kind of like the chain of title so you can see the heritage of a table but it does get confusing when comments aren’t added to explain what changed. I appreciate the Diff process but I’ve found that it does create these variant dependencies sometimes. For example, when an author of original table produces an update to bug fix but now the variant branch is broken. Assuming the original author of record likes the Diff, it would be awesome if they incorporated this Diff into the official table release. I do love the idea of a more sophisticated asset management approach where you could see the “family tree” for a given table (links to previous versions, variants, etc). Currently, different authors follow wildly different file numbering schemes so you often just rely on the release date to tell what the latest and greatest is. It’s also worth noting that a backglass files sometimes have a similar family tree although there are certainly less active backglass designers (compared to tables). Outside of real-world recreations, there are the truly “Original” tables. I personally feel like those tables deserve special attention in terms of “permission to mod” status but perhaps some folks would disagree. The community definitely benefits from creative input and the continued evolution of tables as the underlying virtual pinball software and computer capabilities progress so I love that you’re trying to codify that idea (even when an original author is spending less time in the hobby). At the same time, I can think of some high drama situations in the recent past where creators felt put off by someone “improving” their work or felt they didn’t get the credit they deserved for their original contribution. Anyway, sorry if this was rambling but it’s great to get a dialog going. Edited April 24 by ejvfx
GeorgeH Posted April 22 Posted April 22 I like the direction this is going. There is a great deal of discussion about remixes but not much discussion about publishing a revision to a table where the author has left the site. I bring this up because I work on Future Pinball tables that don't have the ability to create a remix. The only option is a table revision or nothing.
Administrators Dazz Posted April 24 Author Administrators Posted April 24 On 4/22/2026 at 12:07 AM, GeorgeH said: I like the direction this is going. There is a great deal of discussion about remixes but not much discussion about publishing a revision to a table where the author has left the site. I bring this up because I work on Future Pinball tables that don't have the ability to create a remix. The only option is a table revision or nothing. Future Pinball is slightly different. We will need to look into it further. Visual Pinball has the most people creating mods, by far, so it needs the most attention as far as modding/remix goes.
Content Provider Schlabber34 Posted April 24 Content Provider Posted April 24 On 4/22/2026 at 5:56 AM, ejvfx said: Dazz, this is excellent and clearly you’ve put a lot more thought into this than I have. Nonetheless, I’ll share a few thoughts, even at the risk of stating things that are obvious. Here are a few different kinds of tables I’ve encountered: 1) Variant/Remix Tables - Tables where cosmetic elements like graphics or lighting have been changed but the underlying gameplay is more or less unchanged. Re-Skins are generally in this category as well (Same table/New Name). 2) Mod Tables - Changes in physics scripting, adding menu items like LUTs or mod options 3) PupPack or DOF function additions to a table that is otherwise unchanged 4) Significant reworking of a base table, modernizing scripting, graphic or 3D object rebuilds, etc. The table may play noticeably differently. 5) Complete rebuild of a table but perhaps starting with the base playfield or other core elements 6) Tables that have been updated to VPX from VP9, etc but otherwise unchanged. 7) VR Environment additions - Table is unchanged but VR elements added. 😎 Reworking an exiting table with a new theme but significantly reworking the gameplay, graphics, etc. into an “Original” game. Since many tables are based on some pre-existing, real-world pinball machine, it’s sometimes hard to tell what assets an author starts with and it seems like people generally credit any and every author that ever touched the table - even if most of their work has been replaced by someone else in the relay race. I kind of like the chain of title so you can see the heritage of a table but it does get confusing when comments aren’t added to explain what changed. I appreciate the Diff process but I’ve found that it does create these variant dependencies sometimes. For example, when an author of original table produces an update to bug fix but now the variant branch is broken. Assuming the original author of record likes the Diff, it would be awesome if they incorporated this Diff into the official table release. I do love the idea of a more sophisticated asset management approach where you could see the “family tree” for a given table (links to previous versions, variants, etc). Currently, different authors follow wildly different file numbering schemes so you often just rely on the release date to tell what the latest and greatest is. It’s also worth noting that a backglass files sometimes have a similar family tree although there are certainly less active backglass designers (compared to tables). Outside of real-world recreations, there are the truly “Original” tables. I personally feel like those tables deserve special attention in terms of “permission to mod” status but perhaps some folks would disagree. The community definitely benefits from creative input and the continued evolution of tables as the underlying virtual pinball software and computer capabilities progress so I love that you’re trying to codify that idea (even when an original author is spending less time in the hobby). At the same time, I can think of some high drama situations in the recent past where creators felt put off by someone “improving” their work or felt they didn’t get the credit they deserved for their original contribution. Anyway, sorry if this was rambling but it’s great to get a dialog going. Excellent list! The thing is, no matter how you put the table on this web site, either remix or full upload, it's all about the amount of work and improvements that are brought to the table. 1) and 2) in your list should only be shared personally to your Pinball buddys. 3) should be uploaded as a v1.1 on the original DL page under the name of the original author with the DOF / Freezy guy now being one of the tables team members! Everything greater then 4) is a new upload under the modders name. Just my 2 cents! Great topic btw. Thanks Dazz!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now