To be honest, if you are too afraid to edit the code in fear it will mess it up, then you really aren't going to get anywhere.
So rule one: Backup.
When you get your code working, make a copy. Copy the whole folder into a "backups" folder, and date and time it:
That way, you can go back to a previous version at any time and know it should work. For more advanced students, create a repository on Github, and use source control to "Check in" working versions, and "Check out" to get them back again when you mess it up.
The rule two: Learning.
You won't learn much - and certainly not anything useful - by getting others to do it for you. You learn best by trying, and making mistakes: so if you think a "max patch" might do the job, then try it! All you have to lose is a little time, and it might work. If it doesn;t, you will have learned something about "max patches" which may be useful next time.
But to be honest, if you are new to coding, you are probably attempting a project which is well above your current pay grade, and I'd strongly suggest that you get some experience under your belt with simpler stuff, rather than diving in with something that even experienced developers would probably want to sit down and think about for a couple of days before even starting to design the system!