Title of Invention: Presenting network-wide events in network wagering venue Abstract: A wagering game system and its operations are described herein. In embodiments, the operations can include determining a player account, from a network wagering venue, that is eligible to participate in a network-wide wagering game event, and selecting the player account to be a player that performs for an audience of other users from the network wagering venue. The player can win at least some portion of awards by playing a wagering game during the network-wide wagering game event. Audience member users can participate in the event using interactive features (e.g., betting features, chat features, etc.) presented in a presentation, or view, of the network-wide wagering game event. The operations can also include involving, or incorporating, the audience members, into the network-wide wagering game event in a variety of ways, such as assisting the player participant to perform better at the wagering game, engaging in side-bets, receiving awards, etc. Detailed Description: Part general_description_paragraphs: Part RELATED APPLICATIONS: This application is a continuation of U.S. application Ser. No. 13/143,798 filed Jul. 8, 2011, which is the National Stage of International Application No. PCT/US10/21089 filed Jan. 14, 2010, which claims the benefit of U.S. Provisional Application No. 61/144,907 filed Jan. 15, 2009. Part LIMITED COPYRIGHT WAIVER: A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. Copyright 2012, WMS Gaming, Inc. Part TECHNICAL FIELD: Embodiments of the inventive subject matter relate generally to wagering game systems and networks that, more particularly, presenting network-wide events in a network wagering venue. Part BACKGROUND: Wagering game machines, such as slot machines, video poker machines and the like, have been a cornerstone of the gaming industry for several years. Traditionally, wagering game machines have been confined to physical buildings, like casinos (e.g., resort casinos, roadside casinos, etc.). The casinos are located in specific geographic locations that are authorized to present wagering games to casino patrons. However, with the proliferation of interest and use of the Internet, shrewd wagering game manufacturers have recognized that a global public network, such as the Internet, can reach to various locations of the world that have been authorized to present wagering games. Any individual with a personal computing device (e.g., a personal computer, a laptop, a personal digital assistant, a cell phone, etc.) can connect to the Internet and process wagering games. Consequently, some wagering game manufacturers have created wagering games that can be processed by personal computing devices and offered via online casino websites (“online casinos”). However, online casinos face challenges and struggles. For instance, online casinos have struggled to provide the excitement and entertainment that a real-world casino environment provides. Some online casinos have struggled enforcing jurisdictional restrictions and requirements. Further, some online casinos have struggled adapting the online gaming industry to a traditionally non-wagering game business environment. As a result, wagering game manufacturers, casino operators, and online game providers face growing pains and challenges in making the online gaming industry appealing and profitable. Part DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS: This description of the embodiments is divided into six sections. The first section provides an introduction to embodiments. The second section describes example operating environments while the third section describes example operations performed by some embodiments. The fourth section describes additional example embodiments while the fifth section describes additional example operating environments. The sixth section presents some general comments. Part Introduction: This section provides an introduction to some embodiments. Wagering games are expanding in popularity. Many wagering game enthusiasts are demanding greater access to wagering games and content related to wagering games. As stated previously, some wagering game companies have created online wagering game websites that provide a way for wagering game enthusiasts to play wagering games while connected to the Internet (e.g., via a web-browser). Some online wagering game websites provide various features, such as social network functionality. Social networks allow wagering game players (“players”) to create user accounts with one or more unique identifiers that represent an online persona. One example of a unique identifier is a profile that describes personal information about the user. Another example of a unique identifier is an “avatar”. Avatars are graphical, “cartoon-like” depictions of a social network persona. These online personas, unique identifiers, profiles, associated avatars, etc., add to the fun of belonging to a social network. Many online casinos, however, present an unsatisfactory wagering game experience to players who enjoy a more true-to-life gaming experience. Some players avoid the artificial feel of online casinos and gaming websites, even online casinos with some social network features, in favor of the feel and atmosphere provided by a physical, or “brick-and-mortar”, casino. Embodiments of the inventive subject matter, however, present solutions to many of those challenges. For example, embodiments describe examples of presenting a network-wide wagering game event in a network wagering venue (e.g., an online casino, a wagering game website, a wagering network, etc.). The network-wide wagering game event may also be referred to herein as a network-wide event, or site-wide event (for wagering events presented on a website). The network-wide wagering game event can be presented over any type of communications network (e.g., public or private) that provides access to wagering games, such as a website (e.g., via wide-area-networks, or WANs), a private gaming network (e.g., via large-area-networks, or LANs), a file sharing network, a social network, etc., or any combination of networks. Multiple users can be connected to the networks via computing devices. In embodiments, the multiple users can have access and/or participate, in a network-wide event, whether as a wagering game player (“player”), an observer, or some other type of participant. The multiple users can have accounts that subscribe to specific services, such as account-based wagering systems (e.g., account-based wagering game websites, account-based casino networks, etc.). In some embodiments herein a user may be referred to as a player (i.e., of wagering games), and a player may be referred to interchangeably as a player account. Account-based wagering systems utilize player accounts when transacting and performing activities, at the computer level, that are initiated by players. Therefore, a “player account” represents the player at a computerized level. The player account can perform actions via computerized instructions. For example, in some embodiments, a player account may be referred to as performing in a network-wide event. Although a player, or person, may be activating a control to perform the activity, the player account, at the computer level, is associated with the player, and any associated devices that communicate the control activation to a processor, a server, or other device and/or initiates computerized instructions to perform the activation. Therefore, for brevity, to avoid having to describe the interconnection between player and player account in every instance, a “player account” may be referred to herein in either context. Further, in some embodiments herein, the word “gaming” is used interchangeably with “gambling”. FIG. 1 is a conceptual diagram that illustrates an example of notifying network users that a network-wide wagering game event is commencing, according to some embodiments. In FIG. 1, a wagering game system (“system”) 100 can include multiple network-enabled clients (“clients”) 132, 134, 136 (e.g., computer systems, laptops, cell phones, personal digital assistants, applications, etc.) that can connect to and communicate data via a communications network 122. Also connected to the communications network 122 is a network wagering venue 130. The network wagering venue 130 may also be referred to in some embodiments as a network wagering game venue, an online wagering venue, an online wagering website, a wagering network, or some other description that describes a location, or venue, where users can perform many types of wagering activity. The network wagering venue 130 can provide various types of wagering-related content, such as wagering games for users to gamble with, or other computerized or electronic-enabled gambling activity. The network wagering venue 130 can provide access to all types of activity that involves some degree of chance and gambling, or betting, based on the chance. Gambling games and activities offered on the network wagering venue 130 can include, but not necessarily be limited to, casino games, slot games, table games, sports betting, bingo, wagering pools, fixed-odds betting, and so forth. The network wagering venue 130 can include account servers (e.g., wagering account servers, social network account servers, etc.), that users can subscribe to, and on which the users can store personal, accounting, and other information. The network wagering venue 130 can also include one or more servers that provide wagering-related content to the clients 132, 134, 136. Clients 132, 134, 136 can present, respectively, a display 102 that presents an application capable of presenting network content, such as a web browser 104. Some client devices (e.g., the “cell phone” client 136) may present more compact displays of content because of limited screen space. The web browser 104 can present different wagering related content at different times to different users that utilize the clients 132, 134, 136 to access the network wagering venue 130. Sometimes, however, the system 100 can present a network-wide (e.g., site-wide) event in which all users can access and/or participate in, either as a wagering game participant (e.g., a player) or as an observer (e.g., an audience member). The system 100 can notify all users of the network wagering venue 130 (e.g., via a notification panel 106) that the event has commenced and provide participation options, settings and/or controls that a user can use to participate in the event. A casino network 140 can also be connected to the communications network 122. The casino network 140 can present wagering games on wagering game machines (e.g., FIGS. 10 and 11), and other client type devices, within the casino network 140. The wagering game machines, and other client type devices, can also access the network-wide event. In some embodiments, the network-wide event can select any user of the network wagering venue 130 to perform an activity that other users may find entertaining. For example, the network-wide event can present a user's activity when playing a specific game that at which the user is having an amazing run of luck or that is especially important. In other examples, the system 100 can select a user, or users, to perform a special wagering game, as a bonus game. In both these examples, and in other examples, a user's wagering activity can provide a form of entertainment that other users may find interesting, and which other users may want to participate in as observers, betters, etc. In some embodiments, the system 100 can hold contribution amounts from all bets for any wagering activity performed within the network wagering venue 130, whether on traditional casino games or other gambling activity. All users, therefore, of any gambling activity can be eligible to be selected by the system 100 as a host, player, or other performing participant of the network-wide event. Although FIG. 1 describes some embodiments, the following sections describe many other features and embodiments. Part Example Operating Environments: This section describes example operating environments and networks and presents structural aspects of some embodiments. More specifically, this section includes discussion about wagering game system architectures. Part Wagering Game System Architecture: FIG. 2 is a conceptual diagram that illustrates an example of a wagering game system architecture 200, according to some embodiments. The wagering game system architecture 200 can include an account server 270 configured to control user related accounts accessible via a network wagering venue, a wagering game network, a social network, etc. The account server 270 can store and track player information, such as identifying information (e.g., avatars, screen name, account identification numbers, etc.) or other information like financial account information, social contact information, etc. The account server 270 can contain accounts for social contacts referenced by the player account. The account server 270 can also provide auditing capabilities, according to regulatory rules, and track the performance of players, machines, and servers. The account server 270 can include an account controller 271 configured to control information for a player's account. The account server 270 can also include an account store 272 configured to store information for a player's account. The wagering game system architecture 200 can also include a network wagering venue server 250 configured to control wagering game content, provide random numbers, and communicate wagering game information, account information, and other information, to and from a client 260. The network wagering venue server 250 can include a content controller 251 configured to manage and control content for the presentation of content on the client 260. For example, the content controller 251 can generate game results (e.g., win/loss values), including win amounts, for games played on the client 260. The content controller 251 can communicate the game results to the client 260. The content controller 251 can also generate random numbers and provide them to the client 260 so that the client 260 can generate game results. The network wagering venue server 250 can also include a content store 252 configured to contain content to present on the client 260. The network wagering venue server 250 can also include an account manager 253 configured to control information related to player accounts. For example, the account manager 253 can communicate wager amounts, game results amounts (e.g., win amounts), bonus game amounts, etc., to the account server 270. The network wagering venue server 250 can also include a communication unit 254 configured to communicate information to the client 260 and to communicate with other systems, devices and networks. For example, the communication unit 254 can track and communicate with community wagering game servers, account servers, community servers, social networking servers, file sharing servers, etc. The network wagering venue server 250 can also include a network event tracker 255 configured to track data related to network-wide wagering game events, including data related to game results, awards, social contacts, player accounts, etc. The network wagering venue server 250 can also include a network event controller 256 configured to control presentation of network-wide wagering game events including controlling views of network-wide games, selecting players to play the network-wide games, inviting network users to view and participate in the network-wide games, controlling interactivity and communication between players and other network users, etc. The network wagering venue server 250 can also include an agency controller 257 configured to determine data related to long-term, network-wide games, determine that a selected player is off-line, and generate options for wagering agents to perform a network-wide game as an agent of the selected user account. The network wagering venue server 250 can also include a progressive game module 258 configured to determine contribution holds from wagering game bets from all wagering games available on a network wagering venue, and associate the holds with a progressive jackpot. The wagering game system architecture 200 can also include at least one client 260 configured to present wagering games and receive and transmit information to control and present online wagering games. The client 260 can include a content controller 261 configured to manage and control content and presentation of network wagering venue content on the client 260. The client 260 can also include a content store 262 configured to contain content to present on the client 260. The client 260 can also include a processor 263 configured to process wagering game content, present online wagering game objects, control gaming devices, etc. The client 260 can also include a wagering game module 264 configured to control presentation of network-wide wagering game events for a network wagering venue. The wagering game system architecture 200 can also include a web server 290 configured to control and present an online website that hosts wagering games and other wagering activity. The wagering game system architecture 200 can also include a social network server 240 configured to control social network interactivity, features, and functionality for a wagering game social network, or other social networks, integrated with a network wagering venue. The social network server 240 can include a network event social feature controller 241 configured to present features that users of a social network can utilize in conjunction with a wagering game network, a wagering game website, an online casino, or other network gaming venue. For example, audience members that are social contacts with a player can interact with each other, and with the player, during a network-wide gaming event. In some embodiments, the network event social feature controller 241 can also be a part of the network wagering venue server 250. The network event social feature controller 241 can provide chat features, betting features, award features, award redemption features, etc. The social network server 240 can also include a social network award controller 242 configured to provide awards to user accounts that participate socially (e.g., as audience members) of a network-wide wagering game event. The social network award controller 242 can offer incentives and awards for participating as observers and interactive participants of the network-wide wagering game event. The social network award controller 242 can also redeem awards, Each component shown in the wagering game system architecture 200 is shown as a separate and distinct element connected via a communications network 222. However, some functions performed by one component could be performed by other components. For example, the network wagering venue server 250 can also be configured to perform functions of the content controller 261, the content store 262, the wagering game module 264, the network event social feature controller 241, the social network award controller 242, and other network elements and/or system devices. Furthermore, the components shown may all be contained in one device, but some, or all, may be included in, or performed by multiple devices, as in the configurations shown in FIG. 2 or other configurations not shown. For example, the progressive game module 258 may itself be a separate server, or associated with other servers (e.g., a progressive game server). In another example, the account manager 253 and the communication unit 254 can be included in the client 260 instead of, or in addition to, being a part of the network wagering venue server 250. Further, in some embodiments, the client 260 can determine wagering game outcomes, generate random numbers, etc. instead of, or in addition to, the network wagering venue server 250. In some embodiments, the client 260 can be a wagering game machine. A wagering game machine can take any suitable form, such as floor standing models, handheld mobile units, bar-top models, workstation-type console models, surface computing machines, etc. Further, a wagering game machine can be primarily dedicated for use in conducting wagering games, or can include non-dedicated devices, such as mobile phones, personal digital assistants, personal computers, etc. In some embodiments, clients (e.g., computer systems, wagering game machines, etc.) and servers (e.g., network wagering venue server 250, wagering game servers, etc.) work together such that the clients can be operated as thin, thick, or intermediate clients. For example, one or more elements of game play may be controlled by a client or a server. Game play elements can include executable game code, lookup tables, configuration files, game outcome, audio or visual representations of the game, game assets or the like. In a thin-client example, the server can perform functions such as determining game outcome or managing assets, while the client can present a graphical representation of such outcome or asset modification to the user (e.g., player). In a thick-client example, the client can determine game outcomes and communicate the outcomes to the server for recording or managing a player's account. In some embodiments, either the client or the server can provide functionality that is not directly related to game play. For example, account transactions and account rules may be managed centrally (e.g., by the network wagering venue server 250, or other wagering game server(s)) or locally (e.g., by the client 260). Other functionality not directly related to game play may include power management, presentation of advertising, software or firmware updates, system quality or security checks, etc. Furthermore, the wagering game system architecture 200 can be implemented as software, hardware, any combination thereof, or other forms of embodiments not listed. For example, any of the network components (e.g., the wagering game machines, servers, etc.) can include hardware and machine-readable media including instructions for performing the operations described herein. Machine-readable media includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a wagering game machine, computer, etc.). For example, tangible machine-readable media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory machines, etc. Machine-readable media also includes any media suitable for transmitting software over a network. Part Example Operations: This section describes operations associated with some embodiments. In the discussion below, some flow diagrams are described with reference to block diagrams presented herein. However, in some embodiments, the operations can be performed by logic not described in the block diagrams. In certain embodiments, the operations can be performed by executing instructions residing on machine-readable media (e.g., software), while in other embodiments, the operations can be performed by hardware and/or other logic (e.g., firmware). In some embodiments, the operations can be performed in series, while in other embodiments, one or more of the operations can be performed in parallel. Moreover, some embodiments can perform more or less than all the operations shown in any flow diagram. FIG. 3 is a flow diagram (“flow”) 300 illustrating presenting network-wide wagering game events in a network wagering venue, according to some embodiments. FIGS. 1 and 6 are conceptual diagrams that help illustrate the flow of FIG. 3, according to some embodiments. This description will present FIG. 3 in concert with FIGS. 1 and 6. In FIG. 3, the flow 300 begins at processing block 302, where a wagering game system (“system”) determines one or more user accounts that are eligible to participate in a network-wide wagering game event. The network-wide wagering game event can occur on a network wagering venue, such as a website. The system can determine that the one or more user accounts are eligible to win at least some portion of awards available for the network-wide wagering game event. For instance, the system can determine that the players have met or performed one or more qualifying operations, activities, tasks, or conditions. For example, the system can determine that a player has collected multiple items on a website, from various wagering games. In another example, the system can determine that a player has made a wager on any wagering game within the network wagering venue within a given time period. The system can require that the player perform financial requirements, such as wagering, or betting, certain limits of money (e.g., $10 denomination bets qualify for some types of network-wide events, whereas $1 denomination bets qualify for other types of network-wide events). The network-wide event can allow all users of the network wagering venue to be eligible for some events as some form of participant (e.g., the system can review everyone's account for the last 30 seconds or minute before triggering the network-wide event, and determine that players that have bet within that time period are eligible to play the network-wide wagering game event). For instance, a player may be eligible to be selected as a host, or performing participant, based on certain qualifications made by that player, while all other users of the network wagering venue can also participate, but as lesser participants (e.g., audience members). The system can provide different awards to different types of participants. For example, the system can provide monetary awards, credits, cash, etc. to performing participants for performing during the event. The system can provide lesser awards, in some cases, to audience member participants, for performing as audience members during the event. In some embodiments, the network-wide event is a surprise, or mystery, event, that the system presents at random times. In other embodiments, however, the system can pre-plan the network-wide events and send out invitations far in advance. The system can notify players of qualifying activities that the players must perform to be eligible to participate as players, or playing performers, for the event (e.g., play five different wagering games within a week's period). In some embodiments, the eligibility could be based on group play or a competition environment (e.g., the system indicates that at the end of the week it will hold a network-wide wagering game event, but to be eligible to perform, a user will have to complete or perform a certain number of group activities to be eligible). The flow 300 continues at processing block 304, where the system selects at least one of the one or more user accounts to be a player that plays in the network-wide wagering game event. In some embodiments, the system can allow a single player into the network-wide wagering game event as a player participant and can show only the first player in the event (i.e., lock out views of other people). In other embodiments, however, the system can present multiple independent instances of the network-wide wagering game event. For example, multiple players can trigger multiple different, independent, instances of the network-wide wagering game event at, or around, the same time. When multiple players are in the network-wide wagering game event, then the system can present multiple views (e.g., split screens of the event) or give options for users to select which event they would like to attend at the time. Thus, users can have the option to select which event in which they want to participate. In some embodiments, the system can provide features so that a user account can subscribe to see only friends' instances of network-wide wagering game events instead of others they do not know, if they occur at the same time. Some network-wide events can be so significant, however, that system may only present one instance of the network-wide wagering game event, although multiple players may be eligible to participate. In some embodiments, the system can randomly select one person to perform for the entire group of eligible participants. In other embodiments, however, the system can select multiple players to players to perform in turns in the event. Whoever is currently performing (whether one person at a time, or in turns) the system can determine an avatar for the player and put their avatar in a prominent place on the view of the network-wide wagering game event (e.g., in the center of a screen view) to indicate who is performing. The system can randomly select who is next. Some players who are in the event can opt out of performing. Some players can group together as groups to perform. The system can choose the performer based on a number of friends. The system can also choose performers based on recent activity performed by their friends on the network wagering venue. The system can also auction the opportunity to perform in the event. For instance, if multiple players are eligible, the system could hold an auction for the opportunity to be selected as the player participant. In some embodiments, when the award for the network-wide event is incremental, and progressive (e.g., when an award for participating in the network-wide event is a progressive jackpot), then the system can increase the auction increments as the progressive jackpot amount grows. The system could also have a “buy-it-now” option, to by-pass the auction process if the player provides a high enough bid. In some embodiments, the system can include unknown, or random, components, into the selection process to reduce the predictability of the selection process. In some embodiments, the system can select players that are not logged in to the network wagering venue, such as players who have characters running in long-term games on the system (e.g., fish-tank games that are running while the player is not logged on). In such cases, the system can present a remote notification (e.g., email, instant message, text message, phone call, etc.) to the player who is not logged and hold the network-wide wagering game event for the player until the player can log on again. The system can also can assign agency, or provide an option for the player to assign an agent (e.g., friend, bot, etc.) to play the game for them if the player's account is selected when the player is not logged on. The system can also present capabilities for a player to play remotely (e.g., via a cell phone). The flow 300 continues at processing block 306, where the system presents a notification to users of the network wagering venue that the player will play the network-wide wagering game event. In some embodiments, the system can present a notification to all users that are logged on. In one example, the system can interact with a news feed, ticker, etc. on a website so that when a player enters the network-wide wagering game event, the news feed breaks out of its normal mode to notify all users on the site that someone has entered the network-wide wagering game event. The system can also publish the news feed on an instant messaging network, so that it sends messages to users that are logged in or logged off and to contacts of those users that may be outside of the network wagering venue network. In some embodiments, when a network-wide event has been triggered, or when a network-wide event will be initiated, the system can present a count-down meter (and accompanying visual and audio effects) that indicate an amount of time until a player will enter the network-wide wagering game event. The system can select a time period for the counter that serves a marketing purpose. For example, in some embodiments, the system can select a time period that is long enough to engage maximum interest in the event or to allow users enough time to complete qualifying activities that would make them eligible to potentially participate as player participants. In other embodiments, however, the system can first select a player and then present the count-down meter. The system can notify users that someone has already been selected so that users are not confused into thinking that they might be able to qualify for that particular event based on current activity. In some embodiments, the system can present a notification to all social contacts of the player, that may not be online, which have indicated a desire to be notified when the player is selected to play the network-wide wagering game event. The flow 300 continues at processing block 308, where the system determines that at least some of the users desire to participate in the network-wide wagering game event as audience member users. In some embodiments, the system can present a control (e.g., a button), a link, a news feed, or other mechanism where a user can select an item presented on a web-browser, or other display, on a client. For example, in the case of a news feed, the user can click on the news feed that indicates the network-wide wagering game event to express a desire to view the event. FIG. 1 shows a notification panel 106 that pops up and presents a button for the user to view a game room, a chat room, or other such view, of the network-wide wagering game event. In some embodiments, the system can read from an account setting that indicates that the user would automatically want to participate when the player is selected. The flow 300 continues at processing block 310, where the system presents a presentation of the network-wide wagering game event to the player and the audience member users. The presentation can include a web-page, a Flash-animation, toolbars, videos, image maps, graphics, chat screens, instant messaging controls, player settings, sounds, etc., or any combinations thereof. The presentation can present different controls and functionality to a participant of the event based on the participant's role in the event. For example, the system can present playing controls (e.g., spin buttons, selector buttons or functions, etc.) to a player participant, so that the player can activate, select, control, or otherwise manipulate playing elements of the network-wide wagering game event. On the other hand, if a user is an audience member participant, the system can present a view that shows a representation (e.g., an avatar) of the player participant as the player participant plays the event, but the system would not necessarily provide playing controls to the audience member participant. However, the system can provide user communication functionality so that the audience member participants can function as audience members. Thus, the system provides sufficient functionality in the presentation for a player participant to play the network-wide wagering game event and for the audience member participants to watch and participate as audience members. The system can also present functionality for the player participant to interact with audience members (e.g., multi-way chat features). The flow 300 continues at processing block 312, where the system presents one or more interactive user features to the audience member users that the audience member users can use to participate as audience members of the network-wide wagering game event. FIG. 6 illustrates an example of a presentation of a network-wide wagering game event (e.g., a site-wide, progressive bonus game) in a web-browser application (“web browser”) 602. In FIG. 6, a computer system 645 is connected to a network wagering venue server 650. The computer system 645 presents a display of the web browser 602. The system 600 provides content from the network wagering venue server 650 and presents the content on the web browser 602. The content is related to a wagering game event that is broadcast to multiple users on a website for a network wagering venue. FIG. 6 presents information from the perspective of an audience member of the wagering game event. The web browser 602 includes game play information in a game play section 630 (e.g., playing elements 608 that a player participant avatar 609 appears to select during the wagering game event, game status information in a bonus round progress section 618 related to the player's progress during the wagering game event, etc.). The system 600 can also present features that relate to the network-wide wagering game event, such as betting features. For example, the web browser 602 presents a betting console 631 that the audience member can use to shadow bet, side bet, or perform other wagering activity (e.g., an audience member can bet side-bets on how far a player progresses in the network-wide wagering game event). For example, the web browser 602 can present a selector dropdown control 620 than an audience member participant can use to select a game result graphic that may appear during the wagering game that is being played. The audience member participant can also specify a bet amount in a bet amount control 622 and place the bet using a bet activation control 624. The system 600 can also provide other financial related features, such as account transfer features and “buy-in” features. For instance, an audience member can use “buy-in” controls to buy-in, or pay an amount of money, that would allow the user to win some amount of what the player participant wins (e.g., may not win the full amount that the player would win, but a smaller amount). The system 600 can also present chat features 632 that audience member can use to chat with other audience members participants and with the player participant. The chat features 632 can include a chat display 626 that displays text communications, a chat text entry section 628, a sender selector control 603 and a send activation control 601. The flow 300 continues at processing block 314, where the system incorporates one or more other network-wide event participants into the network-wide wagering game event. In some embodiments, the system can present special features that reward audience members. For example, the system can include a special game that only audience members can play while watching the network-wide wagering game event. The special game may be only activated for friends of the player participant(s). The system can also provide prizes to audience members for watching the event. The system can provide awards to audience members based on events that occur during the network-wide event (e.g., if the player participant gets to level three, then, because the audience member is watching the event, the audience member gets a prize). In some embodiments, the system can combine qualifying audience member activity with specific events that the player performs from the network-wide wagering game event (e.g., if the audience member is playing the special game, and has bet over $10, and the player participant gets to level three, then the system can provide a prize to the qualifying audience member). In some embodiments, the system can involve an audience member participant in the game play by inserting an identifier (e.g., an avatar) that identifies the audience member and gives the audience member a reward (e.g., a prize, a chance to play special games, a chance to pick items, etc.). For example, in FIG. 6, the system 600 can utilize an avatar 616 associated with the audience member user. The avatar 616 can be associated with a user account belonging to the audience member user (e.g., see avatar 716 belonging to the player account of the current audience member user, PokerAce). Referring still to FIG. 6, the system 600 can present the avatar 616 in connection with logon information 604 on the web browser 602. The system 600 can randomly select one of the audience participants, such as PokerAce, and present its avatar in the game play (see the avatar 616 next to the star element 614 within the game play section 630). The system 600 can then present a notification section 633 notifying the audience member participant (e.g., PokerAce) that its avatar 616 was selected and that an award can be selected via one or more award selection controls (e.g., button 605). In some embodiments, the system 600 can present one or more options for the network-wide wagering game event participant to incorporate one or more social contacts into the network-wide wagering game event (e.g., to pick elements). The player participant can use the options to select audience members as part of the network-wide wagering game event. For instance, a player can select an audience member to play a portion of a wagering game presented in the network-wide event. If the audience member performs positively, or accomplishes a specific goal, then the system 600 can award the player participant for the audience member's activity (e.g., the system 600 can prolong the player's duration in the network-wide wagering game event, the system can increase credit values in the network-wide wagering game event, etc.). For example, in FIG. 6, the system 600 can provide “assistance” functionality, or features, that that permit audience members to assist the player participant in performing a game, or other activity, of the network-wide event. For example, the system 600 can present an assistance section 637 with one or more activity controls 607 that the audience member can select to perform activities (e.g., visit a vendor website, play a game, accept an offer, view an advertisement, make a comment, etc.). In some embodiments, the system 600 can determine the activity that the other network-wide event participants complete and adjust the game rules, results, wagering game playing elements, etc., to enable a higher chance of winning (e.g., produce more win elements, increase the win values to win value elements, produce more progression elements, produce fewer loss elements, etc.). Thus, an audience member's activity can help, or enhance, the player's chance of winning and/or advancing in the network-wide wagering game event. The flow 300 continues at processing block 316, where the system incorporates one or more outside events into the network-wide wagering game event. In some embodiments, the system can incorporate a predictable event that occurs outside of a wagering game venue (e.g., not a random number generated by wagering venue servers or devices). The outside, or external, event can have a predictable occurrence (e.g., pre-known that it will occur), but also has a random value associated with the event when it occurs (e.g., a final value of a stock index, a final score in a sporting event, a result of a Senate vote, etc.). The system can incorporate the random value into the game as a result factor, a bet factor, a selection factor, etc. The outside event could be an event that the system knows about ahead of time, or that occurs regularly, (e.g., a daily ending time of trading for US stock markets), but that has a random result (e.g., the last digit of the Dow Industrial Average at the daily ending time). The system can tie the outside event into account services (e.g., notify the player through the account that the Dow Industrial Average ended at the value). The system can use the outside event as an eligibility condition for being selected to play in a network-wide wagering game event (e.g., “guess the number of the Dow Industrial Average at the end of day to be eligible to receive a network-wide wagering game event.”) In some embodiments, the system can select the outside event from a player preference setting and utilize the outside event during the network-wide wagering game event (e.g., select a player setting that indicates that the Dow Industrial Average is a preferred outside event which the system can utilize in conjunction with results, bets, etc.). FIG. 4 is a flow diagram (“flow”) 400 illustrating presenting a site-wide, progressive bonus game in an online wagering venue, according to some embodiments. FIGS. 5, 6, and 7 are conceptual diagrams that help illustrate the flow of FIG. 4, according to some embodiments. This description will present FIG. 4 in concert with FIGS. 5, 6 and 7. In FIG. 4, the flow 400 begins at processing block 402, where a wagering game system (“system”) receives one or more contribution amounts to a site-wide progressive bonus game (“site-wide bonus game”) from all available wagering games played on an online wagering venue. A site-wide bonus game is a network-wide event that is broadcast across a web site, or “online” wagering venue, and is thus referred to, in this example, as a “site” wide event. The “event,” in this example, is a bonus game based on a progressive jackpot. In some embodiments, the system can configure all available games on the website to contribute a progressive contribution amount, so that any wagering game and/or other gambling activity (e.g., slot games, table games, fixed-odd bets, raffles, bingo, etc.) can potentially trigger the site-wide bonus game. A game that triggers the site-wide bonus game may be referred to as the “base” game, or game from which a portion of the progressive fund was funded, and from which the “bonus” game is initiated. The system can hold a contribution amount (“hold”) for all the games and contribute the hold to the progressive jackpot fund, which can be used later during the site-wide bonus game to provide awards to a player participant, and in some cases, to audience member participants. Some games on the website, however, may contribute higher holds than other games, or in other words, contribute a higher percentage of the players bet to the progressive fund. For example, table games (e.g., roulette, black-jack, poker) all may have holds from the base game that are much lower compared to holds from slot games. Consequently, players who play slot games may have higher chances of being selected for the site-wide bonus game. FIG. 5 illustrates an example wagering game system (“system”) 500 that includes a configuration server 555 that can configure all wagering games on an online wagering venue to have different holds. The configuration server 555 is connected to an online gaming server 550 (e.g., a wagering game server, a progressive game server, etc.) via a communications network 522. The configuration server 555 can present a configuration display 502 with a game type selector 533. An operator can select the game type selector 533 and the configuration display 502 can present a list 530 of games related to the game type. Each game can have a hold percentage control 504, which can be utilized to set a percentage amount of a player's bet that will be contributed to the site-wide progressive bonus game fund. The flow 400 continues at processing block 404, where the system determines that an online wagering account user is eligible to participate in the site-wide bonus game. In some embodiments, the system can configure eligibility based on hold percentage and bet amount within a specific time period. For example, in FIG. 5, the configuration display 502 can include a bonus game eligibility section 532 with a game selection control 506. When the game selection control 506 is selected, the system 500 can present several configuration controls (e.g., a hold weight control 512, a social contact weight control 514, a bet weight control 515, and a bet eligibility control 513). Each of the configuration controls 512-515 can indicate values that can be factored into eligibility and selection algorithms for the site-wide bonus game. The bet eligibility selection control 513 can specify a time period, a number of games, or any other condition or factor, for which a player can be eligible to be considered for selection. In some embodiments, the system can include additional configuration settings, such as the additional configurations section 534, which includes settings related to (1) allowing multiple instances of the bonus game, (2) allowing community ride-along features (e.g., special games or prizes for being audience member participants), (3) tying selections and results to events outside of the online wagering venue, (4) selecting a single player from a group of selected, or equally eligible, players, (e.g., via a multiple player selector control 518), etc. The flow 400 continues at processing block 406, where the system selects the online wagering account user to be a player participant. In some embodiments, the system can select the player participant randomly (e.g., after a hand is completed, a spin is completed, etc.). In some embodiments, however, every individual game on the online wagering venue can have its own specific, unique, chance of triggering. In some embodiments, the player's chances of getting the site-wide bonus game is tied to the amount that the player bets based on the hold. So, the more that a player is contributing to the jackpot, at the time, the greater the chances can be. Also, the more that a game contributes to the jackpot (i.e., the “hold”) the greater the chances can be that a player may be selected. The chances of being selected, therefore, can be proportional to both the amount of the bet and the hold for the particular game. For example, some types of games produce more holds—slots may provide ten times more hold than black-jack games. As a result, the system can afford players who play games with higher holds a greater chance of being selected as a performing participant in a network-wide event. Similarly, even amongst the same type of game, some particular game themes may provide greater holds. The system can advertise that some games have greater holds, which may provide players with more incentives to play those specific games instead of others because the chances of getting the jackpot would be higher at the time. The system can configure, and advertise, new games, or less popular games, with higher holds, and, thus, increase interest in the new games or less popular games because they offer higher chances for being selected as a player in a network-wide bonus game event. For example, in FIG. 5, for the game of “blackjack”, as selected in the selection control 506, a user on the online wagering venue can have a different chance of being selected to participate in the site-wide progressive bonus game based the value of the user's activity related to the values specified in the configuration controls 512, 514, and 515. For instance, the chances for being selected as a player participant may not be entirely random. A portion of the selection factors may be based on random data, but chances can improve based on the hold for the game, an amount of a user's last bet (or average of last number of bets), a number of social contacts that the user has, etc. For example, the selection process that the system employs may be compared to a wagering pool selection process. In a wagering pool, a player can buy-in to the pool as many times as they want, like in a raffle contest where a player can buy as many raffle tickets as desired. All raffle tickets are then placed into a pool from which a raffle ticket is randomly selected. If a person purchases more raffle tickets than other people, then the person would have a greater chance that one of their tickets would be
{'bibliographic_information': "{'country': 'US', 'doc-number': '13709552', 'kind': 'B2', 'date': '20121210', 'extension': '84', 'disclaimer_text': 'This patent is subject to a terminal disclaimer.', 'invention_title': 'Presenting network-wide events in network wagering venue'}", 'source_file': './grant/2015/ipg150609.xml', 'source_data': 'USPTO-Grant'}