I will write documentation for unity game mechanics and systems in obsidian

I will document you game mechanic or a system in an Obsidian vault. You may provide an existing vault, or I can create one. I will first review your code so that I may understand what I'm writing, then I will start to map out the mechanic, then the scripts.

If you wish to format the documentation differently, I am open to that as well.

My usual documentation structure:

For the mechanic:

• About - What the mechanic or the system should do, its possible quirks
• Get started - A guide on how to get started, set up the system.
• Mechanics / Methods / Technicalities - this depends on the mechanic or system
• Nuances - if needed
• Dependencies - links to scripts connected to the specific script, system or mechanic

For the scripts:

• About - this includes the path to the script, its purpose and possible quirks.
• Get started - if needed for that particular script.
• Variables - this section will explain the role of each variable, private or public.
• Technicalities - This includes methods, their proper usage, nuances and more if needed.