.
Posts made by 3axap4eHko
-
RE: lookForAtArea and lookForAt return different values at the same point
Game.rooms.E10N4.lookForAtArea(10,13,10,13) return all types of gameobjects at area and there are no swamps!
Game.rooms.E10N4.lookAt(10,13) return all types of gameobjects at point and there are no swamps!
Game.rooms.E10N4.lookForAt('terrain',10,13) return only terrains and there are no swamps!
Game.rooms.E10N4.lookForAtArea('terrain',10,13,10,13) return only terrains and there are swamp present!
Fix it please! -
RE: lookForAtArea and lookForAt return different values at the same point
heggico, you are wrong too! How you describe this?
JSON.stringify(Game.rooms.E10N4.lookAtArea(10,13,10,13))
{"10":{"13":[{"type":"terrain","terrain":"wall"}]}}
-
RE: lookForAtArea and lookForAt return different values at the same point
chris, instead of wall ramparts is a structure, but wall, plain and swamp is a terrain
-
RE: lookForAtArea and lookForAt return different values at the same point
[{"10":{"13":"swamp"}},"wall"]
-
RE: lookForAtArea and lookForAt return different values at the same point
JSON.stringify([ Game.rooms.E10N4.lookForAtArea('terrain',10,13,10,13), Game.rooms.E10N4.lookForAt('terrain',13,10) ])
Still not same
-
RE: lookForAtArea and lookForAt return different values at the same point
But lookAtArea and lookAt is ok
JSON.stringify([
Game.rooms.E10N4.lookAtArea(10,13,10,13),
Game.rooms.E10N4.lookAt(10,13)
])
[
{"10":{"13":[{"type":"terrain","terrain":"wall"}]}},
[{"type":"terrain","terrain":"plain"}]
]
-
lookForAtArea and lookForAt return different values at the same point
room E10N4
JSON.stringify([
Game.rooms.E10N4.lookForAtArea('terrain',10,13,10,13),
Game.rooms.E10N4.lookForAt('terrain',10,13)
])
[{"10":{"13":"swamp"}},"plain"] -
RE: All screps are died (they don't move,work and etc.)
But I don't receive any errors...
-
RE: All screps are died (they don't move,work and etc.)
Are you realy? Look at rooms E10N4, E8N3, E11N4 !!! And this is just a part of all picture...
-
All screps are died (they don't move,work and etc.)
I think there is problem with scripts execution and as the result CPU usage is 0.
-
RE: What's wrong with findPath?
Also I'm worried about moveTo method that does not return
ERR_NO_PATH
for the first case -
What's wrong with findPath?
I'm trying findPath for point 25,18 placed into walls and this method return not empty array, but findPath(100,100) return empty array. Both point are unavailable for moving, what is wrong?
-
RE: Object.defineProperty does not work
This is strange, but this is work now for me without changes...
Thank you! -
RE: Object.defineProperty does not work
I mean that Source.prototype.memory is exists but property memory at object is absent
-
RE: Object.defineProperty does not work
No! You wrong! Just try it and you understand me
-
RE: Algorithm debug improvement
But how I can get game data from Greasemonkey?
-
Object.defineProperty does not work
// Source.js Memory.sources = Memory.sources || {}; Object.defineProperty(Source.prototype, 'memory', { enumerable : true, configurable : false, get: function () { return Memory.sources[this.id]; }, set: function (value) { Memory.sources[this.id] = value; } });
but on:
source.memory.test = 1;
I have an error. What is wrong?
-
RE: Algorithm debug improvement
I just ask about feature. If this impossible and you can't todo this, it's ok. I needn't flags with their not disabled name I need just circles, points and lines for debug visualizing.