/hostgame – courtesy of WebAfrica
Exciting times! Twilight and WebAfrica have been in talks since many moons ago about setting up a hostbot. Well, the good news is that everything seems good to go. As of a few minutes ago, the server restarted with the new hosting functionality which allows WebAfrica customers to host DotA games on the WAGE hostbot. This has several benefits:
- No bandwidth is used if you’re on the WebAfrica network as the hostbot is located in the WAGE freezone.
- Stable, low latency host because the game is not hosted on DSL where many factors (lightning, cats..) can cause lag.
- Stats, replay and game saving and much more!
So, how to host a game? Simple:
- Login to Twilight using your WebAfrica account.
- Use the hostgame comand as follows:
/hostgame <level> <game name>
The bot will then host a game at the given level (currently only supports DotA). Once your game is up you will need to spoof check by whispering the WAGE bot:
/w WAGE spoof
You will then have several commands available to you (listed at the end of this post).
Please note that this feature is currently in a trial phase. We have limited the maximum number of games to 5. If you find your game is not being hosted, then you might want to join the WebAfrica channel on the server in case the bot is giving error output. Also please note that only one game can be in the lobby at a given time. For example, if Bob hosts [5]AP, then you will not be able to host another game until that game starts or is cancelled. As such, please be considerate when hosting games and don’t go idle for hours in the lobby (or wait 15 minutes for your friends). We will put up official usage rules in due course, but for now just apply common sense to avoid racking up punishments.
We hope you enjoy this service and the low latency, free DotA games it brings.
A couple of points:
- Consumers of WebAfrica’s IS accounts do not receive the hosting/free-usage benefits. Those benefits apply to users of the WebAfrica network only. This is similar to all other WAGE offerings.
- We are working on improving the feedback the bot gives (when both successfully and unsuccessfully hosting games).
- This is a trial service – please give us meaningful feedback and don’t abuse the service!
List of commands
In game lobby
.a alias to .abort .abort abort countdown .announce <sec> <msg> set the announce message (the bot will print <msg> every <sec> seconds), leave blank or "off" to disable the announce message .autostart <players> auto start the game when the specified number of players have joined, leave blank or "off" to disable auto start .autosave <on/off> enable or disable autosaving .check <name> check a user's status (leave blank to check your own status) .checkme check your own status (can be used by non admins, sends a private message visible only to the user) .clearhcl clear the HCL command string .close <number> ... close slot .closeall close all open slots .comp <slot> <skill> create a computer in slot <slot> of skill <skill> (skill is 0 for easy, 1 for normal, 2 for insane) .compcolour <s> <c> change a computer's colour in slot <s> to <c> (c goes from 1 to 12) .comphandicap <s> <h> change a computer's handicap in slot <s> to <h> (h is 50, 60, 70, 80, 90, or 100) .comprace <s> <r> change a computer's race in slot <s> to <r> (r is "human", "orc", "night elf", "undead", or "random") .compteam <s> <t> change a computer's team in slot <s> to <t> (t goes from 1 to # of teams) .dl <name> alias to .download .download <name> allow a user to start downloading the map (only used with conditional map downloads, it tries to do a partial match) .fakeplayer create or delete a fake player to occupy a slot during the game (the player will not do anything except stay AFK) .from display the country each player is from .hcl <string> set the HCL command string .hold <name> ... hold a slot for someone .latency <number> set game latency (20-500), leave blank to see current latency .lock lock the game so only the game owner can run commands .messages <on/off> enable or disable local admin messages for this game (battle.net messages relayed to local admins in game) .mute <name> mute a player (it tries to do a partial match) .open <number> ... open slot .openall open all closed slots .owner [name] set game owner to yourself, optionally add [name] to set game owner to someone else .ping [number] ping players, optionally add [number] to kick players with ping above [number] .priv <name> rehost as private game .pub <name> rehost as public game .refresh <on/off> enable or disable refresh messages .say <text> send <text> to all connected battle.net realms as a chat command (this command is HIDDEN from other players) .sendlan <ip> [port] send a fake LAN message to IP address <ip> and port [port], default port is 6112 if not specified .sp shuffle players .start [force] start game, optionally add [force] to skip checks .stats [name] display basic player statistics, optionally add [name] to display statistics for another player (can be used by non admins) .statsdota [name] display DotA player statistics, optionally add [name] to display statistics for another player (can be used by non admins) .swap <n1> <n2> swap slots .synclimit <number> set sync limit for the lag screen (10-10000), leave blank to see current sync limit .unhost unhost game .unlock unlock the game .unmute <name> unmute a player (it tries to do a partial match) .version display version information (can be used by non admins, sends a private message visible only to the user) .virtualhost <name> change the virtual host name .w <name> <message> send a whisper on every connected battle.net realm from the bot's account to the player called <name> (this command is HIDDEN from other players)
In game
!autosave <on/off> enable or disable autosaving !check <name> check a user's status (leave blank to check your own status) !checkme check your own status (can be used by non admins, sends a private message visible only to the user) !fppause force the FakePlayer (if it exists) to pause the game !fpresume force the FakePlayer (if it exists) to resume the game !from display the country each player is from !kick <name> kick a player (it tries to do a partial match) !latency <number> set game latency (20-500), leave blank to see current latency !lock lock the game so only the game owner can run commands !messages <on/off> enable or disable local admin messages for this game (battle.net messages relayed to local admins in game) !mute <name> mute a player (it tries to do a partial match) !muteall mute global chat (allied and private chat still works) !owner [name] set game owner to yourself, optionally add [name] to set game owner to someone else !ping ping players !say <text> send <text> to all connected battle.net realms as a chat command (this command is HIDDEN from other players) !stats [name] display basic player statistics, optionally add [name] to display statistics for another player (can be used by non admins) !statsdota [name] display DotA player statistics, optionally add [name] to display statistics for another player (can be used by non admins) !unlock unlock the game !unmute <name> unmute a player (it tries to do a partial match) !unmuteall unmute global chat !version display version information (can be used by non admins, sends a private message visible only to the user) !w <name> <message> send a whisper on every connected battle.net realm from the bot's account to the player called <name> (this command is HIDDEN from other players)
Rule Change — Forfeit Rule Is Now A Bit More Intense & Forum Bug Fix
Changed rule for forfeiting games:
Used to be 20 kills behind in 30 minutes, now changed to:
Players may forfeit a game (from the losing team) if they are 25 kills behind the winning team before 25 minutes. Four out of the five players, on the losing team, will need to vote for the forfeit for this to be legal.
This will be strict, and it will be upheld. If you quit at any time before this you may be punished via the game or ticket system.
No restores will come from this rule.
We’ve changed it to 25 in 25 due to many players simply giving up. If this is abused, or becomes as lame as the previous rule it will be removed. Players will then be required to play the entire game without the forfeit option.
So, please use this in a rare case where you are really getting smashed.
Come backs allow for awesome games.
Also, fixed bug on forum:
Click Twilight Gaming Forum no longer takes you to main Twilight Gaming page, it will take you to forum front page.
Staff Amendments: Take Three!
Forced Leave:
DeAtH-rOaD, Storm and Whitewolf2, as of the 22nd of February until the 8th of March, shall be taking a two week break.
During this period, we’d like to see more activity from the ops, we’ve noticed you guys being a little hesitant on the harder tickets and gracing the other three with them; with great power comes great responsibility.
Amendments:
Operator Removals:
DeMoNiK
VeNGeNCe
Operator Additions:
TSR
Inquisitor Removals:
HamstaDawG
Shingami_Ryu
Inquisitor Additions:
DeMoNiK
Moderator Removals:
TSR
*Njarfie and ToXic have been added on a trial basis for the CA Team.
*Goddy has been added to the trial list for the Operator Team
Twilight Contacts:
Community Activists: ca @ tga.za.net
Inquisitors: inq @ tga.za.net
Development: dev @ tga.za.net
Support: support @ twilightgaming.co.za
League: league @ tga.za.net
Signup issues resolved
For the past little while we’ve been having some issues with users signing up with mixed-case passwords. We are pleased to announce that these issues have been resolved. In-game signups have once again been disabled. Further reading below.
Mumble 1.2.2
The Murmur server has been updated to the latest version of Murmur. Please ensure your client is updated to 1.2.2 to avoid connection issues.
Rule Changes as of 07 February 2010
- Removed the blasphemy rule.
- Changed the game modes rule
- Changed dropping/countdown rule
- Amended hacking rule to include name spoofing (this was already there, but made it more obvious now)
Dropping during countdown/load screen:
If you drop during the countdown you can only be punished if somone manages to printscreen you leaving (server input required) during the countdown.
If you drop during the load screen and you are punished, you can be restored if you can (1) prove it, or (2) someone in game print screens that you left the game during load. If you choose to be restored via option 2, the player supporting you will need to prove that you were being punished in that game.
Game modes
It is required that the full game mode be present in the game name. Failure to comply will nullify your games legitimacy.
To change the game mode when in the game lobby the host will need to ask the players waiting to play. Six or more of the players must agree to the change. If the host fails to adhere to these rules you may leave the game due to the game mode being displayed incorrectly.
This means, it is exempt from all further DotA rules (but not server rules). For example, players may leave the game at any point, but are required to uphold general server etiquette.
Visit our new Inquisitor role.
Visit our Knowledge base for all help and rules here.
Remember our quick-links to move around:
http://help.twilightgaming.co.za/ — All help files
http://register.twilightgaming.co.za/ — Register a new account
http://ticket.twilightgaming.co.za/ – Quick link to open a new ticket
Inquisitors — What they do, and why we need them?
Who are the inquisitors? The Inquisitors are a group within the admin team that primarily ensure that staff members do not abuse their powers. Inquisitors going forward will also handle all staff related matters and be more involved in tickets. In general if you’re having issues as a twilight admin, you should speak with an inquisitor.
The inquisitors are responsible for the following:
- Staff and General Complaints
- Staff Related Matters
- Disciplinary Matters
- Transfer Requests
- Resignation
- Staff Abuse Cases
- Ticket Reviews
- Tournament Reviews
- General Information and Enquires
1. Staff and General Complaints
Inquisitors will handle all complaints directed towards twilight. If an email complaint is received, this should be forwarded to inq@tga.za.net. For any other form of complaint either email these to inq@tga.za.net or speak to an inquisitor directly. This includes complaints coming from people on the server as well as staff complaints against other staff members.
Staff members should always first speak to the Inquisitor team before contacting the Root team. Any staff member that feels that an Inquisitor is being unfair should first speak to another member of the Inquisitor Team. If the staff member feels that the Inquisitor team as a whole is being unfair, they may contact the Root admins directly.
2. Staff Related Matters
a. Disciplinary Matters
All disciplinary issues will continue to be handled in the same way. The Inquisitor team will review and vote on each case.
b. Transfer Requests
Not enjoying your current role? You may apply every 3 months to change positions. So for example if you’re tired of being a mod/op/inq/ca why not try something else. If you’d like to try something different, drop a note to the Inquisitors and we will look at availability within the other teams.
c. Resignation
If you’re planning on leaving the administration team for whatever reason, please drop a note to inq@tga.za.net
3. Staff abuse cases
All cases of serious staff abuse should be forwarded to the Inquisitors to handle. This can either be done via email, or a ticket. This is to eliminate “abuse” that may occur when a staff member deals directly with a user abusing them. Please note: If you are sexually abused by a user, call childline.
4. Ticket Reviews
The Inquisitors will make sure that the tickets are being created, and dealt with, correctly. If there is a problem with a certain ticket, the Inquisitor team will handle this appropriately. An Inquisitor will only intervene in a few cases where the Operator is making a mistake on a ticket. In the event that an Inquisitor changes an action on a ticket, you should consult with the Inquisitors before changing it back. Any “action” changes made to a ticket by an Inquisitor will be mailed through to the general Operator email. (op@tga.za.net)
Operator jobs will not change at all. Operators will still be required to open and deal with tickets.
5. Tournament Reviews
The Inquisitors will also be making sure that tournaments are fair, and that tourneys maintain a certain level of professionalism. This includes discrimination better players, poor running of events etc. The Inquisitors will also make sure that the tournament winners receive their prizes for the respective events.
6. General Information and Enquires
If any staff member is unsure about rulings, a certain ticket, or general etiquette they should consult the inquisitors. If the inquisitors are unsure, they will contact the Root team about the matter. Please refrain from constantly going to the roots directly.
As always, comments and suggestions are welcome. Either visit the Inquisitors in #twilight.inq or drop them an email inq@tga.za.net
I would like to once again state: Operator jobs will not change at all. Operators will still be required to open and deal with tickets. They move forward as if nothing has happened.
Minor updates to server
The following updates have been applied:
- Server synchronised against PvPGN developments (mostly Westwood Online updates)
- Added the ability to target bans against certain clients
- Added a warning to /level if you are not activated
- /clan whisper no longer bypasses /dnd
All you need to know about accounts
There is still some lingering confusion about how accounts work. Here’s the low-down!
This article will explain how to validate an existing account or signup a new one. Once validated, you will be able to join games above level 20 and create a forum account. A brief note on softlocks:
Our new “softlock” allows us to restrict a user to a certain level of games without permanently altering their level. For example, a level 30 user might be restricted to level 20 games for the duration of the lock, but will still gain experience as if he was level 30. This system also automatically applies to non-validated accounts (see below) to force users to validate their accounts. Once validated, you will be able to use the forum and receive email notifications if tickets are raised against you. Having a valid account is essential to participation on Twilight.