nkholski

Members
  • Content count

    111
  • Joined

  • Last visited

  • Days Won

    1

nkholski last won the day on September 16

nkholski had the most liked content!

About nkholski

  • Rank
    Advanced Member

Contact Methods

  • Twitter
    nikbrg

Profile Information

  • Gender
    Not Telling
  • Interests
    x

Recent Profile Visitors

1,770 profile views
  1. Phaser 3 Beta 4 Released

    Did something text-related change with Beta 6? I updated from Beta 5 and there are no error messages but the texts are invisible (or non-existent), everything else seems to work fine. class BootMenu extends Phaser.Scene { constructor () { super({ key: 'BootMenu' }) } create () { let config = { x: 100, y: 100, text: 'Phaser 3 - Examples', style: { font: '64px Arial', fill: '#ff00ff', align: 'center', stroke: '#ffffff', strokeThickness: '4' } } this.make.text(config) } update () { } } export default BootMenu
  2. That's great. I hope to update the repository next week with the upcoming Beta 3, and I'll link to your game in the readme then. Will try to look into what breaks deploy too.
  3. Are you using JavaScript ES 6?

    I wouldn't do anything but very basic stuff without any kind of transpiler anymore, and I would definitely not do anything with phaser without it. Thanks to node and transpilers we don't have to think about browser compatibility or being stuck with aged standards. ES5 is valid ES6 and Typescript so there is nothing new to learn, just new possibilities. With babel or typescript you can focus on your codebase without any worries about deploying the code. Node and projects such as babel has (partly) liberated us from browser hell :-) The same goes for+ css and transpilers such as sass.
  4. Phaser 3 Beta 1 Released

    @rich Thanks, I'll check it out. I had an idea to recreate 1-1 of Super Mario Bros just to see how far I would get. I just bumped Phaser 3 to Beta 2 in the bootstrap project I've been posting about in the forum and got the following error from webpack: ERROR in ./node_modules/phaser/src/camera/local/CameraManager.js Module not found: Error: Can't resolve './inc/AddsmoothedKeyControl' in '/home/niklas/projekt/phaser3-es6-webpack/node_modules/phaser/src/camera/local' @ ./node_modules/phaser/src/camera/local/CameraManager.js 37:27-65 @ ./node_modules/phaser/src/scene/local/Systems.js @ ./node_modules/phaser/src/scene/local/Scene.js @ ./node_modules/phaser/src/phaser.js @ multi phaser I haven't tried to solve it but it appeared just by switching from Beta 1 so I thought you might want to know.
  5. Phaser 3 Beta 1 Released

    @richNo wonder that you're a bit behind after everything. Plus it isn't normal to be on schedule with stuff like this anyway no matter how well you plan. I got an sudden urge to try to make a basic platformer demo to share, but I guess I'll need to be a bit more patient. :-)
  6. Phaser 3 Beta 1 Released

    Great work as always! Two quick questions: 1. Will you add this.load.tilemap or should we user this.load.json / this.load.text / this.load.xml? 2. Will Impact physics replace Arcade physics or will it be two separate things?
  7. I merged the PR and made a boot menu to choose from different examples. I also scaled the player up in your example and added a bit higher velocity. Deploy should work now.
  8. Wow. I'll take a look tonight. Actually it's not a bad idea to treat the example as a playground that can be packed with additional features one may think of. I think it could be helpful for getting a insight to Phaser 3. I'll merge the PR when I have tested it! Thanks
  9. There is an open issue on GitHub for that. I'll update the repository when the first Phaser 3 beta is out, and will close this issue then too. However, I'm a bit curious why someone would need deploy at this stage :-).
  10. Sounds great! Yeah, 'updateOutsideCamera' was just a thought. No big deal to implement a custom solution.
  11. That explains it, and a good reason too! I had a quick look at updateList.js (I'm on mobile so no testing) and it seems to be exactly what I would suggest. Having an array with objects who should have their update methods called. Something like scene.updatelist.add(gameobject), plus remove method, would be great. Or gameobject.activate/deactivateUpdate(). I think it's cleaner to keep it inside of Phaser instead of custom solutions, even if the problem is trivial. Also I really appreciate the approach of extending sprites (or other game objects) to be self contained and in separate files. It's really helpful to keep the code clean, easy to navigate and to debug. Maybe a property for the gameobjects too like updateOutsideCamera that just skips the update method if the object is outside camera and the property set to false. Would be great for platformers etc.
  12. I updated the excellent Phaser + ES6 + Webpack bootstrap project (https://github.com/lean/phaser-es6-webpack) with Phaser 3. Most of my repository is an exact copy of that repository, only with the Phaser package updated to Phaser 3 and the example replaced with one based on Phaser 3. The example source code is not an example of best practices, it's basically guess work but it works and take advantage of ES6 classes. This will do for testing out Phaser 3 but I think it would be a really great idea if Phaser 3 got an official bootstrap project when released (with ES5/ES6+/Typescript options), and that could be community driven. Github: https://github.com/nkholski/phaser3-es6-webpack
  13. I decided to take Phaser 3 for a spin but hit a wall I can't find my way around. The update-method is ignored when I extend Phaser.GameObjects.Sprite (when I cheat and call it from the scene update method everything works as expected). I import this to the scene script: import 'phaser'; export default class extends Phaser.GameObjects.Sprite { constructor (config) { super(config.scene, config.x, config.y , config.key); this.scene = config.scene; this.scene.add.existing(this); } update () { this.angle++ } } And I create an instance like this in the create method of the scene: this.sprite = new mySprite({ scene: this, key: 'sprite', x: this.game.config.width/2, y: this.game.config.height/2-150 }) It shows up and there are no errors in the console, but it is not spinning as expected. Any ideas?
  14. Zoko & the Fireflies ( 2d platformer )

    Looks really polished and professional but it crashes when I select level before gameplay. It says zoko on black background and freezes.
  15. Grid-based physics plugin

    If you just want to check it out there is a demo online here: http://metroid.niklasberg.se/gridPhysics/ Otherwise, there are instructions at the end of the README.md-file ("brunch watch --server" to watch files and launch the server). Note that you need to navigate to http://localhost:3333/demo/ (not http://localhost:3333). I have had an unexpectedly busy period with unrelated stuff and haven't had time to work on the plugin for a while. However, it's far from abandoned and I plan to pick up the development as soon as things calm down.