W:A Not detecting external IP correctly

[Genexi2]

Been getting into the hosting thing recently after learning I could assign static IPs on my router via MAC addresses, making port forwarding hassle-free without the need to disable DHCP.

Came across the problem where I'm forced to enter my external IP manually in W:A and checking Force-IP because it is detecting it incorrectly (it gets the first two sets of numerals right and that's it). Is there anything I could do to fix this?

I'm finding it a bit annoying having to enter W:A, set the right IP, force it, close W:A, and then work from ProSnooper.
(I find ProSnooper to be faster at hosting/joining games overall vs. W:As built-in browser)

On a side note, does anyone know if the schemes on Worms2d.info are the accepted standards? I've seen one too many hosts with crap Shopper schemes for instance, and I'd rather not be one of them myself.

[EDIT] May as well add more questions in while I'm at it. Is there a full list of rubberworm commands out there? I've seen some hosts doing things such as increasing game-speed, and I can't find information about that on Worms2d.info.

[GreeN]

My personal choice for this problem you are having, is to use a DNS address. DynDNS (https://www.dyndns.com/) is a free service allowing you to choose a personal DNS address for your IP (This works with dynamic IP's by having a small application constantly log your IP and routing the DNS address accordingly). You can therefor use this DNS for an infinite amount of routing purpouses, including a permanent link to use in worms for others to connect to you

As for the RubberWorm commands, see here (http://worms2d.info/Rubberworm)

[CyberShadow]

The IP address detected by WormNET is the IP address that WormNET sees you connecting from. Note that WormNET performs a reverse DNS (which W:A uses as-is in the game list, unless it's too long - in which case it resolves it to the IP address). So, what's really happening is most likely one of these:
1) Your ISP's DNS servers aren't working properly
2) Your ISP is doing something extremely weird, and your connection goes through a NAT and apparently comes from another address than what should be used for incoming connections to your router
3) Your description of the problem is inaccurate, and the problem is somewhere else

There are no "standards" for most community schemes, some leagues/tourneys may define such standards within the bounds of the event though.

GreeN: DynDNS is obsolete except in such situations (which are extremely rare) or if you want a customized hostname appearing in the "Connecting..." dialog.

[Wormetti]

I took a look at the ProSnooper code and it gets the hostname from win.ini by default. If you untick a checkbox then it tries to get it from this broken website (http://djlol.dk/ipaddress.php) (even if the site worked, the detected hostname would be unreliable if your ISP uses a transparent proxy). It should be updated to get your hostname from the IRC server (like WA does) but until then you will need to put the right hostname in win.ini (dyndns would save you from updating it) or use another client.

WA only reads a new hostname when it connects to the IRC server but since ProSnooper tells WA to run with the /host parameter, WA never connects to any IRC server. WA also only saves the hostname to win.ini on exit.

[Muzer]

My personal choice for this problem you are having, is to use a DNS address. DynDNS (https://www.dyndns.com/) is a free service allowing you to choose a personal DNS address for your IP (This works with dynamic IP's by having a small application constantly log your IP and routing the DNS address accordingly). You can therefor use this DNS for an infinite amount of routing purpouses, including a permanent link to use in worms for others to connect to you

As for the RubberWorm commands, see here (http://worms2d.info/Rubberworm)
Most routers also have a service in which they will do this automatically, eliminating the need to have a program running. Check in your router's settings for something along the lines of Dynamic DNS or DDNS, and see which service(s) it is compatible with.