1 |
That's exactly the point. Those stats you see are part of the [color=DarkRed]spring engine[/color]. The [color=DeepSkyBlue]website[/color] is (for the purpose of this) completely unrelated, it doesn't even know about the [color=DarkRed]spring engine[/color]. It only knows about the database and files behind itself, some of which is also used by Springie (the automated host that hosts games for you) to tell the [color=DarkRed]spring engine[/color] how to build the commander.
|
1 |
That's exactly the point. Those stats you see are part of the [color=DarkRed]spring engine[/color]. The [color=DeepSkyBlue]website[/color] is (for the purpose of this) completely unrelated, it doesn't even know about the [color=DarkRed]spring engine[/color]. It only knows about the database and files behind itself, some of which is also used by Springie (the automated host that hosts games for you) to tell the [color=DarkRed]spring engine[/color] how to build the commander.
|
3 |
In order for the [color=DeepSkyBlue]website[/color] to consistently display those stats, it would either have to check the ingame information (by running [color=DarkRed]spring[/color], just as you have to at this point, which is not feasible/possible for the [color=DeepSkyBlue]website[/color] to do) or have the [color=DarkRed]engine[/color] code duplicated, which would mean that maintaining consistency between these is going to be painful.
|
3 |
In order for the [color=DeepSkyBlue]website[/color] to consistently display those stats, it would either have to check the ingame information (by running [color=DarkRed]spring[/color], just as you have to at this point, which is not feasible/possible for the [color=DeepSkyBlue]website[/color] to do) or have the [color=DarkRed]engine[/color] code duplicated, which would mean that maintaining consistency between these is going to be painful.
|