Forged Alliance Forever Forged Alliance Forever Forums 2012-12-20T00:12:46+02:00 /feed.php?f=45&t=2554 2012-12-20T00:12:46+02:00 2012-12-20T00:12:46+02:00 /viewtopic.php?t=2554&p=25339#p25339 <![CDATA[Re: Fixing the com upgrade bug]]>
and ask what the f*** you have done

Statistics: Posted by ColonelSheppard — 20 Dec 2012, 00:12


]]>
2012-12-19T23:18:20+02:00 2012-12-19T23:18:20+02:00 /viewtopic.php?t=2554&p=25335#p25335 <![CDATA[Re: Fixing the com upgrade bug]]>
Yours is fixed too : https://bitbucket.org/thepilot/forged-a ... ced2326bc0

Was not very difficult to track either. If there is any other upgrade/assist exploit, it's around there.

Statistics: Posted by Ze_PilOt — 19 Dec 2012, 23:18


]]>
2012-12-19T22:24:36+02:00 2012-12-19T22:24:36+02:00 /viewtopic.php?t=2554&p=25334#p25334 <![CDATA[Re: Fixing the com upgrade bug]]>

Statistics: Posted by Ze_PilOt — 19 Dec 2012, 22:24


]]>
2012-12-19T22:20:08+02:00 2012-12-19T22:20:08+02:00 /viewtopic.php?t=2554&p=25333#p25333 <![CDATA[Re: Fixing the com upgrade bug]]>

Statistics: Posted by pip — 19 Dec 2012, 22:20


]]>
2012-12-19T22:14:04+02:00 2012-12-19T22:14:04+02:00 /viewtopic.php?t=2554&p=25331#p25331 <![CDATA[Re: Fixing the com upgrade bug]]>
PS - for that patch to be released it needs testing (seton/shield replays).

Statistics: Posted by Combo — 19 Dec 2012, 22:14


]]>
2012-12-19T22:13:14+02:00 2012-12-19T22:13:14+02:00 /viewtopic.php?t=2554&p=25330#p25330 <![CDATA[Re: Fixing the com upgrade bug]]>
https://bitbucket.org/thepilot/forged-a ... 74449c8e90

Statistics: Posted by Ze_PilOt — 19 Dec 2012, 22:13


]]>
2012-12-19T21:58:58+02:00 2012-12-19T21:58:58+02:00 /viewtopic.php?t=2554&p=25329#p25329 <![CDATA[Re: Fixing the com upgrade bug]]>
1) Choosing values for the ACU so that repairing it with t1 engies cost the same as assisting a RAS upgrade:

BuildCostEnergy = 5000000,
BuildCostMass = 250000, (from 18 000)
BuildTime = 50000, (from 6000000)

T1 engies will consume 25 mass and 750 energy. That is the exact value required to assist a RAS upgrade. If that happens, players will immediately know they have to look at the engies assisting their ACU.

2) Just revert back the buildtime of the ACU to 60000 (from 6000 000 000) so that it costs a shitload of energy to repair the ACU, thus making it a warning to stop then re assist the ACU. This fix involves no mass consumption so it's less punishing for the eco of someone accidentally doing it. This is the c) solution mentioned by Sheppard.

GPG used the 2nd solution for many years, I think we should just go back to it and that also makes ACU repairing not profitable at all (they have regen already, or upgrades, they don't need to be repairable). I am very much for going back to the 2nd "hotfix".

Statistics: Posted by pip — 19 Dec 2012, 21:58


]]>
2012-12-19T21:50:56+02:00 2012-12-19T21:50:56+02:00 /viewtopic.php?t=2554&p=25327#p25327 <![CDATA[Re: Fixing the com upgrade bug]]>
Combo wrote:
It seems that fixing this the right way (making engies restart their beams) is quite involved.

As a quick-fix solution, TA4LIFE suggested adjusting the ACU repair cost so each assisting engie spends -750 nrg, which would punish eco enough to deter anyone from doing this. This seems like it would be an easy to implement solution. :idea:


you obviously did not read my post
and restarting beam does not change anything

Statistics: Posted by ColonelSheppard — 19 Dec 2012, 21:50


]]>
2012-12-19T21:36:24+02:00 2012-12-19T21:36:24+02:00 /viewtopic.php?t=2554&p=25324#p25324 <![CDATA[Re: Fixing the com upgrade bug]]>
As a quick-fix solution, TA4LIFE suggested adjusting the ACU repair cost so each assisting engie spends -750 nrg, which would punish eco enough to deter anyone from doing this. This seems like it would be an easy to implement solution. :idea:

Statistics: Posted by Combo — 19 Dec 2012, 21:36


]]>
2012-12-19T21:23:28+02:00 2012-12-19T21:23:28+02:00 /viewtopic.php?t=2554&p=25323#p25323 <![CDATA[Re: Fixing the com upgrade bug]]> Statistics: Posted by ColonelSheppard — 19 Dec 2012, 21:23


]]>
2012-12-19T21:13:16+02:00 2012-12-19T21:13:16+02:00 /viewtopic.php?t=2554&p=25321#p25321 <![CDATA[Re: Fixing the com upgrade bug]]>
In other words repairing a mex with engies then starting an upgrade doesn't make it free. That's the correct behavior of course.

If the code is similar then perhaps someone can copy/paste the mex upgrade code over to the acu upgrade code -- that's probably oversimplified but it's a start (and wouldn't need any of the 3 drastic changes suggested by Sheppard).

The key difference is that the engies assisting mex's will briefly stop their beam then restart it once the upgrade command is issued. That's the solution.

Statistics: Posted by Combo — 19 Dec 2012, 21:13


]]>
2012-12-13T12:49:37+02:00 2012-12-13T12:49:37+02:00 /viewtopic.php?t=2554&p=24936#p24936 <![CDATA[Fixing the com upgrade bug]]>
http://www.youtube.com/watch?v=mB52mOvC ... e=youtu.be

1. get you commander damaged
2. start repairing it with engines (-4 engery and -0.X mass on t1)
3. start and uprade and pause it on the commander
4. engines will finish the upgrade for the cost of the repair so you can easily get microwave lazor or res upgrade

HOW TO FIX:

that the big question i ask myself since quite a while:

a)
hardcore workaround: make all engines near to the commander completely lose any kind of commands by just ordering to "stop"
b)
as the first one would surely piss of many soon i think we have to go to the core of the problem: make engines restarting their support beam like they should do whenever the activity of the commander changes
c)
set the commanders buildtime to"ver low" again (step back, worst solution)

this thread is there to discuss the FIXING of the bug, and NOT for use (meaning abuse) reporting!
i will post my so far coding solutions later when i put finally together my main PC again

Statistics: Posted by ColonelSheppard — 13 Dec 2012, 12:49


]]>