PROGRAM_IX

Members
  • Content Count

    9
  • Joined

  • Last visited

About PROGRAM_IX

  • Rank
    Newbie

Contact Methods

  • Twitter
    PROGRAM_IX
  1. RT @AudreyCarville: The apology comes nowhere close to conveying the disgusting behaviour of the journalist https://t.co/a896lfw8b5

  2. Don't worry about it, I wouldn't have tweeted you at all but I had tried a couple of things with no success and wasn't sure just how silly a mistake I was making. --nolib didn't actually fix it, though! The ES5 reduced it to one error, but --nolib freaked it out all over again. I did have to go into the code of Device.ts and comment out a line. So --nolib wasn't the solution in my case, anyway. I probably just did that wrong too. XD
  3. Fair enough. I certainly don't mind implementing it myself on a game-by-game basis. Just wondering if it was a wildly stupid consideration as a library method. Yes, I was going for something that would be faster than rect to rect, as that can get sloooow at times in my games. >.< Poor optimisation on my part, probably.
  4. Well, I didn't have much success over the weekend, but that was due partly to a social life that came out of nowhere, and partly to a compile error that happened almost immediately and caused me to prototype in a different framework. Even then I didn't submit a game. >.< However, I have Phaser running now, so I will definitely be coming back to it. I'm not sure how fun my game is, after the other prototype, but I think I'll still make it in Phaser for laughs.
  5. How unreasonable is radial (vector distance) detection? For cases where you're not too concerned about accuracy or things are simply too small, would it be a handy thing to have? Bullets for example, whether round or not, could easily be small enough that simply detecting if they were x pixels/other units from the centre of a given sprite would be enough. Not sure about performance impact, though. I used it a bit in my game framework thing, but I didn't test that thoroughly enough to say for sure.
  6. Silly me, I should have Googled the new error. Using --nolib as that link suggests does not work, but commenting out the line (which was something to do with Internet Explorer detection) did. Now I can run games at last! Thank you very much for your help.
  7. Thanks, I will! I was looking at those options earlier, but seeing the default is ES3 I thought that ES5 would only *increase* the possibility for errors. --- Oh wow, that was dramatic. The errors have now been reduced to this: .../programming/html5/phaser/phaser/Phaser/system/Device.ts(384,49): The property '$1' does not exist on value of type '{ (pattern: string,flags?: string): RegExp; new(pattern: string,flags?: string): RegExp; }'
  8. I'm clearly missing something. I pulled down from GitHub (just now, again, to make sure) and am running almost verbatim the rect vs. rect test from the test suite. Or rather, I'm trying. I installed Node.js and used npm to get the tsc compiler, which seemed fine. But then I tried to actually compile something and I got screenful after screenful of errors. .../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(140,21): The property 'scrollFactor' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(140,52): The property 'scrollFactor' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(142,55): The property 'scrollFactor' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(143,55): The property 'scrollFactor' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(147,21): The property 'angle' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(149,21): The property '_game' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(150,21): The property '_game' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(152,25): The property 'angle' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(154,25): The property '_game' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(154,57): The property 'angle' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(162,22): The property '_game' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(175,48): The property '_game' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(179,48): The property '_game' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(185,21): The property '_game' does not exist on value of type 'ScrollZone'.../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(16,4): Base type 'any' lacks an implementation..../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(16,4): Base type 'any' lacks an implementation..../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(16,4): Base type 'any' lacks an implementation..../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(16,4): Base type 'any' lacks an implementation..../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(16,4): Base type 'any' lacks an implementation..../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(16,4): Base type 'any' lacks an implementation..../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(16,4): Base type 'any' lacks an implementation..../programming/html5/phaser/phaser/Phaser/gameobjects/ScrollZone.ts(16,4): Base type 'any' lacks an implementation..../programming/html5/phaser/ld48/test.ts(5,28): The property 'Game' does not exist on value of type 'Phaser'.../programming/html5/phaser/ld48/test.ts(15,13): The property 'velocity' does not exist on value of type 'Phaser.GeomSprite' (That's the last few lines, but it seems to have a problem with just about every Phaser class.) It just goes on like that. Here's my directory structure: .../programming/html5/phaser: phaser/ [Phaser library] Phaser/ Docs/ ld48/ [site of game code if it ever works] test.ts [rect vs. rect from test suite, with one change (see below)] The only change I've made to the test.ts file is this: /// <reference path="../phaser/Phaser/Game.ts" /> And here's how I compile: tsc test.ts That should work, right? It's clearly *finding* the Phaser files, but what is the deal with these errors? Any help greatly appreciated. Falling at the first hurdle is never fun.
  9. I've got a free weekend and, even though I'm twelve or so hours late, I think I'm going to try and make something with Phaser for it. It'll be a trial by fire to say the least, considering I've a) never used JS for game development and never used TypeScript at all. But I really want to make something and this is an easy way to impose a deadline. The caveat is that if I get nowhere today I'm going to use my own Python game framework again. http://www.ludumdare.com/compo/ if you want to join me. (The theme is Minimalism.) Here are the links I currently have open in case anybody feels lost like me: http://net.tutsplus.com/tutorials/javascript-ajax/getting-started-with-typescript/ http://stackful-dev.com/typescript-nodejs-vim-and-linux-oh-my.html http://www.typescriptlang.org/Playground/ http://jessefreeman.com/game-dev/building-a-html5-game-with-phaser/ Wish me luck!
  10. Now that my Final Year Project is submitted, I am sooo close to being able to play with this. Soooon. Maybe this weekend for the LD48 warmup, depends whether I want to build something using my own framework. But looking better every time I see it!