[8.73] beacon teleporting

[Helge_F]

....i have no replay atm.....

but the last days more and more problems with the teleporting, one build it the whole team trys to teleport but only one gets in and both die... and much flaming why the others dont come. i read in the feedback section that u add a 4sec delay in the next version but it seems that it is in this version and nobody knows...

[Velocity2k]

The 4sec delay has already been added in the last version (8.73b). The current version is 8.73c.
http://btanks.net/forum/showthread.php?tid=49

[Helge_F]

ah k thx it explain some missing gold never look at the price since the beta

[toyboatt]

I think there is a real bug, not just 4 second delay. Multiple times my tank doesn't teleport to our team beacon on enemy CP, and I get message something like "Can only teleport to friendly Control Point" or something like that. But my screen is on the CP we are attacking, and the beacon is not yet destroyed. I think maybe my tank too far from my CP, but I look and it's right. Since then it happens when my tank is in my base too.

I don't save replays because I'm lazy. For now I just say this out loud so that maybe others will pay attention. Maybe it is not my mistake. I will pay closer attention and write down game time next time this happens and save the replay. It seems to happen with specific players' beacons... So in some game I cannot teleport to Green's beacons, but I can teleport to Orange's beacons.

Or maybe I drink too much. Anyone else see this issue?

[sTacHus]

I have a replay where teleporting to a becon doesnt work multiple times.
The best example is about 23:15. Three tanks begin to teleport at the same time, but only one really teleported...

The replay is already uploaded in the ban request section, so i dont need to upload it again


http://btanks.net/forum/attachment.php?aid=1036

or

http://btanks.net/forum/showthread.php?t...8#pid28978

[Exodus]

@toyboatt: It's unlikely, that the problem has to do with specfic players. But a replay would be really helpful for finding the problem.

@stachus: That's the way it's supposed to work. The cooldown, introduced in 8.73b, prevents multiple players from teleporting to the same Beacon at the same time. Only the first one gets there, the second player has to wait for the 4 seconds until he is able to teleport.

[GEN_Schwarzkopf]

@toyboatt: It's unlikely, that the problem has to do with specfic players. But a replay would be really helpful for finding the problem.

@stachus: That's the way it's supposed to work. The cooldown, introduced in 8.73b, prevents multiple players from teleporting to the same Beacon at the same time. Only the first one gets there, the second player has to wait for the 4 seconds until he is able to teleport.

This new "feature" is not well known and has caused alot of flaming. The change is so significant it almost needs to be on the loading screen so people know about it.

[griffin1987]

As I've already posted in another thread, it seems the beacon cooldown is accounting for enemy player fac-porting as well, that is, only if they port close enough to the beacon.

[ssl]

only if they port close enough to the beacon.

Which is another issue with the teleport beacon. When building one at a CP, there are two port ranges which are slightly overlapping. If you port to the range where ONLY the beacon is in range, you have to pay 75g, which is not intended. When porting to the area where both ranges overlap, is works as intended, but also when porting to the area where only the CP range is, you also have to pay 75g.
Suggestion: Move the porting-range from the tele beacon to exactly match the CP range.

This brings some new questions regarding beacon cooldown: when to people port to an allied CP with tele beacon, the first one should have a free port and the second one should have to pay 75g without having to reorder the teleport.

Some other CP-teleport related things which come in my mind:
When casting CP-TP, your tank should be frozen in place! some times you click port but then, within 2,5sec you give some move-order and you accidentally move out of teleport range. this is VERY annoying.
When casting CP-TP to a CP which is captured right now, and you are too late, the CP-TP cooldown should not get triggered!

[AGGInator]

Which is another issue with the teleport beacon. When building one at a CP, there are two port ranges which are slightly overlapping. If you port to the range where ONLY the beacon is in range, you have to pay 75g, which is not intended.

If i remember right the tooltip says:
if you build a beacon near an allied cp you may be able to teleport for free (not the same but close to it)
this includes the possibility to be out of its range where it's possible to port 4 free.

[toyboatt]

I think beacon is still bugged. I have tried to tp to allied beacon a few times this week, and my teleport was cancelled with message that it's not a control point or whatever. I know at some point you fixed enemy teleports cancelling allied beacon teleports.. but have you looked at when allies self-cancel their own teleports? What if 3 of us all try to go to beacon, and the first person presses "S" to stop there teleport.. could that cancel all our teleports?

Thx
roargasm