dgecko

Thanks for all the advice , and understand the issues re not recommending it for a dev machine, with stuff already binding port 80. Thanks for the link to the jar for 1.2.0, must have overlooked the fact that the one in the launcher is just the same one you've uploaded before, and your link contains different versions. Grabbed it, edited the butterflyserver.properties file in the jar, and worked good, after tweaking ea3-config.xml, because it starts on 0.0.0.0:<port> instead of localhost/127.0.0.1, which is odd, but hey, got it working and running fine. Strange that the devs didnt think of just building a version where you could just pass --port 90 (whatever) in from the cmd line, for these kinda issues. Also once server is running manually, great to still be able to use the DDR P.U.S.S.(I.E.) launcher for everything else, so great work on that. I see the launcher tries to delete the .jar file after trying to launch butterfly.exe (s you've mentioned in your previous post it should), luckily because it's running fails to delete it, and the edited version doesnt get scrapped. Thanks again, and thanks for everyone's (*credit roll*) effort in making this possible for us all.

Noted all the references, been reading the forum from page 1, before jumping in head first, as I tried not to be dumb about it I know that's not taken kindly to here I wouldn't say I am purposefully running something on port 80 already, but this is a dev machine, so quite likely something is just running on it by chance. from the sysmanager I just see SYSTEM (PID 4) hogging port 80, and from all the googling and trying to get the OS to release it, not much has worked. even stopping almost all services related to http/IIS etc. netstat also just shows it being listened to by SYSTEM. And yes you referenced the correct post As I've edited ea3-config.xml and apppended a new port, didn't really resolve it. Butterfly.exe just starts up in the bottom and dies 2 seconds later, so thought the port could be hard coded, as the log still shows the game trying to connect on 127.0.0.1 90, but I'm assuming the game log is getting that from ea3 conf for the game for server info. But if it's not actually running, the game wont find it, unless eas3 is the config file for butterfly and not just the game. Also editing ea3 conf, and running butterfly.exe from cmd still logs to console to show its trying to bind to port 80, regardless of what is set in ea3 conf file. Hence I referenced the post, as I guess Im not sure that there is a config file for butterly itself to set it's running port. I did realise the launcher extracts the files to temp and then generates butterfly.exe , my AV flagged it a few times for that, until I've disabled the AV entirely and started from scratch so it doesn't interfere on launch, however it's the same. Upon Launching DDR P.U.S.S.(I.E.) , everything loads fine, just buttterfly.exe opening and dying straight after. Hope that explains the situation.

Thanks for the reply. I am using the new DDR P.U.S.S.(I.E.).exe launcher from Topek2k2001. However I notice on launch Butterfly.exe starts then dies shortly thereafter. The game launches afterwards just with the message in bottom left "Confirming Network Connection Status : Gameplay is not accessible at the moment". The log confirms this: [2020/08/17 02:53:00] M:servurl: "services" => "http", "localhost", "/", 127.0.0.1, 0. [2020/08/17 02:53:00] W:servurl: bad services host(localhost) And then just running butterfly.exe from cmd: java.io.IOException: Failed to bind to /0.0.0.0:80 at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:346) at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:308) at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80) at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.server.Server.doStart(Server.java:396) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at spark.embeddedserver.jetty.EmbeddedJettyServer.ignite(EmbeddedJettyServer.java:149) at spark.Service.lambda$init$2(Service.java:574) at java.lang.Thread.run(Unknown Source) Caused by: java.net.BindException: Address already in use: bind Hence why I'm thinking it's because of the port 80 issue, and being able to still change it should fix it.

Hey guys. Wondering if it's still possible to change the default port on which Butterfly runs, 80 to something else. I saw the old post by BlueSupernova22 by which you could just modify butterflyserver.properties file in the jar was useful, but now Butterfly is a compiled .exe. I found that SYSTEM (Process PID 4) is hogging port 80 on my machine, and after numerous steps to kill it (net stop http etc), its not giving up. So was hoping it's still possible to modify the default port.