Temple Siege G, Temple Siege G3e Released
Post #1 IAGG Jun 26 2011, 3:22 am
Post #2
Dem0nS1ayer
Jun 26 2011, 4:18 am
Post #3
Roy
Jun 26 2011, 4:44 am
|
Everything green is safe to eat.
|
Nope, today.
Wait... So IDT isn't working on TS anymore? ![]() ![]() ![]() ![]() ![]() ![]() Learn how to make EUDs: [EUD] A Mapmaker's Guide for Creating EPDs
Don't like learning? [EUD] EUD Generator Other stuff: [EUD] Text to Value Converter Bound Maker SC1 Maps: Dash: 1 2 3 4 5 6 7 8 9 X Jog: Original Warp Other: Super Mario SC Fireball Guard Your Civilian Strength Contest Interceptor Arena |
Post #4
ClansAreForGays
Jun 26 2011, 5:20 am
Post #10
Dem0nS1ayer
Jul 2 2011, 1:40 am
Post #11
lil-Inferno
Jul 2 2011, 1:51 am
Post #12
Dem0nS1ayer
Jul 2 2011, 2:20 am
|
;_;
|
Well he's complaining about a bug in a RECENTLY released version like it's the end of the world. He can play other versions (there's at least 20 other ones) until the bugs get fixed. Or if he's too stubborn to go back to an older version, then he can deal with it. No need to rage at the map maker by saying that he just keeps adding bugs. This guy obviously has never debugged anything in his life; obviously new bugs arise when you try to fix something. Maybe if he wasn't slobbering over every new version of the same old boring map, he'd realize this and stop being so impatient.
![]() ![]() ![]() ![]() ![]() ![]() KIND FUCKIN' REGARDS,
- DS |
Post #13 Tank_7 Jul 2 2011, 2:51 am
|
Well, I may have sounded harsh sorry, but it's really dissapointing to find a bug like 30 minutes into a good game. There's probably double use of some unit, location name, or death count... I do suspect IAGG could be more careful and text search for unit names, location names, and death counts when he wants to use them in some way. I mean, this is not a subtle bug, the L3 is a simple stun + aoe spawn kill, and now it just doesnt work.
This guy obviously has never debugged anything in his life; obviously new bugs arise when you try to fix something. ![]() ![]() ![]() ![]() ![]() ![]() |
Post #14 Zhuinden Jul 9 2011, 11:46 am
|
Well, I may have sounded harsh sorry, but it's really dissapointing to find a bug like 30 minutes into a good game. There's probably double use of some unit, location name, or death count... I do suspect IAGG could be more careful and text search for unit names, location names, and death counts when he wants to use them in some way. I mean, this is not a subtle bug, the L3 is a simple stun + aoe spawn kill, and now it just doesnt work. This guy obviously has never debugged anything in his life; obviously new bugs arise when you try to fix something. ws-Tank-7, the creator of StarQuest and many other unique strategy war maps, not debugging anything? What the hell do you know? -.- It's easier to create new bugs in a map if you have no idea about how it originally worked and what uses what, though. This post was edited 1 time, last edit by Zhuinden: Jul 9 2011, 1:52 pm. ![]() ![]() ![]() ![]() ![]() ![]() |
Post #15 IAGG Jul 14 2011, 3:02 am
|
Ive looked into the warrior stunning glitch. Unfortunatly, people don't care to look at the replays. It will show that the defiler for the enemy unit is out of reach of the stunning location. Sometimes the defiler isnt even spawned close to the enemy unit. That tracking system was from the original ts version. Im not going to change it because i cant think of a better way to do it.
![]() ![]() ![]() ![]() ![]() ![]() |
0 members in this topic (italic members are currently writing a reply): None
+ guest(s)
+ guest(s)
Please log in to shout.







![[close]](/images/up.gif)