Bug with localized names of blocks and string length. Script unmodded, single programmable block.

I use russian localized game, so names of blocks use by default cyrillic instead latinic characters. In cases, when command supposes to display blocks AND some data (Working, BlocksCount) - data is displayed beyond supposed border (checked by decreasing font size to 0.2 - data is there, but far away).
Also blocks with cyrillic names seems to be "not found" by some commands (i.e. InventoryX, Cargo), so their data not included in displayed info. I mean, if there supposed using "type" filter - it not works with cyrillic. Or I'm an idiot and and pretend to use 'reactor' w-t quotes as type and only with '[]' or '{}' as name.

I clearly understand, that it is impossible to check without using non-latinic localization, but bug is quite disturbing (because there is no group renaming, and renaming even 20 thrusters one-by-one is pain). I suppose, some of Russian players not familiar with English (I at least can understand English without Google) to use English version of SE.

Oh yeah. There is no way for me (as single person) to handle all 15 languages currently supported by SE. I did what I could to make it as compatible as possible, but I see how cyrillic can be a problem. Names should work correctly as script does not translate those in any way and just searches for blocks with the same string you entered. Also font width of non-latin characters is not correct in most case I know about that. Really sorry you have such problems, but until keen comes up with some more universal way to handle cases like these in scripts I'm afraid I won't be able to fix that. Really really sorry about that.
I can suggest trying 'mass rename' scripts like these two (see which one works for you):
http://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=377001903
http://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=367612757

Also the first argument is always name. never type. suggest you watch the video guide :)

As I was thinking, exactly. There was just hope there is a way to fix.. well, sad, but I happy with your script anyway)) About non-latin characters - maybe, you can add "Known issues" to description? Many people can run into it without any idea, what's going on.

PS: I better with text, than with spoken words in English. So I watch, what you type more, than listen what you say)) Also name "reactor" is much same with type "reactor"... I figure it out anyway, just not so fast.

@jack I knew that not everyone will understand what I say thats why I showed it with "Small" and "{Small Cargo}" in the guide so it is understandable. Good that you figured it out. There is not any place left in the steam page description, but I will create special page for guide itself and we will have more place in Workshop Description to add known issues and other things I would like people to know. Thanks for suggestion!

is number of rows calculated form size of letters? because i still have free space on display and its scrolling(size 0.8)

number of lines always exactly fits the display size. if your display is scrolling it probably means there are empty lines. What is your command line?

this script was made for font size 0.8. I use only that font size on all my panels. There is no free space. Maybe you can try to post screenshots?

have been trying to reference turret blocks. with both "Working" cmd and the BlockCount cmd. block count for turrets show as 0. and Working cmd gives no info status back for any turret (gatling turret or missle turret) block. I am indeed using full name and using correct {}. have also tried [] an * with name. can anyone else reference block type turrets?

please tell exact command that you use

Large Gattling Turret type = largegattlingturret
Large Interior Turret type = largeinteriorturret
Large Missile Turret type = largemissileturret

So your command would look like Working * largegattlingturret

I will probably improve that by removing the large from the front.

UPDATE: it's now much better set so missileturret gatlingturret and similar should work now.

I see the conflict that I have created. Thank you again for your effort to make such a lively product. Your code is also very clean an easy to look through; makes a a good tool to learn from.

This script does not sort the output. It shows it as the game tells it.

If I use "Working {Bridge Light Nav} Lights:On" as a command on LCD panel I get an script too complex. Seems any string over a certain length will cause this.

If I use "Working {Bridge Light} Lights:On" it works fine.

Zero modification to script.

@Delta99: I've improved it - check if it is better now.