danwdart/vinski2

Long awaited sequel of the original Vinski

Vinski II

Long awaited sequel of the original Vinski, announced 10 years ago. Aimed to have a Lovecraftian feel a la Quake and Oblivion

Features

• Mouse, keyboard and PS3 controller controllable
• Renders and rotates objects
• HUD (currently static)
• Runs on modern browsers

Intentions

• Play as and fight all of the original monsters, and more!
• More controllers
• Better HUD
• Proper collision detection
• Crazy physics
• Unexpected loopholes
• Chaos Magic
• Interactive objects
• Desktop, phone and tablet installable
• Multiplayer nonsense
• Directional audio
• Proper sound speeds
• Procedurally generated terrains
• Game saves
• Confusion of other players
• Portals
• Ninjas
• Lasers
• Shouts
• Singing Trees
• To be a learning project for me as I've always wanted to make an FPS
• For it not to become the Duke Nukem Forever of Vinski

Playing the game

Go to the github pages page: https://vinski2.dandart.co.uk/ (warning: high loading times)

or clone the repository and open index.html in your browser.

Screenshots

Warnings

There's not much about yet, I'm just making more models and scenes at the moment. Things could be refactored and improved vastly.

Contributing

Please make a pull request with anything you think might be cool!

vinski2's Issues

get those shadows working

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Get more models

Streaming videos of gameplay via HTML5?

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

LibreJS

Get more ideas for game