Split Plugin Loader 1.1.3

I might add support for building plugins for deployment IE like marking methods as [Carbon] or [Oxide] and then having a built plugin folder

Good stuff. In future updates I'd also like to see region support and the ability to prioritize placement in the file.
At the moment you can set the priority by putting numbers in front of file names, but it is not very convenient.

3 hours ago, 0xF said:

Good stuff. In future updates I'd also like to see region support and the ability to prioritize placement in the file.
At the moment you can set the priority by putting numbers in front of file names, but it is not very convenient.

Oh yeah I can add region support I’m finishing up the carbon and oxide specific methods and I’ll push them together  . File prioritization though might be tricky without hitting performance! I can look into that though.

8 hours ago, 0xF said:

Good stuff. In future updates I'd also like to see region support and the ability to prioritize placement in the file.
At the moment you can set the priority by putting numbers in front of file names, but it is not very convenient.

Added the #region support in 1.1.0! Tell me if theres any issues with it

Hi, I found a not very nice thing, overloaded methods with different arguments are combined into one method, although they should not.

14 hours ago, tsunderella said:

Added the #region support in 1.1.0! Tell me if theres any issues with it

Also about regions, it works not bad, but there are some errors. For example, when you put one field in a region, all the fields are put in this region after compilation, and I would like the regions to specifically complement each other, combined, as well as it would solve the problem with priorities to some extent.
There is also a moment with duplicating the beginning of regions. When you make regions of fields in several files, after compilation you get:
#region Variables
...
...
#region Variables
...
...
#endregion

This is where combining regions with the same name would be great.

7 hours ago, 0xF said:

Also about regions, it works not bad, but there are some errors. For example, when you put one field in a region, all the fields are put in this region after compilation, and I would like the regions to specifically complement each other, combined, as well as it would solve the problem with priorities to some extent.
There is also a moment with duplicating the beginning of regions. When you make regions of fields in several files, after compilation you get:
#region Variables
...
...
#region Variables
...
...
#endregion

This is where combining regions with the same name would be great.

My bad I didn’t account for variables in the region . I’ll edit the transpiler to do that! I did some code reforms as well so it shouldn’t take long when I get home

also for the override can you show me an example?