AppLovin’s attempts to acquire Unity last year turned sour when Unity opted for a  merger with rivals ironSource instead . Now, in the ongoing shockwave of Unity's unpopular introductio...

AppLovin’s attempts to acquire Unity last year turned sour when Unity opted for a merger with rivals ironSource instead . Now, in the ongoing shockwave of Unity’s unpopular introductio…

  • Dangdoggo@kbin.social
    0·
    1 year ago

    Wow well I guess I’ll eat crow. I never thought that was possible to automate but given the use of LLMs I guess it is… Excited to see how it turns out

    • Match!!@pawb.socialEnglish
      0·
      1 year ago

      From their GitHub, they use this prompt to ChatGPT:

      You are professional Unity engineer who is migrating a large project from Unity platform to Godot 4.1. Migrate code to GDScript, which you are an expert in. Follow the following rules: 1. Output code only, put explanations as comments. 2. Do not skip any logic. 3. Preserve all comments without changing. 4. If migration is impossible leave “TODO [Migrate]” comment. 5. Use GDScript best practices. 6. Convert camelCase variable names and method names to snake_case. 7. Unity namespaces should migrate into ‘class_name’ directive. 8. Unity class should migrate into ‘class_name’ directive.

      Personally I find this kind of thing adorable and I hope it works out for them