Create.sh doesnt work on mac without modification

[PlantDaddy]

Create.sh doesnt work on Mac based computers. I have already submitted a PR with a possible fix for this issue

#80

Symptoms of this are when executing create.sh and populating the required module info, sed fails:

sed: 1: "Test/projects/example ...": invalid command code T
sed: 1: "Test/projects/example ...": invalid command code T
sed: 1: "Test/projects/example ...": invalid command code T
sed: 1: "Test/projects/example ...": invalid command code T
sed: 1: "Test/projects/example ...": invalid command code T
sed: 1: "Testprojects/example ...": invalid command code T
sed: 1: "Test/projects/example ...": invalid command code T
sed: 1: "Test/projects/example ...": invalid command code T
sed: 1: "Test/projects/example ...": invalid command code T
sed: 1: "Test/projects/example ...": invalid command code T

Which causes the creation of the named directory and files for the new module to not be created.

[bad-antics]

This is a well-known macOS vs GNU sed incompatibility. macOS ships with BSD sed, which requires a backup extension argument with -i (even an empty string), while GNU sed on Linux does not.

The fix is to use sed -i '' (with empty string backup extension) on macOS, or better yet, make the script detect the OS and adjust:

# Cross-platform sed in-place
if [[ "$OSTYPE" == "darwin"* ]]; then
    SED_INPLACE="sed -i ''"
else
    SED_INPLACE="sed -i"
fi

Alternatively, you can use perl -pi -e as a drop-in replacement that works identically on both platforms:

perl -pi -e "s/PLACEHOLDER/$MODULE_NAME/g" "$TARGET_FILE"

I see you've already submitted PR #80 with a fix — that's the right approach. For anyone encountering this in the meantime, installing GNU sed via Homebrew (brew install gnu-sed) and using gsed also works.

Worth noting: this same issue affects many Hak5 scripts that use sed -i — it's a recurring pattern across the ecosystem.