Which leads to the following error: /homenode/browserquest/BrowserQuest/server/js/map.js:15Īt .extend.init (/home/node/browserquest/BrowserQuest/server/js/map.js:15:11)Īt Class (/home/node/browserquest/BrowserQuest/server/js/lib/class.js:50:23)Īt .n (/home/node/browserquest/BrowserQuest/server/js/worldserver.js:151:20)Īt /homenode/browserquest/BrowserQuest/server/js/main.js:79:15Īt Function._.each._.forEach (/home/node/browserquest/BrowserQuest/node_modules/underscore/underscore.js:153:9)Īt main (/home/node/browserquest/BrowserQuest/server/js/main.js:77:7)Īt /home/node/browserquest/BrowserQuest/server/js/main.js:134:13Īt /home/node/browserquest/BrowserQuest/server/js/main. WorlizeRequest = require('websocket').request, MiksagoConnection = require('node-websocket-server/lib/ws/connection'),
Wsserver = require("node-websocket-server"), I also tried updating the server/js/ws.js file directly as follows (added node- to the websocket-server fields): var cls = require("./lib/class"), One prior SO post I saw said to replace websocket-server with node-websocket-server in the package.json file, however there are existing direct calls to websocket-server in the BrowserQuest codebase. Can be dropped by greater skeletons Ruby- dropped from specters and can be found in the volcanic wasteland. Chain Mail- can be in grey chests or found in the desert.Plate-can be in grey chests or found in No mans land. I have added the ws and node-websocket-server packages, however neither of them seem to be an easy replacement for the existing calls to websocket-server. Leather-Can be in grey chests in the village or be dropped by monsters. BrowserQuest, was sponsored by Mozilla and it inspired a huge catalog of games because the code was released as open source. It depends on the websocket-server node package, and unfortunately that has been deprecated and removed from the npm library. Play the earliest multiplayer RPG game ever released using the HTML5 technology. I am trying to get Mozilla's BrowserQuest up and running and have run into a problem.
0 kommentar(er)
