I got one problem taken care of for it. But I am getting a "connection lost: timed out" error when trying to break a block on a server with GT enabled. The only recourse is to reboot the server so it "kicks" me off. What exactly would I check for in my log to see what the issue is that could be keeping me from connecting, and staying connecting ?
Hmm...assuming the server is not on the other side of the world and/or your Internet connection is fine, it sounds like a client/server "network" sync. issue. There's a substantial amount of Minecraft and Forge code that keeps clients and servers in sync. If they get too far out of sync., the algorithm can't recover and you'll get the "connection lost : timed out" error.
Are you running the exact same Forge version and GT versions on your client and server ? Also, are the libraries the same ?
I've learned through error that the only reliable way to build a client/server matched pair is to use a single "master" and copy the master to both the client and the server. And, whenever I do an upgrade or new install, I need to start from scratch. Otherwise, I may be picking up old libraries or other .jar files.
If you haven't already, wipe your server's minecraft folder clean of everything except for the base files like:
- bannned-ips.json
- bannned-players.json
- eula.txt
- ops.json
- server.properties
- usercache.json
- usernames.json
- whitelist.json
- ServerStart.sh (or whatever script you use to start it)
...and put aside (save) any config files or Minetweaker .zs files you've tweaked. Then,
install Forge 1.7.10 on the server, and make sure it's the same Forge as your client.
After you install Forge, boot the server and make sure it boots just basic Forge OK. Then, copy the following files from your 'master' distro (your client):
- config
- mods
- scripts (if you have any)
...and don't copy anything else. The folders like 'libraries', 'reports', 'logs', etc.,. will be self-built by the server .jar files.