Vessel(name) always fails to find the current cpu vessel.

[Dunbaratu]

If ship:name is "foo", and you try to call vessel("foo")., you get an exception that there is no such vessel called "foo", when clearly there is one - your own.

It seems that the candidate vessels that the Vessel(...) constructor function chooses from is the list of all vessels other than the current vessel.

I think it might be using the same list of vessels that LIST TARGETS uses, and scanning through that list (I haven't looked at the code to know for sure - I'm just reporting this bug and moving on). It might make sense why LIST TARGETS doesn't list the current vessel - you can't target your own ship. But you should be able to access it by its name.

(Note, as an aside, while it might make sense why the current vessel isn't a candidate among the LIST TARGETS, that does also raise the issue that if that's the case then we are still missing a means to actually really list all the vessels. Also, I never liked that LIST TARGETS lists vessels. By name it sounds like it should list all potential targets, meaning vessels, bodies, and docking ports, but that may be a different issue to raise separately.)