Calculator Community > Escheron: Shadow over Ragnoth

Escheron: Shadow over Ragnoth

<< < (135/135)

Geekboy1011:

--- Quote from: Zera on February 24, 2014, 10:16:18 pm ---
--- Quote from: Geekboy1011 on January 28, 2014, 09:34:02 pm ---So I have a question for you. Would you be against the idea of quick saves? Or if we have the ability to implement them should we? I feel that on the platform we are programming this for it would be unwise to not be able to exit ... err promptly.

--- End quote ---
I guess it could be implemented, as long as it doesn't aid in save scumming. A quicksave file would have to be erased as soon as its resumed.

--- End quote ---

Yes it would be treated exactly like that. I just see kids playing this in class and not being able to quick save would make it playable during class and such which IMO is the broad user base for the game.

Iambian:
I'm still going to keep the old assets as it's just another folder. An additional project can be made in b/w, but after the subproject is finished. People are expecting a full 4 level grayscale game, and they've been waiting for it for ages. We're gonna deliver that at some point.

Also, I wouldn't be worried about save scumming on the calcs, since most of the time, yanking a battery while running a typical assembly program results in data loss. Most people wouldn't think of doing something like that to try save scum. They might do things such as rename/copy files. If you wanted to protect against save scumming, you would want to keep something of a counter on hand to check against the version of the save file being presented. If there's a mismatch, then you could call them out on it.

Streetwalrus:
* Streetwalrus suggests an md5 in smc* Streetwalrus runs

Iambian:
There was actually some suggestions in HCWP (off-day) that involved using MD5 hardware and messing around with the certificate page. I suggested writing to the boot code if the calc is a newer model, but that suggestion got shot down and I then suggested writeback to the app.

I don't think I'm going to make the protection too strong, but I am going to make it such that if you want to cheat, you're gonna have to work at it.

Geekboy1011:
Kerm said cert is to unsafe to muck with, a write back of the app is better and easier to achieve safely.  Also why not just store the md5 back? Might be best :p because the chances for a collision are very hard.

Navigation

[0] Message Index

[*] Previous page

Go to full version