Hazae41 submitted a new resource: [RUNTIME] Kotlin4MC - Use Kotlin in your Minecraft plugins! Read more about this resource...
Hazae41 updated [RUNTIME] Kotlin4MC with a new update entry: 1.2.50 Read the rest of this update entry...
Hazae41 updated [RUNTIME] Kotlin4MC with a new update entry: 1.2.50 Read the rest of this update entry...
Hazae41 updated [RUNTIME] Kotlin4MC with a new update entry: 1.2.50 Read the rest of this update entry...
1. ...yes lmao I use kotlin all the time 2. Google it meant to have YOUR javadocs for YOUR api/library? Lol wot?
Hazae41 updated Kotlin4MC : Kotlin for Minecraft with a new update entry: 1.2.60 Read the rest of this update entry...
Hazae41 updated Kotlin4MC : Kotlin for Minecraft with a new update entry: 1.2.61 Read the rest of this update entry...
Hazae41 updated Kotlin4MC : Kotlin for Minecraft with a new update entry: Coroutines Read the rest of this update entry...
I honestly would say this is useless. Sure it can be helpful if you develop all your plugins privately and then use one main plugin as a shade, but in the case of public plugins. Some may use a somewhat oldser version of kotlin shaded, and some may use a later version shaded. What happens if I have two plugins that use yours One with kotlin "1.1" One with kotlin "1.2" Your plugin is latest "1.2" The "1.1" plugin breaks because it uses an older version of kotlin and requires that version. In my opinion for public plugins the best idea is to just shade kotlin yourself then relocate it. If you plan to use the same version of kotlin through multiple plugins, relocate it to the same package in all of them so they are shared and only loaded once. I think that's how it works. Anyway this is just my opinion.
Hazae41 updated Kotlin4MC : Kotlin for Minecraft with a new update entry: 1.2.71 Read the rest of this update entry...