214764
Level 25 Chipist
Flaminglog
post #214764 ::
2025.04.06 8:17pm :: edit 2025.04.07 8:45pm
arceus413, lasersphaser, Titan of Plasma, Melon, Kaytse, retrokid104, RadamLee, Arda, big lumby and kleeder liēkd this
arceus413, lasersphaser, Titan of Plasma, Melon, Kaytse, retrokid104, RadamLee, Arda, big lumby and kleeder liēkd this
I haven't started planning this yet, but would anyone be interested if I held another Famiswap event?
This is the previous one:
Listen to FamiSwap 2019, a playlist by FamiSwap on #SoundCloud
https://on.soundcloud.com/uqeLMgRcA6PrB5k78
I want to do another one later this year, probably around autumn. The gist is the same as a monsquaz style swap, but with famitracker modules instead of .it modules.
Noticeable rule changes:
1. Participants are allowed to modify existing segments in cases where a previous participant clearly engaged in 'griefing'. Examples of griefing include (but aren't limited to) adding segments that 'sound bad' on purpose, or appear to be low effort. In extreme cases, changes may be reversed entirely, and the offending participant may be asked to leave.
2. You must be competent with famitracker. You do not need to be an expert, but you should be familiar with the program, understand how to make and edit instruments, know how to control volume, etc. The best proof of this is to have a few nsf entries, or uploads elsewhere.
3. The starter for each file will determine the chip configuration. Altering the chip configuration on a file you did not start is forbidden. If a file is started as a 2a03, no expansions are allowed.
4. Adding new instruments (excluding dpcm) is permitted at any point, but dpcm samples will be submitted in advance and will be included in the starter file.
5. Files will no longer return to the starter for finishing, but the finishing period will be one week.
If you were around for Famiswap 2019, then you may recall there were some difficulties. Here is what the previous iterations rules were like:
https://battleofthebits.com/academy/GroupThread/20111/Famiswap%3A+March+17th_+Sign-ups%21%21/
Apart from the above changes, I do think this was a fun event and I am willing to host it again.
If you are interested please be aware that this event may span multiple weeks, and you are expected to participate each day. If you cannot commit to that but you are interested in participating anyway you are encouraged to join as a backup or an alternate. If someone cannot participate or must drop out, an alternate will fill in for that day or a backup will replace that participant going forward.
I would prefer to have no more than 15 core participants, because I don't want the event to drag on for longer than 15 days before polishing (would get exhausting).
(I am okay with more than 15 participants, we will just split it into multiple working sessions)
We'll hash out the details once I know whether there are enough people to hold the event in the first place. But for now, let me know if you're interested in joining, and whether you'd like to be a core participant, a backup participant, or an alternate.
Thank you for your consideration.
This is the previous one:
Listen to FamiSwap 2019, a playlist by FamiSwap on #SoundCloud
https://on.soundcloud.com/uqeLMgRcA6PrB5k78
I want to do another one later this year, probably around autumn. The gist is the same as a monsquaz style swap, but with famitracker modules instead of .it modules.
Noticeable rule changes:
1. Participants are allowed to modify existing segments in cases where a previous participant clearly engaged in 'griefing'. Examples of griefing include (but aren't limited to) adding segments that 'sound bad' on purpose, or appear to be low effort. In extreme cases, changes may be reversed entirely, and the offending participant may be asked to leave.
2. You must be competent with famitracker. You do not need to be an expert, but you should be familiar with the program, understand how to make and edit instruments, know how to control volume, etc. The best proof of this is to have a few nsf entries, or uploads elsewhere.
3. The starter for each file will determine the chip configuration. Altering the chip configuration on a file you did not start is forbidden. If a file is started as a 2a03, no expansions are allowed.
4. Adding new instruments (excluding dpcm) is permitted at any point, but dpcm samples will be submitted in advance and will be included in the starter file.
5. Files will no longer return to the starter for finishing, but the finishing period will be one week.
If you were around for Famiswap 2019, then you may recall there were some difficulties. Here is what the previous iterations rules were like:
https://battleofthebits.com/academy/GroupThread/20111/Famiswap%3A+March+17th_+Sign-ups%21%21/
Apart from the above changes, I do think this was a fun event and I am willing to host it again.
If you are interested please be aware that this event may span multiple weeks, and you are expected to participate each day. If you cannot commit to that but you are interested in participating anyway you are encouraged to join as a backup or an alternate. If someone cannot participate or must drop out, an alternate will fill in for that day or a backup will replace that participant going forward.
We'll hash out the details once I know whether there are enough people to hold the event in the first place. But for now, let me know if you're interested in joining, and whether you'd like to be a core participant, a backup participant, or an alternate.
Thank you for your consideration.
