BioAndy

Thanks for all the replies everyone. I will edit my post and mark it solved. I ended up using config files. I was just worried about storing information in them that should not be stored in them. NBT just seemed like overkill for my purposes.

Good Afternoon Everyone! So I have been writing my first mod for Minecraft using Forge 1.8. My son comes up with the idea and I help him implement it. He's only 9, but really interested in software development and I think this is a good way for him to experience it and gives us some fun times together. I have worked with c++ for the past 15 years in a professional setting, so if you can help with my problem, pointing me in the right direction should be good enough. I highly doubt I would need full code examples, and really dislike going through other peoples code anyway! The problem - Saving state information between sessions. Example - Lets say I have a simple GUI (no inventory attached and client side only) that when opened lets the user re-position an overlay onto the screen. Now this overlay needs to have it's X and Y coords. saved between sessions. I'm just not really sure where I would be saving this information -> Config File - From what I've read it's mostly for Block and Item ID's. NBTData - Seems like overkill to save what little information I need saving in here. Now I have only been digging through the Forge API for a couple days now, so I'm sure that I am missing something. Questions? Am I missing some other way Forge easily enables the saving of client side data? With something as generic as x and y coords. that is not an item, block, or entity do I just need to write my own input / output handler that does what i need and saves it in my mod folder? I guess before writing my own, I'm just wondering if Forge already implements an easy to use Interface for this. Thanks everyone and I'm looking forward to being a part of the Minecraft modding community!