Adoxa's "RandomJumps" plugin error
-
My RandomJumps.ini like that:
[RandomJump] object = Un03_to_Em02_hole goto = Ai01, Ai01_to_Bh01_hole, 1 goto = Ai01, Ai01_to_Dj01_hole, 1 goto = Ai02, Ai02_to_Je01_hole, 1 goto = Ai02, Ai02_to_Co01_hole, 1 goto = Dj01, Dj01_to_Ai01_hole, 1 goto = Em02, Em02_to_Un03_hole, 1 ;original jump goto = Em04, Em04_to_Re03_hole, 1 goto = Je01, Je01_to_Ai02_hole, 1 goto = Nr03, Nr03_to_Re02_hole, 1 goto = Nr04, Nr04_to_Un01_hole, 1 goto = Bh01, Bh01_to_Re04_hole, 1 goto = Bh01, Bh01_to_Ai01_hole, 1 goto = Re02, Re02_to_Nr03_hole, 1 goto = Re03, Re03_to_Em04_hole, 1 goto = Re04, Re04_to_Bh01_hole, 1 goto = Co01, Co01_to_Un04_hole, 1 goto = Co01, Co01_to_Ai02_hole, 1 goto = Un01, Un01_to_Nr04_hole, 1 goto = Un03, Un03_to_Em02_hole, 1 goto = Un04, Un04_to_Co01_hole, 1Only the “goto = Em02, Em02_to_Un03_hole” is original jump, the other jump hole is not original jump, do I make a mistake?
-
Experienced the same issue when I use the Server-machine as client.
According to this, please read the appropriate section in my pluginlist:
Pluginlist regarding settings(Meaning do NOT provide a randomjump.ini clientside for Multiplayer !!!)
Greetings J.R.
-
Although this seems to be the wrong topic anyways…
My server is running the “old” NON-Plugin FlHook 1.67 and there is an option to do item-restrictions via the settings of it.
But I presume u are using the Plugin-version of FlHook.
I´m not familiar with it … so I have to say: sorry but I don´t know…Greetings
J.R. -
Yes, how do you know I use the Plugin-version of FlHook?
I was tell my user to delete the clientside of Randomjumps.ini file, but still can’t slove the problem.
About the NON-Plugin FlHook 1.67, I’m very like its function, but because it can’t do some function I want, so I change it to Plugin-version of FlHook.
-
When I in the A system go into the jump hole, then I come to the B system, the system show me of info is C system, but actual I was stay in the B system.
A quick test with Solo Multiplayer seems okay, but I did only test one alternate destination (redirecting New York->Colorado hole to California, and California->Texas hole to New York). It sounds like the client is still seeing the original system, which suggests you haven’t added the DLL to the client (dacom.ini).
