-
Posts
701 -
Joined
-
Last visited
-
Days Won
12
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by jtedal
-
Hi. Forgive me for my absence. Please tell me, have you been able to solve your problem?
-
Yes- 206 comments
-
- 1
-
-
- #jtedal
- #mad mappers
- (and 7 more)
-
During this month
- 206 comments
-
- 1
-
-
- #jtedal
- #mad mappers
- (and 7 more)
-
CodeLock - access to the wagon movement. Yes, at the moment any player can change the frequency of the wagon , but this will be fixed in future updates- 129 comments
-
- 1
-
-
- #jtedal
- #mad mappers
- (and 10 more)
-
@Dead Nasty @SocietyTime I am sorry that you are faced with such a problem, but unfortunately it cannot be solved 100%. Any program provides that it will be completed by the correct, otherwise the user may encounter problems. In this case, the program was completed incorrectly and of course this led to a malfunction. If you change the hosting that will not break, then you will be able to return my plugin back to the server and you will not have such problems
-
So far, it is technically almost impossible to do this, so we will wait for either the appearance of carbon for the client part of the game or changes to the existing code.
-
Plugin causes "inside terrain violation" player kicks since March 7th force wipe
jtedal replied to miniMe_rust's Support Request in Support
@tenzu You can temporarily disconnect the markers from the zone so that these problems do not occur There is no exact schedule, but I think it will happen during April -
I haven't tested it, but it should work well, but even if there is some problem, I will solve it
-
It's a good idea. I will do it in one of the future updates
- 129 comments
-
- 1
-
-
- #jtedal
- #mad mappers
- (and 10 more)
-
Of course
-
In this case, there is no error in the plugin. For correct operation, your server must be rebooted using standard methods
-
Changed Status from Pending to Closed Changed Fixed In to 1.0.8
-
Please create a ticket in our discord and attach as much information as possible to solve this problem
-
Plugin causes "inside terrain violation" player kicks since March 7th force wipe
jtedal replied to miniMe_rust's Support Request in Support
Changed Status from Pending to Work in Progress -
Plugin causes "inside terrain violation" player kicks since March 7th force wipe
jtedal replied to miniMe_rust's Support Request in Support
I am currently working on a global update of this plugin and after its release, I suggest you test it again. If the problem persists, I will try to find a solution for it. Once again, I apologize -
Plugin causes "inside terrain violation" player kicks since March 7th force wipe
jtedal replied to miniMe_rust's Support Request in Support
I'm sorry, I didn't mean to offend you, but you can understand me. In 1 year of the plugin's operation, not one person has written that my plugin creates such a problem and I do not see a connection because this error has nothing to do with what my plugin does. That's why I wrote it that way. -
If the player does not have quantity permissions, then he will not be able to have them. There's no point in you doing that.
-
the maximum number of wagons for a player
-
I'll think about it.
- 129 comments
-
- 1
-
-
- #jtedal
- #mad mappers
- (and 10 more)
-
try version 1.0.6
-
Changed Status from Pending to Work in Progress
-
I am going to fix it in the next version
-
Changed Status from Pending to Closed Changed Fixed In to 1.0.3
-
Plugin causes "inside terrain violation" player kicks since March 7th force wipe
jtedal replied to miniMe_rust's Support Request in Support
Changed Status from Pending to Not a Bug -
Plugin causes "inside terrain violation" player kicks since March 7th force wipe
jtedal replied to miniMe_rust's Support Request in Support
The errors have nothing to do with my plugin. I would say that your server was updated incorrectly and some part of it was damaged. I logged into my server today and did not experience any similar problems. Try to completely reinstall your server. This will probably fix the problem.