Editing Openai/69185ed9-16a4-8011-b841-20ce53d80746 (section)

=== Assistant: Ah, okay—this makes sense. ===
Ah, okay—this makes sense. 😅

Here’s what’s probably happening:

Even though the DRGBase dev mentioned it as a multiplayer bug, the underlying issue (a table being passed instead of a string) can still technically happen in singleplayer under some conditions, like:
* Spawning certain NPCs that have multiple default relationships stored as a table.
* Addons or custom scripts that modify or extend DRGBase’s relationship system.
* Race conditions or delayed initialization: sometimes the entity isn’t fully set up, and UpdateRelationshipWith gets a table by accident.

So even in SP, it’s possible to hit that same error.

The good news: as the dev said, NextBots still work—this is more of a warning/error in the console than a crash. It only happens when DRGBase tries to string.upper() something that isn’t a string.

If you want, I can give you a tiny local fix you can drop in SP that completely stops the error from spamming, without touching multiplayer compatibility.

Do you want me to do that?