Designing Games with Game Maker - YoYo Games

file_bin_close(fileid) Closes the file with the given file id.
file_bin_size(fileid) Returns the size (in bytes) of the file with the
given file id.
file_bin_position(fileid) Returns the current position (in bytes; 0 is
the first position) of the file with the given file id.
file_bin_seek(fileid,pos) Moves the current position of the file to the
indicated position. To append to a file move the position to the size of the file
before writing.
file_bin_write_byte(fileid,byte) Writes a byte of data to the file with
the given file id.
file_bin_read_byte(fileid) Reads a byte of data from the file and
returns this.
If the player has checked secure mode in his preferences, for a number of these routines, you
are not allowed to specify a path, and only files in the application folder can e.g. be written.
If you included files in the game executable and did not automatically export them at the start
of the game, you can use the following functions to do this.
export_include_file(fname) Exports the included file with the name
fname. This must be a string variable, so don't forget the quotes.
export_include_file_location(fname,location) Exports the included
file with the name fname to the given location. Location must contain the path
and the filename.
discard_include_file(fname) Discard the included file with the name
fname, freeing the memory used. This must be a string variable, so don't
forget the quotes.
The following four read-only variables can be useful:
game_id* Unique identifier for the game. You can use this if you need a
unique file name.
working_directory* Working directory for the game. (Not including the
final backslash.)
program_directory* Directory in which the game executable is stored. (Not
including the final backslash.) When you run a standalone game this is
normally the same as the working directory unless the game e.g. opens a file