-
Posts
1,615 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by ZEODE
-
Hi, sorry I didn't see this request. Are you using plugin named Prevent Looting? People have reported this issue and using that plugin. If you are using this plugin, just add the shortname "marketplace" into the excluded items list in the config and enable it.
-
No worries at all, thanks for being cool about it.
-
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
-
@RustyW and @Neighigh, so sorry for this error, indeed I am an idiot. I found the error which was my fault. It wasn't anything you guys were doing wrong. Next and all future updates will work seamlessly now I have identified the issue. Thanks for your patience and help.
-
- 399 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 16 more)
-
Changed Status from Pending to Work in Progress
-
Yes it works when plugin loads from scratch, but when trying to copy the config on an update it throws and error because you have some invisible characters in your profile name, maybe put in by the editor you use. I will show you what I mean when back at the PC.
-
Hey, I did some testing and found that you have invisible characters in your profile names on HeliSignals. "直升机(精英)": { "Helicopter display name": "直升机(精英)", There is invisible characters and the chinese characters seem to break the plugin too. Did you get errors when you updated the plugin when it loads?
-
OK, so I already knew what the error means, but I couldn't understand it before, as it shouldn't throw that error unless it has an issue reading from the JSON file. I have done some testing, and the only time I can reproduce the error (without missing or blank profile names) is when there are special or invisible characters within the Profile Name. For example, I tested with another users config file which has some Chinese characters in the profile name, as well as two invisible characters and this causes it to throw the same error you are seeing. So I can test a little further, would you be able to send me your current config files over so I can test with you guys config also.
-
I'm sorry you are having these issues guys, I will look into it to see if I can see anything that may cause it. But understand that I do test it compiles and auto updates the config file before I release it. So it's very hard to find an issue when I cannot reproduce it at my end. But I will look over it and see if I've missed anything.
-
I’ll have a look later and try different scenarios to see if I can reproduce.
-
Yup, I’ve done that. I always do that before I release the update.
-
hi, sorry your having this issue. You must have an error in the config or a character that shouldn’t be there. Otherwise it will update just fine. I always make sure before releasing an update that it updates the config. Without seeing the old config I can’t tell you where the error could be.
-
Currently that isn't possible, but I could add this as an option in a later release. You could use this config option instead: "Map Scale Distance Away to Spawn Helicopter (Default: 1.25 = 1.25 x Map Size Distance)": 1.25, This sets the distance from the caller that the heli spawns, so reducing this number makes it spawn closer. 1.25 is default so it spawns out to sea and flys in. But you could make it spawn closer to the player, over the land. 1.0 = map width distance, 0.5 = half map width distance etc. This way it takes less time to fly to the player.
- 399 comments
-
- #helicopter
- #helicopters
- (and 16 more)
-
- 399 comments
-
- #helicopter
- #helicopters
- (and 16 more)
-
hmmm, not sure why I decided on these HP numbers. You are correct, vanilla heli HP is 10k, rotor HP is correct though. I’ll change the default config options on a future update and advise changing in the change log unless people have their own custom numbers set. https://rustlabs.com/entity/patrol-helicopter
- 399 comments
-
- #helicopter
- #helicopters
- (and 16 more)
-
Changed Status from Pending to Closed Changed Fixed In to 1.0.8
-
Changed Status from Pending to Not a Bug
-
I will look at it when i have a little more time yes.
-
A couple of people have had a similar error when trying to update to 1.0.7, it is something to do with a config value that is incorrect. Please backup your existing config, delete it from the server and then load 1.0.7 again. Then go back in and change the default config to match the values you want.
-
- 399 comments
-
- #helicopter
- #helicopters
- (and 16 more)
-
Changed Status from Pending to Not a Bug
-
what is the error message? Also please post your config file
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.0.7
-
- 72 comments
-
- 1
-
-
- #rust
- #marketplace
-
(and 7 more)
Tagged with: