[Feature request] Allow splitting script into multiple files

[UnliquidSnake]

Allow using multiple files for the code of one set, like #include in C++.
This would help with really big sets where there's just a lot of code to go through, right now it's a pain having to scroll to wherever the heck you decided to define X function when needed. Imagine doing a game like, say, BlazBlue with its 800+ code notes, it's nuts.
Also it would help with the lag that happens when these files get too big.

[Jamiras]

right now it's a pain having to scroll to wherever the heck you decided to define X function when needed

You can use "Edit > Goto Definition" (default F12) to jump to the function under the cursor, then use Mouse4/Mouse5 buttons to jump back and forth between the cursor locations

[wescopeland]

I concur this would be helpful, for developer experience reasons outside of UI lag.

In VSCode, I like to set up my RAScript files into logical regions:

Code.mp4

In this file I have the following regions:

• Memory Symbols (actual variable names from the game's source code)
• Constants
• Memory / Code Notes
• Common Utils
• Special-purpose Achievement Functions
• Core Achievements
• Subset - Bonus Achievements
• Leaderboards
• Rich Presence

I'd probably split these all into individual files, hoping to have them bundled at compile-time. It does beg the question of what that would actually look like syntactically. This is a contrived example of what I would propose:

// MemorySymbols.rascript

// These are addresses from compiler output that we can change as the devs release new patches for the game.
_MEM_DISPHEALTH            = 0x26DE        // (B disphealth)

// Memory.rascript

open MemorySymbols

function CurrentHealth() => byte(MemorySymbols._MEM_DISPHEALTH)

// Utils.rascript

open Memory

function IsDead() {
  return Memory.CurrentHealth() == 0
}

// Mega Man The Sequel Wars - Episode Red.rascript

// ~Homebrew~ Mega Man: The Sequel Wars - Episode Red
// #ID = 24453

open Utils

// do some interesting things here ...

In this proposal:

• If an RAScript file has no "// #ID = ..." comment, it's considered a "module".
• Modules can be imported by any RAScript file using the open keyword at the top of the file.
• The module name matches its filename.
• Everything within a module is considered public and exported.
• Accessing a module's contents after it has been "opened" can be done like ModuleName.ExportedThingName.

Granted, the example given above has a few pitfalls. For example, what should happen if there's a circular dependency?

I think this would open up some interesting opportunities. For example, the thought has definitely crossed my mind that it would be nice to have a "standard library" of reusable utils across my sets for certain things like RP and leaderboards. All of a sudden, that would be possible.

[UnliquidSnake]

right now it's a pain having to scroll to wherever the heck you decided to define X function when needed

You can use "Edit > Goto Definition" (default F12) to jump to the function under the cursor, then use Mouse4/Mouse5 buttons to jump back and forth between the cursor locations

My mouse does not have Mouse4/Mouse5 buttons, so I still have to scroll that shit. It does help a little, but splitting would be infinitely easier to work with as long as it's done right. The only problem I see with this is that the code always compiles automatically every time a change is made, and honestly almost everyone here would be fine if there was an option to do it manually.