landing page templates
  1. HOW TO UPDATE JAVA - The following gist explains how to update your Java version: Try it now!
  2. Fixing Issues With OneDrive - In twitch, at the top right, click your name and a dropdown should appear. Within this, click Settings and then on the left side of the menu that comes up click Minecraft. Click Change and change the file path to an area that has nothing to do with OneDrive. Sometimes windows will default the Documents folder to be on a OneDrive share so be careful to investigate that even if it doesn't appear to be OneDrive related, that windows settings can be making it so behind the scenes as Curse installs to Documents and windows makes Documents a part of OneDrive unless you tell it not to . You can then go and copy the files inside the Minecraft folder from the old location to the new location or alternatively reinstall packs. It appears the issue arises when OneDrive becomes full.
  3. FPS (frames-per-second) lag is on your client and usually GPU doesn't make a big difference. Avoid shaders and resourcepacks when troubleshooting FPS. Adequate allocated RAM and custom JVM start arguments can mitigate FPS lag in some cases. Many users find that "animated textures" cause a massive FPS issue and this can be disabled if OptiFine is installed. Optifine can also help increase FPS for most cases and lastly, the mipmaps setting should be kept at 0 or 1 when having FPS concerns.
  4. TPS (ticks-per-second) lag is when the total number of ticks-per-second drop below 20. Minecraft is hard-coded to give a single game tick up to 50 milliseconds. You want a low tick TIME (i.e. under 50ms) because once that time takes longer than 50ms the game has to pause to finish processing the previous ticks or skip some ticks entirely. Even if tick time is far less than 50ms, the TPS will never be higher than 20, thus a TPS of 20 is considered "perfect." There are many things that can affect TPS and finding the cause can be difficult to track down. Here's some common causes:
     - Overflowing items/mobs
     - Large/Complex storage networks
     - Worldgen (exploring new chunks)
    - Anything in unreasonable excess

    Basic troubleshooting of TPS lag should include making sure enough RAM is allocated and using GC-tuning JVM start-args. Power down / turn off RS/AE2 networks, kill all items on the ground: /kill @e[type=item], and kill all hostile creatures: /cofh killall. If these make a noticeable difference then you have some clues to start troubleshooting. Even if briefly better because in the case of an overflowing farm they can quickly overflow again shortly after being cleared.

    Some mods/tools that can help find sources of TPS lag if the basic steps haven't helped are: 
    VisualVM (not a mod, an external profiler)
  5. How to use MultiMC to install Curse modpacks - Imgur Album

  6. To update a server from one pack version to another
    Download the server files zip for the newest version, unzip it somewhere and run the serverstart script file  (Running the batch first locally lets it download the proper Forge version and libraries)

    Run a backup on the server just in case before changing anything then stop/shutdown the server

    On your "real" server, delete (or move/rename) the forge universal .jar and the folders scripts, mods, config, libraries and any other folders/files that were included in the original serverfiles zip (before the batch file setup was run)  
    (if files are included in the server files zip download they usually contain different stuff from one version to the next)

    From the downloaded, extracted files after running the script, you can now copy the relevant files/folders that you removed in the previous step over to your server (Dont' skip the previous step -- they need to be removed before new ones are copied or duplicate files can and will happen and cause trouble)

    Once the folders/files/Force have been copied/uploaded, you should be able to restart the server (if you use a host, you might need to pick the new Forge universal Jar in the dashboard as the file to be launched)

    Method 2 
    Similar steps as above, you could also simply remove everything except the world folder from your server and copy/upload the entire contents of the server zip files (still needing to run serverstart first to fetch forge) this is a more comprehensive update but can involve more files to download/upload and could lose some minor stuff specific to your server like serverside journeymap data or ftbu ranks configuration etc.
  7. Recomended JVM args for ATM3 server and/or client
    (suggested RAM: ~5gb to ~8gb)

    -d64 -server -XX:+AggressiveOpts -XX:ParallelGCThreads=3 -XX:+UseConcMarkSweepGC -XX:+UnlockExperimentalVMOptions -XX:+UseParNewGC -XX:+ExplicitGCInvokesConcurrent -XX:MaxGCPauseMillis=10 -XX:GCPauseIntervalMillis=50 -XX:+UseFastAccessorMethods -XX:+OptimizeStringConcat -XX:NewSize=84m -XX:+UseAdaptiveGCBoundary -XX:NewRatio=3 -Dfml.readTimeout=90 -Ddeployment.trace=true -Ddeployment.log=true -Ddeployment.trace.level=all

    NOTE: These are just a blanket/generic suggestion and what helps one player might not help another. Your mileage may vary, use at your own discretion