(Java Minecraft 1.14.2) How to have recursive raycasting function determine if it has passed through an entity?Can Skeleton Killed Creepers Be AutospawnedAt what distance (from the player) do iron golems spawn in villages?kill @p causes kill @eMob grinder does not spawn more than 63 mobsNot able to link portals properlyMinecraft - Run commands as a dead player(Java Minecraft 1.13) How to get a fireball to shoot in the same direction as the summoning player is looking?(Java Minecraft 1.14) How to detect multiple item entities which are stacks of the same size on a particular block?(Java Minecraft 1.14.2) How to make a charged creeper do more damage without increasing explosion radius or summoning multiple?(Java Minecraft 1.14.2) How to recursively (or otherwise) determine if a closed 2D arbitrarily sized rectangle of blocks has been placed?
Is it advisable to add a location heads-up when a scene changes in a novel?
Do SFDX commands count toward limits?
How can you estimate a spike story?
That's not my X, its Y is too Z
What's the best way to quit a job mostly because of money?
DateTime.addMonths skips a month (from feb to mar)
What is Gilligan's full Name?
What does "lit." mean in boiling point or melting point specification?
Why did the World Bank set the global poverty line at $1.90?
Are the guests in Westworld forbidden to tell the hosts that they are robots?
Placement of positioning lights on A320 winglets
How to change the headfont of newtheorem environments to match komascript font?
In American Politics, why is the Justice Department under the President?
What would the consequences be of a high number of solar systems being within close proximity to one another?
If absolute velocity does not exist, how can we say a rocket accelerates in empty space?
What exactly "triggers an additional time" in the interaction between Afterlife and Teysa Karlov?
Grandpa has another non math question
How to represent jealousy in a cute way?
Is there a better way to do partial sums of array items in JavaScript?
Why does there seem to be an extreme lack of public trashcans in Taiwan?
Can you open the door or die?
Why are ambiguous grammars bad?
ASCII Meme Arrow Generator
Playing a trill with grace note ending
(Java Minecraft 1.14.2) How to have recursive raycasting function determine if it has passed through an entity?
Can Skeleton Killed Creepers Be AutospawnedAt what distance (from the player) do iron golems spawn in villages?kill @p causes kill @eMob grinder does not spawn more than 63 mobsNot able to link portals properlyMinecraft - Run commands as a dead player(Java Minecraft 1.13) How to get a fireball to shoot in the same direction as the summoning player is looking?(Java Minecraft 1.14) How to detect multiple item entities which are stacks of the same size on a particular block?(Java Minecraft 1.14.2) How to make a charged creeper do more damage without increasing explosion radius or summoning multiple?(Java Minecraft 1.14.2) How to recursively (or otherwise) determine if a closed 2D arbitrarily sized rectangle of blocks has been placed?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am writing a datapack with an item which functions like a sniper rifle - you can shoot it and a particle beam created by a recursive raycasting function will shoot out and any entities it encounters should die. However, entity detection is a big problem, because I can shoot right through a creeper's head and it doesn't die. You can download the datapack here if you want to test it out. Use /function rituals:give/sniper_rifle
to get the item.
I noticed that this is true for almost every mob in the game greater than an endermite or silverfish: if you shoot it through the feet, it dies, but anywhere above that or else than that, it doesn't. Pigs, cows, zombies, evokers, drowned, wither skeletons, anything, only die when shot through the feet. I don't intend for it to kill bosses so they are not a problem, luckily.
I've been detecting mobs by having every iteration of the recursive function run kill @e[distance=..0.1]
, and it moves ahead by 0.25 blocks each iteration. I have tried to get around this difference in @e
detection, mob hitboxes, and visible mob sizes (which for some reason are all different) by using scoreboards to give every mob a value equal to their approximate height, and then changing the distance based on what type of mob it is: kill @e[scores=mobHeights=2,distance=..2]
, but that is at best buggy and at worst making it so you can shoot next to a mob and kill it.
As you can see in this image, the cursor is well over the pig, yet it insta-dies because of this imprecision.
If anyone knows a better way to detect mobs a raycasting function is moving through that would be great, because right now it is really frustrating to have to try to manually implement a fix which is really imprecise. Also, if anyone knows why the function only recognizes entities by their feet, that would also help a lot. I know that coordinates are also calculated at an entities feet, so maybe that has something to do with it.
minecraft minecraft-commands
add a comment |
I am writing a datapack with an item which functions like a sniper rifle - you can shoot it and a particle beam created by a recursive raycasting function will shoot out and any entities it encounters should die. However, entity detection is a big problem, because I can shoot right through a creeper's head and it doesn't die. You can download the datapack here if you want to test it out. Use /function rituals:give/sniper_rifle
to get the item.
I noticed that this is true for almost every mob in the game greater than an endermite or silverfish: if you shoot it through the feet, it dies, but anywhere above that or else than that, it doesn't. Pigs, cows, zombies, evokers, drowned, wither skeletons, anything, only die when shot through the feet. I don't intend for it to kill bosses so they are not a problem, luckily.
I've been detecting mobs by having every iteration of the recursive function run kill @e[distance=..0.1]
, and it moves ahead by 0.25 blocks each iteration. I have tried to get around this difference in @e
detection, mob hitboxes, and visible mob sizes (which for some reason are all different) by using scoreboards to give every mob a value equal to their approximate height, and then changing the distance based on what type of mob it is: kill @e[scores=mobHeights=2,distance=..2]
, but that is at best buggy and at worst making it so you can shoot next to a mob and kill it.
As you can see in this image, the cursor is well over the pig, yet it insta-dies because of this imprecision.
If anyone knows a better way to detect mobs a raycasting function is moving through that would be great, because right now it is really frustrating to have to try to manually implement a fix which is really imprecise. Also, if anyone knows why the function only recognizes entities by their feet, that would also help a lot. I know that coordinates are also calculated at an entities feet, so maybe that has something to do with it.
minecraft minecraft-commands
add a comment |
I am writing a datapack with an item which functions like a sniper rifle - you can shoot it and a particle beam created by a recursive raycasting function will shoot out and any entities it encounters should die. However, entity detection is a big problem, because I can shoot right through a creeper's head and it doesn't die. You can download the datapack here if you want to test it out. Use /function rituals:give/sniper_rifle
to get the item.
I noticed that this is true for almost every mob in the game greater than an endermite or silverfish: if you shoot it through the feet, it dies, but anywhere above that or else than that, it doesn't. Pigs, cows, zombies, evokers, drowned, wither skeletons, anything, only die when shot through the feet. I don't intend for it to kill bosses so they are not a problem, luckily.
I've been detecting mobs by having every iteration of the recursive function run kill @e[distance=..0.1]
, and it moves ahead by 0.25 blocks each iteration. I have tried to get around this difference in @e
detection, mob hitboxes, and visible mob sizes (which for some reason are all different) by using scoreboards to give every mob a value equal to their approximate height, and then changing the distance based on what type of mob it is: kill @e[scores=mobHeights=2,distance=..2]
, but that is at best buggy and at worst making it so you can shoot next to a mob and kill it.
As you can see in this image, the cursor is well over the pig, yet it insta-dies because of this imprecision.
If anyone knows a better way to detect mobs a raycasting function is moving through that would be great, because right now it is really frustrating to have to try to manually implement a fix which is really imprecise. Also, if anyone knows why the function only recognizes entities by their feet, that would also help a lot. I know that coordinates are also calculated at an entities feet, so maybe that has something to do with it.
minecraft minecraft-commands
I am writing a datapack with an item which functions like a sniper rifle - you can shoot it and a particle beam created by a recursive raycasting function will shoot out and any entities it encounters should die. However, entity detection is a big problem, because I can shoot right through a creeper's head and it doesn't die. You can download the datapack here if you want to test it out. Use /function rituals:give/sniper_rifle
to get the item.
I noticed that this is true for almost every mob in the game greater than an endermite or silverfish: if you shoot it through the feet, it dies, but anywhere above that or else than that, it doesn't. Pigs, cows, zombies, evokers, drowned, wither skeletons, anything, only die when shot through the feet. I don't intend for it to kill bosses so they are not a problem, luckily.
I've been detecting mobs by having every iteration of the recursive function run kill @e[distance=..0.1]
, and it moves ahead by 0.25 blocks each iteration. I have tried to get around this difference in @e
detection, mob hitboxes, and visible mob sizes (which for some reason are all different) by using scoreboards to give every mob a value equal to their approximate height, and then changing the distance based on what type of mob it is: kill @e[scores=mobHeights=2,distance=..2]
, but that is at best buggy and at worst making it so you can shoot next to a mob and kill it.
As you can see in this image, the cursor is well over the pig, yet it insta-dies because of this imprecision.
If anyone knows a better way to detect mobs a raycasting function is moving through that would be great, because right now it is really frustrating to have to try to manually implement a fix which is really imprecise. Also, if anyone knows why the function only recognizes entities by their feet, that would also help a lot. I know that coordinates are also calculated at an entities feet, so maybe that has something to do with it.
minecraft minecraft-commands
minecraft minecraft-commands
asked 35 mins ago
Nik3141Nik3141
535116
535116
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "41"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgaming.stackexchange.com%2fquestions%2f352566%2fjava-minecraft-1-14-2-how-to-have-recursive-raycasting-function-determine-if-i%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Arqade!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgaming.stackexchange.com%2fquestions%2f352566%2fjava-minecraft-1-14-2-how-to-have-recursive-raycasting-function-determine-if-i%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown