Quick question about using this MIT-licensed plugin in my game

e7de84f7c71249dc8a21a7d1f05899f3 · June 4, 2026, 2:07pm

LICENSE

master

MIT License

Copyright (c) 2019-2026 pafuhana1213

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

This file has been truncated. show original

Hi everyone,
I recently used this plugin in my Unreal Engine 5 project. However, I’m a bit confused about how the MIT License works in this case.

I am not redistributing the plugin itself; I am just using it to build and release my own game.

In this scenario, is it enough to just list the plugin’s name in my game’s in-game Credit screen? Or do I need to include the full license text and copyright notice as well?

Any clarification would be greatly appreciated. Thanks!

Countsie · June 5, 2026, 12:50am

For MIT, you only need to keep the copyright with the source. No need to credit at all in finished game. You can redistribute source as much as you want.

EDIT: This isn’t totally correct. See my reply below.

e7de84f7c71249dc8a21a7d1f05899f3 · June 5, 2026, 2:06am

(post deleted by author)

e7de84f7c71249dc8a21a7d1f05899f3 · June 5, 2026, 2:06am

Thank you for your reply.

When you say “keep the copyright with the source”, could you clarify what exactly that means in this case?

For example, if I create a license file such as:

YourGame/
├ Binaries/
├ Content/
├ Licenses/
│ └ KawaiiPhysics_LICENSE.txt

and include the full MIT license text and copyright notice:

"MIT License

…"

inside that text file, then package and distribute my game with that license file included, would that be sufficient?

Or are you specifically referring to keeping the copyright notice inside the plugin’s source code files?

I just want to make sure I am complying with the MIT license correctly when releasing my game.

Thank you for your time.

Countsie · June 5, 2026, 5:09am

Keep the license/copyright in the source code file, if you re-distribute the source. That’s it. Otherwise you are free to use the code as you please with no attributions needed, no need to include the license or mention it with your game.

Edit: Not totally correct. See my reply below.

e7de84f7c71249dc8a21a7d1f05899f3 · June 5, 2026, 2:15pm

Thank you for such a kind reply! This plugin seems really generous.

Countsie · June 5, 2026, 7:47pm

OK, just clarified with someone more familiar with the legal stuff. I was wrong, you are required to add the license file to the final build. As you showed above would be fine, you just have to provide access to the text of the license somewhere in your distribution.

Apologies for being hasty in my answer!

And yes, the plugin author is very generous, for sure. We are lucky to have devs like that in our community!

e7de84f7c71249dc8a21a7d1f05899f3 · June 6, 2026, 4:08pm

(post deleted by author)

e7de84f7c71249dc8a21a7d1f05899f3 · June 6, 2026, 4:08pm

Thank you so much for taking the time to look it up. I tried looking it up myself, but these kinds of conditions are really hard to figure out, aren’t they? Thank you so much for telling me the answer!