Message Spell Checker

https://github.com/exawon/UnityScriptAccessories/blob/master/Editor/MessageSpellingChecker.cs

Just place the file in the folder 'Assets/Editor' of your project.
It will try to find out doubtful spelling whenever your scripts are changed.

Don't hesitate to leave your question or opinion.

Thank you.

 

I would recommend getting comfortable with the debugger and then putting a breakpoint inside the function you THINK should be getting called, then when that breakpoint fails to trip, you can quickly start checking the obvious things like misspelled method names, etc.

If I write a function, run the code and the function doesn't get called when I think it should be, the first thing I do is attach MonoDevelop debugger and put a breakpoint in and start tracing what's going on, and that draws your eye right away to the method name.

 

Hi, Kurt.

I don't know why you are lecturing me here about "getting started with debugging".
However, I'm very comfortable with the debugger and I do THINK when I use it.

As you already know well, misspelling is not the only one reason for missing a message call.
I've intended to exclude a misspelling case from those reasons with less effort.
Like lint and compiler warning.

Would you tell me why I still have to trace the breakpoints
when I know how to recognize troublesome before attaching debugger?

 

You are welcome to code however you see fit. Carry on!