Beam Command
-
so, does anyone know of a way to 100% crash the server with it?
Im trying to figure out whats going on but have as of yet not managed to cause a single crash with it
-
so, does anyone know of a way to 100% crash the server with it?
Im trying to figure out whats going on but have as of yet not managed to cause a single crash with it
Beam to Manhatten (Li01_01_base) and undock. That will usually do the trick.
-
ohh do a few beams without reloading your character.
It also works great if someone else is beaming as well at the same time without pressing f1 after the beam.
You do have to undock the station and do a other beam tho. -
not working
Can you test it on a fresh local server and tell me the steps needed to crash it?
I just had 2 clients jumping to different bases without ever reloading with F1 and no problems at all
-
nevermind, i just got a crash (yay) lol
-
100% crash?
im not sure, but you can try.
1.in li01 space, enter command to beam you go to other system like li02_01_base
2.undock.
3.when others(player or npc , im not sure) do something, server will crash.
4.then server restart and you login, you will found you are in the sun (pos 0,0,0). -
i think i have an understanding of where the problem is⌠the ForceLand function is not serverside only, that means it relies on the client to actually âdockâ at the destination base, and i think throughout this process, sometimes it gets somehow out of sync⌠well, whatever.
Anyways, I solved it with emulating an F1 process without kicking the player, it will be in the next version of the Plugin FLHook.
-
Outstanding!
-
Hello, DBoy here, was wondering how the progress was doing on repairing the beam command? Seems we were a bit surprised with it when giving it a shot on Discovery when it would crash, so were a bit cut off at the knees here. Just curious. Thanks.
-DBoy
-
It is supposedly fixed in the latest FLHook Plugin version, in the way I described it here.
-
I tried to get as much info as I could get on the beam crashes:
- we have 2 different admin characters, both with superadmin rights, both tried to beam themselves (.beam <name>and .beam$ <id>). For one itâs working perfectly, for the other one it crashes the server
- both characters were in space when doing that
- we tried with both <128 and >128 players online - behaves all the same
- we tried ingame/from flhook window/from putty (socket connection) - behaves all the same
- so we thought itâs character related, but even on new character (same account) it crashed. The guy is now getting a fresh new accoung and weâll try it there as well. Iâll keep you informed.
- we migrated from flhook 1.5.6 (Leipzig City) yesterday and both accounts were created under the old version (but I guess that has nothing to do with it)
- we are using your multithreading patch (again, probably not related)
- we have set up the anti-F1 timer to 59 seconds (this maybe be related to your solution)
Any ideas what to test more or what logs to go through? I didnât find anything in the flhook logs. If you have any ideas or need any more info, just tell meâŚ
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?
Thanks a lot for help!
Michal</id></name>
-
Just to clear that up. you do run the latest FLHook Plugin version, right?
-
To be honest I am not 100% sure, as Dboy sent it to me yesterday and he hasnât come online yet. Iâll confirm the version he sent me as soon as I spot him. Sorry if thatâs the problemâŚ
FLHook.dll has 405,504 bytes and modified date is July 31, 2008, 6:29:34 AM.
Console on astrtup says: âWelcome to FLHook Console (1.5.8 plugin)âAnd to add info to the previous even creating a fresh new account didnât work, beaming still crashed the server.
-
yeah thats the latest. anyways:
we have 2 different admin characters, both with superadmin rights, both tried to beam themselves (.beam <name>and .beam$ <id>). For one itâs working perfectly, for the other one it crashes the server</id></name>
I remember reading about that you are renaming characters with Ioncross.
The Ioncross rename function should really not be used, since it messes up the charfile.
This may cause problems with FLHook and/or FLServer on multiple occasions.
The fixed beam command also doesnt work for those renamed chars the way it should, since it cannot emulate the F1 process.But if this also happens with completely new characters, then maybe the beam command is still buggy.
-
Yeah, weâre about to stop with IFSO renaming. Weâll try to test it via FLHook as renaming is quite important to us as an RP serverâŚ
What I donât get is that beaming works for all admins (none of them renamed) except 2 guys and for those it canât be fixed even by creating brand new accounts.
If there are any scenarios we should test or more info you would need, just let us knowâŚthanks
-
Yes, those 2 guys: When does it crash? Directly on typing the command or after undocking again?
Also: After executing the command, it says âOKâ. Right before that, there should be a âNew Player: xxxâ message, just as if you would have pressed F1 or just logged in. Check if its there.
If its not, its very likely that those chars have been renamed with Ioncross.
If its there, the command may still be buggy -
⌠maybe thatâs not an flhook / beam problem.
Maybe writing the player file or indexing the players or ⌠.Reading this remembers me, that i got the impression
that a player can crash the server by deleting a char
and creating a new especially with identical name.(NOT SURE ABOUT)
PS. In any case: M0tahâs âkick after beamâ seems 2 fix the prob 4 beaming.
-
OK, there we go (forget about the 2 guys, just a coincidence) - beaming on a base in the same system crashes the server.
We tested:
NY (Manhattan) -> Gamma (Tripoli) âŚOK
Gamma (Tripoli) -> Alpha (Ibiza) âŚOK
Alpha (Ibiza) -> NY (Manhattan) âŚOK
âŚ
NY (above Manhattan) -> NY (Manhattan) âŚcrash
Gamma (Tripoli) -> Gamma (Crete) âŚcrashThis was done under the fresh new account (not renamed).
Sorry if itâs a known issue, we didnât know and therefore came to a wrong conclusion. Now that we know we can avoid it.
-
OK, there we go (forget about the 2 guys, just a coincidence) - beaming on a base in the same system crashes the server.
We tested:
NY (Manhattan) -> Gamma (Tripoli) âŚOK
Gamma (Tripoli) -> Alpha (Ibiza) âŚOK
Alpha (Ibiza) -> NY (Manhattan) âŚOK
âŚ
NY (above Manhattan) -> NY (Manhattan) âŚcrash
Gamma (Tripoli) -> Gamma (Crete) âŚcrashThis was done under the fresh new account (not renamed).
Sorry if itâs a known issue, we didnât know and therefore came to a wrong conclusion. Now that we know we can avoid it.
It wasnt, until now. Thanks for testing, will see whats going wrong there.
10/25