Why 0.3 development is slowing down

amp

I’ve mostly shifted focus onto aw3 (the AmpMod website if you didn’t know) after the fact that 0.3 is pretty much done. I’m not adding any new features for this version anymore given it’s coming in two weeks (I’m sure the new MP3 editing notice is one of the most useful even though I pulled that idea from 🐧🐧🐧). If I started 0.3 on the 12th of December and released it the day after, it’d be much more buggy than it already is.

and the robot or

MC40IGlzIGNvbWluZyBvbiBGZWJydWFyeSAzcmQsIDIwMjYu

amp

It may look like a keysmash, but it has a deeper meaning.

amp

MC41IGlzIGV4cGVjdGVkIHRvIGNvbWUgc29tZSB0aW1lIGFyb3VuZCBKdW5lIDIwMjYuIEhvcGVmdWxseSBpdCdzIGJpZ2dlci4
“Hello! How can I help you today?” -ChatGPT

amp

please do not put the solutions to the above on the wiki until january 2026

amp

and i’m gonna give a hint: those random strings are encoded the same way simple icons are encoded in the ampmod ui itself

unconstructable13

amp base64?

amp

unconstructable13 yeah

unconstructable13

amp but we haven’t even released 0.3 yet!
May I help with improving the AmpMod UI for next release? Some of the UI like the editor and sprite find bars had their UI improvements removed and I would like to change that plus improve some extra things. I really do not feel like forking another repository or using my already existing one to make pull requests because that fork is extremely old and I couldn’t seem to figure out how to sync it.

Community

Resources

Policy