⚖️ [Artifact 1045] ブラックホール・ミニの弾が一定時間経過後に強制的に起動するように #1057
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
haiiro2gou
reviewed
Mar 6, 2025
Comment on lines
20
to
22
| data modify storage asset:object Field.Speed set value 1 | ||
| data modify storage asset:object Field.Range set value 50 | ||
| data modify storage asset:object Field.MovePerStep set value 0.6 |
There was a problem hiding this comment.
Q: 前より速度も射程も小さくなってるけど大丈夫なの？
There was a problem hiding this comment.
射程は短くなってるので直す 弾速は...どれくらいなのこれ？
There was a problem hiding this comment.
弾速は...どれくらいなのこれ？
もともとは 0.75m/t を lib:motion/ で付与していた
バニラの仕様で速度減衰みたいなのがなければそれで一定のはず
There was a problem hiding this comment.
Range100のMovePerStep0.75かな
There was a problem hiding this comment.
Range100のMovePerStep0.75かな
そこまで MovePerStep が大きいとすり抜けまくりそう
|
わざわざ別 Object にせんでもなー、という気持ちにはなった |
|
haiiro2gou
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #682