Abandoned Bases 2.1.6

@NoxiousPluK

you can try the ab.debug command then sar

if no bases convert then it's a permission or config issue or whatever bug is happening with sar can happen with automated too

1 hour ago, nivex said:

@NoxiousPluK

you can try the ab.debug command then sar

if no bases convert then it's a permission or config issue or whatever bug is happening with sar can happen with automated too

Thanks, I tried that and at least got some feedback - but it is not entirely clear to me what this refers to:

At least I figured why the automatic conversion didn't work. After my uncertainty last week I had the plugin unloaded for a day, and that purged its active player database (I thought it could interface with Rust for that; but this makes more sense. I notice more plugins have a database like that - it would be neat to have a centralized API plugin for that stuff, that does nothing else on its own).

@NoxiousPluK

ty. ill take a look when I get home

I try not to use third party plugins as they're prone to issues too

7 minutes ago, nivex said:

@NoxiousPluK

ty. ill take a look when I get home

I try not to use third party plugins as they're prone to issues too

Thank you! And yea I get that too Wish there was a native API call for it

@NoxiousPluK

see below

yes, the smaller base next to the larger base is preventing the conversion as you suspected because the smaller base is active. I will have to fix it, but that requires properly identifying external TC versus a whole base.

edit: removed some information since I cannot think clearly enough 

the joy. lots to think about and fix 

Thanks! I was not entirely clear about this, but the 2x2 is build by another player and there's no shared authorization between the 2x2 and the big base (in fact it was someone building the 2x2 in anticipation on the big one becoming raidable, since the owners were banned about a week ago lol). Good luck with the thinking. I will ask them tomorrow to move their 2x2 away and try /sar again

@NoxiousPluK

np, I think I fixed it so waiting on testing results to confirm that everything is working

Hi @nivex. I want to buy Abandoned Bases but idk if this plugin works with SimplePVE.

Can u let me know?

Thanks!

@Notz

hi, it will work with any PVE plugin that properly implements the required hooks which I think that plugin has.

On 8/25/2024 at 6:30 AM, nivex said:

@NoxiousPluK

np, I think I fixed it so waiting on testing results to confirm that everything is working

Helloes, did you ever get progress with this?

@NoxiousPluK

heya, it will be released this coming Rust update to address pooling changes by Facepunch too. I can send it to you sooner if you don't want to wait, but it will break on Rust update due to those pooling changes by Facepunch

10 hours ago, nivex said:

@NoxiousPluK

heya, it will be released this coming Rust update to address pooling changes by Facepunch too. I can send it to you sooner if you don't want to wait, but it will break on Rust update due to those pooling changes by Facepunch

No worries, I will happily wait! Thanks a lot!

2.1.6 has been released. It requires the Rust update to compile. Enjoy

Hi nivex,
I have the same problem with the latest version. /sar does not work when another base is too close.
Was there a parameter modified?

@Roofer

hi, can you be more specific?

when another player base is too close, or another abandoned base event?

what do you mean by /sar doesn't work? does it do nothing, or does it give you a message? if you do not get any message then type /ab.debug and type /sar again. the /ab.debug command requires abandonedbases.admin permission

22 hours ago, nivex said:

@Couvreur

Salut, peux-tu être plus précis ?

lorsqu'une autre base de joueurs est trop proche ou qu'un autre événement de base abandonnée ?

que voulez-vous dire par /sar ne fonctionne pas ? Est-ce que cela ne fait rien ou est-ce que cela vous donne un message ? si vous n'obtenez aucun message, tapez /ab.debug et tapez à nouveau /sar. la commande /ab.debug nécessite l'autorisation d'abandonedbases.admin

@Roofer

heya, 400 radius is way too large. the plugin will not function properly with such a large radius. the maximum radius should be around 75

75 okay I take note. But last year I had no problem enlarging the radius even putting several bubbles. I use it for a pvp event

@Roofer

I added multi-TC support, so 400 radius will not work unless it is away from all TC owned by others.

you can still set Sphere Amount higher to darken the bubble, but I would not set it too high because it would impact performance.

I have a possibly silly (since this might be TruePVE configuration) question - I noticed incen ammo impact does damage, but the burning does not.

@NoxiousPluK

hi, this is blocked by TruePVE. when players use incendiary ammo and it spreads the fire the game isn't assigning the player as the initiator. so neither plugin can determine who caused the damage and it gets blocked (because I am explicitly blocking it in TruePVE). otherwise any player on the server could use incendiary ammo to kill another player. 

I have reported this to Facepunch but they haven't gotten around to addressing it yet

I do have a harmony patch if you would like to use it, but you should be aware that harmony patches might prevent your server from booting if the patch breaks after a Rust update.

Have only ever had this happen 1 time but a bubble got left over somehow from an abandoned tug raidable base.  Unloaded the plugin and the dome is still there. Just waiting for server restart and im sure that will fix it. 

Just a heads up

On 9/20/2024 at 5:18 AM, Dead Nasty said:

Have only ever had this happen 1 time but a bubble got left over somehow from an abandoned tug raidable base.  Unloaded the plugin and the dome is still there. Just waiting for server restart and im sure that will fix it. 

Just a heads up

 

Adding to this, I think tugs are bugged. The dome will disappear completely or stay. after the raid finishes the tug doesnt destroy like usual and it spams chat with what is pictured below.