Warrior General Games

+1

How about the one that adds your %'s in your AI Outputs and tells you when it's 100 or over / under? I get tired of counting them up.

+1

It is not nearly as simple as the OP makes it sound.

-1

Originally posted by IdRatherFlyFish
It is not nearly as simple as the OP makes it sound.

-1

Why not?

+1

Originally posted by IdRatherFlyFish
It is not nearly as simple as the OP makes it sound.

-1

Didn't say it was simple but if players can script it why couln't professional developers? I think this kind of stuff would fall under the finished product category. Or maybe just give pabst and the others a paycheck.

First of all, thanks Osiris for, at least, putting all the scripts in one "easy-to-find" place. Have a beer on me.
Second, I hear ya Fish...

Originally posted by IdRatherFlyFish
It is not nearly as simple as the OP makes it sound.

-1[/QUOTE

... But, even though it wouldn't be easy... it should be considered. And attempted as best can be if wanted badly enough.

+1

Show remain training point amount if it could be~~~~~~

GLB has adopted scripts before. Some may be harder to work in than others, but perusing the scripts is a great way for Admin to see what the main customer base really wants. Adapt as best you can. People will notice.

+1

+1

+1 : I've recommended most of those to be part of the program myself.
If GLB adopts the field script, they can institute some controls over fields used along with a few other things.

Originally posted by Myd
Why not?

Most of you know that Greasemonkey is client side script (Most likely Javascript). Each of the major browsers implements Javascript slightly differently. So, take the Player Builder as an example. If we want it to run in IE, FF, Safari and Chrome, there is a real strong chance that four different versions of the same script need to be written so that we get the same functionality in each of the different browsers. (Chances are that FF and Chrome would interpret the Javascript in the same way).

So while it seems easy enough to "Implement a few of the most popular Greasemonkey scripts", you can see where that quickly becomes a versioning nightmare as each of the four major browsers are on their own development and release cycle. Not to mention the lesser browsers (such as the one on Kindle Fire), huge testing burden there - and we know how good GLB is at testing

Peace,

Fish

Originally posted by IdRatherFlyFish
Most of you know that Greasemonkey is client side script (Most likely Javascript). Each of the major browsers implements Javascript slightly differently. So, take the Player Builder as an example. If we want it to run in IE, FF, Safari and Chrome, there is a real strong chance that four different versions of the same script need to be written so that we get the same functionality in each of the different browsers. (Chances are that FF and Chrome would interpret the Javascript in the same way).

So while it seems easy enough to "Implement a few of the most popular Greasemonkey scripts", you can see where that quickly becomes a versioning nightmare as each of the four major browsers are on their own development and release cycle. Not to mention the lesser browsers (such as the one on Kindle Fire), huge testing burden there - and we know how good GLB is at testing

Peace,

Fish

If it worked that way, but if you make the 'scripts' part of the actual GLB programming then the various browsers are only having to read the website. The browses themselves should not see any differences.

Originally posted by Skoll Wolfrun
If it worked that way, but if you make the 'scripts' part of the actual GLB programming then the various browsers are only having to read the website. The browses themselves should not see any differences.

It does work that way. The site would have to have a different set of Javascript for each of the major browsers.