Beam Command
-
Too lazy to look up whats exactly the problem, so I will skip the F1 emulation when beaming to a base in the same system. This has never caused issues anyway so far.
Will be in the next FLHook Plugin version, gonna release it today.On another note our anti-cheat was using functions like getclientid and enumeqlist in the 1.5.6LC version. First one just returning client id, the second one returning id and archid of equipment of a given character. Are there any plans on including those or should we plan to include them in a plugin?
No, that should indeed go into a plugin. The reason for this is that added functionality should always go into plugins.
The only stuff I change in the FLHook Plugin version is fixing/optimizing/enhancing stock FLHook features. -
On another note our anti-cheat was using functions like getclientid and enumeqlist in the 1.5.6LC version. First one just returning client id, the second one returning id and archid of equipment of a given character. Are there any plans on including those or should we plan to include them in a plugin?
No, that should indeed go into a plugin. The reason for this is that added functionality should always go into plugins.
The only stuff I change in the FLHook Plugin version is fixing/optimizing/enhancing stock FLHook features.OK, then I’ll try to push Korrd into looking at the plug-in tutorial… After that it shouldn’t be such a big deal to do some copy&paste…
-
I’m looking at the tutorial now.
has the plugin be written on C++, or can any other languages be used? if no, i will then learn C++ again, as it’s been like 10 years since I last used it.What i am looking forward to write is a name-change automation, with a web front end that will load all the requests on a datafile, and a server side program that reads the file and does the namechanges with the hook. . .
