Relative include paths aren't working about vscode-pawn

[Southclaws]

See #2 for some relevant information. It might help to use the -D flag for pawncc to specify the working directory. I'll have a proper read of this later and figure out a more comprehensive answer and/or fix for the issues with paths because I've noticed a few people running into this.

[Southclaws]

Okay so what's happening here is exactly the same as #2 - my assumption was wrong about the typical server folder setup. If you use the quick fix I provided in #2 you'll solve your issue and I will try to solve this on the extension end with minimal consequences.

sampctl is a different build toolchain that focuses on a more modern compilation workflow inspired by languages/ecosystems like Go, NodeJS and Ruby. It resolves a ton more issues than just this one and also facilitates proper package management and automatic plugin downloads.

In conclusion, it's clear that this setup is causing confusion for users so I'll try and improve the documentation and default configuration settings.

Since this is a duplicate of #2 I'll close this and push any further discussion there.