Neighigh
-
Posts
496 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Neighigh
-
Mhm we've tried this but the steering is still scaled like it is on water. What caught my eye here was the reduced steering on snow and ice. I was sure when we first got the plugin this wasn't the case but maybe I was imagining things? The speed seems totally fine, it's only the steering scale. -
Thanks @ThePitereq! Best of luck with the health, we really appreciate the effort to release this feature
-
@_senyaaWe've noticed the steering scale config option is affecting them while on land as well as water. I'm sure this wasn't the case in a previous version? I could be mistaken there but I remember the steering being more responsive on ground terrain. The scale is 100% needed for the water steering so I understand the need for it. Any way to make it more responsive on ground terrains?
-
Yup, you can add permission based skills. You can also set it to wipe the skills on map wipes. The plugin naturally removes players permissions when players log off, I think the perms also remove when it's unloaded as well. Very convenient overall! -
I may be misunderstanding a component of the config, can anyone help me out? "Команды для приза | Command for the prize": For this option - the commands we have set up do not execute on wipe day. Players do get a notification message for their rankings, but do not receive the command rewards we try to use. If anyone has success or tips to help us use this correctly, we would highly appreciate the help -
03/03 08:52:14 | Error while compiling: IQBearRide.cs(2193,55): error CS0176: Static member `ItemContainer.Drop(string, UnityEngine.Vector3, UnityEngine.Quaternion, params ItemContainer[])' cannot be accessed with an instance reference, qualify it with a type name instead We're seeing this after yesterday's update. Hope all is well and this isn't too big a fix.
- 1 reply
-
- 1
-
-
Thank you so much for looking into and resolving this - it's hugely appreciated that you took the time to find the issue - you're awesome!
-
I can PM you our config.
-
Thanks, I'll keep a copy of my current config in the event this happens again. Sorry I didn't hang on to it prior to this ticket, I checked to see if I could recover it but it's been overwritten at this point.
-
My config worked without issue in all cases up until the updates. In a compare test, the only difference between my config and the new one was the new lines added and my variables for each option. Adding those lines allowed the config to update without any issue. I'd suggest trying a test with one of your previous versions configs and then switching to the newest .cs.
-
When trying to update to the current version, the config is not updating. This is 3 versions in a row that we had to rebuild the config. Can we please make this a little more user friendly?
-
.thumb.png.a167af6d204c8731865ddb8c7651fe66.png)
@Raul-Sorin SorbanAny chance you'd be interested in adding permission based multipliers for loot found in the containers? Thinking along the lines of offering out .vip perms that multiply the quantity of loot items and size of containers. Thinking globally would be sufficient for us. I can see some interest in being able to include/omit containers from permissions like that though. Mostly interested in this because we use a skill based system and would love to offer players the option to scavenge more loot from containers by granting permissions. -
@ZEODEIs it possible we could also have a loot table variant option? It would be nice to make a loot table list that adds those items to the vanilla drops rather than replacing the vanilla drop list. For us, we'd like to add the possibility of our more elite custom items to the vanilla loot tables. I've seen similar options elsewhere and it's been very helpful. Below is an example of what we're thinking about: "Which loot table should be used? (1 - default; 2 - own; 3 - combine the 1 and 2 methods)": 3 Thanks for all the help lately! You're aweosme!- 413 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
Great system to call helis that matches ZEODE's other plugin, Bradley Drops. Configuration had parameters to control all stats of called patrols along with some well thought out ruling options. Loot tables are simple to configure and players knew axactly how to handle the signals without any prompting. This has been the smoothest 'call patrol to fight me' plugin we've tried! Edit: We've made a whole promo video showcasing ALL our event calls like Bradley Drops and Heli Signals to demo the experience you can have with this. Check it out!
- 413 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
That gets us pretty close I think? I do want other players to be able to aggro helis, but they should need to be within a range where both parties also would have to deal with eachother. With Bradley this isn't as much of an issue because of terrain, but with patrol, it's in the open mostly. Thank you for helping us out with this
- 413 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
I do agree, the skill to hit it at range should be rewarded. We're looking to find an appropriate balance for players that want to 'steal' a signalled heli. If players pay for the heli, or Bradley, we want them to have priority on the aggression, but still allow other players to engage respectfully. A limit on the range to damage the enemies helps us prevent people stealing an expensive called heli/bradley from across the map. Of course we're open to other possibilities that allow players to engage/counter these signals fairly. We don't want to lock the signals to the caller, only reduce the likelyhood of losing their rewards to poachers.
-
Was wondering if we could add a <Maximum Range Players Can do damage to Heli:> option? Actually this would be awesome for Bradley Drops too! This would help me keep players from tagging helis/bradleys from silly distances.
-
Hey just a heads up, making a more expensive respec cost is already possible. We start players by default with a respec cost modifier of 0.1 and every ten levels we up that value until it reaches the 'maximum' amount at 1.0. And thanks to your system, that all goes away on a wipe too!
- 1,362 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Would be cool as a skill. That way players can choose to have it.
-
Thank you! Highly appreciated, it helps with our dense map and situation a lot- 264 comments
-
- 1
-
-
- #bradley
- #bradleyapc
- (and 17 more)
-
@ZEODEIs it possible we can have control of the variable for the distance from objects/buildings we're allowed to throw the signals? I've noticed for buildings and objects it looks to be using the patrol distance currently. For us that's a little much so I went in and divided it by 10 in the .cs(this way I was able to keep our large patrol distance while shortening the distance from objects/buildings) but it would be super helpful to have a variable to control in the config.
- 264 comments
-
- 1
-
-
- #bradley
- #bradleyapc
- (and 17 more)
-
Hey that would be great on our end. We have furnace levels and it works that way as well. Definitely helpful if the players are using the Button for pickup that you have.
-
Khan's helped us gain full control over variables surrounding every power source with this plugin. He's even taken special requests to improve the quality of life of the plugin and provided even more variables than originally laid out. 5 stars for the genuine support and 1 on 1 consultation, Khan has gone above and beyond in working with us, keeping an open mind and passionate attitude. 5 stars on the efficient execution and usefullness of the plugin itself! Awesome idea, great implementation! -
You're awesome! Thank you!!
- 264 comments
-
- 1
-
-
- #bradley
- #bradleyapc
- (and 17 more)
-
Do your config names match like so? "Angry Bradley Signal": { "APC display name": "Angry Bradley Signal", I had the same problem, the plane would never spawn unless the names were listed the same in both lines for every signal I made for our server.
