When/if Unity switch to .NET core, will they be renamed to NetCoreBehaviour?
And break every single thing in the entire universe, ever? I doubt it.
A more likely solution would be to simply have an alternative behaviour with the option to choose which framework to use for your project. After all .NET Core only has a fraction of the framework that Mono has. Removing Mono would destroy more projects than it would likely benefit.
Maybe we’ll get an additional class called Behaviour or Component at some point. They’ve talked about it before. MonoBehaviour is so widely used that it simply can’t be removed, but they can deprecate it and have the code upgrader switch it out.
It’s just a name, you know. They could be lazy and leave it like it is.
No. Nothing will change most likely.
MonoBehaviour hasn’t been directly linked to Mono for a long time. It’s just a name.
It may be an unfortunate name, but it’s not one that’s worth fixing.
I propose the Unity community unites and votes for a new name!
NoMoreGarbageCollectionBehaviour is one that springs to mind…
That would make it an even bigger lie ![]()
I have many axes to grind against MonoBehaviour, but I don’t think its name was one of the most prominent abominations of the class.
I seem to recall somebody from Unity saying something about replacing monobehaviour functionality with something else but I can’t for the life of me actually find where it was said.
We share the same memory, false or not. Can’t find it either ![]()
I’m more annoyed with the u in behavior than I am in mono.
They’re European. Just get used to it ![]()
I think they showed something called ScriptBehaviour in the recent Unite videos. They mentioned that it would require a slightly different way of thinking about scripts, if my memory serves me correctly.
That must be it. I’m interested to see what comes of that, but I imagine we won’t be seeing it until at least Unity 2018
The first name that came to my mind was NoBugsPleaseBehaviour. ![]()
You’ll need C++ bindings for that. Garbage generation is deeply entrenched into C#, and if nothing collects the garbage, it is not going to do well
My vote goes for BehaviourMcBehaviourface.
Unity have been talking about replacing monobehaviours for a while now though, so there’s probably not much point in renaming them before this happens.
Have they?
ok I’ve had my laughs:
And I think I finally remembered which game your avatar is from but I don’t think It’s safe to speak of it here. Also I forgot the title. Just answer this: It’s a game where you dig out a labyrinth/maze, correct?
Any linkes to the talks about replacing monobs?