http://pastebin.com/raw.php?i=p58DVkKh

Same as reported before 2.0 update. I use RandomLocation to randomize where players drop in to the nether when they go. It seems like Nether Portals don't trigger it, but any warping or teleporting (including mv portals) does.

Do you use the spawnLastLocation strategy anywhere? If not, an easy fix until I can reproduce and look at the code is just to turn off the saving of lastLocation by setting core.recordLastLocation: false in your core.yml.

Troubling that this is happening - what the code should be doing is looking for the existing record and updating it in the database. What the error indicates is that it's trying to insert a new row with the same values and the DB contraints I put in are rightly refusing it. Also very odd that it doesn't happen on Nether Portals but does on MV portals - could be related to different events being called and different code being executed.

I believe I've found the source of the error stack trace, so that should be fixed as of build 577 - give it a try and let me know.

However, I still don't know why the nether portals are not triggering it the same as other teleports, most likely that's a bug and related to the way Bukkit does eventing for nether teleports, something I need to do some local testing on and research further.

Closing issue as assumed fixed since code was modified to resolve the reported error and no new updates have been posted to indicate this is still a problem. Feel free to re-open case if this is still an isssue.