EEPROM Crusade - Fixing the games that overwrite reserved EEPROM

Though given the amount of hassle doing that entails,
another option is to not redistribute code released under the GPL and just stick to the more forgiving licences. :P

Whereabouts?

Assuming the source is being taken from GitHub repos,
the licence files should already be provided with the source code in most cases.
Some people might specify the licence as part of the source code but not provide a licence file.

If the licence isn’t part of the source code and there’s no licence file then technically you probably aren’t allowed to redistribute the game or the code.

The zip files are in the same folders as the .png and .hex

1 Like

I’m already retired from homebrew developer.
but @Pharap summon me. ‘:)’

First, I fixed the gamebuino games.
eeprom writting offset: 0 -> 16.

Thank you @Mr.Blinky. I used your list and game source code.
@bateske I requested pullup(ArduFXTest github). please if it is no problem, marge hex files.

memo

1.Crabator          60     name + score(MSB+LSB)
2.Armageddon        80     score + name
3.Jezzball           4     id + score
4.WHG               22     levels
5.Big Black Box      1     level unlock
6.Digger            10     game mode, score, etc. fixed eeprom init 1024 -> 10 byte
7.Solitaire      0x120     c++ object added. simbuino debug(rough 0x120 byte)
8.Uforace           60     name + score(MSB+LSB)
9.101Starships       2     score(MSB+LSB)

source code

5 Likes

Hi @akkera102 -that’s awesome!
Welcome back :smiley:
Could you look over some of your other nice games ? ~

Many thanks, Andrew

ありがとうございます、akkeraさん。

この番号はEEPROMセーブのサイズですか?

A post was split to a new topic: Storing EEPROM data on the FX chip

6-7 days after. I will fixed my tiny game series.
Most problems are resolved. Too many bugs I made! :rofl:

はい。その通りです。memo is eeprom size.
セーブデータのサイズを理解していないと、容量を超過して
書き込むバグを作ってしまいます。調査は必要でした。

2 Likes

I am working my games now.
On the way, I make another 5 game fixing “draft” too. :slight_smile:
If source code is bad, tell me.

A few days away… Can I pull up this too?

I think Last one is only Starduino.
Starduino is no source code…

eeprom size memo

1.arduloop          201   crc + SONG struct
2.CalenderApp      1030   printf debug.
                          changed EEPROM_NOTES_MAX 50 -> 45(now 930 byte)
3.Evade              60   id + score(rough 60 byte)
4.Fanboat             3   id + mute flag + score
5.HarambesRevenge  max?   id + score, etc.
                          changed Almost save,load code(now 11 byte)
1 Like

※ You’re even trying to fix other people’s games?

私は驚いていますよ。
(I am surprised!)

それは私の意思じゃないでした、
でも、もう一度、ありがとうございます。
(That wasn’t my intention, but once again, thank you very much.)

ソースコードが秘密です、
akkeraさんの問題じゃないですからね。
(The source code is secret, so it’s not your problem.)

FanboatとEvadeとCalenderとarduloopで、問題ないと思います。
(With Fanboat, Evade, Calender and arduloop, I think there is no problem.)

Fanboatで、あれはライセンスの問題です。
(With Fanboat there’s still a licence issue.)

でも、akkeraさんの問題じゃない。
(But it is not your problem.)

英語モードになる…
(Changing into English mode…)


@acedent said he was going to contact Fanboat’s author (whose name is also Fanboat).

@acedent, have you managed to get a reply?
(Presumably you sent a PM on the forum?)


デュアル モードになる… :P
(Changing into dual mode… :P)

Haramebe’s Revengeは大問題ですと思います。
(Harambe’s Revenge is a big problem I think.)

CRCと多重セーブシステムがあります。
(There’s a CRC and a multiple save system.)

※ I intend to contact the authors to discuss the problem in greater depth.

akkeraさんのHarambe’s Revengeバグフィックスは作戦二です。これはいいですか?
(akkera-san’s Harambe’s Revenge bug fix is plan 2. Is this ok?)

でも、akkeraさんの他バグフィックスは作戦一です
(However, akkera’s other bugfixes are plan 1.)


※ means “I don’t know how to say this in Japanese…”

Before I try to contact the authors, @acedent or @Mr.Blinky, do either of you remember what exactly the problem with Harambe’s Revenge was?

  • Harambe’s Revenge
    @Pharap san. ok! I do nothing
    But The technical problem is solved. I changed ALL save/load code.
    If you can’t contact the author, you and I can use fix hex file.

  • Fanboat, Starduino
    It’s difficult for me to solve. I’m rooting for community.

  • Evade, Calender, Arduloop
    As I declared, I will pull up the modified version. Code reading Thanks!

Yes. I know. :slight_smile:
When I was active Arduboy community, there was no emulator or fx chip.
Now, The community is still active. I have respect.
I will work with you for a little while. hahaha.

2 Likes

Fanboat has an interesting licence …

Copyright © 2016 Richie ‘Fanboat’ Davidson
I own everything. In fact, stop reading this. Give me your shoes.
J/K I’m easy.
Copyleft sharealike GNU whatever, I’m not a lawyer.

The code is a pretty easy fix really.

1 Like

はい、それは作戦二です。
(Yes, that’s plan 2.)

Yeah, that’s the annoying thing.

If it had always had a proper licence we could have fixed it right off the bat and been on our merry way.
Instead we’re stuck trying to get hold of the original author to ask for permission.

This is precisely the situation open source is intended to prevent.

With most of the other games, if we can’t get ahold of the authors we can just fix it however we choose to.

He did publish an email address … fanboat@gmail.com.

With that licence, I would just update it.

Hence why I said:

I’m intending to hold out for at least three more days (which will be the two week mark) and if there’s no reply then we can argue about what to do with it.

The problem is that each new high score is stored at new EEPROM location (after the previous one) So after the126th new high score all of the EEPROM has been overwritten

1 Like

All the EEPROM including the first 16 bytes?

If yes, that’s a problem, if not it’s a bit annoying but it’s technically a different issue.
(Either way I’ll contact them to discuss it.)

No not the 1st 16 bytes.

1 Like

Ok, that puts things into perspective.
But it’s late now, so I’ll contact them when I’m next free and not juggling other things.

Re. @fanboat - Our last email correspondence was 5th Aug. He realised CodeBender wasn’t viable anymore and was planning on looking at GitHub. I’ve just sent him another nudge and link to this forum. :crossed_fingers:

3 Likes