Originally Posted By: Reconnoiter
Fantastic thread guys. Still little bit confused about one thing; so should I use 3Run's idea to edit the hard coded path and than change it in every other shade-c file? Or is there a faster way?
There is no easy way out. You have to go throw all shade-c evo script/header files (mostly headers I guess) and check each string, sound, bmap and any other defined reasources to do not have any fixed folders, so you won't need to recreate resource folders, plus you could publish .wrs archive without problems. I don't really see any reasons to double string like Malice did (maybe there is a reason for that, if so I would like to hear it laugh ), what for if you could just define the file itself and be aware that it will be found withing defined with PRAGMA_PATH folders or in projects root folder.

Greets.


Looking for free stuff?? Take a look here: http://badcom.at.ua
Support me on: https://boosty.to/3rung