Counter Strike 1.6 Online Asian Tournament 2009.

[Sad1d]

Ever dreamed on playing Counter Strike 1.6 tourney playing online ?

Ever imagined what skills u will gain with competiting with Asian teams ??

well now here is your chance.

Teams from Singapore , Malaysia , India , Pakistan , Philippine , Vietnam are participating this tourney , so i too thing that Bangladesh should attend this tourney.

And as SresHTHo said earlier that there are more then 10 Counter Strike 1.6 teams in Bangladesh , So i don't think that there will by any hesitation of teams in participating this tourney.

This tourney will be a great practice and experience to the teams who are gonna participate and a good warm up for doing better in WCG.And represent Bangladesh at the same time.

Just try pinging :

A typical V-street.net server : 202.63.160.186

A typical IGL server : 115.112.247.52


Just click start button >> go to run >> type cmd and enter >> type ping 202.63.160.186 -t and after that ping 115.112.247.52 -t

Reply here with the pings you get so i can get an idea of whether it will be playable for u and others in our region.

For more Details Call me : 01190393541

More updates and information are coming soon..Stay tuned.

[_Nviable]

Good stuff... lets see what HTH says...

202.63.160.186 -t:

Pinging 202.63.160.186 with 32 bytes of data:

Reply from 202.63.160.186: bytes=32 time=992ms TTL=118
Reply from 202.63.160.186: bytes=32 time=121ms TTL=118
Request timed out.
Reply from 202.63.160.186: bytes=32 time=119ms TTL=118
Reply from 202.63.160.186: bytes=32 time=239ms TTL=118
Request timed out.
Reply from 202.63.160.186: bytes=32 time=1050ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=531ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=967ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=829ms TTL=118
Reply from 202.63.160.186: bytes=32 time=388ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=987ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=121ms TTL=118
Reply from 202.63.160.186: bytes=32 time=847ms TTL=118
Reply from 202.63.160.186: bytes=32 time=837ms TTL=118
Reply from 202.63.160.186: bytes=32 time=769ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=577ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=912ms TTL=118
Reply from 202.63.160.186: bytes=32 time=120ms TTL=118
Reply from 202.63.160.186: bytes=32 time=1074ms TTL=118

ping 115.112.247.52 -t:

Pinging 115.112.247.52 with 32 bytes of data:

Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=1024ms TTL=118
Request timed out.
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=1044ms TTL=118
Reply from 115.112.247.52: bytes=32 time=369ms TTL=118
Request timed out.
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=664ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=1067ms TTL=118
Reply from 115.112.247.52: bytes=32 time=187ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=659ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=447ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=727ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=1017ms TTL=118
Reply from 115.112.247.52: bytes=32 time=192ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=691ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=1041ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=883ms TTL=118
Reply from 115.112.247.52: bytes=32 time=263ms TTL=118
Request timed out.
Request timed out.
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Request timed out.
Reply from 115.112.247.52: bytes=32 time=127ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Request timed out.
Reply from 115.112.247.52: bytes=32 time=126ms TTL=118
Reply from 115.112.247.52: bytes=32 time=128ms TTL=118
Request timed out.

[Scorp1o]

n0, am nt participating....jst interested in pinging........ :>

1st:

Ping statistics for 202.63.160.186:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 206ms, Maximum = 209ms, Average = 207ms

2nd:

Ping statistics for 115.112.247.52:
Packets: Sent = 72, Received = 72, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 138ms, Average = 127ms

[Sad1d]

n0, am nt participating....jst interested in pinging........ :>

1st:

Ping statistics for 202.63.160.186:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 206ms, Maximum = 209ms, Average = 207ms

2nd:

Ping statistics for 115.112.247.52:
Packets: Sent = 72, Received = 72, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 138ms, Average = 127ms

it's ok , thanx for posting da pings anyways.

[darkcrunk]

115 average on both servers. Playable. But not up to the edge.

Heck we dont play pro 1.6.

[Cyberreaper]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Cyberreaper Xition>ping 202.63.160.186ping 115.112.247
.52
Ping request could not find host 202.63.160.186ping. Please check the name and t
ry again.

C:\Documents and Settings\Cyberreaper Xition>ping 202.63.160.186

Pinging 202.63.160.186 with 32 bytes of data:

Reply from 202.63.160.186: bytes=32 time=545ms TTL=116
Reply from 202.63.160.186: bytes=32 time=585ms TTL=116
Reply from 202.63.160.186: bytes=32 time=703ms TTL=116
Reply from 202.63.160.186: bytes=32 time=521ms TTL=116

Ping statistics for 202.63.160.186:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 521ms, Maximum = 703ms, Average = 588ms

C:\Documents and Settings\Cyberreaper Xition>ping 115.112.247.52

Pinging 115.112.247.52 with 32 bytes of data:

Reply from 115.112.247.52: bytes=32 time=1998ms TTL=116
Reply from 115.112.247.52: bytes=32 time=446ms TTL=116
Reply from 115.112.247.52: bytes=32 time=405ms TTL=116
Reply from 115.112.247.52: bytes=32 time=478ms TTL=116

Ping statistics for 115.112.247.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 405ms, Maximum = 1998ms, Average = 831ms

C:\Documents and Settings\Cyberreaper Xition>

[Sad1d]

Updates : The games will be hosted frm Garena.

[sresHTHo]

good thing....reveal the details regarding whos hosting...where it is being hosted..etc....nd yea interested obviously...

[Pyro.Dynamics-]

I think lag will become a deciding factor in this case unless you can get the type of setup we had when we played SKOTH.

[SP|WeRewOLF]

i think lag will become a deciding factor in this case unless you can get the type of setup we had when we played skoth.

true!!

[SenSeiFAR]

If DotA will laag, I doubt CS will be even playable. =|. Let's see what BG or anyone else can do, to fix this. And hopefully, we can play with them and learn new stuff, if not win some! =D

[Sad1d]

Ill talk to da headadmin of dis tourney about out prob but all u have to do is get ready , dekhi singapore'e host manage kora jai naki.

[Z]

singapore keno bangladesh ei tou server ase .. bd vs bd games could be hosted in them ..

and actually bideshe online matches e 60-70 latency teo khele .. and sometimes 150+ latency niyeo khelte dekhsi .. its definitely a big disadvantage but they still play rather than not play at all..

[Pyro.Dynamics-]

Oder 150 latency thakleo delay khubi kom hoy! Was a time I used to play with 0 delay with Europe on Garena even when they showed 200+ ping. Ar I doubt even Singapore hosts will be good enough. I mean playing in lag is fine as long as your opponents are facing the same problems. If only one side is lagging, the other will capitalize and win, no problem.

[Sad1d]

singapore keno bangladesh ei tou server ase .. bd vs bd games could be hosted in them ..

and actually bideshe online matches e 60-70 latency teo khele .. and sometimes 150+ latency niyeo khelte dekhsi .. its definitely a big disadvantage but they still play rather than not play at all..

well did u read my thread ??
and wat do u mean by singapore keno bd server ase , bd v bd games could be hosted in dem ??
tomar ki monehoi je bd v bd khela porbey ??
It's as simple as dis , jei duita server disi oigulai 100 ms avg pawa jai , to me it shud be lagg free , if it still lags or any complains is given , SG er host deya hobey or a better host provide kora hobey.

[SenSeiFAR]

They play with 60 latency. TRUE.

BUT, their net is STABLE, something BD's net isn't. Not to mention wiring and other technical ¤¤¤¤, which is better abroad.

Still, I guess, we all should play and try. =)