Added GetArgs

[schwarper]

[ConsoleCommand("css_testx")]
public void OnTest(CCSPlayerController player, CommandInfo info)
{
    var args = info.GetArgs();

    Console.WriteLine($"TESTX args count => {args.Count}");

    for (int i = 0; i < args.Count; i++)
    {
        Console.WriteLine($"{i}. {args[i]}");
    }
}

[ConsoleCommand("css_testy")]
public void OnTest2(CCSPlayerController player, CommandInfo info)
{
    var args = info.GetArgs(0, 3);

    Console.WriteLine($"TESTX args count => {args.Count}");

    for (int i = 0; i < args.Count; i++)
    {
        Console.WriteLine($"{i}. {args[i]}");
    }
}

[schwarper]

#504

I improved this a bit.

[KillStr3aK]

I'd also like the enumerator version maybe? from #504

[schwarper]

I'd also like the enumerator version maybe? from #504

I thought that getting arg once and split them is better than using GetArg multiple times. However, it might be better.

[WidovV]

Perhaps a solution like this would be the way forward, as I can see calling getarg multiple times might not be the best way forward (my solution), but nor do I think creating a list and a regex expression is (your solution).
I made a minor test project to showcase what could become the end result. It kinda combines both yours and mine. The if statement or rather ternary don't need to be implemented, I was just too lazy to copy the original.

   // Emulation of argstring
   private static string ArgString = "my test string";
   // Emulation of ArgCount
   private static int ArgCount = ArgString.Split().Length;
   static void Main(string[] args)
   {
       Console.WriteLine(string.Join(" ", TestMethods(2))); // Output: string
       Console.WriteLine(string.Join(" ", TestMethods(1))); // output: test string
       Console.WriteLine(string.Join(" ", TestMethods(1, 2))); // Output: test
       Console.WriteLine(string.Join(" ", TestMethods(0, 1))); // Output: my
       Console.WriteLine(string.Join(" ", TestMethods())); // Output: test string
   }

   private static IEnumerable<string> TestMethods(int startIndex = 1, int endIndex = -1)
   {

       endIndex = (endIndex > ArgCount || endIndex < 0) ? ArgCount : endIndex;
       startIndex = (startIndex > ArgCount ||  startIndex < 0 || startIndex > endIndex) ? ArgCount : startIndex;
       Console.WriteLine($"Start: {startIndex} | end: {endIndex}");
       
       return ArgString.Split((char[]?)null, StringSplitOptions.RemoveEmptyEntries).AsEnumerable().Skip(startIndex).Take(endIndex - startIndex);
   }

Splitting with (char[]?)null is reffering to any whitespace as I understand.
The reason for starting startindex at one is, iirc, argstring comes with the command input as first argument, in case of not, my bad. Not sure that "all" of these method calls on enumerable is that performance heavy, but we're avoiding object initialization by using As, which is a thumbs up. Either Take or Skip could be removed by using "TakeWhile" and checking index also.

Glad to see that a PR I made back in June and forgot all about is something that other people (you at least) would have the benefit of 😅