Primary tabs

Comments by User

Wednesday, September 6, 2017 - 11:03

Thanks for sharing all your beautiful work, true masterpieces.

Tuesday, September 5, 2017 - 20:17

I went over the paypal api docs and was bombarded with dependencies, prerequirements and stuff... one of those "oh this needs a new NET oh new NET needs a new OS oh new OS needs a new Computer" things..


So I may use the paypal html interface, by a form or even over the url. The "return" variable I can set to a path the payer will be redirected to after successful payment. This cannot be hidden totally, because it's in his browser, a fradulent person could call this url manually, making me think he has paid. There is ipv instant payment verification, an other paypal feature, seemingly harder to implement
...edit: IPN, not IPV:


So, what is missing imho in the paypal html interface, is an encryption option for the "return" url,  the seller gives paypal the key and he gives the payer the encrypted url, that the payer will send to paypal, so they can send the payer the plain text url after payment. This url however should contain further security features, such as encrypted timestamp, uniqueness etc. to make this a one time green light thing.


However, if in an assumed poker game the bank hast to pay cash to a player, it still can/must be verified, whether he really paid the entrance fee.

Great about html5 is also that you are already in a browser, btw...

Tuesday, September 5, 2017 - 19:36

works perfectly, thanks! tested local access and apache over localhost in opera, not expecting problems with other browsers.


does load the page, just like




In the file tho, a document.write(window.location.href);

shows the entire URL, including the parameter.

And now to process this string in js is easy.





Monday, September 4, 2017 - 20:05

That is a huge project, and great looking. Maybe on you Project page you should Add an Abstract or Quick-About and a Screenshots Section that gives a first Overview.

Wish you lotsa success with this project. Good engine choice.

Monday, September 4, 2017 - 16:34

Even tho, the e3 consortium warns, that the html5 support for the semsors orientation, accelleration and compass could be explemented (is that a word) or being dropped in future specs (due to privacy issues...:) .), you may want to consider to use them optipnally, if present and supported. Esp. Orientation can be used for steering.

That being said, you should provide choice and fallback controls for all devices, imho.

Monday, September 4, 2017 - 16:20

I'n new here, so maybe this is a silly question: is this realtime 3d rendered, or some fancy z-scaled 2d isometric engine? looks great btw.

Monday, September 4, 2017 - 15:59

While there are some conventions, from the old fps etc games, I would not neccessarily reuse them, because I tend to lean towards html5 games for mobiles, that allows them to run on any device, and I can even update it on the server without to bother the player with update notifications.


Now mobiles have like fullHD screen and 2d/3d gpu, totally satisfying, but they have no keyboard. So a game should offer both keyboard / Mouse as well as touchscreen support.  To keep this simple, I would suggest an "arcade hall device" standard, that may consist nothing more than a joystick and one to 3 buttons. The joystick can be emulated by mouse, WASD or arrow keys, onscreen virtual joystick for touchscreens, device orientation sensors in mobiles (that one I like)


By providing such a minimal set of "keys", porting to all platforms becomes easier. Basicly, it's the "what if there is no keyboard" scenario.

Monday, September 4, 2017 - 11:23


Monday, September 4, 2017 - 02:13

Nina, click the titles.


To the Artist: this is fantastic, tremendous production value, thanks a lot!