Stats Large Packet Identifier

[wildwang]

Author

WildWang

Contributors

N/A

Quickbar Entry

javascript:
$.getScript('https://dl.dropboxusercontent.com/s/p1yobrxt9a3uwtb/WildWang_identifyBigStacks_1.0.0.js?dl=0');

Public?

Public

Script locates large packet sizes as defined by user and returns that information to you. Especially useful when you have thousands of support packets in your villages, and want to quickly locate where some villages are 'over-stacking'.

Currently works with English and Portuguese.

An example of what it looks like on 117:

javascript:
$.getScript('https://dl.dropboxusercontent.com/s/p1yobrxt9a3uwtb/WildWang_identifyBigStacks_1.0.0.js?dl=0');

 

[RedAlert]

Approved.

 

[The Quacks]

Hi @wildwang , here is the Portuguese translation:

Spoiler: code

pt_PT: {
    'Lanceiro': 'spear',
    'Espadachim': 'sword',
    'Viking': 'axe',
    'Arqueiro': 'archer',
    'Batedor': 'spy',
    'Cavalaria Leve': 'light',
    'Arqueiros a cavalo': 'marcher',
    'Cavalaria pesada': 'heavy',
    'Ariete': 'ram',
    'Catapulta': 'catapult',
    'Paladino': 'knight',
    'Nobre': 'snob',
}

Also, if you wish to check the language directly, you can see the following object:
game_data.locale

 

[The Quacks]

One more thing, do I have to be on an English speaking server for the script to work? If not I am not sure how to use it, this is all I get:

 

[wildwang]

One more thing, do I have to be on an English speaking server for the script to work? If not I am not sure how to use it, this is all I get:
View attachment 7289

Going to add in your translations, thanks for the tip. Yeah you need to be on an English server for it to work (as we use the title of element to fetch the unit type). With the translations, it should hopefully work for your server.

Edit: Translations added, and we now fetch language based on `game_data.locale`. Hopefully it works for you now

 

[The Quacks]

Going to add in your translations, thanks for the tip. Yeah you need to be on an English server for it to work (as we use the title of element to fetch the unit type). With the translations, it should hopefully work for your server.

Edit: Translations added, and we now fetch language based on `game_data.locale`. Hopefully it works for you now

Thank you very much!

 

[wildwang]

V1.1.0 is now out for the large packet identifier. New UI was designed to make visibility MUCH better.

 

[RedAlert]

Hello @wildwang ,

Is the new updated script version here?
https://dl.dropboxusercontent.com/s/p1yobrxt9a3uwtb/WildWang_identifyBigStacks_1.0.0.js

Script seems to not work anymore since you removed this:

var settings = {
    maxTroopCounts: {
        'spear': 200,
        'sword': 200,
        'axe': 0,
        'archer': 200,
        'spy': 50,
        'light': 0,
        'marcher': 0,
        'heavy': 100,
        'ram': 0,
        'catapult': 50,
        'knight': 1,
        'snob': 0,
    },
};

 

[wildwang]

Hello @wildwang ,

Is the new updated script version here?
https://dl.dropboxusercontent.com/s/p1yobrxt9a3uwtb/WildWang_identifyBigStacks_1.0.0.js

Script seems to not work anymore since you removed this:

var settings = {
    maxTroopCounts: {
        'spear': 200,
        'sword': 200,
        'axe': 0,
        'archer': 200,
        'spy': 50,
        'light': 0,
        'marcher': 0,
        'heavy': 100,
        'ram': 0,
        'catapult': 50,
        'knight': 1,
        'snob': 0,
    },
};

Ah my mistake, I uploaded the wrong file to dropbox. Should now be working

 

[RedAlert]

Can not test at the moment if the script is working or not ... 2 small suggestions.

Update the version number of the script on each script iteration.

Do not include in the filename the script version. Just because its confusing and misleading if you are on script version 1.1.0 for example and filename still says 1.0.0.

But do not change the filename now otherwise it would break quick-bar entry scripts.

Just suggestions not rules, its up to you if you want to follow them.

 

[wildwang]

Can not test at the moment if the script is working or not ... 2 small suggestions.

Update the version number of the script on each script iteration.

Do not include in the filename the script version. Just because its confusing and misleading if you are on script version 1.1.0 for example and filename still says 1.0.0.

But do not change the filename now otherwise it would break quick-bar entry scripts.

Just suggestions not rules, its up to you if you want to follow them.

yeah I realized that the version shouldn't be in the filename because it messes up the quickbar scripts :| version already added inside the script at least