You can improve your ship with armor, weapons, shields, and thrusters. But skill and tactics determine the outcome of most fights. Even the best equipped battleship can be helpless against small craft that are too agile to hit and too fast to pursue or escape from. It’s recommended to train combat early on using small craft to get a grasp of tactics.
Learn to dodge fire by using thruster (TAB key), randomly changing direction, and strafing (A and D). Quick-docking with lanes and gates (fly to the right spot before pressing F3) will save you long docking sequences. The cruise disruptor keeps enemies from escaping, but also detonates nearby mines, torpedoes, and missiles. Not the biggest ship wins, but the better pilot. Building skill requires practice, and there are many tricks that experienced pilots are willing to teach players who work with them. Combat can also be learned by reading tutorials at discovery.gc or Tutorial Buoys in Connecticut (type /conn while docked to get there).
(10-21-2017, 03:36 PM)sindroms Wrote: Please remember the maximum amount of lines the chat window can display. If you overdo it, you will run into the same issue as pimpship item listings needing dsace.log open all the time to use. The game font resize system also makes anything that is longer than the default chat text limit very hard to display. If the thing requires more than a paragraph, you really have no choice but to use a commodity for it.
The POB Plugin displays its help commands in dialog boxes, it might be possible to transfer that to other help commands.
(10-21-2017, 03:36 PM)sindroms Wrote: Please remember the maximum amount of lines the chat window can display. If you overdo it, you will run into the same issue as pimpship item listings needing dsace.log open all the time to use. The game font resize system also makes anything that is longer than the default chat text limit very hard to display. If the thing requires more than a paragraph, you really have no choice but to use a commodity for it.
That's why it's split up into several subject commands. I think each individual topic is short enough to not bust the chat length in normal font (larger than the current /help command). Would also be nice if you moved your comment to after the commands are listed to keep it oversee-able.
I decided to go ahead and create this. It loads each section from a cfg file and I've also added some dummy sections that can effectively be used to print whatever text an admin would want. I didn't actually check any of the content or w/e as I just C+P'ed it in - more a point to show it works. There are currently a couple of bugs that I'm going to see if I can work my way around (like the weird A being my only way of doing a line break).
I don't know anything about FLHook, but isn't it possible to make the text standard size or a bit larger? Also, maybe use
.
instead of
Â
as a paragraph separator?
If there are any formatting options in FLHHook I could paste them into the posts to make it easier. There seem to be, since the server messages are displayed in different sizes, colors, and even italics or fonts on other servers.
Would be nice to know why devs think its better to have [Helpers] type out this stuff over and over again instead of helping everyone who wishes to help with this.
I think you both deserve MAJOR kudos for all the effort put into this. Why is this not a thing yet? Would probably be a good idea if we're (hopefully) expecting an influx of new players thanks to this, don't you think?
(02-04-2018, 02:31 AM)Quantum~Flux Wrote: Why is this not a thing yet?
A very annoying issue I ran into when developing a bit of FLHook. Ideally, I don't want to submit the above as it looks horrific and noobs won't want to read it all. I would like to format it similar to the laws plugin, but that is being made impossible for the same reason this hasn't been developed any further. To save a long story, remember this thread. This bug prevents large amounts of text being put inside boxes or existing infocards, but only when placed there via FLHook. I would attempt to fix it myself, but the sourcecode for this particular segment isn't public.
While I wait for a fix so I can continue, I am forced to work on other things. When eventually it is fixed, we should have a lot of new FLHook toys to play with all at once.
