Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fix] Butletron / Бутлетрон #105

Merged
merged 1 commit into from
Oct 31, 2024
Merged

[Fix] Butletron / Бутлетрон #105

merged 1 commit into from
Oct 31, 2024

Conversation

Spatison
Copy link
Member

Описание PR

Уменьшена колизия у Бутлетрона


Изменения

🆑 Spatison

  • fix: Сorrection of a Butlutron collision / Исправлена коллизия Бутлетрона

@Spatison Spatison requested a review from Remuchi October 27, 2024 13:09
@Spatison Spatison self-assigned this Oct 27, 2024
Copy link
Contributor

coderabbitai bot commented Oct 27, 2024

Walkthrough

The changes involve the addition of a new Fixtures component to the Roboisseur entity in the roboisseur.yml file. This component includes a fixture named fix1, which has specific physical properties, including a defined shape, bounds, density, and associated layers. No other components or properties of the Roboisseur entity were modified.

Changes

File Path Change Summary
Resources/Prototypes/DeltaV/NPC/roboisseur.yml Added a new Fixtures component to the Roboisseur entity, including a fixture named fix1 with defined properties.

Suggested labels

Changes: YML, Status: Needs Review

Suggested reviewers

  • Remuchi

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.

Copy link
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: 0

🧹 Outside diff range and nitpick comments (1)
Resources/Prototypes/DeltaV/NPC/roboisseur.yml (1)

44-44: Add newline at end of file.

Add a newline character at the end of the file to comply with YAML best practices.

   # WD EDIT END
+
🧰 Tools
🪛 yamllint

[error] 44-44: no new line character at the end of file

(new-line-at-end-of-file)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8091fce and defbd3a.

📒 Files selected for processing (1)
  • Resources/Prototypes/DeltaV/NPC/roboisseur.yml (1 hunks)
🧰 Additional context used
🪛 yamllint
Resources/Prototypes/DeltaV/NPC/roboisseur.yml

[error] 44-44: no new line character at the end of file

(new-line-at-end-of-file)

🔇 Additional comments (1)
Resources/Prototypes/DeltaV/NPC/roboisseur.yml (1)

31-43: Verify collision box size and density values.

The addition of the Fixtures component is a good solution for fixing collision issues. However, please verify:

  1. Is the collision box size (0.3x0.3 units) sufficient to cover the entire sprite?
  2. Is the density value of 60 appropriate for this type of structure?

Let's check other similar entities for comparison:

✅ Verification successful

Based on the extensive search results showing fixtures configurations across the codebase, I can now make an informed assessment about the collision box size and density values for the Butletron character.

Collision box and density values are appropriate for this type of entity

The current configuration:

  • Box size: 0.3x0.3 units (-0.15 to 0.15 in both dimensions)
  • Density: 60
  • Mask: MachineMask
  • Layer: MidImpassable, LowImpassable

This aligns well with similar entities in the codebase:

  1. Most stationary machines use box sizes between 0.25-0.45 units
  2. The density value of 60 matches the base_structure.yml template which many machines inherit
  3. The MachineMask and MidImpassable/LowImpassable layers are standard for machine-type entities

The values are particularly consistent with:

  • Other NPCs/robots with similar roles (density 50-80)
  • Stationary service machines (box size 0.25-0.35)
  • Base structure template (density 60)
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for other entities with Fixtures components to compare values
rg -U "type: Fixtures" -A 10 "Resources/Prototypes"

Length of output: 408145

@Remuchi Remuchi merged commit fc16941 into master Oct 31, 2024
12 checks passed
@Remuchi Remuchi deleted the butletron-fix branch October 31, 2024 03:22
VMSolidus added a commit to Simple-Station/Einstein-Engines that referenced this pull request Nov 13, 2024
# Description

Fixes Butlertron's hitbox. Thanks to
WWhiteDreamProject/wwdpublic#105

# Changelog

:cl:
- fix: Butlertron is no longer as wide as a barn.

---------

Co-authored-by: Spatison <[email protected]>
Spatison added a commit that referenced this pull request Nov 19, 2024
Spatison pushed a commit that referenced this pull request Nov 19, 2024
# Description

Fixes Butlertron's hitbox. Thanks to
#105

# Changelog

:cl:
- fix: Butlertron is no longer as wide as a barn.

---------

Co-authored-by: Spatison <[email protected]>
(cherry picked from commit c90972449df39f808c3d5088613e62c87d4df74d)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants