The CMD displays "Do you agree to the Mojang EULA available at /documents/minecraft_eula? ". So I double click the new launcher's variant, the WBF called "start" and that where I encounter the following problem. However -as with the servers from the old FTB launcher- when trying to set up the server to run, it required activating the Windows Batch File(WBF) "ServerStart". I do use Hamachi to host so I enter the IPv4 in the server settings and such, save, and close. Then I activate the "forge-1.7.10-10.13.-1.7.10-universal" Executable Jar File and I let it do its thing completely before ending the process. ![]() I then double click "eula" Notepad file and set it to true, save, and close. I double click the "serverinstall_23_23" and agree to the prompt, it installs Forge and so forth. I have been wondering if it an issue with the way I've been installing it so for a quick summary: Now, installation was fine on the app, I downloaded the modpack and then downloaded the server file. I'm unsure if this matters or not but I thought I'd included it with it being related to the software have file searching/location/access issues. The FTB Infinity 1.7 modpack specifically, a server that I've been able to run successfully on the previous launcher for years now with no issue -small scale, private servers, 1-5 friends at maximum.Īt the time of this post: I'm using Windows 7, I'm using the most up-to-date version of Java (first thing I checked), and my C: drive is partitioned into two drives (C: and S: ) and I have the old launcher, the new, and the modpack downloads in. So, I've been trying to run a server that I've downloaded from the New "FTB App" launcher (first time trying to set up a server from the new launcher).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |