Incomings Overview

misteralb

Non-stop Poster
Reaction score
111
Incomings Overview

Approved: t14466468

incomings-overview.png

This is how the script looks in action:

Script Loader:

JavaScript:
javascript:var NOBLE_GAP=100;var FORMAT='%unit% %player% %sent%';$.getScript('https://dl.dropbox.com/s/hsmkwy13l62y9ha/incomingsOverview.js');

User Variables:
NOBLE_GAP defines the attack gap in milliseconds. From world to world this changes and there is no automatic way to get this from the world config (a call here for Inno devs to add such info somewhere, either on world config files or even better on game_data global object)
FORMAT defines the mass tagger format. Possible format variables that can be used are:

%unit% - type of unit sent, example Spy, LCav, etc
%sent% - time when attack was sent as calculated from the unit type, example Jan 13, 15:38
%duration% - duration in formatted time, example 0:09:02 (so 9 minutes and 2 seconds)
%distance% - how many fields away is the attacker from defender, example 1
%origin% - origin village info, example A001 (430|516) K54
%arrival% - time of arrival of incoming, example Jan 13, 15:56
%player% - attacking player, example RedAlert
%coords% - attacking village coordinate, example 430|516
%return% - shows the return time of the incoming, example Jan 13, 15:38
%destination% - destination village info, example A001 (430|516) K54 (posted this only for reference, DO NOT add this on the script format since it will break the script loading even though it is a valid tag)


Notes:
- When you click the Mass Tag Incomings button the incs screen will reload so you will have to re-run the script to continue doing whatever you where doing.

Feel free to suggest features, ideas and/or report any issues/bugs or let me know if you need any help with this script by replying on this thread.
 
Last edited:

misteralb

Non-stop Poster
Reaction score
111
Hello @The Quacks ,

I consider as possible nobles 2-3-4 or more consecutive incomings for as long as their millisecond difference is equal to the NOBLE_GAP.

So if you have 2 incomings which land for example at:
00:00:00:200
00:00:00:400
and NOBLE_GAP is 200 then these 2 incomings will be considered as possible nobles.

If the enemy player has sent some attack to land in between those 2 ... then the script will fail to highlight the incomings as possible nobles :(

Something that probably could be improved in the future.
 

The Quacks

Member
Reaction score
14
Alright, still pretty nice. You could probably sort all attacks and compare each attack with all incomings in the previous / following 1 second and it would still work without being too slow. Eager to use the script!
 

misteralb

Non-stop Poster
Reaction score
111
Script is now updated.

Changelog:
- export incomings is now working as it should
- added mass tagging capability

Regarding mass tagging ...
It generates a tagging by default following this format: %unit% | %sent%
The format is player editable though :)
So if you don't like it ... you can use for example something like:
%unit% %player% %sent% :p

How can that be done?
JavaScript:
javascript:var NOBLE_GAP=100;var FORMAT='%unit% %player% %sent%';$.getScript('https://dl.dropbox.com/s/hsmkwy13l62y9ha/incomingsOverview.js');

Attention:
When you click the Mass Tag Incomings button the incs screen will reload so you will have to re-run the script to continue doing whatever you where doing.
 

misteralb

Non-stop Poster
Reaction score
111
Script is updated.

Latest script version (v1.3.0) now includes a watchtower timer tool also.

Thanks to @DaWolf85 for the watchtower timer :)

I have actually integrated his script into Incomings Overview.