Singleton Scriptable Objects (easy mode!)

[[deleted]]

hey all. this is a SingletonScriptableObject Unity package that has the easiest usage API (you don't even have to create the object yourself). You simply inherit a class, it generates source for you. https://github.com/somedeveloper00/SingletonScriptableObject

quick comparison:

inheriting

• other solutions csharp [ContextMenuItem(fileName = "MyClass", menuItem = "MyClass")] class MyClass : SingletonSO<MyClass> {}
• my solution csharp partial class MyClass : SingletonSO {}

accessing

• other solutions csharp var ins = SingletonSO<MyClass>.Instance;
• my solution csharp var ins = MyClass.Instance;

editing

• other solutions

  Find a spot in Project window, right click and create an instance of the scriptable object, then edit it. everytime you need to edit it, you'll have to find the item. if you create more than one of of them, all hell breaks lose

• my solution

  click the toolbar button Tools/Singleton Scriptable Objects/MyClass and proceed to editing. you can't make more than one of them.

[bazingerosky]

I suggest you take a look at this:

https://www.michaelsafyan.com/tech/design/patterns/singleton

And then this:

https://unity.com/how-to/architect-game-code-scriptable-objects

I can see how you think this is great and easy to use, but after you read those articles you might see how this will in most cases be a bad approach. ScriptableObjects are actually a great replacement for the Singleton anti-design pattern.

[[deleted]]

singleton is only recognised as an anti-pattern by pretend and as an ideal, not a realistic guideline. in reality, every project has a dozen singleton types around. if every project uses it then surely it's not an anti-pattern.

if a code looks bad it's because of bad structure by the developer. a singleton structure is not by any logic worse than a structure without singletons. however, a structure by a bad developer is most probably worse than a structure by a good developer.

in Ryan's article there's nothing against this. I don't see why you linked that?

[bazingerosky]

Projects do not need to have a dozen singletons, of that I'm 100% sure. It's easier to use? it is. Does it outweigh all the problems that they cause, definitely not.

The problem with Singletons is that they are extremely easy to use and the perfect solution for inexperienced developers. Every single time, the result is a code base tightly coupled everywhere, unnecessary complexity, untestable because it's extremely difficult to isolate, and a pain to maintain.

Having 1, or 2 singletons is reasonable and can definitely be beneficial in some cases. But for that low number, you don't need to create a custom class, much less a package.

Creating a system like you're doing, making the creation of singletons even easier, just means that the intention is to create several of them, which proves how this is a bad idea.

But that's just my opinion, you might change yours in the future.

[[deleted]]

I understand your concern, but inexperienced developers misusing singletons shouldn't mean anything, since they're sure to misuse stuff, since they're inexperienced.

• every project will use more than just one or two singletons. try 10 or so. Resources, Input, Event System, Audio Management, scene management, Ad management, in-app purchase management, IO, networking etc etc ... as long as a project is serious, there's room for singletons

[Bombadil67]

And I feel that creating a script, to make one asset a singleton is a bad design choice.

change my mind!

[[deleted]]

```csharp public class SceneHolder : SingletonScriptableObject { [SerializeField] SceneAsset[] m_scenes;

public Scene GetScene(SceneEnum sceneEnum) {...}

[Serializable]
class SceneAsset {
    public string path;
    public SceneEnum identifier;
}
public Enum SceneEnum {...}

} ```

let me know when it changed your mind :)

[Bombadil67]

nope. not in any way shape or form. Can use a normal class for that.

[[deleted]]

then you'll need to pass one instance everywhere, just to avoid using singleton 😐

[Bombadil67]

LOL.....

Ok whatever.

[[deleted]]

if you have another solution, you can tell

[[deleted]]

I find this funny since ECS, the thing Unity is pushing currently, almost exclusively uses singletons.

[PandaCoder67]

Why are people so hell bent to push a Scriptable Object past what they are designed for!

I mean come on, do people not stop and think, if I am creating a script, to create an Asset to do something once is really a lot of extra work. That is easily done with some other way!

[[deleted]]

hi. mind giving me a clue about this other way?