search

SalvationDevelopment / YGOSalvation-Server

Server, Launcher, build test, and management system for YGOPro and related technologies.
http://ygosalvation.com
Other
23 stars 18 forks source link

Brand new committed cards are unplayable without server restart #358

Closed StormWulf closed 7 years ago

StormWulf commented 7 years ago

From what I noticed, I committed new cards, then confirmed that they exist in the Deck Edit. However, if I try to lock a deck using them, this error prompts.

"TypeError: Cannot read property 'tcg' of null at validateDeck (C:\Users\root\Documents\GitHub\YGOPro-Salvation-Server\libs\validate-Deck.js:237:26) at responseHandler (C:\Users\root\Documents\GitHub\YGOPro-Salvation-Server\libs\manual.js:347:40) at WebSocket.<anonymous> (C:\Users\root\Documents\GitHub\YGOPro-Salvation-Server\libs\manual.js:698:17) at emitTwo (events.js:87:13) at WebSocket.emit (events.js:172:7) at Receiver.ontext (C:\Users\root\Documents\GitHub\YGOPro-Salvation-Server\node_modules\ws\lib\WebSocket.js:816:10) at C:\Users\root\Documents\GitHub\YGOPro-Salvation-Server\node_modules\ws\lib\Receiver.js:477:18 at C:\Users\root\Documents\GitHub\YGOPro-Salvation-Server\node_modules\ws\lib\Receiver.js:361:7 at C:\Users\root\Documents\GitHub\YGOPro-Salvation-Server\node_modules\ws\lib\PerMessageDeflate.js:247:5 at afterWrite (_stream_writable.js:346:3) at onwrite (_stream_writable.js:337:7)"

I'm aware that restarting the server remedies this, but is there a better solution? If not, it needs to be taken into consideration.