18,700
edits
Introduction to modding: Difference between revisions
m
→Editing scripts: wording
m (→Introduction to the game data: wording) |
m (→Editing scripts: wording) |
||
| Line 39: | Line 39: | ||
==Introduction to types of modding== | ==Introduction to types of modding== | ||
===Editing scripts=== | ===Editing scripts=== | ||
The easiest kind of modding is scripting. Scripts are written in the BungieFrameWork Scripting Language and stored as plain-text files with the suffix .bsl in the sub-folders inside GameDataFolder/IGMD/. Scripts take a lifeless level and spawn characters in it (the AI-driven [[wikipedia:Non-player_character|NPC]]s | The easiest kind of modding is scripting. Scripts are written in the BungieFrameWork Scripting Language and stored as plain-text files with the suffix .bsl in the sub-folders inside GameDataFolder/IGMD/. Scripts take a lifeless level and spawn characters in it (Konoko and the AI-driven [[wikipedia:Non-player_character|NPC]]s), give the level a logical flow of events, drive cutscenes, make the AIs play certain roles, and alter the level's appearance. | ||
Scripting is the easiest way to mod because you can work with existing game data, and only have to modify BSL files using a text editor. It's quick and easy to see the results of your work (just reload the level), and you have lots of accessible examples to learn from (14 levels' worth!). That being said, scripts | Scripting is the easiest way to mod because you can work with existing game data, and only have to modify BSL files using a text editor. It's quick and easy to see the results of your work (just reload the level), and you have lots of accessible examples to learn from (14 levels' worth!). That being said, scripts sometimes reference game resources in technical ways, so you will have to learn how certain data types work in order to script effectively. | ||
*Go to the [[BSL]] namespace to start learning about scripting, or; | *Go to the [[BSL]] namespace to start learning about scripting, or; | ||