Live data from Hacker News

Show HN: RESTful Doom – HTTP+JSON API inside Doom

1amstudios.com

11–20 of 31 posts

Re: Show HN: RESTful Doom – HTTP+JSON API inside Doom

#11

Now to add Twitch integration.

Haha yes... although I would be slightly nervous to expose my janky C code to the internet. Where I'm confident it would crash and burn in a very short amount of time :)

Most certainly your machine will suddenly reboot to a newly installed arch ;)

Re: Show HN: RESTful Doom – HTTP+JSON API inside Doom

#13
post #11

Earlier quoted context omitted.

Haha yes... although I would be slightly nervous to expose my janky C code to the internet. Where I'm confident it would crash and burn in a very short amount of time :)

Most certainly your machine will suddenly reboot to a newly installed arch ;)

haha yes!

Re: Show HN: RESTful Doom – HTTP+JSON API inside Doom

#15

That's pretty cool! Well done. Now I'm wondering whether the game clock could be suspended unless ticks were sent via API, to turn it into a turn-based game to be played only via API calls...

I had an idea to write a text adventure interface, where you would type in 'forward', 'left', 'shoot' etc via the API. We understand nearby objects like doors, monsters and pickups, so could implement things like "An 'IMP' appears 300 yards away", or "There is a door requiring a red key in front of you" etc. Could be fun!

Re: Show HN: RESTful Doom – HTTP+JSON API inside Doom

#18

Now to add Twitch integration.

Haha yes... although I would be slightly nervous to expose my janky C code to the internet. Where I'm confident it would crash and burn in a very short amount of time :)

Use a proxy. Openresty (nginx+lua) or a Go app would do. Only allow whitelisted commands through like the basic control commands and then pass it on to your C code.

Re: Show HN: RESTful Doom – HTTP+JSON API inside Doom

#19

Earlier quoted context omitted.

Haha yes... although I would be slightly nervous to expose my janky C code to the internet. Where I'm confident it would crash and burn in a very short amount of time :)

Use a proxy. Openresty (nginx+lua) or a Go app would do. Only allow whitelisted commands through like the basic control commands and then pass it on to your C code.

yep, that would definitely be a good idea!
Post reply on HN