Default Voice Chats
A lot aren't needed. I'd suggest making a list of vital, on the fence and useless chats in the default selection. Then cutting them out and having the useless ones as an add on chatpack. I'd be willing to go through them and draw up the lists if there is support for this idea.
slap wrote:QUOTE (slap @ Oct 7 2009, 01:28 AM) good point, I concede.
Is this the beginning of the "Community VC development" thread? /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />
I think a desirable end-product would be is:Have a team in charge of VCs.Make a code change so that users can toggle between a 'default' VC pack to a 'custom' VC pack.If the user selects 'default', the only VC that are displayed would be ones the team decides would be "official defaults", all others would be muted and no 'Unknown chat' sent.If the user selects 'custom', then any VC the team decides would be "official custom VCs" would be displayed (and played if the user has the .wav file).If someone wants to make new custom VC, then they submit it to the team and decisions are made from there. Should be a fairly relaxed procedure.If someone wants to make new default VC, then they submit it to the team and they decide if it is 'vital' and hence get included.Code change so that the quickchat.mdl is seperated from quickchatmenu.mdl. Then people can maintain their custom menu layout without updates of new VC (custom or default) overwriting it.Somewhere to host the new .wav files, and a readme explaining how to make changes to your quickchatmenu.mdl and the relevant lines of code.umm, I think that's everything.
+++Edit. Nope, thought of one more thing. With the above system it would be "See/play all custom VC" or "See/play none at all". It would be nice if a player could make simple changes to quickchat.mdl to customise which ones played (For instance, wants all the Family Guy VCs but none of the Star Wars ones). Perhaps a 3rd file, quickchatplayed.mdl which would have three sections: Default, Custom, and Never. It would be a list of all VC IDs, and could be modified by cut-pasting an ID from one section to another.
So if a player toggles to Default, only the VC IDs he has put in there will be played. If he toggles to Custom, then the VCs in Default & Custom would be played.
Unfortunately, because this file would be a comprehensive list of VCs, it would need to be overwritten whenever the team sent out an updated version of VCs, and the player would have to re-modify it.
...
So, let's pretend the system is in place.
R3cord3r comes along with a whole bunch of VCs he has scraped from the latest episode of the Gilmore Gals and the team decides to include it as part of the custom VC. A new quickchat.mdl is sent out as part of autoupdate, which would add the new VC IDs to everybody. With that on their computers people that have 'Custom' selected will have the relevant lines of txt displayed when any other user sends a Gilmore VC (and the sound played if they have the wav file).
People using 'Default' will, of course, be unaffected (as far as they know).
An announcement is made in News that new custom VC available, and a link to download the .wav files. The announcement would also include the relelvant lines of code. ie.
QUOTE Gilmore Gal VC created by R3cord3r are now available. If you wish to hear and use them download the sound files here and download the new menu here. Note: This menu will overwrite any custom menu layout you currently use (you can download the sound files with impunity though).
Don't forget to toggle to 'Custom VC' in the in-game menu.
If you are using a custom menu layout and wish to add these VC yourself, the relevant code can be found here. Note: Don't blame us if you're a retarded coder and after making changes you start getting Alleg Crash Guard.[/quote]
I think a desirable end-product would be is:Have a team in charge of VCs.Make a code change so that users can toggle between a 'default' VC pack to a 'custom' VC pack.If the user selects 'default', the only VC that are displayed would be ones the team decides would be "official defaults", all others would be muted and no 'Unknown chat' sent.If the user selects 'custom', then any VC the team decides would be "official custom VCs" would be displayed (and played if the user has the .wav file).If someone wants to make new custom VC, then they submit it to the team and decisions are made from there. Should be a fairly relaxed procedure.If someone wants to make new default VC, then they submit it to the team and they decide if it is 'vital' and hence get included.Code change so that the quickchat.mdl is seperated from quickchatmenu.mdl. Then people can maintain their custom menu layout without updates of new VC (custom or default) overwriting it.Somewhere to host the new .wav files, and a readme explaining how to make changes to your quickchatmenu.mdl and the relevant lines of code.umm, I think that's everything.
+++Edit. Nope, thought of one more thing. With the above system it would be "See/play all custom VC" or "See/play none at all". It would be nice if a player could make simple changes to quickchat.mdl to customise which ones played (For instance, wants all the Family Guy VCs but none of the Star Wars ones). Perhaps a 3rd file, quickchatplayed.mdl which would have three sections: Default, Custom, and Never. It would be a list of all VC IDs, and could be modified by cut-pasting an ID from one section to another.
So if a player toggles to Default, only the VC IDs he has put in there will be played. If he toggles to Custom, then the VCs in Default & Custom would be played.
Unfortunately, because this file would be a comprehensive list of VCs, it would need to be overwritten whenever the team sent out an updated version of VCs, and the player would have to re-modify it.
...
So, let's pretend the system is in place.
R3cord3r comes along with a whole bunch of VCs he has scraped from the latest episode of the Gilmore Gals and the team decides to include it as part of the custom VC. A new quickchat.mdl is sent out as part of autoupdate, which would add the new VC IDs to everybody. With that on their computers people that have 'Custom' selected will have the relevant lines of txt displayed when any other user sends a Gilmore VC (and the sound played if they have the wav file).
People using 'Default' will, of course, be unaffected (as far as they know).
An announcement is made in News that new custom VC available, and a link to download the .wav files. The announcement would also include the relelvant lines of code. ie.
QUOTE Gilmore Gal VC created by R3cord3r are now available. If you wish to hear and use them download the sound files here and download the new menu here. Note: This menu will overwrite any custom menu layout you currently use (you can download the sound files with impunity though).
Don't forget to toggle to 'Custom VC' in the in-game menu.
If you are using a custom menu layout and wish to add these VC yourself, the relevant code can be found here. Note: Don't blame us if you're a retarded coder and after making changes you start getting Alleg Crash Guard.[/quote]
Last edited by juckto on Tue Jul 24, 2007 4:45 am, edited 1 time in total.
Usually though, "skill" is used to covertly mean "match the game exactly to my level of competence." Anyone who is at all worse than me should fail utterly (and humorously!) and anyone better is clearly too caught up in the game and their opinions shouldn't count.
-
BlackViper
- Posts: 6993
- Joined: Thu Aug 07, 2003 7:00 am
- Location: Green Bay, WI
BlackViper wrote:QUOTE (BlackViper @ Jul 24 2007, 08:01 AM) Personally I know a lot of players have no use for the newer voice chat packs. Do not force us into listening to the latest teen rage. Sorry, just an opinion.
QUOTE People using 'Default' will, of course, be unaffected (as far as they know).[/quote]
Apparently a California "cabin" is any place more than 4 blocks from a McDonalds.
-
finnbryant
- Posts: 360
- Joined: Sat Feb 17, 2007 11:18 am
- Location: England
that sounds really good, one suggestion i have is that you have the default rules for what files are visible when the default VCs or custom VCs are on inside an existing file (bottom of quickchats.mdl for example) and then have a second completely blank file that the user can use to set things to default/custom/off. this would mean that people could have everything autoupdate except the actually wav/ogg files without losing any custom settings.
obviously the game would use the user edited file first and only use the defaults in the quickchats.mdl if they arnt mentioned in the user edited file.
if thats not clear just say so.
always try to find a way for the users settings to survive updates /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
obviously the game would use the user edited file first and only use the defaults in the quickchats.mdl if they arnt mentioned in the user edited file.
if thats not clear just say so.
always try to find a way for the users settings to survive updates /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
Last edited by finnbryant on Tue Jul 24, 2007 4:57 pm, edited 1 time in total.
-
fuzzylunkin1
I think it would be good to have a default pack that ONLY includes chats that directly impact gameplay. Perhaps have a Basic Gameplay pack with the essential and most used gameplay chats and then an Extended Gamplay pack with lesser used and not critical chats.
Then have other categories of "approved chats". Have a taunt pack for example. One that contains greetings or responses that don't affect gameplay such as "Hey, wassup?" "heh heh heh" etc.
Then have 2-3 different styles selectable in game that organize the quick chat menu in different ways.
Then have some kind support for downloadable chats created by the community.
Then have other categories of "approved chats". Have a taunt pack for example. One that contains greetings or responses that don't affect gameplay such as "Hey, wassup?" "heh heh heh" etc.
Then have 2-3 different styles selectable in game that organize the quick chat menu in different ways.
Then have some kind support for downloadable chats created by the community.
I recently removed all the useless non tactical VC from the default.fuzzylunkin1 wrote:QUOTE (fuzzylunkin1 @ Jul 24 2007, 06:23 PM) Some people need to have more fun /unsure.gif" style="vertical-align:middle" emoid=":unsure:" border="0" alt="unsure.gif" />.
And what a difference it makes to game play.
Finally I get to hear just the important vc I need to hear and not loads of "whoopeedoo" rubbish.
Your saying more VC = Fun
Me Less VC = Fun+less headache from the latest cartoon/tv fad.

-
finnbryant
- Posts: 360
- Joined: Sat Feb 17, 2007 11:18 am
- Location: England
the problem with having 2 gameplay packs, is that if someone decides that "attack carrier" isn't needed in the basic gameplay pack because "attack capital ship" is good enough, but it is kept in the extended, when the comm uses the extended to say "attack carrier", all the players using the basic pack never receive the order.AEM wrote:QUOTE (AEM @ Jul 24 2007, 06:46 PM) I think it would be good to have a default pack that ONLY includes chats that directly impact gameplay. Perhaps have a Basic Gameplay pack with the essential and most used gameplay chats and then an Extended Gamplay pack with lesser used and not critical chats.
so maybe in the basic gameplay pack it removes the menu items, but you still have the files etc. then you can hear it sent, but it doesn't waste your menu space.
your idea could even be partially done without any code changes, so it would be a very good interim.
IB_ there is definitely support, but probably not the kind that actually gets anything done.
Last edited by finnbryant on Tue Jul 24, 2007 10:46 pm, edited 1 time in total.
To be a little more clear, for the extended, I'm talking about stuff that aren't orders and is more for information.
They have a shipyard.
They have capitols.
Our miners are dead!
He cloaked!
He ripped!
etc
But I just took a quick look through the quick chats and yeah there probably isn't much point in having an extended gameplay pack. Just have one default pack that includes all chats that are related to gameplay.
They have a shipyard.
They have capitols.
Our miners are dead!
He cloaked!
He ripped!
etc
But I just took a quick look through the quick chats and yeah there probably isn't much point in having an extended gameplay pack. Just have one default pack that includes all chats that are related to gameplay.
Last edited by aem on Tue Jul 24, 2007 10:53 pm, edited 1 time in total.