Correct changelog, avoid out-of-bounds array access.

In updating to changelog to actually include an example of the effects of mixing up screen and player indices, I realized that there was no protection against out-of-bounds array accesses in these functions, so I fixed that.

Author: MageKing17

CHANGELOG.md

@@ -39,7 +39,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 - Fixed an issue where palette index 255 was incorrectly showing as black.
 
-- Fixed instances of `CameraMan:GetScrollTarget()` and `CameraMan:SetScrollTarget()` supplying a player index instead of a screen index.
+- Fixed instances of `CameraMan:GetScrollTarget()` and `CameraMan:SetScrollTarget()` supplying a player index instead of a screen index. This could prevent the functions from working properly, or at all, when playing as a player other than 1, potentially screwing up camera effects.
 
 - Fixed a bug in Decision Day that could cause an error when trying to set the camera's scroll target, in addition to the previous issue.
 

Source/Managers/CameraMan.cpp

@@ -64,10 +64,16 @@ void CameraMan::SetScroll(const Vector& center, int screenId) {
 }
 
 Vector CameraMan::GetScrollTarget(int screenId) const {
+	if (screenId < 0 || screenId >= c_MaxScreenCount)
+		// Would it be preferable to just set screenId to 0?
+		return Vector();
 	return g_NetworkClient.IsConnectedAndRegistered() ? g_NetworkClient.GetFrameTarget() : m_Screens[screenId].ScrollTarget;
 }
 
 void CameraMan::SetScrollTarget(const Vector& targetCenter, float speed, int screenId) {
+	if (screenId < 0 || screenId >= c_MaxScreenCount)
+		return;
+
 	Screen& screen = m_Screens[screenId];
 
 	// See if it would make sense to automatically wrap.