Closed delphiactual closed 2 years ago
The reason this is happening is that the singleInitialItemHash of the void 3.0 sockets isn't actually the void empty plug, but rather the stasis empty plug. The one in the plug set is a different one. So Void subclasses start with the stasis empty plug inserted. Once the user plugs something else it's never considered empty by DIM.
You can see that the subclass plug drawer also shows the empty sockets when it really shouldn't.
Bungie said this won't be fixed on their side https://github.com/Bungie-net/api/issues/1606
I'll put something up that opens a path to addressing this very soon.
https://dim.gg/fw3wada/VOIDLOCK-2.0