-
Posts
895 -
Joined
-
Last visited
-
Days Won
11
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Martian
-
Changed Status from Pending to Work in Progress
-
Changed Status from Pending to Work in Progress
-
Hello, those are hooks for developers. You don’t need to do anything — another person was the one who requested them. -
Hi @andyb_83, Thank you for the detailed report. I have just pushed a new update to the plugin with improvements and additional adjustments related to NPC movement. Please update to the latest version and test it again to see if the issues with the movement behavior have improved. I will also review the NPC naming behavior related to the removal of NPC Spawn to make sure their custom names appear correctly instead of showing as Heavy Scientist in death notes. When you have a chance, please test the updated version and let me know if the problems have improved or if you are still experiencing the same behavior. Your feedback will help me refine it further.
-
Changed Status from Pending to Fixed Changed Fixed In to 3.7.1
-
Changed Status from Pending to Fixed Changed Fixed In to 3.7.1
-
void OnDungeonSpawn(ulong OwnerID, Vector3 Position, string Grid, string TierName) { PrintWarning($"Dungeon spawned at {Position} by {OwnerID} Grid: {Grid}, Tier: {TierName}"); } void OnDungeonDespawn(ulong OwnerID, Vector3 Position, string Grid, string TierName) { PrintWarning($"Dungeon despawned at {Position} by {OwnerID} Grid: {Grid}, Tier: {TierName}"); } void OnDungeonWin(ulong playerID, string tierName) { PrintWarning($"Player {playerID} cleared the dungeon tier: {tierName}"); }
-
Thank you for the feedback, I will be making improvements to the NPCs soon.
-
Changed Status from Work in Progress to Fixed Changed Fixed In to 3.7.0
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Fixed Changed Fixed In to 3.7.0
-
Changed Status from Pending to Not a Bug
-
Hi, That’s a great idea, I like it! However, I’d need to improve the plugin structure a bit before adding something like that. Maybe it’s something we can look at in the future Cheers!
-
Changed Status from Pending to Work in Progress
-
Please update the NpcSpawn and check if the issue still occurs afterward. If the problem persists after updating, please report it again with the new logs so we can investigate further.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.3.2
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Fixed Changed Fixed In to 3.6.6
-
Changed Status from Pending to Fixed Changed Fixed In to 3.6.6
-
Changed Status from Pending to Fixed Changed Fixed In to 3.6.6
-
I couldn’t reliably reproduce the issues on my side, but I prepared an updated version with changes that should address what you described: Access/protection: FarmPro container/planters can only be opened/used by the owner, team members, or players authorized in the TC (so strangers shouldn’t be able to loot/use it even with RealPVE). Placement conflict: placement is now blocked before deploying if it’s too close to another FarmPro, and it shows a message instead of “disappearing/deleting”. Stranger interaction: interaction/use of FarmPro-related entities is restricted to authorized players (same owner/team/TC). UI bug: added extra cleanup so the FarmPro UI shouldn’t get stuck (auto-clears on death/disconnect/when the entity is removed). I sent you the updated build via private message so you can test it before I push a public update. Please let me know if you can still reproduce any of these (and what exactly happens / server logs), so I can adjust further if needed.
