Everything posted by LexManos
-
Forge: It's time to say...
FML for 1.8 is already out and available for use on both the modder side on user side. Once that stabilizes, I update Forge. Simple, modders should start working on 1.8 and let me know!
-
Minecraft (forge profile only) suddenly stopped running after launcher?
Update Forge.
-
Bug: Crash on 1.7.10 servers using plugin for lobby+multiple servers
Update your Forge.
-
1.7.10 Forge Server is Being Unstable
It crashes when people connect Because when people connect it has to define a boat load more classes related to people connecting. Simple, it's a permgen issue, simple as that, there is no questioning that it is right there in your logs.
-
Persistent issues hosting Forge server.
When you run the server from the command line Shit gets print to that console That is the log and it will tell you exactly what is wrong. So get us that log.
-
Trouble installing
You need to download the correct version of Forge for the version of Minecraft you're trying to install -.- Each download clearly states what version of Minecraft it is for.
-
Unable to determine registrant mod for cpw.mods.fml.common.eventhandler.EventBus
Its a non-issues, some old debug code I forgot to remove.
-
1.7.10 Forge Server is Being Unstable
Caused by: java.lang.OutOfMemoryError: PermGen space I wonder if there is any tutorials or answers to this issues.. Or if people have asked it .. excessively...
-
Rationale for using Access Transformers and byte code injection
Its simple, don't do coremods or anything like that. There are certian places where it is needed, but for those who dont know how to do them shouldn't be.
-
Using the logging.properties file in 1.7.10
http://logging.apache.org/log4j/2.x/manual/configuration.html Make and edit the config file, I think it looks in the main folder. Relaunch your server. This is basic stuff.
-
Minecraft Forge not Installing Client
If that does not work, just use the full path to where you installed java -.- As for any errors or the like you guys are getting we NEED logs we can't do anything to help you without them.
-
1.7.10 server install errors
You run the forge jar NOT the VANILLA server jar.. as it's vanilla.
-
1.7.10 server install errors
Thos 403s are normal. It downloads the unpacked version if it cant download the packed. That log is fine there are no errors.
-
"Files" Branches Not Working
If this is still an issue let me know, it shouldn't be.
-
Material.rock is not a type !repost!
The mod you have is broken and was not packaged properly. Use gradlew build to obfusicate properly.
-
Save Mod from Java Decompiler
Yes because we totally love closed source obfusicated mods from random unknown users! We totally trust you and your approach to obsidian tools is so unique it MUST be protected! No.. just no...
-
(Solved) Must run server. Eula.text wont generate. How to agree to eula??
Your run configurations have the work directory specified and should put it in the logs. Looks like you just don't know your run directory.
-
1.7.10 Pixelmon Mod (fatal error)
https://github.com/MinecraftForge/FML/commit/1c6b25df740a64c94d9ba05dd7e4412515abf5bb Its all ready for you to debug your own code we cant do any more on our end.
-
World running on backup level.dat?
Post your log file
-
Instalation Problems
This is not a problem, this is most likely caused by the fact taht you ALREADY have the assets downloaded and it skipped the bulk of them. Define "deson't work". Acording to the log it worked just fine. So I dont see where you are running into issues. You have yet to actually state any error or problem you are having. The Assets thing I have told you is NOT a problem.
-
Minecraft Forge crashes INSTANTLY after pressing 'Play'
This is caused by you having a messed up vanilla jar file. Delete your versions folder, re-run the launcher for 1.7.10 into-game and then re-install forge.
-
WorldEvent.Explosion
Yes because this is the only place explosions are created. This is PEFECT i'll pull it RIGHT NAOI! -.- Explosions have a dozen or two codepaths that would need to be edited.
-
Forge: It's time to say...
For those who know how to look into it, a dev version of FML is avalible. I have a few people looking into it and updating mappings so that modders will get some better names. As it sits, 1.8 is still in flux. However: Preliminary support for vanilla clients is in FML Compiles and runs just fine Villager registry needs to be re-worked Network protocol needs to be re-worked to allow for more generic id registries. ID registry needs to be re-written to support the new network stuff. Forge: Needs updating, haven't looked at it yet. I am wanting to get the FML side of things solid before moving forward. However, 1.8 is pretty sweet it has some really cool new features related to modeling and rendering. Combined with a major re-write of how location and metadata works. Still working on it, just slowly. As we're still waiting on modders to update to 1.7.10 I don't think it is a big deal to take some time to do it right.
-
Instalation Problems
Assets are no longer put into the eclipse folder as this is just a lot of duplicate data. You don't 'open' anything in the eclispe folder. It is a eclipse workspace. Use it. Or you can use your own workspace and import the project from your root folder. Please provide a log file of you running gradle {its in the .gradle folder} So that we can see what is going on. It sounds like nothing is going wrong and you simply have no idea what you're doing.
-
Forge claiming I have multiple versions of the same mod installed
1.6.4 is no longer supported, please use a more up to date version if you wish to receive support.
IPS spam blocked by CleanTalk.