Nimbatus - The Space Drone Constructor is probably going to suck a lot of my free time dry with the easy to use drone builder, lots of fun options to give it some AI along with fun combat.
The developer, Stray Fawn Studio, previously released the genetics survival game 'Niche' which also supports Linux. While I liked the idea, I wasn't a big fan of it overall. Then along comes Nimbatus on Kickstarter last year which made me love the developer. Taking inspiration from games like Faster Than Light, Reassembly, Kerbal Space Program and Besiege it was quite impressive. Especially so since they had a working Linux demo from the very beginning.
There's a new gameplay overview to feast your eyes on:
Direct Link
What you're able to make with it is truly ridiculous, I'm still learning and I honestly don't consider myself particularly smart when it comes to things like logic gates. Even so, I've managed to make some designs I personally find extremely fun. It has Steam Workshop support, so if you're not too good at the building side you can download others designs.
Win a key
For those who wish to bag themselves a key, we have three to give away. If you wish to win a copy I will make it easier this time! Simply let me know (clearly!) you want to win a key. Keys will be sent out Saturday around 7PM UTC.
Buy it now
For those not bothered about winning a key, you can find it on Humble Store and Steam.
Thanks :D
This game seemed to be pretty interesting to me, when it popped by chance on my steam storefront. Steam says it's similar to other games I've played. Well, I'm (not) surprised. It looks awesome, and well executed. I also love the way "Nimbatus" is pronounced in the video ^^
Unfortunately, there are so many hours in the day, and so many games to play. I'm sure this game would remain unplayed in my library for quite a while if I were to win the key, so it might be of better use to someone else. I certainly remember how difficult it was for me to acquire a game, as a kid ;)
So, I would not like to enter the giveaway :D
#!/usr/bin/python3
__
def clearly():
__print("I'd like to win a key")
__
def main():
__clearly()
__exit(0)
__
main()
Please use #!/usr/bin/env in your scripts ;)
There is no reason to use "env" as per this article. Admittedly, it might help with platform portability to use "env".
I run Linux with Python2 and Python3 installed. This makes it nice and clear which one is being used.
Wait is UTC American for GMT?
This game seemed to be pretty interesting to me, when it popped by chance on my steam storefront. Steam says it's similar to other games I've played. Well, I'm (not) surprised. It looks awesome, and well executed. I also love the way "Nimbatus" is pronounced in the video ^^
Unfortunately, there are so many hours in the day, and so many games to play. I'm sure this game would remain unplayed in my library for quite a while if I were to win the key, so it might be of better use to someone else. I certainly remember how difficult it was for me to acquire a game, as a kid ;)
So, I would not like to enter the giveaway :D
#!/usr/bin/python3
__
def clearly():
__print("I'd like to win a key")
__
def main():
__clearly()
__exit(0)
__
main()
Please use #!/usr/bin/env in your scripts ;)
There is no reason to use "env" as per this article. Admittedly, it might help with platform portability to use "env".
I run Linux with Python2 and Python3 installed. This makes it nice and clear which one is being used.
Yet I am afraid this answer isn't entirely accurate:
- What if I purposely modified my $PATH to use a different python executable? I might not have admin rights on this computer (or would like not to break other stuff, while using another python version
- Who really need to pass arguments to the interpreter? You didn't, for instance, and you can always call the interpreter directly
- likewise, you can always call the interpreter directly in a cron job, this would be more robust anyway
It is a bad idea to assume anything about an interpreter on a user's machine, and even though /usr/bin/env makes me uncomfortable for the same reason, it's often there ;)
You can also #!/usr/bin/env python3 ;)
See more from me