Steenamaroo
-
Posts
3,678 -
Joined
-
Last visited
-
Days Won
208
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Steenamaroo
-
That's a good approach. Thanks for that. I think I'm going to make the increment adjust dynamically, for example if the value is 80 and click up, it goes up 10, but if the value's over, say, 300, maybe it goes up in 50s, and up in hundreds if it's over 500. That, along with an option to create a new profile by cloning an existing one, should help to keep a lot of people in the UI. -
Hi, Not yet -I dmd a copy to the other guys seeing this, to get confirmation of fix before updating. Seems good so far. Public update to follow today.
-
A few people have mentioned setting very high numbers and wanting bigger increments. Thanks for bringing it up - I might place 5/10/50/100 buttons to let users choose their increment on the fly!
-
I've been working on this tonight @Baron Von Finchus Think I've solved it. Thanks for reporting it to me.
-
I'm not being facetious but while you're in, compare old to new. It's a rewrite.
-
Hi, That's for internal use. You can ignore it.
-
MooDDang, I'm going to DM you. It's hard to keep track here.
-
I'm trying to read everything and stay on top of reports but yes, please do use the Support section particularly when pasting errors - It's much easier to keep track of and make sure everything is being answered. For anyone with the error containing System.NullReferenceException: Object reference not set to an instance of an object at BaseProjectile.ServerUse can you please ensure that your kit belts contain only normal bullet weapons or melee/slashing weapons? If I can find out what specific weapon, or rogue item, causes this to happen, I'll code in protection against it.
-
I think it has to be a kit with an unsuitable item in the belt. I have the plugin removing most unsuitable items but I think there are still a few users can put in. Can you make sure that your kit belts have only normal bullet weapons, or slashing melee weapons please? One of them probably has an unsupported item or tool or something like that.
-
Hi mate. Yes, it's because of the - in the profile name. I'll write in a catch to prevent creation of profiles with - in the name. For now, you could just remove the - in json and reload. Thanks for reporting it.
-
Hi, @lengka Are you on the most recent version? V1.0.3 Do you have anything in your kit belt that's not recommended?
-
Hi, The API will be different, so other plugins would need to update for that, but no...They're not implemented yet. They are next on the list, though. Thanks for flagging it.
-
Yup - It sounds like the plugin isn't installed, or isn't loaded. If you're sure it's installed, do oxide.reload BotReSpawn, and watch console to confirm it loads without issue.
-
Hi! You can't use the commands to create profiles or view the UI unless you are admin, or have that permission.
-
@Covfefe- Are you adding the kits via UI? If not, please do so. It hides any kits which do not have valid weapons in the belt, and if you're manually typing them into the json and that's the case, they'll be removed.
-
0 might be a bit intense, forcing the spawngroup to check very frequently. I'll make some changes to this - Respawn timer (due to being killed) needs to be separated from the respawn timer due to day/night changing.
-
Hi @pinoysaboteur I'm working on RustRewards integration as we speak, and npcs should be respawning/despawning according to time of day, and your population settings, after a short delay. Respawn timer is taken into account for this, and is now in minutes, so it might be worth ensuring it's not set to a very high value. @lengka I think I've found, and prevented, this error now. Thank you. Do you have any unusual items in the npc belts, like a hammer for example? If you do, removing those may stop the error, between now and the next plugin update.
-
Ok, good to know. Thank you again for all the info ^.
-
Damn. I can't replicated it here but, of course, I need to find out what this is and sort it. Not sure where to start, though. It's complaining about a method that I don't even use, as far as I know. Do you have some means of forcing reload of the plugin after server restart, as a temp fix at least?
-
Ok, thank you for the info. I've had multiple successful restarts over here but I'm on a windows box. I'll have someone check on a linux box incase there's some difference.
-
I've seen a few people with the same issue but I don't know how it's happening. Was this when you first installed the plugin, or had it been running successfully before this?
-
I haven't seen that until now - I will find out. Thank you for posting.
-
Scaling npc population to server population would be much easier to do in this new version. I've noted it, and will look into it soon.
-
Type is not a user adjustable setting. It's for internal use.
-
It is in the description although, admittedly, only added recently. The description will be much more detailed and probably will have tutorial videos, soon.
