Well, this was opened as a bug report not a feature request. This worked in 1.5.2 and since it does not in 1.7.2 it is a regression. I respectfully request this issue be reopened as a regression since it's not a new feature but just restoring the previously existing functionality – functionality that existed and worked when I paid for the product but no longer does.
Yes, I did use the search function and I did find that ticket but I disagree with it's Resolution "Works as Intended" since "Works as Intended" is a regression from previous versions where I could play the game I paid for and now I cannot.
No, this is not a duplicate of MC-38872. Talk about completely missing the point. This issue has nothing at all to do with whether java proxy parameters are ignored or not. I was just offering my command line with them in it so that you could see that I was giving minecraft every possible option to find out that it needs to use a proxy. I guess that's what I get for trying to offer as much information as possible.
The point of this ticket is that multiplayer functionality is not using the established proxy, socks5 or otherwise. Single player uses the proxy just fine. Multiplayer is not using the exact same proxy to connect to minecraft servers but is instead trying to connect directly.
So please, re-open this issue and un-duplicate it from MC-38872 and don't close it until multiplayer functionality is actually using the same proxies as single player.
Brian J. Murrell
MC-40758
Well, this was opened as a bug report not a feature request. This worked in 1.5.2 and since it does not in 1.7.2 it is a regression. I respectfully request this issue be reopened as a regression since it's not a new feature but just restoring the previously existing functionality – functionality that existed and worked when I paid for the product but no longer does.
Yes, I did use the search function and I did find that ticket but I disagree with it's Resolution "Works as Intended" since "Works as Intended" is a regression from previous versions where I could play the game I paid for and now I cannot.
No, this is not a duplicate of MC-38872. Talk about completely missing the point. This issue has nothing at all to do with whether java proxy parameters are ignored or not. I was just offering my command line with them in it so that you could see that I was giving minecraft every possible option to find out that it needs to use a proxy. I guess that's what I get for trying to offer as much information as possible.
The point of this ticket is that multiplayer functionality is not using the established proxy, socks5 or otherwise. Single player uses the proxy just fine. Multiplayer is not using the exact same proxy to connect to minecraft servers but is instead trying to connect directly.
So please, re-open this issue and un-duplicate it from MC-38872 and don't close it until multiplayer functionality is actually using the same proxies as single player.
Thanks.