Topics created by Orlet

Update: So far no crashes. However, I am still getting an issue where the client's hardware acceleration would turn off randomly and stay off (and disabled) until restart. Only happens in Steam client.

I've got the same problem with chrome just recently. But hardware acceleration does work with firefox.

I don't have more cpu statistics than a floating average and the impact on my bucket (still onshard3 only). But I realised the cpu usage spike during the last days, to the point my bucket was drained and cpu saving kicked in. My bucket recovered today as well, but it broke down during the last hour(s) again. Does anyone of you see the impact on their graphs again?

This issue has been fixed with yesterday's path, thank you.

@o4kapuk confirm it is working.

@o4kapuk said in PTR stops running my code as soon as I close the tab: @deft-code The expected behavior (as far as I know) is that your code is running but your CPU isn't being replenished so you'll be disabled as soon as your bucket is empty. Please report if you see something else. This is the case for MMO server shards, yes. Though IIRC you currently start with zero buckets on shards you don't have any owned objects on, and the buckets won't regenerate if you don't have anything on the shard even with CPU assigned.

Nope. That's all I could manage to get from it. Just says "suspicious webpage has been blocked". The lack of verbosity of any kind disturbs me in this product. I needed to add exception to even view the damned address it was complaining about. I'll likely be switching once the license expires...

I see. Is there a place I could, say, PR a change for a more stable list order?

@kraiik said in PWR_SHIELD rampart graphic does not go away at expiry: @Orlet In my experience only destroying the last rampart in the room creates this graphical error, if there's still another rampart in the room the destroyed rampart disappears normally (though I haven't tested this with PWR_SHIELD). PWR_SHIELD probably just makes the existing issue more visible. I see, I haven't tried destroying all of ramparts yet @o4kapuk said in PWR_SHIELD rampart graphic does not go away at expiry: This is a known issue, we're working on it But thanks for reporting anyway Roger. Thanks for reply!

@orlet Thanks, we'll take a look

Personally I liked the idea of renew creep. I worry that renew creep would lose most of its usecase (and interesting long range gameplay) if you don't have a good reason over spawning a creep. The kind of spawning idea I would be interested in would be a certain creep type you define, eg. you have have ability to spawn large numbers of a particular creep body. Basically like an aircraft carrier that can cheaply produce fighters, rather than a mobile manufacturing plant than can create anything. However, that just because I think the challenge of going a far distance with renewing along the way sounds interesting. No strong reason against spawning as a power. The idea of building a container to start producing creeps from just outside an enemy base is an interesting concept. Cool thought and good limitation with max energy cost.

Windows 10 here and I have 36 of these folders, taking up ~300MB of space

@orlet should be fixed now.

Yeah, strongholds can possibly create some extra uses for combat boosts, which would be nice.

Replays don't show errors though. They only show that my creeps were sitting still for that period of 1.5 hrs, which is how i found out in the first place.

@orlet Should be fixed atm.

@kyralee said in Update/rework of the ATTACK part's hitback damage: Re-purpose the Tough Body Part - With this suggestion we would remove the hit back of attack parts entirely and move that over to the Tough body part. This would function like the "Thorns" stat in Diablo and other similar games/mechanics. This could hit back every target or limit it to the number of Tough body parts the creep owns similar to my suggestion 2. Obviously cost and damage values would need to be tweaked. Newbie, here, but FWIW I like this idea of ATTACK doing only what it says on the tin, and either turning TOUGH turning into THORNS, or adding a new part that reflects, say, 10% of damage (at a greater cost than TOUGH).

This consistently happens to me as well, with both the sign badge and the owner badge. Moving from a owned/signed room to another without hovering an unowned/unsigned room will not update related badge. It's a little confusing at first, but yeah, it isn't much trouble.

@artch looking through all Events logs where own Creeps/builings are /Filter for rooms with enemy creeps will cost a lot of parsing CPU.

@obamallama indeed, that's one thing I forgot to mention. Thanks!