I agree that the "renaming for clarity" is rather the other way around.
It seems that the only wrapper for the original
sprite function is
dbCreateSprite (just set the ID parameter (to that of a pre-existing Sprite) to move it). Because of this, the same function will also be used to change the sprite's image.
It might be worthwhile to create two more wrapper functions, say "dbSetSpritePosition" and "dbSetSpriteImage" if naming clarity is what is sought after
(Something you can easily do by yourself if you're keen about it by the way).
"Why do programmers get Halloween and Christmas mixed up?" Because Oct(31) = Dec(25)