Part of the design philosophy of the tutorial is to not hide any gameplay mechanics from you... They typically force you into a situation where you see the behavior of the tile being introduced before you need to use that behavior in a straightforward way, then in a way that is a consequence of what you know, but that you haven't seen. That said, I guess I don't really have any problem with deep spoilers for the tutorial, since as you say the point is to teach the game and people have different learning styles. (In my case, I learn better when I had a hand in "figuring out" what someone is trying to teach me, which is the reason for that design.) Unfortunately right now I'm on vacation and can't post spoilers, cuz I don't remember how the end goes. :) |
| |
|
|
| |
Sure, please do! Thanks for asking :) |
| |
Hmm. The issue of big spoilers has been covered, previously. I don't want to spoil it for others who do not want it, so here's what I'll say: Describe what you've been trying as a spoiler comment for that tutorial, so we can see what is holding you up. Another mild hint: how are you going to get around that laser, and note that sometimes a bit of repetition is required to solve a level. |
| |
Doesn't help, I had that already. 90% of the time with this kind of thing the "spoiler" is not something I missed about the level but something I didn't know about the game, eg the ability to pull blocks as well as push them. So I am absolutely looking for maximum spoilers. It's just too bad your game is not popular enough to have YouTube videos of the answers, because without them I will not get to play any more. |
| |
You're a cool motherfucker. |
| |
Giving the solution itself would be too much of a spoiler, but a hint is that the transponder on the right above the rough an be pushed up and used. Hope that helps. |
| |
Will you please post the solution for the tutorial level 20 at escape.spacebar.org/f/a/escape/level/749?spoilers=1 ? There's no point allowing people to get stuck on the tutorial, since it's probably for lack of explaining the game rather than logic problems. |
| |
Hi Tom 7,
I would like to use part of one of your songs (Rutgers) in an intro for my 'chufflangs' YouTube channel. I'm happy to credit you as "Tom 7 Entertainment System" and link to mp3.tom7.org/t7es/ ! Let me know what you think. :) |
| |
Any idea where I might find the reference to localhost in the code? |
| |
Ah, my bad. It's been a while since I read your paper that goes along with it. A lot of it's still over my head (10th grade for you), but I now see the part where you mentioned that as a possibility. I'm not too worried about the lack of redundancy since it'll be in a lab. I'll probably be ready with my side of things to try it on Monday. I'll have to write a program to generate all the helper starter files automatically otherwise I'll be repeating it for ages. Thanks for all the help! |
| |
|
|
| |
Excellent, I'll give it a try. Hopefully I can get it to work with a proxy, because I was having a hard time compiling it. Good to know that my suspicions about how the program works were correct. I'll have to let you know how it goes. |
| |
Yes, I think that would work since it just uses TCP/IP to communicate. I've never tried it, though. I think that it's hard-coded to connect to localhost (127.0.0.1) so you would probably need to change the code to connect to a list of port/ip pairs rather than just ports, but I think that'd be straightforward. (Maybe you could just run proxies on the local machine that redirected the ports to other machines, and then you wouldn't need to recompile.) Other downsides would be: It currently aborts if any of the helpers die, which is reasonable on a single computer, but basically if any of the machines go off or can't connect, the whole computation would abort. Finally, the protocol it uses is totally insecure, so you'd want to make sure that others didn't have access to the open ports. |
| |
At my school, I have permission to use an entire computer lab full of nice computers as a server farm for rendering, and anything else I want. Is there any way to run playfun on a network to distribute the load? Total it's 64+ i5 cores and 128+ gigs of RAM. I'm not as good at coding as you are, and I think it would make for some really interesting possibilities. |
| |
The physician studies the pattern on the paper to see if the heart rhythm is normal |
| |
You need to run multiple copies of the program (one for each processor)-- these are helpers--and one main program to coordinate, which is the master. The README explains. |
| |
Sorry for dumb question, but I'm getting the numworking error, what is a helper? |
| |
Nice! Thanks for the update.
|
| |
I think so, maybe without an attractive image! Thanks for watching :) |
| |
Weird, I missed episode 2 entirely. Did you mention it on this here radar thingy and/or Twitter? Cuz it seems like I would have seen that. Scratching my head intensely right now, but happy to have these two new episodes to watch regardless! |
| |
Sure, if you can figure out how to run it and everything, then you can do some experiments and show off the results. It's open-source. It won't work for two-player simultaneous human vs compute play, though, as it needs to be able to emulate the game into the future. |
| |
I've just downloaded the binaries. This is a brilliant concept, and I'd like to make use of it. I'm something of an AI hobbyist and retro gamer. I'd rather like to use Playfun for a series of experiments pitting human players against it in games I find it good at, as well as a series of related events for a local convention.
Would this be alright with you? |
| |
Nice Video! What would be great is a in depth Tutorial on how to set this up and make it work for yourself. |
| |
I used to use Visual Studio on windows, probably VS 2001? I have been using mingw for newer stuff, though mostly 64 bit. It's probably not to challenging to get it working again, just not that fun. I was using Apple's compiler (gcc based, though maybe now it is llvm-based?) on OS X, which is the only game in town. The issue then was compiling for both PPC and Intel, which I thought I had figured out, but it seemed to fail for some people. These days I think everybody has an intel chip, so that might be moot. |
| |