[R0X4R]

Use the script's real location as the base path for loading libraries, modules, and configuration files.

This prevents path resolution issues when the script is executed from different directories and ensures project resources are loaded consistently.

[devploit]

Thanks for the contribution, but I'm closing this PR because it can't be merged as-is:

• Module path and install flow point to your fork. go.mod and main.go change the module to github.com/R0X4R/nomore403, the README replaces the install instructions with curl .../R0X4R/nomore403/main/Makefile | make -f - install, and that Makefile runs go install github.com/R0X4R/nomore403@latest and downloads the payload files from your repository. Users of this project's README would end up installing and executing code from a third-party repo, so this cannot go into main.
• Unrelated changes bundled in. The PR bumps go to 1.26.3 and every dependency, removes the request() helper and dozens of explanatory comments, and changes the output colors and labels. None of that is covered by the PR title and it makes the change impossible to review as a single fix.
• Commit history. Commits like "my repo just for test", "new" and "Update go.mod" suggest this was pushed from a personal test branch rather than prepared for upstream.

The underlying idea of looking for payloads in ~/.nomore403/payloads or next to the binary when -f is not set is reasonable. If you want to pursue it, please open a new PR on a dedicated branch that only touches cmd/root.go (and the README text for that behavior), keeps the original module path, and does not bump dependencies. Note that Docker support with the payloads bundled in the image was just merged in #60, which covers part of the same use case.