Spring RTS Engine

No scouting, no LOS, no radar, perfect nuke aiming.



crap crappy photobucket cache update, no names shall be given.

edit: no enemy radar dots spotted in that zone.


Edit:Opps, this is not understandable without this:
Results

I'm just that good

edit: i had radar...

groundscars, early scouting, nuke aoe widget...

aegis wrote:groundscars, early scouting, nuke aoe widget...

Wrong aegis, read the post, try again.

this is the rigth forum for this stuff.

edit: you can clearly see that this kind of talk goes in this forum, see topics like, double antismurf, who to report to, clans, lets play some new games!, 16 player 1v1 BA tournament July 18 2009, etc its about players social interaction with the game.

mongus wrote:this is the rigth forum for this stuff.

What is this stuff then?

Tell me, where the hell would you have aimed it? Damn thing covers 1/4 the map, and by process of elimination it's not that hard to guess where your base is. Even if he picked a quarter of the map randomly there's 50% chance he would have picked that quarter. Why do you think he queued exactly two (2) nukes?

Evil4Zerggin wrote:Why do you think he queued exactly two (2) nukes?

errr well 1 was qued then the 2nd was qued just before 1st was fired, but imo on a map that size 1 nuke = gg

well... wether this was cheating or not...
the ground scars are an issue, and they are mantissed as such since 2006 or so. basically, we would need a height map per ally team, and only visibly reveal height map changes if they were in your LOS. So each team had basically two height maps, the real one, and the known/seen one. all synced calculations would need the real one of course, while the user should see the known HM, and also widgets shoul only have access to the known one. Maybe this breaks some widgets, but i can not see why they should need the real one. they logically should not be allowed to have it.
Gadgets would need the real one of course (as they are synced).

could allow making buildings without changing the heightmap?

That would be a bigger change, plus it would need the mods to change all their buildings to use this new method (cause of course, we would have the old method as default) to be effective. You would also run into problems with labs built on uneven terrain, and then the produced units would be unable to move out, ...
But yeah... if you like pain, it could be an option too (putting it on my todo list, high priority).

It already is an option (UnitDef::levelGround).

People shouldn't see ground height changes out of LOS imo (probably a massive change tho )

Replay or didn't happen. Also imagine everyone going to whine about how they got nuked by a better player because he aimed it well. Rage less.

hoijui wrote:So each team had basically two height maps, the real one, and the known/seen one.

This should really go without saying as it's 100% obviously a bug in the engine that has been always present. Just talking about it feels silly because it's so obvious. It would be like having a discussion about a bug where enemy units outside your LoS should not be seen.

hoijui wrote:Maybe this breaks some widgets

Let the breaking begin. Please.

Regret wrote:Replay or didn't happen. Also imagine everyone going to whine about how they got nuked by a better player because he aimed it well. Rage less.

No rage here, just curious, really. im cool, just surprised.
I played like crap, i deserved to get nuked, many many times ive got nuked before.

its interesting to nottice, the player who did this:

never saw that base, nor any of my bases at all.

didnt know my commander was there

didnt know my entire build force was there

didnt know i had t2 there to get anti asap.


Also good to know, in a game in that map, the main base is "supposed" to be at the other corner.


When you talk about ground scars, you mean the base groundplate? bc if its that xta does not have them.

Otoh, By reading the heigthmap (pressing F1) and guessing/see where the enemy placed his buildings it will still be hard to get such a good shot. Nottice how it covers the windmills at (from sc view) rigth and the mt and radar at left. Moving the taget more to the rigth would not cover the mt/radar, moving it more to the rigth corner(where there is nothing), would not get the 2 mexes more to the front.
Maybe im exxagerating in that and yeah this could be deprecated by the big nuke area, but then again, looks so perfectly done.

So this could be a los cheat or the spec told him exactly where to nuke.

It's so obvious he cheated i won't even explain myself.

mongus wrote:<lots of irrelevant claims and crying without a replay>

Regret wrote:Replay or didn't happen.

And you said so yourself it could be a spec cheat.

REVENGE wrote:And you said so yourself it could be a spec cheat.

He sent me the replay, he's just raging. The player had 2 places to nuke (the nuke has a radius of quarter of the map and enemy had 2 quarters of the map) and he picked the one where he seen radar dots. OH NOE CHEATS

Based on just the information given in the second screenshot, in which a cluster of radar blips and even a plane (bug?) are clearly visible, I would have nuked in the exact same spot.

edit: beaten by regret.