As I've posted about earlier, I don't believe "forwarding" of ports is even the bigger issue here.  The biggest issue with Demigod is that the level of NAT-filtering (either on out-going or incoming connections) is breaking things.

Unfortunately many people's setups don't allow for changes to the level of NAT-filtering being applied to their connections (and in some cases their ISP's are the culprits).  Symmetric NAT modems, double-NAT scenarios, ISP NAT-filtering etc. are the big problems here.

I have tested the following on my two internet connections (one is DSL, and one cable)

--  Disabling SPI ("telling SPI to back off"), and "relaxing NAT-filtering "  (as described in my generic networking guide Networking for the Gamer  ) was sufficient  (at least for my connections) I did not need to have any ports forwarded.

The problem is, many routers still don't have options for "relaxing NAT-filtering" etc. and so forwarding ports is the next best option.

Since UPnP is essentially "dynamic" port-forwarding (forwarding incoming traffic on ports the program has sent traffic out on) the only issue I see with using it for Demigod is that it may not detect having to forward traffic on a port-range and could therefore prevent incoming connections on ports that haven't been used for outgoing traffic yet.

Your best bet is to try changing the level of NAT-filtering being applied to (all points of..ie modem, router, ISP etc.) your connection, and if you can't do that, then properly forwarding the ports (port-range) as specified.

the Monk