MAMEWorld Forums - News - Re: ARCADE64 0.249.0

> ARCADE64 0.249.0 is released.
>
>
> Download location: https://arcade.mameworld.info/
>
>
> * As mentioned last month, a review of the inbuilt hacks was undertaken, and about
> half were found to be no longer needed and have been removed.
>
> * The audit window has been made larger to the same size as was in MAMEUI.
>
> * The cause of freezing when an incorrect input was made at the command line has been
> traced to a mainline commit 11 months ago. This has been corrected.
>
> * The lack of text in the F4 graphics viewer has been traced to a mainline commit 4
> months ago. This has been corrected.

Still blaming mainline for the inability of your own hackjob projects failing to handle changes made in it. Classy.

Also commenting out licensing violating code while still including it does not prevent it from being a license violation. Banning me from your project on Github for informing you of licensing violating code being included in one of the files I'm attributed to does not help your cause.

Once again, I point out the taito_f3 mods fall within the definition of a creative work as the logic behind them and code used is very unlikely to be the same logic / code anybody else would conclude or author. The code is uniquely identifiable, it is very easy to trace back where it came from. It is sourced from an old MAME license build. You are including them in a BSD licensed file, and now therefore distributing that file under a misrepresentative license.

Since you've now published this, I think the only next option left is that I report the violation to Github. This will be my last resort, but since you're still acting like a Trumpian child over it, I have no other choice. I do not want to have to go down that route, as amicable resolution would have been preferable.

Also, Mameworld admin, if you have any sense, drop this project and it's author, they clearly have no intention to comply with the license MAME is distributed under, and would rather lie, smear and ban and incite hate against those of us who know how the licensing works and have put a lot of effort into ensuring we comply with it while they instead think they can just ignore it because doing so makes them more popular without the effort of doing things properly.

The only thing I'm asking here is that the same rules the rest of the developers have to follow are followed. Not much is it. I would not take uniquely identifiable changes, distributed only under an incompatible license and place them in current MAME, as doing so undermines the integrity of the project licensing.