You probably don't have a cpu subscription, and are trying to play on shard 1 or 2. If you want to play for free, make sure to play on Shard 3.
Posts made by Estecka
-
RE: Help me!
-
RE: My tower just keeps repairing a single piece of wall.
Something big hits me now that I see the code clearly.
var closestDamagedWall = findClosestByRange(STRUCTURE_WALL); var closestDamagedRampart = findClosestByRange(STRUCTURE_RAMPART);
Those are not valid uses of the method: You must use a
FIND_*
constant as first argument. Here your two variables are always going to be null, so your code always falls back to theclosestDamagedStructure
bit.What you'd want to do instead is something more like this:
var closestDamagedWall = tower.pos.findClosestByRange(FIND_STRUCTURES, { filter: (s) => s.hits < 30000 && (s.structureType==STRUCTURE_WALL || s.structureType==STRUCTURE_RAMPART) });
-
RE: My tower just keeps repairing a single piece of wall.
Please make your code a minimum readable.
Place the code between triple quotes ``` and don't write everything on a single line. -
RE: Special caracters aren't properly pulled from github.
Didn't know about that notation. Thank for the tip.
I know I can find some of these codes in the Caracter Table, but otherwise how would I find the code associated with any arbitrary caracter ?
-
RE: Special caracters aren't properly pulled from github.
You can have a samples in the files here : Test, _Archive.Emoji
The emojis were copy-pasted from Emojipedia. Accentuated caracters are native to my french Azerty keyboard. The other fancier caracters were originally copied from Window's Caracter Table, but then implemented into a custom keyboard language so I could type them directly.
The caracters I'd use the most are
é
,è
,∞
,¡
,¿
-
RE: Special caracters aren't properly pulled from github.
I tried creating a new file in the repository directly from Github's website, and as expected, I'm getting the same result a before: github gets the caracters, right but Screeps doesn't.
-
Pulling multiple branches from github
I always actively use multiple branches when working with get; since Screeps do propose a crude branching system, I was actually expcting it would be able to pull multiple branches from github.
To recap, if I understood the way it currently works: 'master' is pulled from the remote into 'default', other branches from both local and remote are ignored.
The way I naturally expected it to work, every branch from the remote would be pulled into a branch with the same name; however I see that it clashes with he current system, and this could be a breaking change.
The way I'd see implementing such a feature without enforcing anyhing new on anyone, is actually just the way Tracking Branches work in git :
By default, everyone has their local (Screeps) 'default' branch tracking their remote's 'master', but anyone would be able to define which additional remote branches they wish to pull, and wich locale branches they should be pulled into : -
RE: Syncing ingame script with github
I'll take it as a "this is how it works" and make a feature request of it instead.
I'll mark the issue as solved since I got something working.
-
RE: Special caracters aren't properly pulled from github.
I'm using sourcetree, I'm not familiar with the command line tool. I've had a dive through the settings and didn't find anything on that matter. (Though I should be able to run some commands if you want me to.)
Anyways, I'd bee really surprised if it was sourcetree re-encoding the files before pushing : Everything looks fine on github, and if I re-download and open the files form there, everything is in order and I find them encoded the way I uploaded them.
Do you (or anyone) not have this issue ?
-
Special caracters aren't properly pulled from github.
Screeps usually handles special caracters and emoji well when using the ingame editor and console; but when I tried pulling scripts from githubs, they all got messed up. The result looks pretty much like what you'd get when changing the encoding of a text.
On local, I've tried saving the files in a variety of format (UTF-8, ISO-8859, windows-1252); the caracters always looked good when looking at the files on github, but never made it through to screeps. (UTF-16 was the worse: it added a few caracters at the begining of the file, making it unable to run at all.)