Everything posted by DaemonUmbra
-
trouble running mods on a server
Are you getting the same error when you try to launch it?
-
trouble running mods on a server
Saw this same error with someone else the minecraft server jar was getting corrupted when Forge's installer downloaded it, try this: Forge is expecting minecraft_server.1.12.2.jar
-
trouble running mods on a server
Ok, I'm not in the mood for a cmd tutorial so let's take a shortcut: open the server folder in file explorer click anywhere that won't select a file hold shift and right click without selecting a file click open <Command Prompt/Powershell Window> here once you've done that follow the instructions from my previous reply
-
trouble running mods on a server
When I say command prompt I mean if you're on Windows use cmd(or Powershell), if you're on a *nix OS or Mac, use a Terminal, navigate to the server's folder and type java -jar forge-1.12.2-14.23.4.2705-universal.jar -Xmx3G -Xms3G nogui
-
trouble running mods on a server
Start it from the command line and show what it spits out
-
trouble running mods on a server
You start the forge universal the same way you would start the server
-
trouble running mods on a server
You're starting it with the forge jar and not the minecraft jar, right?
-
trouble running mods on a server
That's not fml-server-latest, that's just latest. Can you send a screenshot of your server's root folder (the one where the server jars are)?
-
trouble running mods on a server
could you put the fml-server-latest.log on pastebin and link to it here?
-
trouble running mods on a server
Are you opped on the server? If not then that is likely to be spawn protection preventing you from building or breaking blocks too close to spawn.
-
trouble running mods on a server
Can i get a fresh log?
-
Item model doesn't work
Problematic code #1: (this includes the ModelRegistry)
-
[Solved] [1.12.2] My mod doesn't work at all after exporting it.
sourceSets { main { java {srcDirs = ["$projectDir/common"]} resources {srcDirs = ["$projectDir/resources"]} } } should be sourceSets { main { java {srcDirs = ["$projectDir/src/main/java"]} resources {srcDirs = ["$projectDir/src/main/resources"]} } } Gradle seemed to cache this when I corrected it, built, then removed the sourceSets group entirely, and I believe this is the default if not overridden as you did.
-
'decompWorkspace' not found in root project
What are you trying to run decompworkspace for, what are you trying to do?
-
Building failed
- trouble running mods on a server
It starts it but it doesn't mean it's launched with the correct options, create a file called launch.bat and put this in it: java -jar forge.jar -Xmx3G -Xms3G pause Note that you will need to replace forge.jar with the name of the forge universal jar. Double click the launch.bat and it will start the server with more RAM, which might make things a bit clearer.- trouble running mods on a server
Are you starting your server through the command line or are you just double clicking it?- trouble running mods on a server
Where are you getting your mods?- trouble running mods on a server
NEI is almost entirely clientside, it shows you the items that your client can use, not necessarily what's on the server. What server jar are you launching, the forge one or the minecraft_server.1.12.2.jar? Edit: I'm stupid and forgot there are no forge info messages in latest.log- trouble running mods on a server
That log is from a server that is trying to start up when another server(Or another program) is already running using the same port. From the sound of it you have a vanilla server running when your forge server tries to start, so you are joining the vanilla server thinking it's the forge server. Edit: It actually looks like you're starting a vanilla server rather than a forge one anyway- Unable to launch forge-xx-universal.jar, log+cmd error+java versions included
You are very welcome- Unable to launch forge-xx-universal.jar, log+cmd error+java versions included
In the launch command instead of just using "java"- What does this mean?!
If you mean the func_##### stuff, that's an obfuscated name from Minecraft itself, it gets changed into a more human-readable name by Forge during development environment setup, provided there is a mapping for it, it gets turned back into the obfuscated name when the mod is compiled so that it correctly references the function in Minecraft's jar file during runtime. Other than that I'm not quite clear on what you're asking. Edit: If you're seeing it in a mod's source (i.e. on GitHub) it means that mod was developed with a version of Forge that did not have a "mapping" to a more readable name for that function.- Unable to launch forge-xx-universal.jar, log+cmd error+java versions included
Reading the EAQ helps too, you need to launch forge with Java 8, your PC will try to use the latest installed version (in this case 10) unless you specify by using the full path of the Java executable (Java.exe) of the version you want.- Extension for language file inside Resource Pack
For anyone else finding this through google, it's mentioned in williewillus' 1.13 update primer which also has a link to another modder's lang-to-json conversion utility. - trouble running mods on a server
IPS spam blocked by CleanTalk.
Important Information
By using this site, you agree to our Terms of Use.