Some of those features are fairly easy to apply yourself: I’m not criticising for asking lol : )
Hmm a shop would be nice, but afterall it’s an obby.
I’m pretty sure you can remove the forcefield through the settings by setting the duration to 0. I’m not sure where it’s but I cant seem to find it…
Anyways, this is awesome. I look forward to updates, and this a helpful resource and perfect way to kill time when bored 
If you’re talking about the spawning duration, I’ve already done that. Couldn’t find anything else.
Yes, but obbies still sell products, such as gravity coils, speed coils, etc.
Where exactly did you find that. I swear it just magically disappeared or maybe I’m blind.
I know, just sayin.
You can easily remove forcefield by setting all the “SpawnLocation”'s forcefield time to 0.
Is it possible to add area music, so the harder it is, different music plays, also gamepasses for speed/jump coils (for the weaklings), really good system overall
here is a full feature list actually
gamepass for in-game gear
area music
“elevator parts” - very crude script if you want
spinning parts - again, crude
falling parts, I know how to do this, but I don’t think others do
no collisions between players
and a few more.
There is a resource about the area music, check it out:
that is what im currently using, i was just looking for a way for it maybe to be built in
Dude, you have the reset progress thingy already done. why havent you updated it yet?
I’ll include some more things, then update.
Any suggestions are appreciated!
Already using previous version? Then copy the name of the datastore from SavingScript. Then delete every existing scripts and GUIs, put the new ones. In the model, open “Scripts” script and in line 40, change the datastoreName to the name you just copied so you don’t lose data.
Thank you for using my model in your game.
I will no longer be updating this model. This is the final model. I might update if there are a lots of suggestions or if there is any bug to fix. Thank you for using it.
I don’t think stuff like that should be built in, it makes the obby kit less versitatile, not all obbies have that, the obby system should only include what most obbies share in common.
Instead I think what it need is a good scripting API. For example, an event which fires when a person enters a stage, and then you can connect a function to it.
Everything looks great so far, yet I wonder if you could add props and other obstacles. I think this would be a great addition because some people that would use your kit might not know how to script or build yet. Overall, everything is great so far. 
I am not adding any obstacle because there are already some kits such as JToH which includes them. And since this is a Obby System, it should include scripts, not obstacles. Thanks!
Oh, okay. Keep up the good work though
Looking at most replies, you should just make a full obby game completed ready to be monetized and just open source it for them…
Great project, tho I’ll disable some of your features as they literally kill off what, in essence, is a obby game.
This is helpful! Also for my up-coming Difficulty Chart, thank you!
Iv’e noticed when I used the model, some values in configuration do at all. For example, when I tried turning off player collisions in configuration, I made the value true and it did nothing. This also happens with MobileShiftlockEnabled and DeathEffectDisabled. You may need to patch this bug because I had to fix the scripts myself. Besides from that, this is a great open-sourced model and I think you’re really letting a lot of developers start their first game without having to search for scripters.
Thanks! My bad, I didn’t test the model before releasing. I will be fixing all the bugs as soon as I can.
There is also an error in your code. If you buy a donation from a different product, it counts as a stage skip. People can abuse this by buying a 5 robux donation 10 times instead of buying a skip stage once.
Special thanks to @Cadxsan for letting me know about the bugs.
Any suggestions are appreciated!
Already using previous version? Then get the new model. Delete the old model. Replace the GUI with the new one. Delete stages from the new model if you already have stages in Workspace.
Thank you for using my model in your game.