What documentation do you need? The code is right there... I mean I know what you mean but...

What documentation do you need? The code is right there... I mean I know what you mean but...

but...what? :3

But what are you gonna do? List all the built-in script's methods and classes? Seems like if I wanted to look at what they did I would look at the code, though I guess the point of documentation is so you don't have to.

That's actually what I'm going to. I mean yes we can just do it, but clicking and scrolling back and forth in the editor is tedious. Think of a handy reference we can use when aliasing or redefining definitions :3 just something to kill time

You know what I think would work better? More comments! I mean the thing about the default scripts is you kinda need to know how they work more or less exactly if you are going to mess with them don't you?

Hmm... Good idea.

Comments about how they work, the return value and its class... That sounds neat. Compile all the comments to a file for neat viewing :3

Hmmm... Isn't that sorta how java documentation works? I am not sure.

Isn't there this thing called Slip Into Ruby which documents this?

Hmmm... Isn't that sorta how java documentation works? I am not sure.

I was imagining something like the RPG Maker VX Ace's reference in their help files, but this time it documents the classes pre-made in new projects (like Cache, DataManager, BattleManager, etc...)

Isn't there this thing called Slip Into Ruby which documents this?

Slip into ruby? Haven't heard, can you tell me more?