dfdao / game Goto Github PK

Biomes are bad for a few reasons:

1. They make Dark Forest confusing to new players. Even I still don't fully understand what they do for all game entities -- this is because they impact planets and artifacts in very minor ways that aren't really meaningful.
2. They don't add depth to advanced gameplay. I'm okay with a feature compromising legibility if it creates dynamic, deep gameplay, but biomes just don't.
3. They bloat the codebase. I'd rather use Smart Contract and client space to have exciting stuff instead of biomes.

Confusing to have two libraries for artifacts

@phated do you use the TransferSingle event in client? seems like we'll need it but I don't see it currently being used.

#10

On Initial Spawn into the game:

After Refresh:

When first loading a new game, Spaceships are marked as red / unowned and can't be moved in the UI. After refresh, ships are white and can be selected and moved.

This is not a GameManager problem, because I can df.move() the spaceship even when it's marked as red.

Currently there is no getter for the tokenId of silver. This is an issue for a third party trying to make their own client for the game.

We can make a getter, or we can hardcode the tokenId of silver to 1, or we can make mintSilver, burnSilver, etc functions.

We need to remove the score attribute in the player struct. There is no way to transfer score but you can transfer silver tokens, which is confusing for players.

Instead we should allow the admin to choose if they want to make silver transferable and make the win condition based on the number of silver tokens they have at the end of the round.