suggestions
Moderator: Moderators
suggestions
tasclient >
1. player map download status % indicator
2. auto-limit selectable teams to mapped start positions and balanced auto-join player to one of the teams.
3. auto-ready when both conditions are met.
one thing that I don't really figure out is why do we need to calculate paths for maps ? if the calculations are stored in files later, why not store the calculations with the maps in the first place ?
1. player map download status % indicator
2. auto-limit selectable teams to mapped start positions and balanced auto-join player to one of the teams.
3. auto-ready when both conditions are met.
one thing that I don't really figure out is why do we need to calculate paths for maps ? if the calculations are stored in files later, why not store the calculations with the maps in the first place ?
Re: suggestions
Since it would incerese the download time for no reason... it's like removing .zips for big maps just because it takes extra time to unzip em.monohouse wrote: one thing that I don't really figure out is why do we need to calculate paths for maps ? if the calculations are stored in files later, why not store the calculations with the maps in the first place ?
Re: suggestions
Nah, it's because the files need to be recalculated for each mod and each version mod....Kixxe wrote:Since it would incerese the download time for no reason... it's like removing .zips for big maps just because it takes extra time to unzip em.monohouse wrote: one thing that I don't really figure out is why do we need to calculate paths for maps ? if the calculations are stored in files later, why not store the calculations with the maps in the first place ?
So if you bundle it with you map, it will be quickly outdated.
about #2.....I think it might be wrong to do.........I might have abetter idea :
auto-join by default to one of the mapped teams, but allow manually to select an another team.
and in #3 instead of auto-ready, auto-unready when the host selects a map that is not available for the user, until the user downoads it, and if the user was ready before the host switched map, then auto-ready when the download of the new map is complete. but not auto-ready in general.
auto-join by default to one of the mapped teams, but allow manually to select an another team.
and in #3 instead of auto-ready, auto-unready when the host selects a map that is not available for the user, until the user downoads it, and if the user was ready before the host switched map, then auto-ready when the download of the new map is complete. but not auto-ready in general.
oh and #4, lagometer in tasclient battle room.
the lagometer in spring is not good, the latency is incorrect, also I recommend a quake3 style lagometer so that you could know the lag over time, in spring currently the only one that knows the correct latency is the host, and all others have the wrong number.
#5. console, for entering commands, also quake3 style is one I would prefer to have : variables and commands especially the /help command that would show all the commands and what they do, cause over time there are going to be many commands and it's gonna be hard to know what is and what is not possible.
the lagometer in spring is not good, the latency is incorrect, also I recommend a quake3 style lagometer so that you could know the lag over time, in spring currently the only one that knows the correct latency is the host, and all others have the wrong number.
#5. console, for entering commands, also quake3 style is one I would prefer to have : variables and commands especially the /help command that would show all the commands and what they do, cause over time there are going to be many commands and it's gonna be hard to know what is and what is not possible.
Last edited by monohouse on 25 Mar 2006, 12:15, edited 1 time in total.
all that being said, I think first of all the flying units and nano has to be fixed, and information must be provided for hosters how much bandwidth they have and how much is required per player, also I recoommend that not only the host be able to know if a player lags, provide info for the player that lags his lag status correctly.
something i'd like to see: BRIDGES! having bridges would add a new gameplay element, would mean that it might actually be possible to cross certain bits of land/water which look very negligable on maps, but force you into making airports just so you can cross over. On some water maps could be very cool building bridges over towards other bases/islands/whatever, and you could maybe make some platforms too.