When to write editor scripts, and when just scripts?

Yeah that. I'm confused, when should I write editor scripts and when simple scripts? Whats the benefit? Is it better to write editor scripts for some small systems like a player controller or gun script, or something like that?

I'm mainly asking because I wanna make some for the asset store. I made one small Teleporter Pad script, as a simple script, but do you think I should have made it as an editor script? It has almost 300 downloads, 4 five star ratings, and whatever rating that dropped it to 4 stars. Guess someone didn't know how to read the Readme file included. xD

So to repeat my confused question, editor script or script? For controller systems or something, if you need a specific. Or is that not how you decide which to write at all?

 

Simple systems & single scripts can use the Inspector. For larger systems with multiple scripts to get a user up and running and Editor Interface may be desired. I like them when I have to set vars and cannot see the results till I hit Play. If I can see the reaction of a variable change in the Editor then that makes my task as dev or designer easier to cope with and swifter to come to a conclusion about what should be used in context.

 

Yes and make sure you keep that editor organized. I hate it when scripts have this disgusting out of order editor

 

Apples and oranges both can belong in the fruit bowl. I think his question as I understood it is when do you think an Editor script should be hacked together to support the game script/s.

 

That's the question! How are they different, and for what different situations? I started watching the tutorial but got confused because you can do that with normal scripts too.

 

Ah, so editor scripts serve to help existing game scripts, or/and do work inside the editor? I'm sorry if my questions aren't making sense, I got really sick and I'm all dizzy, feverish, hurty, and confused. xD

 

Editor scripts only work in the editor; they literally don't even exist in the final game. If something is only useful in the editor and doesn't need to run in the actual game, then it should be an editor script. If it is something that will run during the game, then it can't be an editor script.

 

It sounds like maybe you're talking about writing a "Custom Inspector", which is a script that lets you change what the inspector looks like for a script. A Custom Inspector is a type of Editor script, but not all Editor scripts are custom inspectors.

 

Thanks guys! I understand it better now. I was confused cause I had no idea the editor scripts don't run at all in the game, but now that I know that, it makes way more sense. xD

 

Thanks again everyone for clearing this up to me, editor scripting is actually pretty fun. Its like filling in little gaps Unity has or adding functions to it. Don't know if clear parent exists built-in but it was fun learning experience anyway.

As my first tools I made:
1. Clear Parent
2. Create empty and parent selection to it
3. Clear, create, and parent selection to it



I use those three things a loooot, especially the last one, so its incredibly useful to me and speeds up making assets.