Add new EFI features to the typescript definition file

[OtterCodes101]

a bunch of new EFI features need to be added to the definition file so it can properly use intellisense

[OtterCodes101]

oh we also need to update the API docs iirc

[OtterCodes101]

nvm the docs are in the EFI repo but it'd still be helpful to link them there

[OtterCodes101]

or we could just move those to eaglerforge.github.io

[radmanplays]

or we could just move those to eaglerforge.github.io

I agree

[OtterCodes101]

yeah i think it'd be better to have the docs just at eaglerforge.github.io

[OtterCodes101]

we should also add descriptions to the d.ts documentation

[ZXMushroom63]

a bunch of new EFI features need to be added to the definition file so it can properly use intellisense

about that...........
EFI's structure is a little bit different from legacy EaglerForge, as instead of having code to manually expose each property, its all based on directly interfacing with eaglercraft at runtime. we'd pretty much need to convert all of minecraft into a .d.ts file (which I've got no clue how to use)

After I'm done doing custom meshes and whatnot I can try writing a script to traverse the modapi object and generate a .d.ts from it, but it's still not gonna be fun.

[STPv22]

Is there any way I can still make ts mods with the new API?

[ZXMushroom63]

Is there any way I can still make ts mods with the new API?

yes, you just wont get autocomplete features

[OtterCodes101]

typescript mods are better for organization as you can have stuff in different files :3 thats why I would recommend using it over just writing a .js file

[STPv22]

declare var ModAPI: any, right?

[STPv22]

typescript mods are better for organization as you can have stuff in different files :3 thats why I would recommend using it over just writing a .js file

ye that's why want to try it :3

[OtterCodes101]

declare var ModAPI: any, right?

pretty sure that would work too

[OtterCodes101]

try it out