This will be a serious issue - it will put the guid of every resonator owner on display into the player name lookup queue. This will hammer the name resolving API and make users hit the server request rate limit in no time.

You *must* lookup the GUID for the player name to highlight, and only do a simple GUID comparison here.

The player name may not be available in the cache to convert to a GUID - so in this case you have a problem and can't highlight any portals.

The 'playerNameResolved' hook is useful for retrying any name->guid lookups if it failed at first.