Stretch Goal 4 Pirates

In this stretch goal, we will be focusing on enhancing the pirate colonies by introducing a boolean feature to indicate whether a colony has security or not. This will add a new layer of complexity to the game, allowing players to make strategic decisions about their colonies' security. We will also be updating the purchase endpoint to randomly fail to add minerals to the colony if it does not have security, and deducting the balance from the colony if it does have security.

Introducing the Security Feature

The security feature will be a boolean value that indicates whether a colony has security or not. This will be represented by a simple true or false value in the database. We will be adding a new endpoint to update the security status of a colony, which will be discussed in more detail later.

Why Security Matters

Security is a crucial aspect of any colony, and it will play a significant role in the game. With security, a colony will be protected from random failures when purchasing minerals, and players will be able to focus on building and expanding their colonies without worrying about losing their resources. On the other hand, without security, colonies will be vulnerable to random failures, and players will need to be more cautious when managing their resources.

Updating the Purchase Endpoint

The purchase endpoint will be updated to randomly fail to add minerals to the colony if it does not have security. This will be achieved by introducing a random failure rate, which will be determined by a probability value. If the random failure rate is met, the purchase will fail, and the colony will not receive the minerals.

import random

def purchase(colony_id, minerals):
    # Check if the colony has security
    if not has_security(colony_id):
        # Randomly fail to add minerals
        if random.random() < 0.5:
            return False
    # Add minerals to the colony
    add_minerals(colony_id, minerals)
    return True

Deducting Balance for Secure Colonies

If a colony has security, the balance will be deducted from the colony when purchasing minerals. This will be achieved by introducing a new endpoint to deduct the balance from the colony.

def deduct_balance(colony_id, amount):
    # Check if the colony has security
    if has_security(colony_id):
        # Deduct balance from the colony
        deduct_amount_from_balance(colony_id, amount)

PUT Colonies/ID/Security Endpoint

The PUT colonies/id/security endpoint will be used to update the security status of a colony. This endpoint will take the colony ID and the new security status as input, and update the database accordingly.

def update_security(colony_id, security_status):
    # Update the security status in the database
    update_security_status_in_database(colony_id, security_status)

POST Purchase Endpoint

The POST purchase endpoint will be used to purchase minerals for a colony. This endpoint will take the colony ID and the amount of minerals to purchase as input, and update the database accordingly.

def purchase_minerals(colony_id, minerals):
    # Check if the colony has security
    if not has_security(colony_id):
        # Randomly fail to add
        if random.random() < 0.5:
            return False
    # Deduct balance from the colony
    deduct_balance(colony_id, minerals)
    # Add minerals to the colony
    add_minerals(colony_id, minerals)
    return True

GET Colonies/ID Endpoint

The GET colonies/id endpoint will be used to retrieve the details of a colony, including its security status. This endpoint will take the colony ID as input, and return the colony details in the response.

def get_colony_details(colony_id):
    # Retrieve the colony details from the database
    colony_details = retrieve_colony_details_from_database(colony_id)
    # Add the security status to the colony details
    colony_details['has_security'] = has_security(colony_id)
    return colony_details

Conclusion

In this Q&A article, we will be addressing some of the most frequently asked questions about the stretch goal 4, which introduces a boolean feature to indicate whether a colony has security or not. We will also be discussing the implications of this feature on the game and how it will enhance the player experience.

Q: What is the purpose of the security feature?

A: The security feature is designed to add a new layer of complexity to the game, allowing players to make strategic decisions about their colonies' security. With security, a colony will be protected from random failures when purchasing minerals, and players will be able to focus on building and expanding their colonies without worrying about losing their resources.

Q: How does the security feature affect the purchase endpoint?

A: The security feature affects the purchase endpoint by introducing a random failure rate. If a colony does not have security, there is a chance that the purchase will fail, and the colony will not receive the minerals. This adds an element of risk to the game, as players will need to weigh the benefits of purchasing minerals against the risk of failure.

Q: What happens if a colony has security and purchases minerals?

A: If a colony has security and purchases minerals, the balance will be deducted from the colony. This is a new feature that adds an additional layer of complexity to the game, as players will need to manage their resources carefully to ensure that they have enough balance to purchase minerals.

Q: How does the security feature affect the game balance?

A: The security feature adds a new layer of complexity to the game, which can affect the game balance. With security, players will be able to focus on building and expanding their colonies without worrying about losing their resources, which can give them a competitive advantage. However, the random failure rate can also make the game more challenging, as players will need to adapt to changing circumstances.

Q: Can I turn off the security feature?

A: Yes, the security feature can be turned off by setting a flag in the game settings. This will allow players to disable the security feature and play the game without it.

Q: How does the security feature affect the GET colonies/id endpoint?

A: The security feature adds a new field to the GET colonies/id endpoint, which returns the security status of the colony. This allows players to retrieve the security status of a colony and make informed decisions about their resources.

Q: Can I use the security feature in a custom game mode?

A: Yes, the security feature can be used in a custom game mode. The game mode can be designed to use the security feature in a specific way, such as by introducing additional challenges or rewards.

Q: How does the security feature affect the game's difficulty level?

A: The security feature can affect the game's difficulty level by introducing an element of risk and uncertainty. With security, players will need to adapt to changing circumstances and make strategic decisions about their resources, which can make the game more challenging.

Q: Can I use the security feature in a multiplayer game?

A: Yes, the security feature can be used in a multiplayer game. The game mode can be designed to use the security feature in a specific way, such as by introducing additional challenges or rewards.

Conclusion

In this Q&A article, we have addressed some of the most frequently asked questions about the stretch goal 4, which introduces a boolean feature to indicate whether a colony has security or not. We have also discussed the implications of this feature on the game and how it will enhance the player experience. The security feature adds a new layer of complexity to the game, which can affect the game balance and difficulty level. However, it also provides players with new opportunities to make strategic decisions and adapt to changing circumstances.