158 karma · joined February 27, 2014
Mastodon: https://mastodon.gamedev.place/@springogeek Twitter (Read-Only): @avivbeeri Github: http://www.github.com/avivbeeri Games: http://avivbeeri.itch.io
Maybe rather than directly attacking the boss, damage boosts can get stacked up for other players to use? Or maybe "shields", which reduce the cooldown / timeout.
Is there a way to get notified about future versions/updates?
Part of the article talks about how testing and confirmation of a COVID diagnosis was a requirement here, which helps narrow down the study.
It's like Love2D, but for Wren instead of Lua.
I started it fairly recently (linking it here will probably cause the server to melt) Just my space to talk about whatever I'm thinking/working on.
Currently it's focused on Fang, the programming language I'm designing/developing.
Mature doesn't mean it's static.
It was originally conceived to have a much less heavy-handed scope though, but has been strengthened over time to something near-impossible to thwart.
The system works, assuming it's adequately funded, which it hasn't been for a while. Salaries aren't high enough to live on (thanks to the conservative government and creeping privatisation), and then brexit and other immigration policies have caused a shortage of trained professionals and no one willing to fill the vacancies.
There's a whole heap of issues (I've left out quite a few) stacked up against the NHS, and yet it powers on, doing its best.
The main thing is knowing that if you need any procedures, services, an ambulance, critical or emergency care, etc, you'll not be asked up front to pay for it, you'll just be treated. Seeing that principle erode over time is heartbreaking and terrifying.
(rant) Healthcare as an industry doesn't function properly under a capitalist model, which expects that competition and consumer choice will encourage innovation and further competition, leading to a better outcome for the consumer. If you need healthcare, you don't really have a choice in it, or your choices are artificially restricted by circumstance, so you can't benefit from a competitive marketplace. It's a broken system, as far as I am concerned.
* A design which can be generalised is inherently more complicated, and is often unnecessary (you probably won't make use of that generality, leaving you the burden of maintaining it), so you'll be glad you made a simpler first pass.
* I don't like working with docker/containers personally. It makes me feel so far removed from how services are deployed that it's basically magic.
I use Badwolf as the primary browser, which comes with built in toggles for disabling images and JS loading, and that makes web browsing tolerable most of the time. I've even managed to stream from it to Twitch using ffmpeg without much of a problem!
Sometimes I treat myself to a nice meal. Reduced responsibilities for the day, just to make it light and fun.
It's a good excuse to arrange a get-together of some kind. A full table for some board games :)
Pitch: You play as either: an elite hacker trying to break into the servers of megacorporations for fun and profit, or the inner workings of said megacorporation, trying to defend against the hacker.
The game requires you to take risks because it's a game about information control. You don't know what the corp will do to defend itself until you make a run at their servers, and corps don't know exactly how the runner plans to get in, or what they'll find when they do.
"'done' is better than perfect"
It's easy to get caught in a trap of trying to "perfect" something. If it's good enough to call done, you can always improve it later if necessary. You do need to have some clear definitions for what "done" means for you though.
"make it work, make it pretty, make it fast"
This is adjacent to the first saying. I sometimes find myself trying to optimise something prematurely. This is a good reminder to wait until the [unit of work] is "complete" before I try to optimise it.
Eventually I wanted to make larger projects, so I was inspired to make my own engine, for when you want to transcend its limitations.
Because of its minimal nature, you can kind of scope up gradually, to whatever kind of project and scale you like.
Lovingly documented and well maintained :)
Make sure each document/page has a clear audience, and it's clear to the reader what that audience is, as well as where other audiences should go.
I've been working on a reasonably large (and cross platform) project in C (https://domeengine.com) for a couple years now, and I find that C generally requires a certain kind of discipline. When you interact with an API, you need to read the docs, figure out their specific preconditions, and requirements on handling frees, establishing what you own and what you don't.
It also helps to make sure that if you allocate something, you clean up after in a clear and well defined way.
You should also get very familiar with debuggers (LLDB/GDB) and other dev tools, to help when you have made a mistake.
In the modern era, you have a couple of options for getting it to run on Windows. C89 using Visual Studio, The MSYS2/MinGW2 gcc toolchain, or a gcc toolchain using the WSL. I use the MSYS2 tools for DOME because it requires the fewest platform-specific modifications to my code, but this varies by usecase.
It was featured on HN last weekend: https://news.ycombinator.com/item?id=22200739
We've even got a game jam and discord server set up now :)