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

Monster walk through bug #1918

Closed
2 tasks done
gugahoa opened this issue Sep 11, 2016 · 9 comments · Fixed by opentibiabr/otservbr-global-archived#1200 or #3533
Closed
2 tasks done

Monster walk through bug #1918

gugahoa opened this issue Sep 11, 2016 · 9 comments · Fixed by opentibiabr/otservbr-global-archived#1200 or #3533
Labels
bug An issue describing unexpected behavior of code

Comments

@gugahoa
Copy link
Contributor

gugahoa commented Sep 11, 2016

Before creating an issue, please ensure:

  • This is a bug in the software that resides in this repository, and not a
    support matter (use https://otland.net/forums/support.16/ for support)
  • This issue is reproducible without changes to the code in this repository

Steps to reproduce (include any configuration/script required to reproduce)

  1. Log into a player, or summon a monster
  2. Create (with /m) 10 rats. 2 Will start random step.
  3. Create a monster that can push (Cyclops/Dragon)

Expected behaviour

I'm not sure as I don't play official Tibia. Something along the line of pushing the weaker monster out of the way or side stepping until there's room is what I think is acceptable in this case.

Actual behaviour

Stronger monster will try to walk through weaker monster, deleting him (weaker monster) in the process

@andersonfaaria

This comment was marked as abuse.

@vankk
Copy link
Contributor

vankk commented Sep 11, 2016

I can confirm that too.

@ranisalt
Copy link
Member

ranisalt commented Sep 11, 2016

In Tibia stronger monsters crush weaker monsters if there is no room to reach the target. Not all monsters do that, though. It's actually used as strategy to kill bosses that summon a lot (such as Ghazbaran's deathslicers), limiting space around the blocker so that the Ghazbaran crushes the deathslicers to get through.

It could be a switch, though, since I would prefer monsters to be pushed instead. We already have the logic for pushing crates around so it should be easy to implement.

@gugahoa
Copy link
Contributor Author

gugahoa commented Sep 11, 2016

In Monster::pushCreatures, any monster that can push, will have that behavior. Can someone confirm if any monster has that behavior or only really strong monsters?

@techrlz18
Copy link

Confirmed that too.

@peonso
Copy link

peonso commented Sep 12, 2016

Fix for that here #922 (comment)

Monsters with canpushitems="1" should be able to push monsters with pushable="1". The pushed monster is pushed to side if there is a free sqm (in the speed of the pushing monster), if there isn't, it is killed.

https://youtu.be/a9FbrBmOseI

@ranisalt
Copy link
Member

ranisalt commented Sep 12, 2016

@wgrriffel I meant players use this stuff to kill bosses, not that it's monster behavior.

Also, monsters are all either pushable or can push. That's like... physics.

@andersonfaaria

This comment was marked as abuse.

@ranisalt
Copy link
Member

As I said, we can just use logic from moving crates. It already does the job of moving if possible, else crushing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue describing unexpected behavior of code
Projects
None yet
7 participants