New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the assets configuration more powerful #4
Comments
Work in Progress: #7 |
Good you are on this, I'll test it when it's ready :) |
Added the ability to use multiple directories for src, includes, assets. Using new functionality with various configurations will partially cover the described case. |
Use objects with |
Right now the way the assets are copied works fine for simple projects, it will just copy the entire folder. But for more complex projects, it will be useful to have the ability to exclude some folders, to add more folders for copying, maybe the ability to avoid copying sub-dirs inside that dir. Doing this will avoid the necessity to use external scripts.
To put it more clear, these are some of the options I would like to see implemented:
For example, I have my project (AG Mod X) which has assets like maps, models and sprites which are fine for those, but I have too files that are platform dependent like the server binaries (custom DLLs, Metamod, etc.). We need to have the ability to export assets by platform, like having two folders inside
dist
, one for Windows for Linux. Right now this stops me from using AMXXPack to its full potential.How can this be implemented? I'm not sure, maybe I can give a draft how this will look inside the
.amxxpack.json
if you are interested.The text was updated successfully, but these errors were encountered: