Skip to content

feat: Emit death when dying#40

Merged
Thomlam merged 1 commit intodevelopfrom
feature/damage_and_death
Oct 28, 2024
Merged

feat: Emit death when dying#40
Thomlam merged 1 commit intodevelopfrom
feature/damage_and_death

Conversation

@AyakorK
Copy link
Copy Markdown
Contributor

@AyakorK AyakorK commented Oct 28, 2024

Summary by CodeRabbit

  • Nouvelles fonctionnalités

    • Événement de socket mis à jour pour indiquer la mort du joueur.
    • Appel de l'émetteur de socket lors de la mort du joueur pour améliorer la communication des événements.
  • Améliorations

    • Amélioration de la lisibilité du code grâce à la suppression de lignes vides inutiles.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Oct 28, 2024

Walkthrough

Les modifications apportées concernent principalement la classe PlayerHealth dans le fichier Assets/Scripts/UI/PlayerHealth.cs. Les changements incluent la suppression de lignes vides inutiles pour améliorer la lisibilité du code. L'événement émis par la méthode SocketEmitter a été modifié de "rooms:end" à "rooms:death", indiquant un changement dans l'événement communiqué via le socket. De plus, la méthode Die appelle désormais SocketEmitter() lorsque le joueur meurt, sans altérer la logique de gestion de la santé ou de transition entre scènes.

Changes

Fichier Changements résumés
Assets/Scripts/UI/PlayerHealth.cs - Suppression de lignes vides.
- Changement de l'événement dans SocketEmitter de "rooms:end" à "rooms:death".
- Ajout d'un appel à SocketEmitter() dans la méthode Die.
- Mise à jour des signatures des méthodes SocketEmitter() et ReturnToMenu().

Possibly related PRs

  • feat: add death system #30 : Les modifications dans le PR principal concernant la classe PlayerHealth, en particulier la méthode Die et la fonction SocketEmitter, sont directement liées aux modifications apportées dans le PR "feat: add death system", qui implique probablement une logique similaire pour gérer la mort du joueur et la communication par socket.

🐰 Dans les champs, je danse et je joue,
Un code plus clair, oh quelle belle voie !
Quand la santé s'éteint, un cri de mort,
"rooms:death" s'éveille, un nouvel effort.
Avec des appels de socket, tout est en place,
La vie d'un lapin, dans le code, s'embrasse ! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@Thomlam Thomlam merged commit c61b7a2 into develop Oct 28, 2024
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Outside diff range and nitpick comments (2)
Assets/Scripts/UI/PlayerHealth.cs (2)

12-16: Suggestion d'amélioration pour les variables publiques

Considérez l'utilisation de l'attribut [SerializeField] au lieu de variables publiques pour une meilleure encapsulation, tout en conservant l'accès via l'inspecteur Unity.

-    public GameObject heartPrefab;
-    public Transform healthBar;
+    [SerializeField] private GameObject heartPrefab;
+    [SerializeField] private Transform healthBar;

Line range hint 97-102: Amélioration possible de la transition

Considérez l'ajout d'une transition en fondu pour améliorer l'expérience utilisateur lors du retour au menu.

Souhaitez-vous que je propose une implémentation de transition en fondu ?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between d343820 and 1e234c7.

📒 Files selected for processing (1)
  • Assets/Scripts/UI/PlayerHealth.cs (3 hunks)

Comment on lines +74 to +81

foreach (GameObject heart in hearts)
{
Destroy(heart);
}
hearts.Clear();


Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Optimisation possible avec l'Object Pooling

La création et destruction répétée des cœurs pourrait être optimisée en utilisant l'Object Pooling, une pratique recommandée dans Unity pour les objets fréquemment instanciés/détruits.

Je peux vous aider à implémenter un système d'Object Pooling si vous le souhaitez.

Comment on lines +56 to 59
async void SocketEmitter()
{
await clientSocket.EmitAsync("rooms:end");
await clientSocket.EmitAsync("rooms:death");
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Ajout nécessaire de la gestion des erreurs

L'émission de socket devrait inclure une gestion des erreurs pour éviter les problèmes de connexion silencieux.

     async void SocketEmitter()
     {
-        await clientSocket.EmitAsync("rooms:death");
+        try {
+            await clientSocket.EmitAsync("rooms:death");
+        } catch (System.Exception e) {
+            Debug.LogError($"Erreur lors de l'émission de l'événement death: {e.Message}");
+        }
     }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
async void SocketEmitter()
{
await clientSocket.EmitAsync("rooms:end");
await clientSocket.EmitAsync("rooms:death");
}
async void SocketEmitter()
{
try {
await clientSocket.EmitAsync("rooms:death");
} catch (System.Exception e) {
Debug.LogError($"Erreur lors de l'émission de l'événement death: {e.Message}");
}
}

Comment on lines 62 to +70
{

if (deadCanvas != null && !deadCanvas.activeSelf)
{
SocketEmitter();
deadCanvas.SetActive(true);
}
GetComponent<PlayerMovement>().enabled = false;
}
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Vérification nécessaire de clientSocket

Il faut vérifier que clientSocket n'est pas null avant d'appeler SocketEmitter pour éviter une NullReferenceException.

     void Die()
     {
         if (deadCanvas != null && !deadCanvas.activeSelf)
         {
-            SocketEmitter();
+            if (clientSocket != null)
+                SocketEmitter();
+            else
+                Debug.LogWarning("Socket client non initialisé");
             deadCanvas.SetActive(true);
         }
         GetComponent<PlayerMovement>().enabled = false;
     }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
{
if (deadCanvas != null && !deadCanvas.activeSelf)
{
SocketEmitter();
deadCanvas.SetActive(true);
}
GetComponent<PlayerMovement>().enabled = false;
}
}
{
if (deadCanvas != null && !deadCanvas.activeSelf)
{
if (clientSocket != null)
SocketEmitter();
else
Debug.LogWarning("Socket client non initialisé");
deadCanvas.SetActive(true);
}
GetComponent<PlayerMovement>().enabled = false;
}

@AyakorK AyakorK deleted the feature/damage_and_death branch October 29, 2024 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants