Labels Milestones

New Issue

Remove mob fence and make all other fences not-jumpable #49

Open

opened 3 years ago by AliasAlreadyTaken · 6 comments

AliasAlreadyTaken commented 3 years ago

Owner

Reporter: Skyisblue

Reporter: Skyisblue

AliasAlreadyTaken added the

1. kind/enhancement

label 3 years ago

AliasAlreadyTaken added this to the (deleted) milestone 3 years ago

Skyisblue added the

2. prio/low

label 3 years ago

Styxcolor commented 2 years ago

Owner

Not jumpable for mobs/pets I hope.

Not jumpable for mobs/pets I hope.

👍 1

flux commented 1 year ago

Collaborator

The mobs fence does prevent mobs from jumping on the top of fence and escaping, but utterly fails in terms of keeping mobs from glitching through - even normal solid nodes can't do that. Additionally, there is no "from above" hitbox for mobs fence, you need to put a mobs:fence_top node on top of them, and almost no-one is aware of those.

My proposal:

1. mobs:fence and mobs:fence_top should be aliased to default:wooden_fence
2. all fences registered w/ default.register_fence should get a collision_box which is type="fixed" and has 3 layers of borders: a normal node (1 1 1), a slightly expanded normal node, and the current borders.

The mobs fence *does* prevent mobs from jumping on the top of fence and escaping, but utterly fails in terms of keeping mobs from glitching through - even normal solid nodes can't do that. Additionally, there is *no* "from above" hitbox for mobs fence, you need to put a `mobs:fence_top` node on top of them, and almost no-one is aware of those. My proposal: 1. `mobs:fence` and `mobs:fence_top` should be aliased to `default:wooden_fence` 2. all fences registered w/ `default.register_fence` should get a `collision_box` which is `type="fixed"` and has 3 layers of borders: a normal node (1 1 1), a slightly expanded normal node, and the current borders.

flux added the

4. step/want approval

label 1 year ago

flux added this to the flux's TODO list project 11 months ago

flux commented 8 months ago

Collaborator

the whole purpose of mobs:fence is to prevent mobs from glitching through them, not to prevent players from jumping over them. the solution is better mob API w.r.t. normal fences (and really, all nodes).

the whole purpose of mobs:fence is to prevent mobs from glitching through them, not to prevent players from jumping over them. the solution is better mob API w.r.t. normal fences (and really, all nodes).

flux added

4. step/at work

2. prio/interesting

and removed

2. prio/low

4. step/want approval

labels 8 months ago

flux added a new dependency 7 months ago

#1362 write a new mob API and port mobs to it

sherkhan30452 commented 6 months ago

The mobs fence does prevent mobs from jumping on the top of fence and escaping, but utterly fails in terms of keeping mobs from glitching through - even normal solid nodes can't do that. Additionally, there is no "from above" hitbox for mobs fence, you need to put a mobs:fence_top node on top of them, and almost no-one is aware of those.

My proposal:

1. mobs:fence and mobs:fence_top should be aliased to default:wooden_fence
2. all fences registered w/ default.register_fence should get a collision_box which is type="fixed" and has 3 layers of borders: a normal node (1 1 1), a slightly expanded normal node, and the current borders.

There is an option in petz mod already: See screenshot and link:

https://forum.minetest.net/viewtopic.php?t=22245

> The mobs fence *does* prevent mobs from jumping on the top of fence and escaping, but utterly fails in terms of keeping mobs from glitching through - even normal solid nodes can't do that. Additionally, there is *no* "from above" hitbox for mobs fence, you need to put a `mobs:fence_top` node on top of them, and almost no-one is aware of those. > > My proposal: > 1. `mobs:fence` and `mobs:fence_top` should be aliased to `default:wooden_fence` > 2. all fences registered w/ `default.register_fence` should get a `collision_box` which is `type="fixed"` and has 3 layers of borders: a normal node (1 1 1), a slightly expanded normal node, and the current borders. There is an option in petz mod already: See screenshot and link: https://forum.minetest.net/viewtopic.php?t=22245

Petz fence.png

166 KiB

AliasAlreadyTaken added the

2. prio/controversial

label 5 months ago

AliasAlreadyTaken commented 5 months ago

Poster

Owner

This change may alter people's existing builds, right?

This change may alter people's existing builds, right?

flux commented 5 months ago

Collaborator

This change may alter people's existing builds, right?

yes, this is certainly a change that should be communicated to players beforehand.

> This change may alter people's existing builds, right? yes, this is certainly a change that should be communicated to players beforehand.

flux removed the

4. step/at work

label 3 months ago

flux referenced this issue 2 months ago

daydream reports: I can jump up and stand on a r ... #4074

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

Labels

Apply labels

Clear labels   

1. kind/balancing

Depends on balancing   

1. kind/breaking

something that alters or disables an existing game mechanic   

1. kind/bug

Something is not working   

1. kind/construction

A build needs fixing   

1. kind/documentation

Needs proper documentation   

1. kind/enhancement

New feature   

1. kind/griefing

players despoiling builds or nature   

1. kind/invalid

Not a valid report, e.g. created by mistake with no content.   

1. kind/meme

issue is mostly a joke   

1. kind/node limit

something which works for or against the node limit   

1. kind/other

Something not within the other kinds   

1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other   

2. prio/controversial

not likely to happen w/out a lot of discussion   

2. prio/critical

Very important   

2. prio/elevated

something players are eager to have fixed   

2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem   

2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.   

2. prio/low

Not so important   

3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.   

3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup   

3. source/engine

Issue is due to a bug or feature of the minetest engine   

3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation   

3. source/integration

Two or more nonbuggy mechanics conflict   

3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues   

3. source/mod upstream

Problem is upstream (not engine/client)   

3. source/unknown

  

3. source/website

Affects the website   

4. step/approved

Alias has approved this feature, someone should implement it   

4. step/at work

Being worked on   

4. step/blocked

we plan to do this, but other work has to be finished first   

4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon   

4. step/help wanted

Need some help   

4. step/needs confirmation

  

4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done   

4. step/question

More information is needed   

4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing   

4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.   

4. step/want approval

Someone can quickly implement this if Alias approves the change/feature   

5. result/cannot reproduce

  

5. result/duplicate

This issue or pull request already exists   

5. result/fixed

problem is fixed   

5. result/maybe

not planned currently, but maybe some day   

5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.   

ugh/petz

yet another petz bugz.   

ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server   

ugh/QA NOK

Fix didn't yield the expected results   

ugh/QA OK

tested

No Label

1. kind/balancing

1. kind/breaking

1. kind/bug

1. kind/construction

1. kind/documentation

1. kind/enhancement

1. kind/griefing

1. kind/invalid

1. kind/meme

1. kind/node limit

1. kind/other

1. kind/protocol

2. prio/controversial

2. prio/critical

2. prio/elevated

2. prio/good first issue

2. prio/interesting

2. prio/low

3. source/art

3. source/client

3. source/engine

3. source/ingame

3. source/integration

3. source/lag

3. source/mod upstream

3. source/unknown

3. source/website

4. step/approved

4. step/at work

4. step/blocked

4. step/discussion

4. step/help wanted

4. step/needs confirmation

4. step/partially fixed

4. step/question

4. step/ready to deploy

4. step/ready to QA test

4. step/want approval

5. result/cannot reproduce

5. result/duplicate

5. result/fixed

5. result/maybe

5. result/wontfix

ugh/petz

ugh/QA main

ugh/QA NOK

ugh/QA OK

Milestone

Set milestone

Clear milestone

No items

No Milestone

Projects

Set Project

Clear projects

No project

flux's TODO list

Assignees

Assign users

Clear assignees

No Assignees

4 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Depends on

#1362 write a new mob API and port mobs to it

your-land/bugtracker

Reference: your-land/bugtracker#49

Write Preview

Loading…

Cancel

Save

There is no content yet.