Start Documenting Roblox's Standard Scripts

[karl-police]

Checks

By submitting your pull request for review, you agree to the following:

• This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
• I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
• To the best of my knowledge, all proposed changes are accurate.

Changes

The changes introduce early documentation about Roblox's Standard Scripts. This is important because things like the CameraModule do things is important to know about. For instance, the RenderPriority of the Camera and how it changes the CFrame of the camera. Otherwise, it causes confusion.

The current text and information is through careful analyzing and from Roblox's own comments within the code. There is not much documentation yet, because I happen to find bugs that need to be resolved before this documentation can continue. Until then, I want to share my vision on how these documentation could be structured and look like and hope to have this PR accepted, which provide this initial set up for documenting Roblox's Standard Scripts, as I did all these changes just by using the GitHub websites. I even had to temporarily change .gitattributes just to upload a PNG.

It also adds info about BoundKeys which is a StringValue that is comma-separated and can be overwritten to change the bindings for Shift-Lock.

This documentation is necessary so that there's also official guidelines on what can be done and what shouldn't be done. Keep in mind that the PlayerModule says that a Creator is allowed to access things that it provides, but never had a documentation.

Bug Reports:

• https://devforum.roblox.com/t/robloxs-cameramodule-doesnt-ever-return-the-camera-to-the-playermodule/4451947

[karl-police]

test

[michaeltipman-gif]

No cousin