Readit NewsOne way to handle that is to provide all the possible tile variations, but that would take up so much space. So you'd have a set of tiles for a regular Ace of Spades, and an entirely different group of tiles for a Lucky Ace of Spades for example.
The GBA has 4 backgrounds, so it would be doable to grab three of them and use them to render cards. That would only leave 1 background left for, well, the background :)
Another option would be to use a memory buffer and implement tile rendering yourself that accounts for transparent pixels. That would be the best of backgrounds and sprites combined into one. That would solve many problems, at the cost of the implementation would probably take up a lot of space. My hunch is this would be the best approach.
This right here might be why I find this platform so interesting. It's very limited, and the limitations usually bump into each other and you often steel from Peter to pay Paul.
Oh and the post didn't mention debuffed cards (they have a red X drawn over them). That'd be yet another card layer to throw into this mix.
Trying to read between the lines here, if your objection is to half-pixels because they’re not precise enough for (good) physics, then I apologize for being unclear - I mean half-pixels, or quarter-pixels, or eighth-pixels, or whatever.
Another way of wording my comment is that I think it’s easier - especially for beginners - to think in terms of smaller units (represented as integers) than in terms of a new number format for representing fixed-size fractional parts of larger units. But the two concepts are ultimately the same.
To be fair, rereading the post I realize I did make it sound like you would only need this for positioning sprites. I'll see about rewording it.
Or maybe we're both talking about the same thing and you're taking a different approach. That is fair too.
Since this article is talking about more precisely positioning sprites in a 2D world, it could practically be a one-liner: "instead of tracking positions/velocities in pixels, track them in half pixels". Everything falls out of that intuition.
Some time back in an HN thread about programming languages I read a response in a thread about inference which said that a particular feature doesn't really save on typing. And it seemed ludicrous. Until I realised the author of the comment has seen the word "typing" (which everybody else in the thread is reading as "The thing you do with a keyboard") and they're interpreting it as "The thing the compiler does". And yeah, with that perspective of course inference isn't saving typing, all your variables still have types, we were just happy because we spent less time operating the keyboard to write a program. Their comment was not wrong and we weren't correcting them, we'd just understood things differently!
Edited to add, link: https://news.ycombinator.com/item?id=36593110
Why would you think you won? You didn't choose that one with the car and you aren't offered the opportunity to switch to the open one, only the closed one. The only interpretation which makes sense is that he always shows you a goat.
What's your website so I can take a look at the parsing?
It says last updated today because I really did update it today :)
anyway, cool project!
But a few websites set their updated date to the current date which was annoying, maybe to rank better in Google? And some people (including me) only mention the update time in the page text content.
I've used GPT to parse human formatted dates in another project too, it's quite reliable if you validate the output timestamp. And relatively cheap too if you only pass in the first part of the page text.
Oh, now aboutideasnow shows no date at all.
I find it really weird that they dismissed fixed point as being too technical because it's actually really simple, it's basically just this.