Spring RTS Engine

yes.

nobody finds useful such information as "25326" ...

it should show the seconds instead, and maybe the original buildtime value inside brackets.

Ye, im talking about the default UI, a lot of people use it.

I call upon Neddie to dispatch topic of little information! Come forth o' mighty one!

Edit: Nice flash edit again Trade, you really are the master of those ¬_¬

And yes, I agree. Buildtime should be converted to actual reali life time.

Im playing, i just wrote something fast lol

Edit: seriously, this is like 5 year old flaw in the engine, someone should fix it :<

TradeMark wrote:nobody finds useful such information as "25326" ...
it should show the seconds instead [...]

Based on what? Different builders have different workertime.

SirMaverick wrote:

TradeMark wrote:nobody finds useful such information as "25326" ...
it should show the seconds instead [...]

Based on what? Different builders have different workertime.

Based on the actual time it would take in relation to all the builders in the area. If there are 4 nanos in range of where you're about to place that building, it would calculate how much time it would take if all 4 nanos assisted it with full resources. That would be winrar.

I would be happy if it calculated the seconds by using the current builder. Like my commander is trying to build kbot lab, i want to know how long it takes. If i have multiple builders on something, i usually dont care how long it takes, because i know it takes fucking long anyways and i will stall metal/energy probably...

buildtime/workertime = seconds needed to build

When you see the buildtime you can see how long it takes to make with whatever assist. Just remember the workertime of different things in a game and you're set. As said you can't judge a time from the buildtime value alone


Jazs proposition is kinda stupid, what is in range to assist something doesnt always have anything to do with what you actually will be building it with.

comm building kbot lab, 6760/300 =~23 seconds.

JohannesH wrote: Jazs proposition is kinda stupid, what is in range to assist something doesnt always have anything to do with what you actually will be building it with.

comm building kbot lab, 6760/300 =~23 seconds.

My idea was going more for potential time rather than probable time but yeh, I can see why it wouldn't really be as helpful as other methods.

JohannesH wrote:buildtime/workertime = seconds needed to build

When you see the buildtime you can see how long it takes to make with whatever assist. Just remember the workertime of different things in a game and you're set. As said you can't judge a time from the buildtime value alone

1) i cant see workertime anywhere.
2) i dont want to waste 10 seconds in calculating such things with my calculator while im playing.
3) I said that the buildtime would still exist inside brackets.

It doesnt have to predict anything, just convert the absurd numbers into seconds! Big deal!? Nobody finds a number like 42362346 any useful and nobody can calculate it in their heads how many seconds it takes to build that unit since there is no workertime printed anywhere on the UI.

I'm sure there was a widget somewhere that divided build time by worker time and displayed the ETA among with other useful information. I used to use it but ended up getting rid of it because it got in the way of more important GUI items and I couldn't move it around.

Dont say a word about widgets here... This is default UI problem.

Default UI should be considered only as a placeholder. There's no way it could accomodate the variety of games being produced today.

Widget.

Not all games have such absurd buildtime numbers anyway.

trolls. they are everywhere.

Not engine issue - and anyway it's in mod's control to change it. CA uses sensible values all the time.
Idea to sum buildpower of nearby units is just crazy...

x/y=z

I have X. I want Z. Y can easily range from 100 to 10000. Gimme Z now.
BTW, SWIW has seconds of buildtime, because there is no assist.

Licho wrote:Not engine issue - and anyway it's in mod's control to change it. CA uses sensible values all the time.
Idea to sum buildpower of nearby units is just crazy...

Evo does something very similar, but mostly, workertime of 1 makes the calculation easy

Not only does CA not use crazy bt numbers it displays total selected workertime on the default UI.

Just make a widget and include it in BA by default. It's now part of your default UI. It is a very easy widget to make.

Trademark's request would just add another default UI thing that most games have to disable.

Really, engine feature requests should be limited to game/widget/ai/etc developers, and feature requests from players should be directed to them.

luckywaldo7 wrote:Really, engine feature requests should be limited to game/widget/ai/etc developers, and feature requests from players should be directed to them.

Hiding requests from players behind game devs might be a too big gatekeeper. Not all requests might be useful for a mod, but maybe for the engine in general. I think a discussion that is not bound to a mod is the best way.