Block-breaking game in vim 8.0

Related, a self destroying game I built some time ago: https://void4.github.io/ The yellow dot is the instruction pointer, the red dots represent the program memory. If you hit the ball just right you can introduce graphic glitches. Most times, the instruction pointer gets out of bounds however.

Re: Block-breaking game in vim 8.0

#5

Post by johngrib » Tue, Jul 04, 2017, 4:47 AM UTC

mahmoudhossam wrote: post #2

Does this work with Neovim or vim only?

Maybe vim 8.0 only. I did not tested in Neovim.

Re: Block-breaking game in vim 8.0

#6

Post by davidbanham » Tue, Jul 04, 2017, 5:23 AM UTC

figgis wrote: post #3

mahmoudhossam wrote: post #2

Does this work with Neovim or vim only?

If it works in vim it should work in neovim?

It doesn't work in my neovim, sadly.

Lots of errors. Most common seems to be:

E117: Unknown function: funcref

And similar.

Re: Block-breaking game in vim 8.0

#7

Post by asdfpoiuqwer » Tue, Jul 04, 2017, 5:32 AM UTC

mahmoudhossam wrote: post #2

Does this work with Neovim or vim only?

Works for me; nvim v0.2.0

Re: Block-breaking game in vim 8.0

#8

Post by bitwize » Tue, Jul 04, 2017, 5:32 AM UTC

7373737373 wrote: post #4

Related, a self destroying game I built some time ago: https://void4.github.io/ The yellow dot is the instruction pointer, the red dots represent the program memory. If you hit the ball just right you can introduce graphic glitches. Most times, the instruction pointer gets out of bounds however.

That's kinna like the story about the guys who coded a Tron lightcycle game on the Apple II. Failure to properly bounds-check the lightcycle position meant that the cycles could be driven off screen, corrupting main memory and the game code itself -- much like what happened in the move Tron.

Re: Block-breaking game in vim 8.0

#9

Post by colejohnson66 » Tue, Jul 04, 2017, 6:17 AM UTC

bitwize wrote: post #8

7373737373 wrote: post #4

Related, a self destroying game I built some time ago: https://void4.github.io/ The yellow dot is the instruction pointer, the red dots represent the program memory. If you hit the ball just right you can introduce graphic glitches. Most times, the instruction pointer gets out of bounds however.

That's kinna like the story about the guys who coded a Tron lightcycle game on the Apple II. Failure to properly bounds-check the lightcycle position meant that the cycles could be driven off screen, corrupting main memory and the game code itself -- much like what happened in the move Tron .

Story: http://blog.danielwellman.com/2008/10/real-life-tron-on-an-a...

Re: Block-breaking game in vim 8.0

#10

Post by 7373737373 » Tue, Jul 04, 2017, 6:39 AM UTC

colejohnson66 wrote: post #9

bitwize wrote: post #8

Earlier quoted context omitted.

That's kinna like the story about the guys who coded a Tron lightcycle game on the Apple II. Failure to properly bounds-check the lightcycle position meant that the cycles could be driven off screen, corrupting main memory and the game code itself -- much like what happened in the move Tron .

Story: http://blog.danielwellman.com/2008/10/real-life-tron-on-an-a...

One of the most brilliant applications of this concept is the Pokémon Yellow Total Control Hack: http://aurellem.org/vba-clojure/html/total-control.html

Similarly, arbitrary code execution in Super Mario World: https://www.youtube.com/watch?v=OPcV9uIY5i4

It's like transforming a chess game into Mikado just by playing it.