Forged Alliance Forever Forged Alliance Forever Forums 2014-12-09T01:17:45+02:00 /feed.php?f=2&t=8973 2014-12-09T01:17:45+02:00 2014-12-09T01:17:45+02:00 /viewtopic.php?t=8973&p=87534#p87534 <![CDATA[Re: Bug with stuned units]]>
IceDreamer wrote:
Hey Ithilis, Sheeo and I have come up with working code to force allied Chrono to sync with the game clock (and hence each other) so that hitting allies can be turned off. It's a bit of a balance change though, so it will have to be debated, but good idea man! :)


Thanks, hope it will work, and bring more chrono to game :)

big thanks again

Statistics: Posted by Ithilis_Quo — 09 Dec 2014, 01:17


]]>
2014-12-09T00:52:49+02:00 2014-12-09T00:52:49+02:00 /viewtopic.php?t=8973&p=87530#p87530 <![CDATA[Re: Bug with stuned units]]>
IceDreamer wrote:
Hey Ithilis, Sheeo and I have come up with working code to force allied Chrono to sync with the game clock (and hence each other) so that hitting allies can be turned off. It's a bit of a balance change though, so it will have to be debated, but good idea man! :)

It would be nice to find a possible balance solution so allied units aren't stunned, because right now people can just give their units to the aeon player and avoid the stun. Vee's idea of toggling seems pretty interesting.

Statistics: Posted by Aulex — 09 Dec 2014, 00:52


]]>
2014-12-09T00:28:34+02:00 2014-12-09T00:28:34+02:00 /viewtopic.php?t=8973&p=87528#p87528 <![CDATA[Re: Bug with stuned units]]>

Statistics: Posted by IceDreamer — 09 Dec 2014, 00:28


]]>
2014-12-08T23:53:12+02:00 2014-12-08T23:53:12+02:00 /viewtopic.php?t=8973&p=87525#p87525 <![CDATA[Re: Bug with stuned units]]>
Chrono not counter all units, it stun units and its preatty nice. but its ridiculous risky. I like the cheese strategy but this is to big cheese also for me:D

This hight risk, and no option for make this risk less extreme is responsible for situation when is use chronodumper in normal game as small holiday.

On yeah replay, what is really nice, but i think you make same effor with shield and T3acu. But it would not be so risky.

maybe are some game where would chrono look as so op think, but most of all its used for troll win game, where doesnt mather that someone (acu with chrono chase army) die.

Statistics: Posted by Ithilis_Quo — 08 Dec 2014, 23:53


]]>
2014-12-08T18:58:05+02:00 2014-12-08T18:58:05+02:00 /viewtopic.php?t=8973&p=87505#p87505 <![CDATA[Re: Bug with stuned units]]> witch is kinda weird in case of air and naval units

you can force chrono to work with groundfire

but i do not think you can do that underwater xD
but it still should stun surface ships for sure if acu is on land, not sure about subs

Ithilis_Quo wrote:
1. dangerous against everything. you have only 11000 hp. Used mostly in time where are plenty of T2 tanks and first T3 bot out. you can overcharge as hell but it is extremly risky. It so risky that it is nearly never use. And turets stop you,


i think chrono kinda counters all t1 t2 t3 land units except arty snipers and mmls
http://content.faforever.com/faf/unitsD ... 05,XRL0305

chrono and overcharge range are same as brick/percy range, hoplite does outrange ACU but man, who even cares about hoplite

problem for land units that they can't chase ACU, as soon as they catch up they get stunned and meanwhile ACU can OC or retreat
if there are large amount of units they will bunch up really much cause 1rst units will stop while second row of units will catch up

so it gives oppotunities for EPIC overcharges
and good t3 arty shots
and you can always have t2 flack with you that will rape gunships that are stunned in mid air

also do not forget that units loose their orders after they got stunned, so they kinda use momentum if they were trying to get in range of acu or surround...

about tech + chrono, it is pretty hard to attack with that acu, cause you can only pd creep and you are still getting countered by mml/t3 arty
but if you drop that t3 acu somewhere, it can be major pain in the ass

i played FFA (2v2v2v2) where me and my ally tryed to finish guy that was in very bad position, we didn't even really tryed to kill him
we just send strats few at the time... and i think we lost huge amount of time and about 15 strats
he was not even trying to dodge, but some how just with flack and stunn strats mostly we doing only one pass, in result my team didn't get 50% of map fast enought and we lost

after that fail i attempted t3 acu with chrono drop http://youtu.be/P1zHjPfkIz8?t=5m43s
and it was quite good

Edit: i didn't really saw much of OP usage of chrono dampener dunno why tho...
Edit 2: engineers still continue building while stunned

Statistics: Posted by ZLO_RD — 08 Dec 2014, 18:58


]]>
2014-12-08T18:07:51+02:00 2014-12-08T18:07:51+02:00 /viewtopic.php?t=8973&p=87497#p87497 <![CDATA[Re: Bug with stuned units]]>
nakeddave wrote:
Do the stunned units reload at their usual rate while stunned


It dont reset reload time, it dont touch reaload time. It let reload time of units as is whitotu stun, but percival have same reload time as si chrono reaload so that mean he will reaload when is in stun, and then imediatly fire because its same 4 sec.

___________

Or maybe, but this is not easy solution but remove this hack how it is work now:

Chrono dumper, is technology that create bubble where is slow time from enemy perspective. That mean everything is 40% slowed. But when GPG programators was lazy to slow every units in chrono range they make it stun for 40% of time, with that it is cca same effect. Cca is, but still isnt. Already its hack solution.

Can it be rework for slow enemy in that range for 40% instead of stun. Slow = change stats from move , rate of fire , muzzle velocity and build rate to 60%.
When is unit affected by chrono projectil (rate of fire on chrono projectil change for every 0,01sec)-> then change stat for 0,6

Statistics: Posted by Ithilis_Quo — 08 Dec 2014, 18:07


]]>
2014-12-08T16:23:50+02:00 2014-12-08T16:23:50+02:00 /viewtopic.php?t=8973&p=87485#p87485 <![CDATA[Re: Bug with stuned units]]>
Resin

Statistics: Posted by Resin_Smoker — 08 Dec 2014, 16:23


]]>
2014-12-08T14:55:44+02:00 2014-12-08T14:55:44+02:00 /viewtopic.php?t=8973&p=87480#p87480 <![CDATA[Re: Bug with stuned units]]>
ie is it possible to horribly abuse this to increase fire rate of allied sniperbots

Statistics: Posted by nakeddave — 08 Dec 2014, 14:55


]]>
2014-12-08T18:16:02+02:00 2014-12-08T12:45:30+02:00 /viewtopic.php?t=8973&p=87468#p87468 <![CDATA[Re: Bug with stuned units]]> When chrono start stun cycle then it will be on game time divisible by ten. then doesnt mater how many chrono is in game, because all have cycle in same time. Thay can only stunn bigger place (what is logical) but not longer time.

example: chrono is build in game time 12:53, first 7 second is dont doing nothing, and first pulse come out in time 13:00, stunn units for 4 second, and another puls come out in time 13:10... And every chrono would have same timing. Problem solve.

stuning ally unit mean that noob with chrono can total interupt ally army/defense. + its usseble only in solo gaming, teamplay with chrono is imposible
___________________

ZLO_RD wrote:
1) get guns and chrono:
- have only 11000 hp
- OC like a Boss
- dangerous againt air (or is it? only dangerous against mercies and corsairs?)
- can't really counter pds alone
2) get t3 and chrono:
- 17000 hp with 45 regen
- can't really OC units
- can build sams and t2 shield that has 11k, shield can get construced in about 6 seconds about 1900 hp emergency hp every second, also shields can regen and recharge


1. dangerous against everything. you have only 11000 hp. Used mostly in time where are plenty of T2 tanks and first T3 bot out. you can overcharge as hell but it is extremly risky. It so risky that it is nearly never use. And turets stop you,

when you would have cheapest shield, you can overcharge as hell but you have 40K hp, where turets dont stop you, you dont risk so much, and it is cheaper. Shield is better choice.

2. When you get T3 you pay 2400+720 mass more. So thats time when enemy have T3 tanks in field. You will go with chrono and significant smaller army and T2 shield and 6K hp more realy dont help you.

3. chrono get bigger cost for 2500 mass (+ 750mass and 22500e + time) but with chrono acu take +5000 HP and +15 regen. 16K hp and +25regen its as T2 UEF acu. It come later, because cost more, but make chrono would be less risk as is incredible risky now. And maybe ussable more as in every 1000th game.

3.5. Or Allow build another upgrade after chrono what get some surviability.
__________________
0. first bug with stun units, this is not only about chrono, but about all stun. Units in stun have not stun reload time. For perci is stunn ussles, he have same 100% dps. Where brick have cca 37% dps less for less rate of fire. Or aeon T2+ uef T3 PD stun dont make nothing on this pd. thay fire before and imediatly after stun.

Statistics: Posted by Ithilis_Quo — 08 Dec 2014, 12:45


]]>
2014-12-08T12:25:39+02:00 2014-12-08T12:25:39+02:00 /viewtopic.php?t=8973&p=87465#p87465 <![CDATA[Re: Bug with stuned units]]>
Less hacky solution is to save for every unit a timestamp last_stunned indicating at which time that unit was most recently stunned. Then when a chrono fires, you check if (now - last_stunned) < chrono_reload_time. If true, then chrono does nothing. This ensures that multiple chronos cannot stun a unit more than a single chrono. For example if chrono reload time is 5 seconds, and stun time is 2 seconds, then after stun is removed the unit becomes immune to chrono for 3 seconds.

The other option is that when a chrono acu fires, then it also fires the chronos of other acus that have overlapping chrono range (distance between acus < 2 * chrono range, note the 2). That would make chronos sync up & ensure that no unit can be stunned twice.

Statistics: Posted by Vee — 08 Dec 2014, 12:25


]]>
2014-12-08T08:34:54+02:00 2014-12-08T08:34:54+02:00 /viewtopic.php?t=8973&p=87461#p87461 <![CDATA[Re: Bug with stuned units]]>
IceDreamer wrote:
I'm going to have a think about ways to get multiple allied chrono to sync up with each other, making it possible and not imba as hell to have them not stunning allied units.


Could be done using code like that in place for overspill, I do think it's a better solution than having it stun allied units.

Statistics: Posted by Sheeo — 08 Dec 2014, 08:34


]]>
2014-12-08T02:14:08+02:00 2014-12-08T02:14:08+02:00 /viewtopic.php?t=8973&p=87452#p87452 <![CDATA[Re: Bug with stuned units]]> Statistics: Posted by IceDreamer — 08 Dec 2014, 02:14


]]>
2014-12-08T01:55:02+02:00 2014-12-08T01:55:02+02:00 /viewtopic.php?t=8973&p=87451#p87451 <![CDATA[Re: Bug with stued units]]> - have only 11000 hp
- OC like a Boss
- dangerous againt air (or is it? only dangerous against mercies and corsairs?)
- can't really counter pds alone
2) get t3 and chrono:
- 17000 hp with 45 regen
- can't really OC units
- can build sams and t2 shield that has 11k, shield can get construced in about 6 seconds about 1900 hp emergency hp every second, also shields can regen and recharge

i have not tryed to abuse chrono with mmls really, wonder how that would work...
or maybe with serenitys (t3 mob arty)

Statistics: Posted by ZLO_RD — 08 Dec 2014, 01:55


]]>
2014-12-08T00:55:43+02:00 2014-12-08T00:55:43+02:00 /viewtopic.php?t=8973&p=87449#p87449 <![CDATA[Bug with stuned units]]>
Example, when you have chronodumper on ACU and percival is stuned, Then he fire shot before stun, and imediatly after restun fire again. So stun against perci iss ussles because unit only dont move.

__________

Another think, chrono dumper stun ally units too. Know that this is because can be OP more chronodumper acu with different timing = perma stun. But it is pretty annoying, and change timing not on time when is build but on every 5 sec is much clever solution who will not stun ally units, and can not be opnes in plenty of chrono.

_____

3th think, chrono dumper need take some HP when is build up. As cybran cloak give hp on chrono it is same. Its insine risky build chrono because acu is paper, and chrono is effective only on havy spam. So it negote chrono.

Statistics: Posted by Ithilis_Quo — 08 Dec 2014, 00:55


]]>