RuneRebels

Thank you for reporting this. This is a known bug as it is caused when an object interaction is intended to trigger a nearby NPC's dialogue. However because the NPC is nowhere to be found, that blitz error appears. This affects all ObjectToNPC interactions.

Edit: I should probably note that as what Bill said, World 2 failed to load a majority of NPCs. This will be fixed along with World 1.

This probably has to do with the power outage at the moment. Some things aren't being loaded and other things are being loaded that shouldn't be lol. Just sit tight for a little bit :)

Quote from: Dev Sean on February 10, 2017, 03:01:37 PM
Thank you for reporting this. This is a known bug as it is caused when an object interaction is intended to trigger a nearby NPC's dialogue. However because the NPC is nowhere to be found, that blitz error appears. This affects all ObjectToNPC interactions.

Edit: I should probably note that as what Bill said, World 2 failed to load a majority of NPCs. This will be fixed along with World 1.

I discovered that there aren't many npcs on this world. That seemed strange to me..

Quote from: Galleta on February 10, 2017, 03:19:46 PM

Quote from: Dev Sean on February 10, 2017, 03:01:37 PM
Thank you for reporting this. This is a known bug as it is caused when an object interaction is intended to trigger a nearby NPC's dialogue. However because the NPC is nowhere to be found, that blitz error appears. This affects all ObjectToNPC interactions.

Edit: I should probably note that as what Bill said, World 2 failed to load a majority of NPCs. This will be fixed along with World 1.

I discovered that there aren't many npcs on this world. That seemed strange to me..

seems like most are coded like members npc so they don't show in nonmembers

Sadly the version of the game engine deployed to World 1 & 2 with Aries has a critical bug where Free to Play worlds stop loading Npcs after the first member's only Npc encountered. :'(

This has been fixed for the next release.