frading

> gta san andreas at 32mb ram

I forgot it was such a small budget, it's indeed important to keep in mind how much could be done with little memory. Although I'd argue it was possible with a language that allowed you to control memory very precisely. With javascript garbage collector, I couldn't stand seeing memory ramp up every frame due to threejs internals or my own js code, and every few frame a major GC may or may not lead to a frame drop.

> advanced reprojection for increasing FPS that takes into account the depth buffer

Ah got it. I completely forgot that webxr of course needs to create textures to see through, so it indeed needs to know which graphic api is used. Thank you for the links, I'll have to study them.

I know it's imgur.com, and it used to load fine from the UK. I was just making the point that we can all make mistakes and that common tools have edge cases we may not be aware of.

Apologies accepted. And thank you for mentioning the issue, it should now be fixed, so the website should load for you now.

Very happy to fix any issue with the website but your link only shows "Content not available in your region", so I propose you to be less pedantic about regions.

Less hate would be good too.

This is a recap of the reasons that led me to bite the bullet and rewrite an engine I used to sell and ship commercial projects.

I kept thinking about it, did some tests, and you convinced me. So the pawns movements are now changed. It works like that now:

- pawns move forward in their "track", just like a rook would do, just one tile at a time.

- if the track reaches the end of the board, the pawn can promote as usual.

- if the track ends on the left or right side of the board, when the pawn reaches it, it changes track. If there are multiple tracks it can take from there, the one that reaches the end in the least amount of moves is selected

- when a pawn captures, it changes track following the same rule.

And I agree now that using capture to change the zone of attack of a pawn is a very nice addition.

On top of that, if multiple pawn are constraint to turn sideways at first, it's not simply a handicap. It also helps strengthen the defense in that area, as you can have more efficient pawn walls.

In all all, it's great, thanks a lot for arguing in favor of this change.

> I won against the hard bot :)

Congrats! Although I wish it had given you an even harder time!

> Add a confirmation to the resign button!

Yes, you're right, it is much needed.

> Can you add a permalink to share the game with my friends so they can see the replay?

Yes, that would indeed be very useful. I'll see how I can make it work. And maybe there is a way to have it so that it works also for the iOS and steam versions.

> Permalikt to checkboard may be nice too.

Absolutely. That's on my list. (although bear in mind that the demo only has 2 different boards)

> I used a magical curved path of my far bishop to stop the atack. It was very surprising to be able to save the rock

Nice. Thanks a lot for sharing this one. Those are indeed the great reversal moments, I love those.

> When the bot is hopeless (like a rock and two knight down) it makes too many silly moves.

There are many factors that drive how the bot behaves. There clearly is room for improvement, although that will probably need a rewrite in wasm, and most likely need someone who has more experience at this than me. Although I could only hire someone if it makes financial sense. Something I keep thinking about.

And I'm still going through some of the feedback I received, so expect an update in the week or so.

oh that is interesting, I haven't thought about changing the appearance of the piece to convey more info. That's definitely something worth exploring.

And I agree as well that pawns changing track when they capture can be a fun one. It could even make you reconsider a capture if the pawn is on a good track and would end up on one that turns to the side.

I'm not promising I'll change the current behavior, but that does make me think.

I just fixed the castling bug. Thanks a lot for letting me know.

ah yes, that's a bit clearer now :) And I'm glad that I used to play starcraft before google decided to be involved.

> I tried the demo. The default player is too weak. It makes too many silly mistakes. The harder players is hard. I'll try again tomorrow.

Thank you for playing it. And that's great, that's more or less how I intended. I want players to start with a bit that isn't too intimidating, so that you can select a stronger one after if needed. And I'm glad that the stronger one gave you some challenge.

> The bishops that bounce against the walls when there is a corner with 3 squares in the border are weird

Currently, I define a diagonal as 2 tiles sharing a point and no edge. So by that definition, you will indeed see tiles on the edge which make up a diagonal. Definitely the type you can't see on a regular board. There could be an alternative definition where you need to have 2 other tiles that share edges with those first 2 tiles (as is the case almost everywhere inside the board), but I like to embrace the weirdness that this brings, so I keep the first one.

And yes, knights here are much harder to predict!