- Should i add those data to debug console everytime i want to log in ?
No; 'add' should add them permanently to your list of peers; 'onetry' just attempts the connection right away.
- When the release of 1.3.0. version? i didn't find it in GitHub releases page.
As soon as new seed nodes are deployed in another two countries I should start building; hopefully within a few days at most.
It is unfortunate that in the current version of the wallet there is no function to do this with one click, as in many other coins with MNs. It would be great if the developers implemented such a function in the new wallet version. Although you say that there is no need to ban the wrong masternodes, I believe that this is not the case. Incorrectly working MNs can lead us to the wrong chains under certain circumstances.
In this particular case, misbehaving nodes can't get you synced with the fork chain. If you use a new client and even if you are connectly to old misbehaving/old peers you will get stuck at block 2xxxxx something (I don't remember the exact number now). At that point you would be stuck forever (i.e. never synced up with the fork chain either) until you manually resolved it by fetching blocks that don't break consensus rules.
Anyhow, 1.3.0 should block connections to pre 1.2.0 nodes.
Be so kind as to give an example of a console command to ban one or another masternode.
setban 0.0.0.0 add 864000
This would ban the IP 0.0.0.0 for 864000 seconds.