With the browser demo, one thing is clear: by default there is probably not much in terms of security for your assets.
What does this mean for you as a developer?
Which isn't a good sign for those that wish to have better security.
Does absolute security exist for browser games?
No. Probably not.
There really isn't a way to prevent people from taking your resources: if the files are sent to their machine, they will be able to analyze it and do whatever they want with it.
Can we do anything about it?
As it stands, all of your assets can be taken without any effort on the player's part. Things CAN be done in an attempt to deter them from simply copy pasting it.
Proprietary Formats
A "proprietary format" is basically a "custom" format, where the specifications are typically not published for everyone to see and use. Rather than using one of the "common" or "standard" formats like PNG, or OGG, or AVI, you implement your own way of storing the data.
If you worked with RM2K, they came with an image format called "xyz".
In XP and above, all of the assets (except for audio and video) were packed into an archive called "rgssad", "rgss2a", or "rgss3a".
Of course, these formats have also been reversed and tools are available to convert and unpack them.
However, that means that someone had to go and provide such a tool, and there are in general less people that can perform reverse engineering work than people that want the resources.
One problem with proprietary formats is that your game needs to be able to read them as well, and if players can take your scripts, they will eventually find how the game is loading the resources by looking through the scripts and all they have to do is do the same thing.
So even proprietary formats are not completely fool-proof and may be easy to take figure out, but it should at the very least deter people from taking them.
Other Solutions?
What are some techniques you can think of to make it more difficult for people to "rip" your resources?
What does this mean for you as a developer?
- People can take your graphics
- People can take your audio
- People can take your scripts
- People can take your fonts
- People can take your videos
- People can take your data
- People can take your cat pictures also
Which isn't a good sign for those that wish to have better security.
Does absolute security exist for browser games?
No. Probably not.
There really isn't a way to prevent people from taking your resources: if the files are sent to their machine, they will be able to analyze it and do whatever they want with it.
Can we do anything about it?
As it stands, all of your assets can be taken without any effort on the player's part. Things CAN be done in an attempt to deter them from simply copy pasting it.
Proprietary Formats
A "proprietary format" is basically a "custom" format, where the specifications are typically not published for everyone to see and use. Rather than using one of the "common" or "standard" formats like PNG, or OGG, or AVI, you implement your own way of storing the data.
If you worked with RM2K, they came with an image format called "xyz".
In XP and above, all of the assets (except for audio and video) were packed into an archive called "rgssad", "rgss2a", or "rgss3a".
Of course, these formats have also been reversed and tools are available to convert and unpack them.
However, that means that someone had to go and provide such a tool, and there are in general less people that can perform reverse engineering work than people that want the resources.
One problem with proprietary formats is that your game needs to be able to read them as well, and if players can take your scripts, they will eventually find how the game is loading the resources by looking through the scripts and all they have to do is do the same thing.
So even proprietary formats are not completely fool-proof and may be easy to take figure out, but it should at the very least deter people from taking them.
Other Solutions?
What are some techniques you can think of to make it more difficult for people to "rip" your resources?
Last edited: