MCBICK'S PROFILE

author=LockeZ
I just couldn't understand your opening post because it kept using the wrong words for things. So the topic has nothing to do with save states at all, and also has nothing to do with comparing save files to any other option? You're just talking about how much to restrict saving? Got it.

Unfortunately that leaves me with a different question: why you made this topic after mentioning in the OP that you'd already read the previous topic about it and then summarizing what people said in it.

The topic is about Save States(like in emulators) vs Regular Saves(save point/menu/etc). It seems most people knew what I meant, but I confused myself when making the topic, so it ended up confusing.

@NeverSilent
Just about everything is custom made in my game from graphics to menus. I doubt anyone would recognize it as just another rpg maker game at this point. Yet I am constantly adding to it because I don't want to settle for something that isn't what I envisioned. I was just curious what the community thought of spending all that time adding instead of just settling for what resources were available and making due.

I know save files is probably not the best term to use since a save state is a save file, but I'm sure you guys will understand what I mean. If you have a better term for me to use let me know and I will edit my post.

A while ago I discussed how often/where you should be allowed to save and surprisingly many of you said you should be able to save any where. That leaves me wondering should save states be implemented into games? Of course you would still have save files, but that leads me to my next question if save states were implemented in modern games would save files become obsolete?

Just to clarify I am talking about games that have an in game feature to save, such as save points, main menu save, etc. I know many PC games save their data like a save state, so that when you load the file you resume the state you were in. If any of those games don't have a save restriction then they will be considered to use save states and not save files.

Save State: The ability to save anywhere at any time, no restrictions.
Save Files/Restricted Saving: Restricted to saving via points, menu and other restrictions.

author=LockeZ
I would rather have the one perfect game than several decent games.

I mean, obviously it won't be objectively perfect, but I want it to be the perfect likeness of what I was imagining it to be. The game that perfectly matches what I wanted to make.

That takes years though. But I tend to work on other smaller games as I'm making the one big one, so that helps...?

I agree with this or at least this is what I do.

I want people to play my game and not recognize it as just another generic rpg maker game. So I feel by adding custom menus, text, graphics, mechanics, etc this will improve my game even if some of the things I add don't exactly improve the core gameplay it will improve the aesthetic of the game.

I notice that games in development that promise many custom features(custom made scripts/engines/events) never seem to get completed and I wonder if its because they try to put so much stuff into their game? I know this to be true for my games. I just added a custom message system(in 2k3!) for my game and I still want to add more. It feels like every time I get close to finishing a game I think of new stuff to implement.

Do you think adding tons of custom stuff is a bad thing?

Is it better to use what resources you have available and complete more games or should you spend your time making custom stuff for your one game so its exactly like you envision it?