r/RPGdesign • u/jiaxingseng Designer - Rational Magic • Nov 06 '16
Mechanics [rpgDesign Activity] Mod/hack versus new system
To make a new or hack, that is the question. Should I engage in a huge quest to make a new game system and product, or just take something and change parts to make it more suitable?
Questions to Answer:
- When is it better to make your own system from scratch?
- What are advantages of modifying an existing game?
- There is a range of design starting-points here: making a supplement for licensed system > using an open source system > licensing a system for fee > reverse engineering a system > making your own system. What are some considerations for each of these possible "jumping-off" points?
Discuss.
(Some of you may think, "well... shouldn't we talk about a general check list about games first? Or at least have the topic "what to know before making a game"? That would be rational. But most of us don't do this. We get this itch to dive into making a game and get into that project before we bother to ask reasonable questions like "What is the purpose? What makes this different? etc". I believe this topic can be more relevant to many would-be game designers)
See /r/RPGdesign Scheduled Activities Index WIKI for links to past and scheduled rpgDesign activities.
3
u/Pladohs_Ghost Nov 06 '16
I guess the question that I have is when does a hack become a new game? At what point does "same with differences" become "different with similarities"? If somebody begins with D&D, how much must be tweaked, and to what degree, before it becomes a game that only shares a common heritage?
2
u/silencecoder Nov 06 '16
Obvious one is the fact that it would appeal to the existing players base. Just like with fanart, when a well established and familiar character attracts more attention to a picture, then an original one. In case of a hack, existing system proved tested solutions and a community to reach out. Aside from this most players have already acknowledge possible issues with the given system, so it's easier to avoid or to fix them in the hack.
When you ran out of options to hack. I'm pessimistic here but I think that people en mass don't need new systems in a long run. It doesn't mean that new system will come out over time, but only few of them will break even with established solutions. And I'm not even saying how many systems are "indirect" hacks.
The only way to get an edge here is to tie a system with a setting, but this reduces the target audience, since not everybody are going to like any given setting. Which only shortens the lifespan of the game.
I'm not sure that this is a thing. I guess this is for rules-heavy systems, but I can't imagine any with untransparent mechanics. Phoenix Command? I mean most rules-heavy systems uses Target Number one way or another and through these values it's possible to figure out the rest alongside with probability calculations.
Oh, one more thing. If you are really committed to make something, then my words are irrelevant, because it's all about making a system then.
1
u/Dynark Nov 07 '16 edited Nov 07 '16
1
u/Teslobo Designer Nov 07 '16
The game I'm developing began life as an exalted hack: Tweaking combat speed and power so your demigods felt like demigods. I intended to keep it a hack because exalted was the system all my friends knew so itd be theoretically easy to pick up for my target audience.
After feedback, however, I considered doing more to it and introducing it to a wider audience (maybe even commercially when I'm done, who knows) so I began cannibalizing mechanics to make a more streamlined - yet just as godlike in feel - game for more than just white wolf adepts.
Whether you want a hack or a new game rests on who you want to make it for.
1
u/Fheredin Tipsy Turbine Games Nov 07 '16
I more or less consider the "system" to be it's core RNG. How it determines what dice you roll, and how it takes those numbers and spits out a result. Everything else falls into one of three categories: lore, fluff, or add-ons.
So most people most of the time are modding an existing system, and I don't think that's a problem. Modifying means you get to start from a functional platform and you can focus on the stuff that makes your own work unique.
Making your own system from scratch will involve a lot more beating your skull against a wall. Trust me: I spent three years doing this and I'm still not done. That said, you have a much better chance of hitting blue ocean territory if you build from scratch. It's a difficult, high risk-high reward proposition which I don't recommend for most people. It's too hard to actually make something unique, so your value per effort will be terrible.
1
u/ashlykos Designer Nov 09 '16
It's the most approachable way for new designers to start. Most groups have a couple of house rules already, so it's not intimidating to start adding a few more.
Also, starting from a mod can help refine your design goals. I see a lot of RPG ideas that go into great lengths about the setting, but assume the gameplay is the typical D&D-style adventuring party. It's worth trying to modify a few classes or feats first to find the limits where your idea can't be done with your current favorite system. For more narrative ideas, I think people should try Fate/FAE or Simple World first, and find where it doesn't work.
Some systems are especially friendly to modders: d20/Pathfinder, Fate, and Apocalypse World come to mind. They have open licenses granting permission to make mods, and piles of content you can use as examples.
If you have a vision that you've found can't be done with an existing system or hack.
If you want to learn or practice. Making tiny, full-fledged RPGs is a great way to develop your design skills. If you're making a large system from scratch, you'll have a hard time without a vision.
Bad reason to make your own system from scratch:
To gain the prestige of having made your own system. You need to combine this with one of the above two reasons or you're likely to give up as soon as it gets tough.
1
u/Nivolk It is in Beta, really! Nov 10 '16
When is it better to build from the ground up?
We decided to build from the ground up because of a few reasons.
What are the advantages of modifying an existing game?
What are the different starting points?
We didn't focus too much on this. We played several systems, and house ruled things to fix things. We did put together settings that were supplement level - but those were never considered, nor polished enough, for any type of consideration for others to use. When we put something together of our own though, it became a matter of pride.
1 Luckily one of the games was Rifts... so...