Porting my JavaScript game engine to C for no reason
phoboslab.org
Porting my JavaScript game engine to C for no reason
1–10 of 139 posts
Re: Porting my JavaScript game engine to C for no reason
#2Re: Porting my JavaScript game engine to C for no reason
#3Cross Code is an excellent game. I knew that it used web tech and I was constantly amazed by how performant it was on the Nintendo Switch hardware. I would guess that this engine deserves some credit there!
Re: Porting my JavaScript game engine to C for no reason
#4Out of respect for your player's battery life, perhaps :)
Re: Porting my JavaScript game engine to C for no reason
#5Re: Porting my JavaScript game engine to C for no reason
#6Re: Porting my JavaScript game engine to C for no reason
#7Re: Porting my JavaScript game engine to C for no reason
#8Re: Porting my JavaScript game engine to C for no reason
#9j/k :D
Re: Porting my JavaScript game engine to C for no reason
#10> Many Web games were created with Impact [the game engine from the article] and it even served as the basis for some commercial cross-platform titles like Cross Code, Eliot Quest and my own Nintendo Wii-U game XType Plus. Cross Code is an excellent game. I knew that it used web tech and I was constantly amazed by how performant it was on the Nintendo Switch hardware. I would guess that this engine deserves some cred…
Imho, that's fantastic! I love to see devs being able to adapt the engine for their particular game. Likewise, high_impact shouldn't be seen as a “feature-complete” game engine, but rather as a convenient starting point.