Skip to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

LexManos

Forge Code God
  • Joined

  • Last visited

Everything posted by LexManos

  1. You can make client side only mods yes, and do not being up hacked anything or else i'll ban you for being retarded. On the client you're limited to manipulating anything that the client has access to but always remember that the server has ultimate controler over the world, movement, entites, etc..
  2. I've been trying to reproduce it, and cant locally we need logs.
  3. We would need to see the full log, notibly the stack trace you cut out all ut the lst line of.
  4. Its just not how netty works, you get a context that holds all the information and go from there. There may not be a generic way of getting it my point is the 'everytime' argument is invalid as it's a basic programming setup to cache the values you need in easy to reference names.
  5. player = ctx.getHandler().playerEntity From then on you only have to type 'player' BOOM magic... Netty is all about generic data it needs a 1:1 ratio, it also needs to have non-abstract classes.
  6. You should ALWAYS be working on the latest Minecraft version, we will never backdate anything and if you work on older versions you just causes more pain and suffering.
  7. For future note, 1.6.4 mods are not supported anymore, 1.7.2 has been released for 9 months, UPDATE.
  8. You can use netty directly, as long as you use the channels FML provides you, you just need to implement it correctly else you get memory leaks.
  9. https://github.com/MinecraftForge/MinecraftForge/commit/6db5d2ed269aa9d29494ea8f069d7f4ac860e061
  10. Whatever source of EarlyAccess builds you guys are getting is breaking things. DO NOT USE EARLY ACCESS JAVA. And for the love of god, Java 8 JUST came out,. it will be another 4 years before Java 9 comes out, so we do not care.
  11. Do not create mods for 1.6.4 anymore it is no longer supported. 1.7.10 is the current version.
  12. Please provide direct links to where you got these mods.
  13. Bektor, please kindly shut up. Unless you are going to be helpful and actually provide ant proof to your claims or possible solutions to it. Then im inclined to believe that its something on your end as Async chunks has caused nothing but performance INCREASES to the end users. Advocating someone move to older outdated versions of minecraft is not something we do on this forum and if you do it again you will be permanently banned. Downgrading causes nothing but issues and stops progress. As doe Dynamic Lights, you say you get console spam, what is this spam. If it's spam about leaked packets on the dyanmic lights end the it is an issue with the mod not us -.- You can try using jprofiler to figure out what is eating memory and processing time.
  14. http://java.com/en/download/faq/java_mac.xml Aside from that, you'll have to Isolate it to a mod. If its TE you will need logs, and go to the te devs with it.
  15. Just drop 5.x and use 6. Its a no brainer, dont mix and match api versions -.-
  16. Read the License.
  17. Try using the standard mojang launcher, and provide us the FULL logs not this. It looks to me like you are trying to run a coremod that is not for the version of minecraft you're running.
  18. Do not use the Early Access 1.8 java, it is broken. Use the orfficial 1.8 release.
  19. 1.6.4 is no longer supported.
  20. The issue with guava is caused by a small derp on cpws end, should be fixed if you update.
  21. your missing the most important part of the log file, the actual error -.- Anyways, try killing the libraries/com/google folder and letting the launcher re-download the common libraries which it seems to be finding a corrupt one. As for your setup, you really should just stick inside .minecraft and do something similiar to what I do ./minecraft/profiles/{profilename}
  22. Changelog - Straight forward, easily accesible text form of the change log UserDev - This is downloaded by ForgeGradle when setting up the development environment. This is not intended for the average end user or even modders to access but only for those who KNOW what they are doing. And jsut want to take a look. Src - The prebuilt, mod development workspace, everything you need to get modding started. Even includes a example mod. JavaDoc - The javadocs for a fully setup workspace, useful as a reference for modders who jsut want to have a offline reference. Universal - This is what is actually run in the game, it contains all our code and changes. This is packaged separately so that server admins do not need to re-run the installer and can just drop this in as a replacement of the previous one. As long as no libraries has changed, dropping it in place will work fine. Installer - A bundle of the Universal, a json to tell it what libraries are needed, and our Installer. Packaged in jar form for cross platform compatibility. Should be able to run this like any standard executable jar file. Installer-Win - Exact same thing as Installer, except run through Launch4J to get a windows header added to it. For windows users who have fucked up there java instalation and can't figure out how to run the jar file.
  23. Different programs poll the keyboard in different ways, you could be confusing LWJGL's keyboard libraries with a bad keyboard. Say for example you are holding shift in MC, then release, and it never tells mc you released due to bad keyboard. Other programs wont be effected cuz they didnt get the intial down shift. Anyways, not much we can do with 'randomly' happening unless you can find a way to reproduce reliably. I doubt its a Forge code issue as we don't do much to that specific part.

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.