Plugin for "TORPEDO-ONLY" HPs
-
@adoxa
You allready managed to have more Shipclasses to be displayed at the shipdealers.
Althogh its not supported by FL for a “REAL” SHIP-CLASS regarding class-restrictions
of equipment and such, its more than GREAT to have this plugin of yours.
So first of all I would like to say a HUGE THANK YOU for this one, aswell as for all the other plugins !!!Question:
Is it possible to have a plugin that enables the display of an EXPLICIT “TORPEDO” only Slot?
`Cause in FL you are able to define in shiparch.ini via
hp_type = hp_torpedo_special_1, HpTorpedo01 (meaning only Torps are mountable)
OR
hp_type = hp_torpedo_special_2, HpTorpedo01 (meaning only CDs are mountable)
While the later only shows “Cruisedisruptor” as Text of the slot
hp_type = hp_torpedo_special_1 will always display “Torpedo/Cruisdisruptor”
regardless if the hardpoint is enabled to carry a CD.
Just altering the IDS-Text to “Torpedo” leads to a problem if you define
hp_type = hp_torpedo_special_1, HpTorpedo01
AND
hp_type = hp_torpedo_special_2, HpTorpedo01
cause the Title will still be “Torpedo” only although it is able to carry a CD aswell.
But since there is a fundamental problem to have FL accepting a NON-HARDCODED HP-Type…
I think this would be the main problem when it comes to building a TORPEDO-ONLY plugin. cause this plugin must be reading further entries to realize if there is a CD enabling codeline in shiparch for this particular slot.Greetings
J.R.P.S.: While I was thinking about it…
How about a plugin that uses an extra codeline like:
“hp_text = IDS (or maybe the text itself), hp_torpedo_special_2”
configurable for each single [ship]-block ?
This way we would be able to override the limits of ANY slot-text.
But… maybe these are just brainfarts… since I´m not familiar with plugin-coding at all… Nevermind. -
freelancer.exe 186C8C 0FB68808705800FF248D->83FE24750683FD017501 FC6F580033EDEB0CBD01->4B0FB6A808705800EB0A = display Torpedo-only hardpoints PART 1 ~adoxa freelancer.exe 2152EC 1521i->978i = display Torpedo-only hardpoints PART 2 ~adoxa ```The logic is that a hardpoint will display the highest available to it. Since Torpedo is 36 and Cruise Disruptor is 35, Torpedo wins when both are present. The above patch detects that Torpedo-only is present and uses the [c]hp_torpedo[/c] entry, redirected to a **Torpedo** string (as 1521 is also **Torpedo/Disruptor**). It doesn't fix the description, though, that's a whole other problem. P.S.: :) That sounded like a whole lot of work for little result.