• 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

Files validation in games

3 posts in this topic


In my game I have a server which stores several mods to the original game. So a casual user can download and play. But before getting into mod I need to validate all its files and ensure that the user didn't corrupt them. Let's assume that I have to check 100 MB of files and that only 1 MB is corrupted. In result checking 99 MB would be a waste of time and the server would have to send only 1 MB of correct data that client would replace. And now I'm wondering if it's worth to use some complex algorithms like CRC-32 or MD5 to check that files are correct? What would be the best solution? I would be very grateful for help!

Edited by savail

Share this post

Link to post
Share on other sites

yes, agreed WRT manifests and checksums.

I had considered similar, sadly if/when I ever get around to generalized network file-copying.



also agreed regarding disk IO:

IME, this is often one of those things which eats a lot of time, but is often underestimated.


a recent example was an observation with a specialized compressed audio-codec of mine:

it was originally designed mostly to save RAM, and allow random-access piecewise decompression (basically, sort of like DXT but for audio, using independently-encoded fixed-size blocks).


however, as a side effect (observed during tests), the reduction in file-sizes resulted in a noticeable speedup vs loading larger WAV files.


while a person can complain some about the CPU cycles needed to decompress the audio, my tests showed this to be a pretty minor factor (overall added CPU cost is negligible). (of what time goes into audio-mixing, most of it goes into other things, like sample interpolation and reverb calculations...).



granted, there may still be an issue for disk-seeks and cluster-overhead for small files, but this can be addressed via bundling (say, rather than having a larger number of small files, we have a small number of larger files). similarly: the entire bundle can be loaded into RAM at once, and it is also possible to do combined checksum over the whole bundle.



there are various options for this, ranging from slightly more complex ZIP based packages, to simpler ones (such as the Quake PACK and WAD2 formats).  this later case can probably be called "WAD variants" (mostly due to "generally similar file structure" to the original WAD).


there are various tradeoffs for why a person might pick one sort of packaging or another, but personally I prefer WAD-like formats for small/specialized data storage, and something like ZIP for "general" storage of lots of heterogeneous data. (not going to go into specifics too much here ATM).


things I have more often used WAD-variants for:

storing globs of compiled bytecode and metadata for my script-VM (produced by "compiling" script-code libraries);

storing voice-fragments for a text-to-speech engine (where there are large numbers of basically short audio-fragments used for unit-selection or similar);

storing samples for the various MIDI-instruments (for a wavetable MIDI synth);



basically: cases where otherwise a person will have a directory with large numbers (100s or more) of tiny (often under 1kB) files.


things I have more often used ZIP-based containers for:

collections of general data files;

collections of textures;



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