I cleared the cache. I can't reproduce with these steps anymore. I hope this is fixed.
Posts made by Xenofix
RE: It is very easy to loose all the seasonal code by accident
It is very easy to loose all the seasonal code by accident
It's actually very easy to loose your seasonal code, it happened to me once before and is very frustrating to write all the code again. Reproduction with Chrome:
- Have your main tab open on shardSeason: https://screeps.com/season/#!/room/shardSeason/W15N38
- click a link from an attack message from your email, e.g.: https://screeps.com/a/#!/room/shardSeason/W11N36
- now the code in Tab 1 will be your mmo code after a short delay.
- modify and/or save in Tab 1. all seasonal code is overwritten with mmo code.
What I expect: the code in seasonal tab is always seasonal code and never changed into mmo code just because another tab opens mmo. I also expect attack messages to link correctly.
RE: Game.cpu.generatePixel change
I got to know about this change by coincidence on slack #general, a week after it was already live. It didn't break my code, so I didn't catch it - but only because I usually use just half of my cpu per tick.
I believe generating pixel should be easy, the 2 liner to generate them is even in the api documentation to make it easy for everyone. An easy way to use wasted cpu is an incentive to waste less cpu. It has been a very welcoming feature for non-optimized users, because a good bot would use all cpu to create more energy or credits. A less advanced bot just has much cpu to waste and can generate pixel easily by wasting less cpu.
I believe there are also not too many pixel. If you try to collect golden decorations, you'll need to spend a lot of pixel. At 13th November I created 312 decorations and got zero golden decorations.
If creating pixel is challenging, then less people care about them at all, leading to the old behaviour to use as much as possible from your cpu with mostly unnecessary calculations. A good example in my humble code base of the optimizations I did after the pixel feature came out:
- towers scan the room only every 41 ticks for damaged structures
- market code runs only every 11 ticks instead of every tick.
- use more reusePath instead of recalculating each path every tick, saves also something.
- collecting room statistics and market statistics every minute instead of every tick.
- disable logging HTML room statistics while I'm offline.
- disable map visuals and room visuals while i'm offline.
- sharing energy across rooms by terminal every 32 ticks instead of every tick.
- more would be possible, but with over 100 cpu saved per tick it has been already enough.
Without the pixel feature, I would still run unoptimized code and I think many other players also optimized their code to create more pixel. No need to make this feature more challenging, it's ok to be an non-challenging incentive for optimization.
RE: Quickly switching between console and script tabs leads to them automatically switching themselves
Happens to me as well often with the steam client. A fix would be nice. This also happens less often with Chrome, usually if I'm on the map and want to access the console quickly. I would click on any room and switch to console before everything is loaded. If I'm too quick, then this bug happens. Maybe it's easier to reproduce on a slow machine.
RE: Hi, here's a little code I wrote to generate random room names, but it gives me the following error:
Additionally, owned rooms and unreserved rooms doesn't have
Grafiti lost probably during steam transfer
I've lost a rare grafiti G-00066:DE:E somehow.
Unfortunately I don't know exactly when and how.
It was last seen at 22.06 on steam and most likely lost during transfer back to my screeps account at 22.06.
In the steam history can be seen that I took the sell offer back. I've never converted any grafiti item back to 400 pixel resources, so it had been lost in transfer.
RE: Steam client "no hardware acceleration available"
I've got the same problem with chrome just recently. But hardware acceleration does work with firefox.