There is something that I think it's necessary for this site, and it's a more transparent handling of the dependencies of each resource. For this purpose, I propose a new submission field which shows exactly that. For instance, if resource A depends on resource B to function, you could have something like this:
To give another example, pretend A depends on B, but there is also C which is newer and has more features than B. In this case, the recommended dependency would be resource C.
In a related note, it would also be very useful to have another field for incompatibilities in patches so the user knows what to avoid if they decide to apply a certain patch. For example, the patch "Mario Tile 8x8 GFX DMAer" is incompatible with the patch "32x32 Player," so both should have a field indicating said incompatiblity with each other.
This might take a lot of work, but I think it would be worth it for the end user.
------------------------------------------------------
Youtube
Twitter
SMWControlLibX GitHub
My Discord Server
Snestorage where you can download my resources
To give another example, pretend A depends on B, but there is also C which is newer and has more features than B. In this case, the recommended dependency would be resource C.
In a related note, it would also be very useful to have another field for incompatibilities in patches so the user knows what to avoid if they decide to apply a certain patch. For example, the patch "Mario Tile 8x8 GFX DMAer" is incompatible with the patch "32x32 Player," so both should have a field indicating said incompatiblity with each other.
This might take a lot of work, but I think it would be worth it for the end user.
------------------------------------------------------
Youtube
SMWControlLibX GitHub
My Discord Server
Snestorage where you can download my resources