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:

• Exclude folders for copying
• Being able to add more folders for copying
• Have the ability to choose if we need to copy also subdirs
• Limit copying by file extension.

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 whole assembly breaks off if at least 1 plugin is not approved by the compiler (Compilation aborted...). It is extremely inconvenient when building a large project - I would like to skip such plugins and continue building the following plugins.

When the project is not gonna use some of the config options (like assets), you probably will try to disable it by making the field empty or removing it. This currently is not possible and it will trigger an error with the parser in resolve.js

For example, you just want to build the .sma files only, then when everything is ready, you build the entire project with the assets included.

A possible fix for this problem would be to provide a default value for these options (to avoid triggering an error when the field isn't isn't defined), and to check that when it's empty, don't do any copying.

// --------------- Case 1 -------------------
"input": {
    "scripts": "./src/scripts",
    "include": "./src/include",
    "assets": "" // Leaving this empty will use the "node_modules" folder instead.
},
"output": {
    "scripts": "./dist/addons/amxmodx/scripting",
    "plugins": "./dist/addons/amxmodx/plugins",
    "include": "./dist/addons/amxmodx/scripting/include",
    "assets": "./dist"
},

// ------------ Case 2 -------------------
"input": {
    "scripts": "./src/scripts",
    "include": "./src/include",
    // Removing the field will trigger a parser error
    // "assets": ""
},
"output": {
    "scripts": "./dist/addons/amxmodx/scripting",
    "plugins": "./dist/addons/amxmodx/plugins",
    "include": "./dist/addons/amxmodx/scripting/include",
    // Removing the field will trigger a parser error
    // "assets": ""
},

This can be workarounded to input to some empty directory like "assets": "./empty", but still it would be good to be able to disable this.

Some options I found useful to disable by the moment are:

• assets in both input/output: Sometimes you want to disable temporarily the copying of the assets
• output.scripts: Sometimes you don't need to distribute the scripting files

Sometimes when your project has a lot of resources (like models, sounds, maps), the building process will get a slowdown.
It will be useful to cache the files for the next amxxpack build command call to avoid wasting any precious time and save it only for the compiling part.

The command amxxpack build --watch help with this issue but the caching is only stored in-memory and not in the disk storage, as soon as you stop the task for some reason, you have to go back to the rebuilding process again.

Maybe this article can help you with this: https://medium.com/@wlarch/avoid-long-running-and-killed-gulp-tasks-with-this-simple-caching-gulp-plugin-67ec8bbf466b

Do not waste time during your build process when there is no reason to.

This plugin will process all files in gulp.src() if at least one file was changed. This plugin uses the features of node-file-cache to keep track of the assets SHA1 hashed content in a cache.json file.

It would be useful to make clear that information to newcorners because right now I'm not sure exactly how to set up the AMXX compiler to version 1.10 - build 5465. I read somewhere in the official thread in alliedmods that is not longer necessary to specify the complete build, but README.MD doesn't specify that.