Please, don't use spaces for team names. It breaks/conflicts with commands etc.

Ok, will look into that. I believe everywhere where you can use parent_obj.property_name, you can also use parent_obj["property name"], but I might change it just for good practice. I also *have to* finally add radars shared vision as option and not necessity. So I guess I might plan update for this weekend.

Some mods, scenarios, commands etc parsing it as arguments. For instance:
/add-money MyForce 300

But it won't work with some symbols:
/add-money My Force 300
Because it'll parse it as 3 arguments ["My", "Force", "300"]

Also, it'll print some strange stuff in the chat sometimes. For instance:
Enemy Forces: player enemy neutral My Force hiddenForce

Also, I have to deal with the stuff, and I think there are other "special" symbols which may confuse people, for example: ', ", \t, \n, ` etc. So, I'll make something for that in some day, because it's kind of complex.

I see, space is very common separator for arguments. Actually the standard separator...

In 0.0.4 I made it, so player force is named player.name+"_force" instead of player.name+" force". I believe it is only thing that I had to change.
I thought about making migration.lua, but I'm quite lazy. I also don't know what implications it will have, especially for games using other mods that remember force names, so I decided I won't do migration file.

From version 0.0.4 new players will receive correctly named forces. Games migrating from v0.0.3 to v0.0.4 of this mod will still have forces containing spaces, if any players ever joined them.

Thanks for highlighting that problem!