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…
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
Does ChatGPT’s code get better if you include “You’re an expert in that language” in the prompt?
It does occasionally because it filters out sources which doesn’t fit that pattern, but it doesn’t guarantee anything (for a variety of reasons, like inevitable statistical cross contamination in the model, bad samples like overconfident answers, smaller number of samples to learn from, etc).
Good question. Based on my limited understanding of LLMs, I don’t see how it could…I’m interested to hear if that’s not the case.
Because an LLM’s goal isn’t to always be the most correct at answering questions. It just says what it thinks you want it to say. It’s not that telling it that it’s an expert necessarily makes it smarter, you’re just specifying not to give you an answer as though it was an amateur, which otherwise it wouldn’t have any reason not to do.
You are professional Unity engineer who is migrating a large project from Unity platform to Unreal Engine 4. Migrate code to C++, which you are an expert in. Follow the following rules: 1. Always output exactly two code blocks: one with headers and other with implementations. 2. Do not skip any logic. 3. Preserve all comments without changing. 4. If migration is impossible leave “TODO [Migrate]” comment. 5. Use Unreal Engine C++ best practices.
