PTR Changelog 2018-11-01: Creep.pull()
-
Can I ask why this is not
creep.pull(target); creep.move(destination)
orcreep.pull(target,direction)
?Those seem much more useful and interesting.
-
@nihilrex said in PTR Changelog 2018-11-01: Creep.pull():
Can I ask why this is not
creep.pull(target); creep.move(destination)
orcreep.pull(target,direction)
?Those seem much more useful and interesting.
Did you miss the part about it being usable on other players creeps, and them having to accept it? Or am I missing where you included that in your post?
-
@maxion Why should they have to accept it? If playercreep pulls enemycreep left, and enemycreep moves right, both should just stay still. Adding in logic so that if player creep pulls downleft and enemycreep moves downright, they both move straight down would just be a bonus.
-
Question: Is this equivalent to an engine? If one engine (move) is more powerful do you overwhelm the other creeps move? That could make for a super interesting aspect to combat.
- You have more move than them. If you try force (unwilling) them with pull, you move them but get fatigue equal to your net move advantage (your move - their move). AKA if you had 20 move they had 10, you get to move them, but get fatigue as if you only had 10 move parts.
- You have less move than them. Can't pull unwillingly, could maybe slow them down at cost of your fatigue?
- You have more or less move than them, and they accept it willingly. You move them.
-
Honestly I don't think this should be usable on other player creeps, but has a lot of interesting prospects for use on your own.
-
Can we also get
Creep.push()
? I wanna have boosted healers pushing50xATTACK
creeps into battle while being safe behind them
-
Will pull mechanics guarantee that pulled creep will take position of pulling creep when multiple creeps try to move into the same spot? (Think attacker - healer pair being separated by enemy creep)
-
Would this make it impossible to get between the creeps? If both creeps are synced intent wise, then an enemy creep couldn't jump the first one and prevent the second from following. This would give an advantage to block move attacks.
-
I cant wait to implement a 50 heal part creep station being carried around by my attackers or just drop a 50 work part creep at someones walls. Ultimate siege strats
What happens to the fatigue gain of the pulling creep when the pulled creep has move parts? Do they contribute to reducing fatigue gain?
-
@zyzyzyryxy not guaranteed, just most likely.
When several creeps trying to move onto the same tile, the priorities are: creep having follower, creep that being pulled, creep that pulls someone, creep with best moves/weight ratio
@davaned That may be interesting, but the current implementation is not supposed to be used unwillingly.
@smokeman When several creeps trying to move onto the same tile creep that being pulled takes priority.
@obamallama No, creep pulling another creep receives another creep's fatigue. Pulled creeps, however, can use his
MOVE
parts to reduce the fatigue he already has.
-
This post is deleted!
-
This post is deleted!
-
@o4kapuk Can you pull someone that has fatigue remaining?
-
@obamallama Yes, because if you call move on a creep nearby, the ERR_TIRED and the ERR_NO_BODYPART checks will be bypassed. Also, the fatigue of the pulled creep will be decreased as usual according to the pulled creep's
MOVE
parts.
-
That's really cool.
How does it handle switching rooms? I can imagine the train creep being knocked into the next room while the pulled creep is still 1 tile in front of the exit
-
@keenathar this is for players to handle. I have a couple of implementations (so I know it's possible), but I'd not spoil it because players should have their own wonderful discoveries.
-
@o4kapuk said in PTR Changelog 2018-11-01: Creep.pull():
When several creeps trying to move onto the same tile, the priorities are: creep having follower, creep that being pulled, creep that pulls someone, creep with best moves/weight ratio
Does this mean we can use
Creep.pull()
to prevent other creeps from squeezing in-between attacker-healer pair creeps? Assuming attackerpull()
s the healer along?
-
@orlet not guaranteed, just most likely.
-
@orlet You would still be able to move past them diagonally if they were next to each other diagonally but you could probably make them create a solid line but it would slow down how fast you can get to places
-
I see. Well, that's still useful and something to consider. Might actually implement a trio train squads, melee-healer-ranger mini choo choo train