Earlier quoted context omitted.
It's in the maze, I've heard, but I can't find Rick.
He's in there. Try unorthodox combinations. I think there's some state stored on whether or not you went through "up" doors or "down" doors.
Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
71–80 of 112 posts
Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#72Earlier quoted context omitted.
It'll be nice when the tech doesn't matter but if someone can't play your game because they prefer a different browser then that kind of sucks.
If you're referring to IE, well IE will give up Flash support anyway.
And yes, I think this separation is ridiculous.
Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#73Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#74Earlier quoted context omitted.
Since they used localStorage, you can modify the state of your character. If you want the best weapons in the game, the sword is called 'goldensword' and the armor is call 'goldenarmor'.
What would be the point of that? The only fun in the game (besides the fact that it works at all) is finding the new gear and getting the achievements. If you just edit your character, then you may as well not even play.
I guess the OP's comment of local storage was also to point out the 'flaw' since it is for a multiplayer game.
Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#75Earlier quoted context omitted.
What would be the point of that? The only fun in the game (besides the fact that it works at all) is finding the new gear and getting the achievements. If you just edit your character, then you may as well not even play.
Cheating single player is only affects the player themselves. But when it comes to online, multiplayer, then cheating/codes need to be restricted. It's more from a sustaining/profitability point of view – nothing drive users away when they first log on and see everyone running around looking identical and having the best items obtained with just a few key strokes. I guess the OP's comment of local storage was also to…
Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#76Earlier quoted context omitted.
Since they used localStorage, you can modify the state of your character. If you want the best weapons in the game, the sword is called 'goldensword' and the armor is call 'goldenarmor'.
What would be the point of that? The only fun in the game (besides the fact that it works at all) is finding the new gear and getting the achievements. If you just edit your character, then you may as well not even play.
Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#77Really organized, easy reading source too: https://github.com/mozilla/BrowserQuest Outstanding work that I'm sure is going to inspire a lot of people. Though I don't see a license file anywhere.
I can see only "{", to view the full i need to go to Raw format. I think Github should provide support for formatted json.
Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#78I like how they made it really easy to get in. No signup just name your guy and go. I generally don't have time to play games however I appreciate the amount of work that goes into them. Good Job.
Realm of the Mad God is even better on that front: it auto-generate a name for you, you just hit "Play" and you're in the game ready to rock (you can edit the game once you're hooked of course, and create a formal account, and start paying your dealer, but the initial experience is "hit play and you're playing")
Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#79Earlier quoted context omitted.
It feels very polished indeed. It works just fine on Safari, SFX included, although there's no music (dunno if it is supposed to have). A little musical theme per area would be nice. There are easter eggs all over the place. I don't want to spoil them but a bunch of them really made me smile.
There is music, it can listen to it on Chrome.
Re: Mozilla's BrowserQuest - Massively Multiplayer HTML5 Experiment
#80works with opera but eats a whole cpu core