alanszlosek/voxeling

Creative mode WebGL voxel game. Runs in Chrome, with multiplayer functionality and very few dependencies

voxeling's Issues

Requesting help getting this set up

This looks awesome and the game works perfectly here, but when I use the instructions here to create my own server, only the css and pictures load. No voxels.

I reckon I need to do something like 'portforwarding node', but I'm not sure what. Which ports do I forward? I see 10005 in the code but non 9966. How could I change it to use a custom port (2077)? I have access to my router settings. Can someone point me in the right direction? What should I do at the vim config.js step? Thanks!

Relevant info: Windows 7 x64 using Windows commandline, latest appropriate version of node and npm

Crashes with high draw distances

New mesher is likely the culprit. Chrome crashes after a few minutes at a draw distance of 6.

Client Refactoring: User Interface

Move code dealing with inputHandler and left-side overlay DOM elements into a separate file.

Reflect camera pitch in head angle

Mainly as a nice touch for multiplayer

Buffer() is deprecated

DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

Commission new texture set so I can redistribute it

The textures used in the demo (testbdcraft) are free, but I'm not allowed to distribute them. This makes setup more complicated than it should be.

I want to commission an artist to create a unique set of textures with a permissive license.

Client Refactoring: Voxel Cursor

At the middle of the game screen is the "cursor". Basically just a very small dot that you point at a voxel to interact with it. If you're close enough to the voxel to interact, the voxel is outlined in red.

It's this highlight logic, starting with inputHandler.on('fire.down', function() { that should be refactored and encapsulated into a separate file. There are some tricky bits to refactor in that code, as there are globals, re-used arrays (to cut down on garbage collection), etc.

Player textures are broken

Likely broken by the refactoring of individual texture PNGs into one sprite

Configuration is confusing

Clarify what server, httpServer, websocketBindAddress and websocketBindPort are used for. Rename if necessary.

Cutouts are broken

Used to be able to see through gaps in leaves, and through glass blocks. Something recently broke that. I vaguely recall messing with alternative shaders so users with slow GPUs can disable haze, so maybe that had something to do with it.

Do we need to cache-bust gzipped chunks?

They're fetched via normal HTTP (not a websocket) from the node app, and it seems the browser is caching old versions. Newly created voxels aren't behaving as expected.

Texture tiling alignment off

Recently decided to try out a combined texture file to reduce number of texture binding calls during rendering. But it seems the floating point offset values are off, as the tiles don't match up seamlessly.

Client Refactoring: Pull out multiplayer position logic

Specifically, refactor client.on('players', function(others) { out of src/client.js into a file concerned with multiplayer stuff.

Sun texture is broken

Pretty sure I broke it when I moved to a texture atlas setup.

Ability to customize keybindings via UI

Choose more helpful name for shaders

Perhaps projectionViewPosition (which is meant to hint at the matrix math going on inside it) should simply be called nonScene to imply that it should be used to players as opposed to voxels. And projectionPosition might simply be called scene to imply it should be used to draw the scene/voxels, as opposed to players, the sun, etc. But first need to verify usage of those shaders.

Convert textures.png generation script to node

Currently it's PHP based (scripts/textures.php) because I had issues getting image generation to work from node. Maybe that situation has improved.

Limit concurrent chunk fetching requests

We load chunk voxel data via gzipped AJAX. But making 10+ AJAX calls at a time can make the browser stutter. Need to queue them up and only fire off N at a time.