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

Investigate the possibility to implement a disable attack system #52

Open
godbit opened this issue Jan 28, 2018 · 4 comments
Open

Investigate the possibility to implement a disable attack system #52

godbit opened this issue Jan 28, 2018 · 4 comments

Comments

@godbit
Copy link
Contributor

godbit commented Jan 28, 2018

By adding orbs to units you can choose which attack that orb enables. This means that if we have 0 attacks enabled on all of our towers but we add an orb enabling Attack 1 they should function as normal as long as we make sure that orb does not do anything but enable attack 1. My suggestion to use is lifesteal since that is almost 100% certain that we wont use anywhere else.

This then means that you can write a system which removes this orb from units at certain time -> disabling their attack for as long as the orb is gone.

@karlek
Copy link
Contributor

karlek commented Jan 29, 2018

Interesting! So this is how we would implement tower stunning functionality?

@godbit
Copy link
Contributor Author

godbit commented Jan 29, 2018

Yeah that could be one possible application! Another is to stop units from attacking whille "casting" a spell cast by a dummy or similar.

@karlek
Copy link
Contributor

karlek commented Jan 29, 2018

Ah, as you did with Cenarius. I like this, do we know if this works?

@godbit
Copy link
Contributor Author

godbit commented Jan 29, 2018

I did some research yesterday and i seems to work for other people. They have used it for systems that items enable attack 1 or 2. For instance a bow would enable attack 2 (ranged) and a sword would enable attack 1 (melee).

To easiest way to test this for us is probably just to implement it x) Maybe on a small scale and then create all the supporting methods later(?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants