Selamat Datang di GTA5-Mods.com

@BOPOHua coroutine is not supported, because the task scheduler may run the task in another thread, while native function can only be called from main thread, you'll have to coordinate the task yourself, e.g. using Script.Wait()

@KimgKomg Thanks!

@scarredface1017 Sorry, I didn't really understand you. Older scripts built with SHVDN won't work with this. This is an experimental asi plugin for developer seeking a way to write script in .NET 7 with little efforts migrating from SHVDN.

@MrVicho13 Call it whatever you want. Microsoft's rebrand does not change the fact that it is fundamentally .NET Core. I mean, look at the GitHub repo, CoreCLR, CoreRT... IMO using this name to distinguish it from SHVDN is justified

If you need to write Function.Call 1000+ time then this will definitely make a difference, saving much time to type Function.Call<T> yourself

@JohnFromGWN if you don't like this library, just don't use it. I made this because I'm tired of explicitly specifying the argument and return type everytime I need to call a native, it was intended for use in my other bigger projects, just sharing it here in the hope to somehow benefit the community

@JohnFromGWN I still don't get you. What do you mean "provides the correct syntax and ensures it the function is also current, more current than the Native DB" ?
If you're referring to scripting API, then yes it's mostly documented and doesn't need to specify argument and return type manually. But what I'm discussing here is calling native directly, not the API someone already made for you.
Function.Call requires you to specify return type via a generic parameter and all argument types, which can go wrong sometimes.

I think you misread the description, this library is a wrapper for calling arbitrary native function (Function.Call) more conveniently. None of them are documented in SHVDN, so I wonder where you're intellisense suggestions come from?

@anon23623 could you post a screenshot of the error message?

@HdyMac22 The mod should still work despite the error message