plowmanplow

[B#347] 2016/04/10 11:43:43 [INFO] [11:43:43] [Client thread/INFO]: LWJGL Version: 2.9.1 [B#347] 2016/04/10 11:43:46 [INFO] [11:43:46] [Client thread/ERROR]: Couldn't set pixel format [B#347] 2016/04/10 11:43:46 [INFO] org.lwjgl.LWJGLException: Pixel format not accelerated You need to ensure you have the correct, and most recent version of your video driver.

Connecting to server: The server I provided is set to 25565. Make sure that is the port you are forwarding. Use CanYouSeeMe to verify that the port you have open is actually working. Make sure the firewall is also open on that port. Feel free to remove the CraftIRC JAR file from the plugins folder. This was connecting to my own IRC server and will likely be of little use to you. Please provide client and/or server logs around the time that the disconnect happens.

Dropbox is a valid modpack host provided you don't go over their bandwidth limits. Unfortunately it seems that Hostgator does not work with the platform. I've run across this with other members trying to use Hostgator. The links appear direct when tested but the platform is unable to use them. I am in the process of compiling a list of valid alternatives: https://www.circlecraft.info/hosts/

Dropbox is a valid alternative for your pack provided you don't have more than 150 pack downloads per day. In order to use dropbox, create a public share link for your modpack archive and make the following alterations to the URL: Change "www" to "dl" Change "dropbox" to "dropboxusercontent" Remove any trailing "?dl=0" or "?dl=0" Client pack analysis: The contents of your pack are in a subfolder. This will not work. The top level folders "bin", "config", and "mods" must be a the top level of the folder structure in the modpack archive. Your /bin/ folder has too many files. It should only contain the file "modpack.jar". The /cache/ folder and it's contents should be removed from your modpack archive. You should remove the /mods/Installers+jars/ folder and its contents from your modpack archive. I can think of maybe two mods out of thousands that require an installer. If you have installers for mods you aren't getting them from the mod author's preferred locations. Always download mods directly from where the author publishes them.

Dropbox is a perfectly valid free host, provided you don't use too much bandwidth. If you go over 20G in a day your account will be suspended for a period of time (not sure duration). If you have less than one hundred downloads per day for your pack as it current is configured you should be fine using dropbox. To use a DropBox public share URL with the platform, perform the following alterations: Change "www" to "dl" Change "dropbox" to "dropboxusercontent" Remove the trailing "?dl=0" or "?dl=1"

Mediafire is not a valid host for use with the platform. Their links change over time and are not usable as a modpack location.

Does the server settle down after you have disconnected? Does it run poorly again after you reconnect when you are at the same location? Is there no useful data showing in up any of the log files? Since you have local access to the box I HIGHLY recommend setting up WarmRoast . This will allow you to isolate specifically which class/method is the source of the lag.

Your modpack location is invalid. Copy.com links must have "?download=1" appended to them in order to function properly in the platform. Keep in mind that Copy.com is terminating their service in less than 3 weeks. Your pack has no config files. This is always bad and sometimes fatal, even for 1.7.10 modpacks. Always include a full compliment of config files. You have Mo' Creatures mod but not the required dependency mod CustomMobSpawner. Your Immibis Core mod it not from a legitimate source. His mods are available here: Immibis' Mods I would recommend using something like the BareBonesPack to build and test your pack before deployment.

Are your plugins functioning correctly? Are you certain your startup script is launching the Cauldron JAR and not the minecraft_server JAR?

Follow this guide: Creating A Server After you have Forge working, switch to Thermos

pCloud offers a way to back up your copy.com account to their service. However, I do not believe pCloud supports direct file links which are compatible with the platform. I'm in the process of compiling data for what does and doesn't work with the platform, as well as trying to work with the devs to figure out why some links don't work when it seems they should.

Dropbox public URLs should be altered in this manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove the trailing "?dl=0" or "?dl=1". I would highly recommend updating to AnimationAPI-1.7.10-1.2.4.jar. Your NEI version is fatally out of date. You should be using the "latest" versions for 1.7.10. I highly recommend using BuildCraft-Compatibility with BuildCraft. Your pack launches successfully as modded (i.e. with Forge and mods) for me. Try incrementing your pack version number, restart your launcher, and accept the update.

Ishara Server 1.9: https://dl.dropboxusercontent.com/s/57073jbmzk6639m/IsharaServer-1.9.zip

Please note that I advised the removal of trailing "?dl=0" or "?dl=1". You seem to have left the "?". Remove that. As I mentioned before, since you are using an old version of Forge for 1.6.4 you must include the Legacy Java Fixer mod in your /mods/ folder or the pack cannot function when the client has Java 8.

@tekkitplanet Or you could give back to the community since I'd say there's about a zero percent chance you made these yourself. Pathetic.

All I can say would be to refer to your manufacturer's documentation about how to select/prefer a specific chip/driver. Make sure you have all the latest drivers for your hardware loaded.

Are you on a laptop? If so, are you sure you have things set to use your dedicated graphics chip instead of the default/integrated one?

My apologies. I should have been more explicit. The "fml-client-latest.log" file is the useful one. The "latest.log" file has almost nothing useful in it. How much physical RAM does your PC have?

How odd. That error is most common when you have a mod that isn't compatible with your current version of Forge/MC. Edit: Looks like v1.9 of your pack has the "correct" Waila and is working fine. Excellent! Edit 2: Decided to make a quick server (Thermos with plugins) to see how things work. Seems to be functioning just fine. Feel free to test your 1.9 client against it: vanilla.wegoboom.biz:25570 Edit 3: Just saw you log in, and the message you sent. Glad it worked.

If you post a crash report in a pastebin service I will see what's up.

If/when you get to the "making a server" phase, feel free to continue this thread for continuity.

For starters, you are allocating way too much RAM to the Launcher. Never allocate more than 4G or half your physical RAM, whichever is smaller. Unless you are using a large HD texture pack, using 3G as the max would be better. The crash reports are all for the same error, but for different block locations. Have there been any changes made to the server configs? Some mods get wonky when the server and client configs differ. Does this only happen for you and other players are able to move through these locations without problems, or is it just you having this issue?

Yeah, unless you really know what you are doing, and have a compelling reason to do so, only ever have one Java version installed (preferably the latest). The most recent Java 8 64bit should work just fine.

Also, don't post the Launcher log. Please provide the most recent crash report from /crash-reports/ as well as the most recent /logs/fml-client-latest.log.

I did the following and the server-side stuff seems to be working as expected (feel free to check it out on the server I posted above): Replace all the Millenaire related files from your server's /mods/ folder with the "Server" download available on the Millenaire website. Change the default language in "/mods/millenaire/config-server.txt" (very bottom of the file, set language=en) The pack even seems to work fine using Thermos (alternative server for vastly improved performance). Villagers seem to be acting wonky with Thermos. Might have to stick to Forge.