Creating a class Player based on instructions

    public abstract class Player
    {
        private enum Disk
        {
            black,
            white
        }
        private string name;

        public abstract void RequestMove(GameBoard GameBoard, string[] ListOfValidMoves);
    }

    public abstract class Player
    {
        private enum Disk
        {
            black,
            white
        }
        private string name;

        public abstract void RequestMove(GameBoard GameBoard, string[] ListOfValidMoves);
    }

    public class HumanPlayer : Player
    {
        public HumanPlayer(string Name, string Disk)
        {
            this.Name = Name;
            this.Disk = Disk;
            
        }
    }

    public class HumanPlayer : Player
    {
        public HumanPlayer(string Name, string Disk)
        {
            this.Name = Name;
            this.Disk = Disk;
            
        }
    }

public abstract class Player
{
    public enum Diskcolor
    {
        black,
        white
    }
    protected string name;
    protected Diskcolor disk;

    public abstract void RequestMove(GameBoard GameBoard, string[] ListOfValidMoves);
}


    public class HumanPlayer : Player
    {
        public HumanPlayer(string name, Diskcolor disk)
        {
            this.name = name;
            this.disk = disk;
            
        }

        public override void RequestMove(GameBoard GameBoard, string[] ListOfValidMoves)
        {
            throw new NotImplementedException();
        }
    }

public abstract class Player
{
    public enum Diskcolor
    {
        black,
        white
    }
    protected string name;
    protected Diskcolor disk;

    public abstract void RequestMove(GameBoard GameBoard, string[] ListOfValidMoves);
}


    public class HumanPlayer : Player
    {
        public HumanPlayer(string name, Diskcolor disk)
        {
            this.name = name;
            this.disk = disk;
            
        }

        public override void RequestMove(GameBoard GameBoard, string[] ListOfValidMoves)
        {
            throw new NotImplementedException();
        }
    }

    <Grid>
        <Button Content="PvE" HorizontalAlignment="Left"  VerticalAlignment="Center" Click="Button_Click" Height="50" Width="100" Margin="245,0,0,0"/>
        <Button Content="PvP" HorizontalAlignment="Left"  VerticalAlignment="Center" Click="Button_Click" Height="50" Width="100" Margin="355,0,0,0"/>
        <TextBlock HorizontalAlignment="Center" Margin="0,170,0,0" TextWrapping="Wrap" Text="Which gamemode would you like to play?" VerticalAlignment="Top" Height="17" Width="224"/>
    </Grid>

    <Grid>
        <Button Content="PvE" HorizontalAlignment="Left"  VerticalAlignment="Center" Click="Button_Click" Height="50" Width="100" Margin="245,0,0,0"/>
        <Button Content="PvP" HorizontalAlignment="Left"  VerticalAlignment="Center" Click="Button_Click" Height="50" Width="100" Margin="355,0,0,0"/>
        <TextBlock HorizontalAlignment="Center" Margin="0,170,0,0" TextWrapping="Wrap" Text="Which gamemode would you like to play?" VerticalAlignment="Top" Height="17" Width="224"/>
    </Grid>

Rules of WPF:

❌ Avoid the WPF Designer to eliminate a category of confusing bugs
❌ Don't rely on Margin as the primary tool for layouts
❌ Avoid writing UserControls or subclassing to extend a default control -- use Behaviors instead (Microsoft.Xaml.Behaviors.Wpf)

✅ Write XAML by hand and autoformat with "Ctrl K,D" or XAML Styler
✅ Rely upon XAML Hot Reload to design your app's UI at runtime
✅ Use layout controls (Grid, DockPanel, etc) to support proper resizing
✅ Use data binding to eliminate glue code and state synchronization issues
✅ Use collection controls and DataTemplate to dynamically create lists of controls
✅ Learn MVVM to create maintainable apps
✅ Use the Dispatcher to update controls from non-UI threads
✅ WPF's default controls can be easily modernized via $wpfuilibs
✅ Include relevant XAML, code-behind, and ViewModel code for questions when possible

Rules of WPF:

❌ Avoid the WPF Designer to eliminate a category of confusing bugs
❌ Don't rely on Margin as the primary tool for layouts
❌ Avoid writing UserControls or subclassing to extend a default control -- use Behaviors instead (Microsoft.Xaml.Behaviors.Wpf)

✅ Write XAML by hand and autoformat with "Ctrl K,D" or XAML Styler
✅ Rely upon XAML Hot Reload to design your app's UI at runtime
✅ Use layout controls (Grid, DockPanel, etc) to support proper resizing
✅ Use data binding to eliminate glue code and state synchronization issues
✅ Use collection controls and DataTemplate to dynamically create lists of controls
✅ Learn MVVM to create maintainable apps
✅ Use the Dispatcher to update controls from non-UI threads
✅ WPF's default controls can be easily modernized via $wpfuilibs
✅ Include relevant XAML, code-behind, and ViewModel code for questions when possible