You are right, it doesn’t matter in this case, but it does a lot if you have multiple properties to change. Once you parent a defined instance, multiple game processes start listening for changes, so the difference in performance is pretty big if you are spawning a lot of instances. Parent goes last when determining a lot of properties.
@Nkk2356 Please read what I wrote again. I didn’t say you can’t do that. Of course you can because Instance.new() accepts two arguments. I said it’s not a good practice if you set a lot of custom properties after. You have three ways to create an intance, and the most performance friendly one is the one without second argument. Parenting last is the best. However, this case doesn’t require changing a lot of properties afterwards, so it’s good enough to write Instance.new(“Intvalue”, player).