Maybe because they all already exist just have no values to them and there all set to null until we modify them with findImg()

If they are set to null then they do not exist. Imagine how much memory it would waste to have all the possible image indexes already associated with an image object in memory.

Stefan said himself that findimg() is creating a new image when one isn't found. showimg() may be shorter but its not clearer to anyone new to GScript.
You're not serious are you? The functions are similar in the fact that they find objects however those objects are used in very different ways. findimg() creates an image when one isn't found for ease of use when manipulating indexed images.

I'm fully aware of that.
In my experience, people learning gscript find showimg() easier to understand than jumping straight into with (findimg()). That's because the other similar functions (findplayerbycommunityname, findnpc, findweapon, etc) do not instantiate anything when called. They expect the object to already exist.
I am not sure how they are used in different ways. All it is doing is providing an object to work with. In your example, it's taking the object and bringing it into the current scope to change a few variables. In my opinion, it should be assumed that the object already exists, because I believe that scripting languages should be semantically consistent.

exactly, if something is null (in computers) it does not exist. Guess I kinda worded that wrong.

May I say something? Stefen, I can't change my font size anymore... Whats up? Its like bulky now :frown: