• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
turkeyremis

How To Save game

4 posts in this topic

Hi everyone at gamedev im one man band working on a unity title i excell at designing and art but drop at programming im at the point in my game where im making menus but how do i make my game save please help help i have no idea where to start. The game is a 3d scifi survival game. oh ya i use java Edited by turkeyremis
0

Share this post


Link to post
Share on other sites
The save/load process is called "serialization".

Most objects you can mark as being serializable and then it should automatically save and load properly.

There are several tutorials for serialization in the Unity wiki.

What have you tried?
0

Share this post


Link to post
Share on other sites
What if you make a file when you write all the information of the actual status of the game... Like the goals achieved, the position of the main character and enemies, and other specific information related to the game you are trying to make, like ammunition, health, weapons, etc. Then you can load that information, and set the values according to it...

I'm still a begginer, but I think it could work too... [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]
1

Share this post


Link to post
Share on other sites
I wrestle with this question myself. I think what you are asking is "What Information Should Be Saved" and "How is the [i]BEST WAY[/i] to save it "
I need help here to. How do I save Where you are? What you have Done? What level you have obtained ? Example : I have created 6 tanks and 4 trucks How do I save and Track them.
I don't need code just format. Someone help us all. I do it but not certain if I am doing it effectively.
0

Share this post


Link to post
Share on other sites
well, in java you could serialize objects, and get perfect replicas (with data element and class -exceptions of your own choosing)
in C i would define structures that consist primarily of what i want, and the offsets between the specific data, so that my saves never get "old"
for example, a small int table in a savefile tells me where this and that starts (in bytes), and ill just grab some generic tables from these positions
assuming you have made changes to the internal structures recently, it will get complicated in C, but there may be tricks you can use in C++ (i don't know the language)

anyways, define structs (classes if you will) that contains pertinent information on the data, and let these structs be so generic that you won't have to go back and look at them ever again =)
harddisk space is .. the least of your problems :) make room for improvements!
when this is done, just put the structs one by one into the file at the locations you'd want them to be in, and disregard completely "open spaces between structs"
the only requirement here is that you know where they are, and that they don't overlap
if you use sizeof(struct) you can pack them well together, and you might still be able to load the structs later, if you consider the differences between any old and new scheme
i recommend discarding old data though, if you make any changes

so, if A is the main savefile struct, and B is a container for where some additional structs are stored, the file layout could be:
ABBBBBBB C C C C C C C C C C C C C C C
the procedure:

// tell our future selves what size A had when we made this file
put (sizeof(A))

// tell A what kind of size B had when we saved
A.container_size = sizeof(B)

// declare a position for where we are in the file, which simplifies things greatly,
// both for loading and saving
int position = 0; // (or 1, depending on if its 0- or 1-based file offsets, its ALWAYS in bytes though!)

// put the entire struct directly into the file
// and increase position by the size of this structure (note that the sizes of structs vary between compilers!)
// (however, differences between compilers is something we don't care about now, and sometimes the language is consistent :P)
put(A); position += sizeof(A);

// put each struct that tells us location of data, and its size
for (int i = 0; i < a.containers; i++)
{ put(B); position += sizeof(B);
}

// for each B, we put each C (for each collection of data, we put each data)
for each B for each C in B
{
// we want to remember the size of each data item, including what type it is, and any other information
// that you would need to know now, or in the future
B.data_size[index] = sizeof(C); // for example..!
// put to file, advance position
put(C) : position += sizeof(C)
}
close()

and so on .. and so forth =)
now the position you are in the file is incremented for each structure, packed tightly
and there is no confusion about where anything is located
this is an ultra-basic system, that leaves less room for problems in your code, but is still not completely resistant to future updates and changes
to compensate for future changes, a version system could be used, but then you'd need backwards compatibility in your games loading system
personally, i say if you make any changes to the saving system - make all the changes, and scrap the old system, if you can :)
i hope this helps Edited by Kaptein
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0