To downgrade a Spine project from version 3.8 to 3.4, you will need to follow a multi-step process because direct downgrading across multiple versions is not supported. You will have to downgrade the project step by step through each intermediate version: first from 3.8 to 3.7, then from 3.7 to 3.6, and finally from 3.6 to 3.5 and 3.5 to 3.4. Each step may require you to adjust or remove features that are not supported in the lower version before proceeding to the next downgrade step. It's important to note that downgrading can result in the loss of data for features that do not exist in the older version you are downgrading to. Therefore, carefully check your project at each step for any issues or lost data.
The JsonRollback tool and specific downgrade instructions provided in various forum threads, such as this one for general downgrading, can be helpful. However, keep in mind that some manual adjustments may be necessary, especially if your project uses features introduced in newer versions that are not available in the older version you are targeting.
