Idle_Scholar Posted May 25, 2008 Share Posted May 25, 2008 (edited) OK, I think I've found an indestructable Bayonet class. Now unfortunately my first log got overwritten before I had the wit to save it but the battle went as follows. 1) I jump in a Corona, 25 Star Vipers and 8 R41 Starchasers (see fig 1)2) For a turn my Corona fires and hits every time with its 3 TLC4 and 1 IC43) At the same time my fighters all take one cycle of shots at the Bayonett and then fly away for some reason (See the line of corpses in fig 2 for their flight path)4) By calculation I've now done enough damage to take down the Bayonet's shields. This is assuming that the damage and shots/cycle info is accurate and that when it says 'x HIT y with a TLC4' in the log it means all the shots in the fusilade (a TLC4 has 4 4x75 strength shots per cycle) hit.5) While this has been going on the Bayonet and Correlian ship have been destroying fighters and do some damage to the Coronas shields 6) New turn7) from the report below the Bayonet has now taken enough damage to be destroyed So my questions are three fold: Why did the fighters fly off and come back?Why isn't the Bayonet dead?Why did the Corona only use its LC4 battery once and miss? http://i136.photobucket.com/albums/q200/Deathblane/OddFighterBehaviour1.jpg fig 1: Everything jumped into the location of the Corona http://i136.photobucket.com/albums/q200/Deathblane/OddFighterBehaviour2.jpg fig 2: The fighters then flew off to the left of the Bayonet, as can be seen by the lines of corpses And finally the report: SVIPER New SVIPER missed by HTLB4 from BYONET Spearhead SVIPER New SVIPER missed by LC4 from BYONET Spearhead SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER missed by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 Turn: 209 Cycle: 2 SVIPER New SVIPER missed by HTLB4 from BYONET Spearhead SVIPER New SVIPER missed by LC4 from BYONET Spearhead SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER hit by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes HULL damage CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 Turn: 209 Cycle: 3 SVIPER New SVIPER missed by HTLB4 from BYONET Spearhead SVIPER New SVIPER missed by LC4 from BYONET Spearhead SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes a critical hit. Onboard System(s) destroyed SVIPER New SVIPER destroyed SVIPER New SVIPER hit by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 Turn: 209 Cycle: 4 SVIPER New SVIPER missed by HTLB4 from BYONET Spearhead SVIPER New SVIPER hit by LC4 from BYONET Spearhead SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes a critical hit. Onboard System(s) destroyed SVIPER New SVIPER destroyed SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER hit by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F Turn: 209 Cycle: 5 SVIPER New SVIPER missed by HTLB4 from BYONET Spearhead SVIPER New SVIPER hit by LC4 from BYONET Spearhead SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes a critical hit. Onboard System(s) destroyed SVIPER New SVIPER destroyed SVIPER New SVIPER hit by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F Turn: 209 Cycle: 6 SVIPER New SVIPER missed by HTLB4 from BYONET Spearhead SVIPER New SVIPER hit by LC4 from BYONET Spearhead SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes HULL damage SVIPER New SVIPER hit by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes a critical hit. Onboard System(s) destroyed SVIPER New SVIPER destroyed CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 CORONA Pricked Finger misses TF New TF with LC4 CORONA Pricked Finger hits TF New TF with LC4 LOST CONTACT with TF New TF at S:50100,50100 pos:5023287,5068795 (DESTROYED) SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F Turn: 209 Cycle: 7 R41 New R41 missed by HTLB4 from BYONET Spearhead R41 New R41 hit by LC4 from BYONET Spearhead R41 New R41 takes SHIELD damage R41 New R41 takes HULL damage SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER hit by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER missed by TLC4 from CLGUN Patawotomie Creek CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F Turn: 209 Cycle: 8 R41 New R41 missed by HTLB4 from BYONET Spearhead R41 New R41 hit by LC4 from BYONET Spearhead R41 New R41 takes SHIELD damage R41 New R41 takes HULL damage R41 New R41 takes a critical hit. Onboard System(s) destroyed R41 New R41 destroyed SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes a critical hit. Onboard System(s) destroyed SVIPER New SVIPER destroyed SVIPER New SVIPER missed by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F Turn: 209 Cycle: 9 R41 New R41 missed by HTLB4 from BYONET Spearhead R41 New R41 hit by LC4 from BYONET Spearhead R41 New R41 takes SHIELD damage R41 New R41 takes HULL damage R41 New R41 takes a critical hit. Onboard System(s) destroyed R41 New R41 destroyed SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER hit by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes a critical hit. Onboard System(s) destroyed SVIPER New SVIPER destroyed CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F Turn: 209 Cycle: 10 R41 New R41 missed by HTLB4 from BYONET Spearhead R41 New R41 missed by LC4 from BYONET Spearhead SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes a critical hit. Onboard System(s) destroyed SVIPER New SVIPER destroyed SVIPER New SVIPER hit by IC2 from CLGUN Patawotomie Creek SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER takes SHIELD damage SVIPER New SVIPER hit by TLC4 from CLGUN Patawotomie Creek SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes HULL damage SVIPER New SVIPER takes a critical hit. Onboard System(s) destroyed SVIPER New SVIPER destroyed CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with TLC4 CORONA Pricked Finger hits BYONET Spearhead with IC4 SVIPER New SVIPER hits BYONET Spearhead with LC4F SVIPER New SVIPER hits BYONET Spearhead with LC4F Edited May 31, 2008 by markb50k Link to comment Share on other sites More sharing options...
Turgidson Posted May 25, 2008 Share Posted May 25, 2008 (edited) As far as I have understood, fighters will "break" when they get too close to their target - that's maybe the reason why yours flew away. Regarding "theoretical" firepower and observed experience, it seems that weapons won't deal as much damage as what their stats say - that's what I've seen in my own battle as well, the enemy took more hits to be destroyed than I had anticipated. Maybe there's some armour or "shield absorption" to factor as well, which might mean that the damage done to the hitpoints stats is somewhat reduced compared to the "raw" firepower value. Having more information on how the calculations are run would definitely be useful. As for the Bayonet, with what I'm throwing at it I'd doubt it'll survive - thanks for softening it a bit, anyway. ;D Edited May 25, 2008 by Turg Link to comment Share on other sites More sharing options...
Idle_Scholar Posted May 25, 2008 Share Posted May 25, 2008 See I think your probably right on both counts there. At a guess it's not multiplying the damage, either by the shot/cycle number or by the number in the LC4 (or whatever it is). And the same with the fighters breaking. But I'm still confused why the Corona didn't use its 2 LC4 batterys. Also there's the fact that the log (on both occasions) didn't record any damage taken by the Bayonet, though that may be because my report isn't privy to that information. The Bayont is the Spearhead if the owner wants to add their info on the matter. Link to comment Share on other sites More sharing options...
Turgidson Posted May 25, 2008 Share Posted May 25, 2008 But I'm still confused why the Corona didn't use its 2 LC4 batterys.That's because these 2 LC4 fire towards the rear. That can be seen on the Unit Characteristics screen, by clicking on the different "W" slots (bottom left of the picture). Also there's the fact that the log (on both occasions) didn't record any damage taken by the Bayonet, though that may be because my report isn't privy to that information.When I select the BYONET on the "Enemy" screen, I can see its damage - its shields are nearly down, so yes you did harm it quite a lot. Sounds like there's quite some stuff that isn't documented yet, once Bern will have written the readme things should be easier to understand... Link to comment Share on other sites More sharing options...
Idle_Scholar Posted May 26, 2008 Share Posted May 26, 2008 (edited) Ahh I get the weapons display now. I missed the writing in the top right. I also didn't realise about the selectable enemy display. I guess eventually it'll appear when you click on an enemy ship on the map, as opposed to having to select it form a list. Edit: Holding down ALT+LMB selects enemy units for perusal Edited May 26, 2008 by Idle_Scholar Link to comment Share on other sites More sharing options...
markb50k Posted May 26, 2008 Share Posted May 26, 2008 wow, sorry didnt see this thread. good discussion. Some tidbits: when a weapon hits, it does a random percentage of its damage. so the full damage amount doesnt apply. Also, instead of constantly tweaking damage amounts for certain weapons, i have a single damage_modifier which is currently set at 0.5, which i use to globally affect damage rates, given users complaints of battles taking too short, i modified damage down to make it accumulate slower giving ships more time to live and the owner more time to make tactical decisions. i also tell you that you hit another ship if at least one of the weapon shots in that weapon (i.e. LCs shoot four times a cycle). if one of those hits, i tell you, but i dont keep telling you if the 2nd 3rd 4th etc. hit, to keep the battle reports at a reasonable length (bandwidth considerations). you can ALT click on any enemy to see where their shield and hull damages are at, that the only realistic feedback you should be able to get anyway. fighters DO break away from their attack and then return, usually when they get within 500m (whatever the BRKRNG is in their specs) of their target, then they fly away until the ATKRNG in their specs, then turn to attack again. Cap ships just eventually sit at the ATKRNG and dont close the distance. Its my attempt at putting in automated tactics. Link to comment Share on other sites More sharing options...
Aroth Posted May 26, 2008 Share Posted May 26, 2008 Well, I'm the former Bayonet owner... not bad for complete autopilot apparently! I haven't been able to log in at all this weekend, so I'm afraid I can't provide much additional data. Oh, btw, Skyblazer if you read this... can you please stop camping my starting sector? The warzone is ten sectors north of here Link to comment Share on other sites More sharing options...
skyblazer Posted May 26, 2008 Share Posted May 26, 2008 lol, I thought it was the combat sector. But yeah ive not been able to play all weekend generally because my email doesn't like it when i get the entire galsim .zip emailed out to me for some reason. It complains of to many files to scan... Anyways i'll be leaving once my TIE Advance are done with ur bayonet Link to comment Share on other sites More sharing options...
Turgidson Posted May 26, 2008 Share Posted May 26, 2008 (edited) I was wondering where everyone was, it's quite empty in the sector. ;D I have a question on how the battle turn is run: I suppose the units get processed sequentially, and that if a unit is dead before its turn it won't fire ? In which case, who gets to "fire first" would have some kind of advantage... A system where all "fire" orders are processed for everyone (including the "just killed"), then destroyed units get erased, would be fairer. About "automated tactics": would be great if the user were able to set his choices... this might not be easy, but would enhance the game for, well, the nitpickers that look into every detail. PS: it might be interesting to test higher numbers, just to see "if the engine is able to handle that". PS2: the mixing of tactical scale means that, at any case and to keep this manageable, "scale" for each player will necessarily be smaller than the former EvR one. Not a "good" or "bad" thing, but I feel this will be different. Considering how much care would likely be needed to nurse a single fleet, managing a whole system might be very time-consuming. Unless a lot of scripts are made available to help automate orders. Edited May 26, 2008 by Turg Link to comment Share on other sites More sharing options...
Idle_Scholar Posted May 26, 2008 Share Posted May 26, 2008 (edited) I was thinking about fighter tactics and started to formulate something. Basically I'd have it split into three. 1) The ship advances into range and just sits there, adjusting for movement of its target but otherwise remaining stationary. Like the defult Cap-Ship behaviour. 2) The ship conducts strafing runs, where it flies at the target, then past it, then turns around and repeats. This is a bit like what fighters do now, but currently this simply leads to a trail of dead fighters, when they'd get more shots off by sitting there and firing. If it can be set up that they are much harder to hit given a high relative speed between target and ship this would be worthwhile. 3) Turning dogfight mode (or really cool fights). Basically two groups of fighters fly at each other, select targets then try to get on each others tail. I've got some good ideas as to how you could code this but before I work out more details how is movement done? Do ships turn at the start of each time unit then fly forwards at whatever speed they select, or does it take one 'pip' to turn, then another to move, or can it turn as it moves (producing a circular trajectory), and do they have acceleration or is it instant? I'm also assuming the game engine already calculates the vector between an attacker and a target. Oh and finally how does it work out priority between ships or is it all simultaneous? Sorry for all the questions but I've done a bit of C++, a tiny bit of Java and plenty of maths and I think I can come up with something really sweet. Edited May 26, 2008 by Idle_Scholar Link to comment Share on other sites More sharing options...
markb50k Posted May 27, 2008 Share Posted May 27, 2008 choosing tactics is something I can look at after i speed up the end turn processing. FYI, during the combat phase, even ships that are destroyed that cycle get a chance to fire. I just made a change in the code to allow for that. Previously if a ship was killed before it got to fire, it didnt, but now it does. Link to comment Share on other sites More sharing options...
Deathwatch Posted May 28, 2008 Share Posted May 28, 2008 It would be quite interesting to allow for more detailed orders for fleets (some default formations come to mind), but preferably those that can be used unattended as well. As for ship target priorities, could it be given defaults like "fighters", "small cap ship", "medium cap ship", "large cap ships" - this would allow for ships to prick their priority targets first, so you won't get a ship equipped with a lot of heavy turbolasers to use these on fighters, while a small anti-fighter ship like a lancer or so would go fire at the enemy star destroyer in stead of the fighters As for the combat sector, after having figured out some of the controls of GalSim, I guess I can move that way as well. I always wanted new ships Link to comment Share on other sites More sharing options...
skyblazer Posted May 29, 2008 Share Posted May 29, 2008 Hey Cracker jack how much damage did ur bayonet take anyways? My fleet was destroyed while i was asleep which is generally when everything happens for me these days so i don't know. I know my fighters knocked about 8% off ur shields and my gunship was attacking for a fair while while ur ship was picking on one of my 2 heavy gunships who never got into firing range. Link to comment Share on other sites More sharing options...
Aroth Posted May 29, 2008 Share Posted May 29, 2008 They Bayonet was down to about 3% shields after the last ships was destroyed. The fighters didn't add much, but CGUN was plunking away for a good while, and the second CHGUN survived long enough to get into firing range and get a few licks in before being taken out. For some observations on my side: First, HTLBs seem to be firing twice as often as they're supposed to, according to the weapons part of the website. Both batteries were firing every cycle. On the other hand HTLBs are *incredibly* inaccurate. Not once in that entire battle did both HTLBs hit at the same time, even when firing at the CGUN which was close enough for the ships to be exchanging LC fire. Every cycle one missed and the other *maybe* hit. I'm not sure exactly how hit detection works, but currently the fact that HTLBs have such a long range seems rather useless, since they seem to miss consistently at their max range, while TLCs never seem to miss at all once they're in range (both targeting capital ships) Link to comment Share on other sites More sharing options...
skyblazer Posted May 29, 2008 Share Posted May 29, 2008 It was interesting watching that fight though even though I only saw some of the fighter combat and not much of it at that though. but reading a lot of it and seeing the amount of damage just 12 TIE Avengers did to ur shields which was a total of 6% of ur shields they took out which if u do the maths is a fair amount of damage for just 12 TIE's. The Cloakshapes did bugger all being to slow, having weak shields and their weapons being no where near as good as the Avengers. So just 24 of them got majorly out did by just the 12 Avengers. A few interesting things I noticed about the cap ships side of the battle from what i read in the reports was that Heavy gunships aren't that worth it but normal gunships seem to atleast be worth their value in points. Long before they got into firing range they had their shields reduced down to 66% and that was on both of them with the Blazing Star being destroyed before Blazing Fire ever made it into range however Blazing Speed my little gunship just got in there and peppered that bayonet for all its worth. All in all my fleet was out classed, due to a lack of range and durable ships. My New fleet has had some corrections made to it to work better in this combat system Link to comment Share on other sites More sharing options...
Idle_Scholar Posted May 29, 2008 Share Posted May 29, 2008 Some of the gunship weakness could be down to not having missiles equipped. Link to comment Share on other sites More sharing options...
markb50k Posted May 29, 2008 Share Posted May 29, 2008 (edited) my comments: - yes, the lack of missiles definitely affects the combat, which should be something considered from now on. but with all of the salvage sitting around, you can scoop up some weapon material to restock your magazines. - ill check the HTLB fire rate but i am positive it is firing every other cycle.EDIT: yup it was screwed up, HTLBs will now fire every other turn - any other opinions on HTLB accuracy? I have been thinking of making them a bit more accurate. Edited May 29, 2008 by markb50k Link to comment Share on other sites More sharing options...
Aroth Posted May 29, 2008 Share Posted May 29, 2008 I suppose it's possible that the HTLBs are firing every other cycle, alternating battieres, and the report.txt just reports the non-firing cannons as automatic misses or something... but that seems unlikely. In my report file, it showed both batteries firing every cycle, with maybe 1 hit for every 4-5 shots for most of the engagement against the Heavy Gunships. If you drop their fire rate down to what it's supposed to be, 1 shot / 2 cycles, then the accuracy, imho, really needs a boost, or they'll be pretty much useless, as you'ld only see 1-3 hits every turn from a Bayonet's TLs, compared to something like the 20 hits / turn the CGUN's TLs was doing. Link to comment Share on other sites More sharing options...
markb50k Posted May 29, 2008 Share Posted May 29, 2008 CJ, read above, the fire rate of HTLB was messed up, its fixed now. Also, FYI, i adjusted the damages and ROF for fighter based weapons. They were insanely deadly so I tweaked them way down. I have not updated the website yet, but these were the changes: for all BCF, LCF, and ICF damage divided by 3ROF divided by 2 so overall their weapons are 6 times less potent. They should be good at killing eachother but not so good killing big ships. Link to comment Share on other sites More sharing options...
Aroth Posted May 29, 2008 Share Posted May 29, 2008 Ahh, you edited while I was posting Link to comment Share on other sites More sharing options...
markb50k Posted May 29, 2008 Share Posted May 29, 2008 i upped accuracies for the following weapons TLB and HIC went from accuracy of 1 to 0.75HTLB went from accuracy 1.5 to 1 Link to comment Share on other sites More sharing options...
markb50k Posted May 29, 2008 Share Posted May 29, 2008 We have a pretty good dogfight going on between a bunch of TDs and ACTISs. The ACTISs looked like they got into firing position first and killed a few TDs, but now it seems to be going both ways. The view of the battle is very chaotic. Its awesome! Link to comment Share on other sites More sharing options...
Turgidson Posted May 29, 2008 Share Posted May 29, 2008 i upped accuracies for the following weapons TLB and HIC went from accuracy of 1 to 0.75HTLB went from accuracy 1.5 to 1 Not sure that upping the precision of HTLBs is the best thing to do... don't forget we mostly have frigates, and Heavy TLBs could/should miss these regularly, especially from some distance. Against much larger ships (the typical MC80 or ISD), they should/would hit much more often. As for weapon's damage, maybe the capship LC and TLC would now be too high, after fighter-based weapons got toned down... they die very quickly to these, and very slowly to their onboard weapons, so I'm not sure interceptors are a good antifighter defense anymore compared to high LC/TLC capships.So another solution (trying not to crush the balance) might be to add an "armour" or "penetration" rate into the calculations, with higher grades absorbing a higher fraction from low-energy weapons - fighters would have lowest rate, so all weapons would affect them the same, regardless of energy. This would make fighter's weapons as deadly to each other as capship-based weapons are, while the efficiency against capships would stay under control. Link to comment Share on other sites More sharing options...
markb50k Posted May 29, 2008 Share Posted May 29, 2008 the accuracies were pretty bad already for the HTLBs, so their improvement still makes them alot worse than TLC and LCs, but maybe we should run some tests. Position MNFRGs at around 28KM from each other, not in ATTACK mode so they dont close the gap, and let them fire at eachother. See how often they hit. IMHO if they hit around 50-75% of the time then the accuracy is good. As for fighter weapons, I saw how quickly those TDs destroyed those SACHN's earlier, like a couple of cycles, so I went with this. Now, lets test it out to see how it goes. Your TDs are making mincemeat of the ACTISs in that last turn, so they can be effective anti-starfighter platforms. I welcome your thoughts. The penetration idea has merit but I would like to get more combat reports. Link to comment Share on other sites More sharing options...
Turgidson Posted May 29, 2008 Share Posted May 29, 2008 (edited) Reading from the logs, I got a few kills from the Corellian Hammerhead; and I guess my fighters didn't start on the best spot. I even wonder if the ACTISes didn't perform some jump to start in the better position - the TDs had the ACTISes as priority targets, and were there for a few cycles already... so if both groups had been closing by patrol they'd both have gotten kills in first pass. Note: as I had to go to sleep and the turns were put to a temporary halt, I had to queue orders and couldn't tell them "jump XX distance YY direction from last observed position of unit something". Giving "relative" orders would be interesting, but not necessarily easy to describe. That would go into the direction of scripting, something that I think would be useful to this game, especially if some of such "behaviours" could be saved and reassigned. My own feeling is that tactical jumps are a huge advantage, and you'd better be online while your opponent is not so you can ensure your units starts in the better position. I've been on both sides of this, actually. With different time zones, it's going to be hard to avoid this fact... There aren't many solutions that I can see: make battles so long that both people will get the chance to be online while the other guy is not (but who strikes first...); make tactical jumps harder/less easy so that fleets have to close in patrol and these tactical jumps will be less devastating; allow more extensive scripting so that players can "code" a kind of "AI" that would react closer to what they'd do in the same situation... Ah... and since we can't always be online, having the previous turns "saved" on the server could allow people who went to sleep, to see what's been going on previously. Better for the analysis, than logging in and seeing lots of events have happened but not knowing exactly what... Edited May 29, 2008 by markb50k Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now