Calling other mods functions in the data stage

[BraveCaperCat]

In my mod, i want other mods to be able to call a function i define in the data stage to create alot of related prototypes. However, i don't think mods can communicate with each other in the data stage, only in the control stage. I would like this ability to be added to the data stage to allow other mods to use my utility functions to create prototypes.

[curiosity]

However, i don't think mods can communicate with each other in the data stage, only in the control stage.

That's because there is no barrier in data stage. All mods are mashed together into the same Lua state. The docs tell you this, by the way. That's why you are able to call table.deepcopy etc. without requiring a base game lib: another mod did it for you. So you make a Lua global function/table of functions and tell people to call them.

[Qon]

In my mod, i want other mods to be able to call a function i define in the data stage to create alot of related prototypes. However, i don't think mods can communicate with each other in the data stage, only in the control stage. I would like this ability to be added to the data stage to allow other mods to use my utility functions to create prototypes.

The solution is in the docs:

Main global objects:
mods :: Mods: A dictionary of active mods and their versions.

Furthermore, it is possible to require files from other mods by using require("__mod-name__.file").

[FuryoftheStars]

You can also define a variable as a global (ie, not use the local keyword), then define functions as elements of the global var. I did that with my Restrictions on Artificial Tiles mod. Just be sure to make it truly unique, like using your mod's name as part of the var.

[BraveCaperCat]

However, i don't think mods can communicate with each other in the data stage, only in the control stage.

That's because there is no barrier in data stage. All mods are mashed together into the same Lua state. The docs tell you this, by the way. That's why you are able to call table.deepcopy etc. without requiring a base game lib: another mod did it for you. So you make a Lua global function/table of functions and tell people to call them.

Last time i checked, each mod ALWAYS ran in a seperate instance of LUA. Table.deepcopy is possible, since when each mod writes to data.raw (or uses data:extend) the game automatically updates the data.raw table for all the mods loaded AFTER. I guess it has changed since i started making mods.

In my mod, i want other mods to be able to call a function i define in the data stage to create alot of related prototypes. However, i don't think mods can communicate with each other in the data stage, only in the control stage. I would like this ability to be added to the data stage to allow other mods to use my utility functions to create prototypes.

The solution is in the docs:

Main global objects:
mods :: Mods: A dictionary of active mods and their versions.

Furthermore, it is possible to require files from other mods by using require("__mod-name__.file").

I literally saw that second documentation after posting this, but i don't know where the delete button is.

You can also define a variable as a global (ie, not use the local keyword), then define functions as elements of the global var. I did that with my Restrictions on Artificial Tiles mod. Just be sure to make it truly unique, like using your mod's name as part of the var.

Ok. That would be like an Interface Variable containing various functions to interact between mods.

[FuryoftheStars]

Sorry, replying from a phone so it's difficult to quote out the needed part. And for some reason I didn't think to put it like this before: pre-control stage, the different mods are not very well sandbox. While they are not able to access each other's local vars, they can access each other's globals (which is something that can't be done in control stage).

So while yes, I created an interface of sorts (but not really), I only did it that way to minimize my footprint in the global environment. I could have made each individual function global directly if I wanted to.

[BraveCaperCat]

Sorry, replying from a phone so it's difficult to quote out the needed part. And for some reason I didn't think to put it like this before: pre-control stage, the different mods are not very well sandbox. While they are not able to access each other's local vars, they can access each other's globals (which is something that can't be done in control stage).

So while yes, I created an interface of sorts (but not really), I only did it that way to minimize my footprint in the global environment. I could have made each individual function global directly if I wanted to.

Just in case some other mod adds a global function with a similar name to yours, you can still have your functions since you use a global variable of functions instead of global functions.

[FuryoftheStars]

Sorry, replying from a phone so it's difficult to quote out the needed part. And for some reason I didn't think to put it like this before: pre-control stage, the different mods are not very well sandbox. While they are not able to access each other's local vars, they can access each other's globals (which is something that can't be done in control stage).

So while yes, I created an interface of sorts (but not really), I only did it that way to minimize my footprint in the global environment. I could have made each individual function global directly if I wanted to.

Just in case some other mod adds a global function with a similar name to yours, you can still have your functions since you use a global variable of functions instead of global functions.

Pretty much, yes.