Discovery Gaming Community
FLHook Improvements & Features - Printable Version

+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Discovery Development (https://discoverygc.com/forums/forumdisplay.php?fid=7)
+--- Forum: Discovery Developers Forum (https://discoverygc.com/forums/forumdisplay.php?fid=183)
+--- Thread: FLHook Improvements & Features (/showthread.php?tid=117808)

Pages: 1 2 3 4 5 6 7 8 9

RE: FLHook Improvements & Features - Ponge - 07-19-2014

A sugestion on /setmsg:
If a #t tag is in <message> this tag will be replaced with the current target name. If a #c tag is in <message> this tag will be replaced with your current map grid location.

Could be a function added similar to #t tag, but with NPC bases? So the name of the targeted NPC base is added to the message.

RE: FLHook Improvements & Features - Alley - 07-26-2014

Changelog 26/07/2014

Quote:=Playercntl=
TLAGSNET
- Implemented restricted access policies (for LH, maybe others later)
- Added values in cfg for restricted access
- Removed mentions of the system parameter. I never managed to get a decent solution working.

Quote:=FLHook=
- Implemented .bob admin command. Usage is .bob shipname


RE: FLHook Improvements & Features - Alley - 07-27-2014

Changelog 27/07/2014

Quote:=Playercntl=
HYPERDRIVE
- Implemented hyperdrive jumping restrictions. If a player is flying a ship defined in the restriction list, he will not be able to jump. This does not prevent the rest of the group from jumping to prevent trolls.
- Implemented .lrs admin command, lists ships that are not allowed to jump.
- Implemented jump.cfg section to define which ships are not allowed to jump.

[Image: kBV40bT.png]
[Image: y7vQItf.png]

Quote:=FLHook=
- Adjusted .bob harassment


RE: FLHook Improvements & Features - sindroms - 07-27-2014

Could it be possible to mix the #t usage with the /allowdock command?

RE: FLHook Improvements & Features - Zayne Carrick - 07-27-2014

Quote:=Playercntl=
HYPERDRIVE
- Implemented hyperdrive jumping restrictions. If a player is flying a ship defined in the restriction list, he will not be able to jump. This does not prevent the rest of the group from jumping to prevent trolls.
- Implemented .lrs admin command, lists ships that are not allowed to jump.
- Implemented jump.cfg section to define which ships are not allowed to jump.
It's already implemented on server? Or just possibility for that created?

RE: FLHook Improvements & Features - Alley - 07-28-2014

(07-27-2014, 09:10 PM)sindroms Wrote: Could it be possible to mix the #t usage with the /allowdock command?

I'll look into it

(07-27-2014, 09:14 PM)Zayne Carrick Wrote: It's already implemented on server? Or just possibility for that created?

ATM no, but be aware that some things might be implemented and not used.

RE: FLHook Improvements & Features - sindroms - 07-28-2014

(07-28-2014, 05:57 AM)Alley Wrote:
(07-27-2014, 09:10 PM)sindroms Wrote: Could it be possible to mix the #t usage with the /allowdock command?

I'll look into it

Also the /givecash command having that option would be nice.

RE: FLHook Improvements & Features - Alley - 08-07-2014

Updated first post todo, UPGRADE NOW.

RE: FLHook Improvements & Features - Sabru - 08-08-2014

(07-13-2014, 02:42 AM)Alley Wrote: - Rewrite techcompat exemptions to fit the new system discussed in aerelm’s deep dark skypechat

wat? MOAR INFO PLEASE!

RE: FLHook Improvements & Features - Ponge - 08-08-2014

Would it be possible to make a feature in the POB plugin, so owners could et a primary repair comodity out of the three? Right now, Reinforced Alloy is used a the prim commodity, to repair wear and tear; the other two are used in case of an attack, if necessary. What I'm looking for, is a command/option to set Hull Segments or Robotic Hardware as the primary waer and tear repair commodity, so the other two is used only in attacks.

This would make the life of those POB owners easier, who does not have RA close to their base, but they have Robotics or Hull Segments not far.