The famitracker+ format is a specific format of the '[[2a03 (soundchip)[2a03] tracker '[[FamiTracker] and its newer forks like 0cc, j0cc, Dn as well as every other fork which might show up in the future.
Just keep in mind that the fork you use has to stay within the scope of the original FamiTracker and nsf format limits, so something like SnevenTracker is off-limits (even though it technically uses the same codebase), as well as E-Fami which adds fantasy chip function.

'[#[Tools]
- '[[FamiTracker]
- '[[0CC-FamiTracker]
- '[[j0CC-FamiTracker]
- '[[Dn-FamiTracker]
.... please add more if there are more.

'[t[b3] What's the deal with Dn 0.4.0.1? '[/t]
Dn-Famitracker 0.5.0.0 and later releases broke forwards compatibility with earlier forks: this means that a module file made in Dn 0.5 or later can no longer be read by vanilla famitracker/0cc/j0cc. For this reason, you might see people stick to using 0.4.0.1 instead of updating.

'[#[Restrictions on submit]
The entry must be saved in the tracker file format. It's basically a no-holds-barred, any-expansion, no-limit format! Well, limited to Famitracker (fork) stable releases.

'[#[Accepted file formats]
- .ftm
- .0cc
- .dnm

'[#[Playback (for voting)]
- '[[FamiTracker]
- '[[0CC-FamiTracker]
- '[[j0CC-FamiTracker]
- '[[Dn-FamiTracker]

The recommended voting tool is the latest version of Dn-Famitracker, which will play all of the above.
(A BotBr interested in 100% perfectly accurate playback should instead use the exact fork and version the author used.)

'[#[See also]
- '[[2a03 (soundchip)]
- '[[0CC-FamiTracker]
- '[[j0CC-FamiTracker]
- '[[Dn-FamiTracker]
- '[[FamiTracker Effects Commands]
- '[[nsf (format)]
- '[[nsfplus (format)]
- '[[nsf_classic (format)]