fix: common sourcemod plugin folder hierarchy

[maxime1907]

No description provided.

[Vauff]

What's the justification for this? I suppose it saves going 2 folders deeper on your server during the install process, but then does the opposite whenever navigating the project folder in a file explorer.

Also please do not remove the pre-compiled .smx, this is provided for beginner users who may not be familiar with the process for compiling plugins.

[maxime1907]

What's the justification for this? I suppose it saves going 2 folders deeper on your server during the install process, but then does the opposite whenever navigating the project folder in a file explorer.

Also please do not remove the pre-compiled .smx, this is provided for beginner users who may not be familiar with the process for compiling plugins.

Its just that there are no general consensus regarding how independent plugins should be structured so i am trying to push that structure so that later on we can use scripts to automate the building process and if for instance we have resources that are specific for CSS, CSGO, TF2.. we also have a clean structure.

What do you think about that hierarchy (implemented here https://github.com/srcdslab/sm-plugin-zombiereloaded):

• addons
  • metamod
  • sourcemod
    • scripting
      • include
    • gamedata
    • translations
• cstrike
  • materials
  • models
• csgo
  • materials
  • models

About pre-compiled .smx in git repositories, its just that it should not belong here but rather in the release part of github with proper CI/CD like any other normal github repository