Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Use when editing AzerothCore gameplay scripts, spell scripts, boss scripts, creature scripts, instance scripts, or script loaders under src/server/scripts. Covers AddSC registration and script placeme
Instruction file imported from Old-Man-Warcraft/oldmanwarcraft (.github/instructions/scripts.instructions.md). Copyright stays with the author.
Script Guidelines
Place gameplay content logic in src/server/scripts/. Place engine or generic gameplay systems in src/server/game/.
Follow the standard registration pattern after placing the script: implement AddSC_*() and wire the script through the relevant script loader.
Keep spell scripts in the existing class-grouped files such as spell_dk.cpp, spell_mage.cpp, or spell_generic.cpp. Use a different file only when nearby scripts in the same feature area already follow a more specific file or loader pattern.
Match the naming, registration style, and nearby helper patterns already used in the surrounding script file.
If a script change touches generic behavior, call out regression risk and test related content, not just the specific scripted case.
{
"ocm": "1",
"id": "old-man-warcraft-oldmanwarcraft-scripts-instructions",
"kind": "skill",
"name": "AzerothCore Script Instructions",
"description": "Use when editing AzerothCore gameplay scripts, spell scripts, boss scripts, creature scripts, instance scripts, or script loaders under src/server/scripts. Covers AddSC registration and script placement conventions.",
"publisher": "Old-Man-Warcraft",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when editing AzerothCore gameplay scripts, spell scripts, boss scripts, creature scripts, instance scripts, or script loaders under src/server/scripts. Covers AddSC registration and script placement conventions."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/Old-Man-Warcraft/oldmanwarcraft",
"path": ".github/instructions/scripts.instructions.md",
"ref": "e9710c16091b78ad4fca7d60621d4aafb3b665bb",
"url": "https://github.com/Old-Man-Warcraft/oldmanwarcraft/blob/e9710c16091b78ad4fca7d60621d4aafb3b665bb/.github/instructions/scripts.instructions.md",
"key": "Old-Man-Warcraft/oldmanwarcraft/.github/instructions/scripts.instructions.md"
},
"applies_to": "src/server/scripts/**/*.cpp, src/server/scripts/**/*.h"
},
"instructions": "# Script Guidelines\n\n- Place gameplay content logic in `src/server/scripts/`. Place engine or generic gameplay systems in `src/server/game/`.\n- Follow the standard registration pattern after placing the script: implement `AddSC_*()` and wire the script through the relevant script loader.\n- Keep spell scripts in the existing class-grouped files such as `spell_dk.cpp`, `spell_mage.cpp`, or `spell_generic.cpp`. Use a different file only when nearby scripts in the same feature area already follow a more specific file or loader pattern.\n- Match the naming, registration style, and nearby helper patt",
"cost": {
"context_tokens": 234
}
}
Fetch it by URL: GET /api/v1/registry/old-man-warcraft-oldmanwarcraft-scripts-instructions/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
