Tonight at 21H55 Paris hours ! 😀
It’s the final #CountdownToMars! Watch mission control live as @NASAPersevere lands.
ETA 12:55pm PT (3:55pm ET, 20:55 GMT)
Live: http://go.nasa.gov/mars2020watchonline
360: http://youtu.be/GIooAx_GkJs
Español: http://periscope.tv/NASA_es
Toolkit: http://go.nasa.gov/mars2020toolkit
Framagit updated
Github should follow
Online Documentation is up to date
STACK type is still WIP hence it’s not documented. The entry in module is a placeholder for now
May 2021 be better than 2020
And here is my entry: a space shooter !
RazorCrest (click here to download)
Task (for NunoMartinez):
Finally, here it is my wishlist:
* Fast game. I mean that you can play a complete “play” in few minutes.
* Minimalistic graphics. Don’t make them complex.
* Finally, select one of your own wishes.
How I achieved the rules:
How to play:
-up to start moving
-arrows to move the ship
=> more XP = quicker
-use the mouse to aim and use mouse button or key CTRL to fire
=> more XP = more and better bullets, better accuracy
-green monsters are light enemies that are just traveling here
-yellow monsters are aggressives enemies that are targeting you
-red monsters are very aggressives enemies that are targeting you, and they are more solid
-the more you kill the more power you have to kill
-hitting the walls or being hit by an enemy makes you loose life and XP (thus fire power)
Screenshots:
Building from source:
-Go with a shell into to SRC/KRAMPUSHACK2020
-Type make
-If it works move the binary to ../..
-If it’s not working, come and complain here :-p
Hint for finishing
-Because the ship can speed up does not mean you should use it all the time
-Kill as much as you can on first levels so you have the firepower for next levels
-Use thrust/slow down/side jumps to avoid enemies while shooting at them
Hoooo yeah !
Rules: https://tins.amarillion.org/krampu20/rules/
To join: go to https://tins.amarillion.org/, register and log in. Then click “Join a competition”.
The game jam is very free and open, there are almost no hard rules. The main point is just to have fun and do something together during the holidays. Below are the rules as I posted them on the site, as you can see they are not very strict. I could still make some modifications in the coming week – so let me know your comments, if there is anything you’re unhappy with.
1. goal: Create a game as a gift for your secret santa.
On Sunday 13 December 2020, you will be assigned one of the other participants and you have to make your game as a gift for them. Each should post a wishlist of features that they would like to see in the game. But this wishlist is not a requirement list – you should tune the game to your giftee, taking the wishlist as well as the person itself into account, and create something that is a nice and thoughtful surprise to them.
2. progress log: Keep an interesting progress record here on the tins website. This progress record is very important, as it will be voted on, and used for determining the winner. During krampushack, your secret santa’s logs will be hidden from you to maintain the surprise a little bit longer.
3. Deadline: Thursday 31 December 2020. End time is midnight in your own time zone. I’m not going to be very strict about time, a few hours off is fine.
4. Dropping out: As is common with game jams, there is always a risk that some people will drop out. Life interferes, you ate a little too much Turkey, or you got that cool new PS5 for X-mas and lost all motivation to do anything else. We won’t be mad. To limit the impact, please let us know as soon as possible, so that we can notify your secret santa.
If your future giftee is dropping out, then you will be notified, your gift will go to the next person in the chain (your giftee’s giftee). You then get the choice of using the original wishlist, the new wishlist, or a clever mix of the two. You’ll have to see what is achievable based on the remaining time. Remember, the wishlists are for fun and inspiration, you won’t be judged on adherence to them.
5. size: There is no size restriction, but for convenience sake I recommend keeping it under 5Mb (zipped). The upload system may have trouble handling larger files. If your entry ends up too large, you have to upload it in your own webspace and send around a link.
6. source: We encourage submission of the complete source code with your entry but this is not compulsory. Of course you don’t have to include the source to Allegro or other publicly available libraries or frameworks
7. Code re-use: You may re-use any code and assets that you are legally allowed to do so: public domain, your own, etc. You do not have to start from scratch, you are allowed to do prep work before, or even re-use an existing game.
8. Allegro & other libs: You are encouraged to use allegro, but this is not compulsory.
Stumbled upon them when having a walk in the campaign.
On the first photo you can see the back of en European Hornet for comparison.
Pretty interesting and a bit scary. Could not approach them much because they were a bit on nerves
In addition to that subject Here is a portable macro that can be used in place of TEMP_FAILURE_ENTRY, without GNU_SOURCE (took from stackoverflow):
#define CALL_RETRY(retvar, expression) do { \
retvar = (expression); \
} while (retvar == -1 && errno == EINTR);/* call example */
SOCKET s ;
char buf[ 4096 ] = "" ;
int retval = -1 ;
/* ... stripped socket initialisation code ... */
CALL_RETRY( br , recv( s , buf , 1024, 0 ) );
In case you receive a “interrupted system calls” signal, there is a chance that this trick may help / guide you to the answer.
#gdb #socket #linux #redhat #EINTR #recv #send
