News & Announcements

• 

  Changelog 2017-06-26
  8 years ago • artch 8 years ago

  3
  3
  Posts
  5.2k
  Views

  8 years ago

  A few issues: You can deal on an order of 5 of a resource for 0.001.  This is because utils.roundCredits does not round up due to usage of toFixed.  Deal cost is calculated correctly (except on subscription tokens, see below). There are several unnecessary utils.roundCredits when calculating the deal cost.  This is because you are already rounding up the value prior to passing it into utils.roundCredits. Orders on subscription tokens are rounded, not rounded up, because this is the only place the dealCost was NOT rounded up prior to sending it into utils.roundCredits. I'd PR these, but I do not know what your intentions are for these (and the last time I tried to post something about a bug to the repo, I got yelled at ) so I'll let you handle them.
• 

  PTR Changelog 2017-06-19
  8 years ago • artch 8 years ago

  10
  10
  Posts
  9.3k
  Views

  8 years ago

  Yes, this is how it works currently. One fully alive TOUGH part with 100 hits will absorb not more than 100*boost hits regardless of heal amount received on the tick.
• 

  Changelog 2017-05-26: public memory segments
  8 years ago • artch 8 years ago

  1
  1
  Posts
  2.0k
  Views

  No one has replied

• 

  PTR Changelog 2017-05-23: public memory segments
  8 years ago • artch 8 years ago

  9
  9
  Posts
  9.0k
  Views

  8 years ago

  This looks like a nice addition.  I would like to see a way to send short messages to other players by code if that is possible .. maybe it could be available in an array the next tick
• 

  Meet our Community Manager
  8 years ago • artch 8 years ago

  4
  4
  Posts
  3.4k
  Views

  8 years ago

  He has a screeps badge. OMG!
• 

  Changelog 2017-05-18
  8 years ago • artch 8 years ago

  2
  2
  Posts
  3.5k
  Views

  8 years ago

  I can tell that this change has been a big improvement for my script. I have had no hard resets since this change over the last 3 hours. My performance-throttling code is now working as expected to avoid them.Thanks Marcel, awesome job!
• 

  Changelog 2017-05-11
  8 years ago • artch 8 years ago

  12
  12
  Posts
  12.5k
  Views

  8 years ago

  Except it doesn't happen all the time.  The behavior is very inconsistent.  More often than not it will fail on transferring one tick despite the OK, and then try again next tick.
• 

  PTR Changelog 2017-05-04
  8 years ago • artch 8 years ago

  16
  16
  Posts
  15.0k
  Views

  8 years ago

  The launch date is moved to May 11.
• 

  PTR Changelog 2017-05-03
  8 years ago • artch 8 years ago

  9
  9
  Posts
  8.5k
  Views

  8 years ago

  We're testing Node.js 7.5.0 on the PTR now, it doesn't have async functions enabled.
• 

  PTR Changelog 2017-03-06
  8 years ago • artch 8 years ago

  30
  30
  Posts
  52.6k
  Views

  8 years ago

  Just wondering about the other end of this. I'm GCL 7 and I would never spawn next to Dissi. I don't think it matters how good your code is, if you spawn there you die. This really raises the stakes when you are GCL 4+ and you get wiped out because you will probably never be able to get a good start ever again.
• 

  PTR Changelog 2017-02-24
  8 years ago • artch 8 years ago

  2
  2
  Posts
  2.6k
  Views

  8 years ago

  Yo dawg! So i heard you like visuals, so we put visuals in your visuals, so you can draw your own client while your are inside our client! Next step is adding `onClick` API, and it would be possible to completely rewrite basic client appearance from js source. Sounds funny, I like da stuff!
• 

  PTR Changelog 2017-02-22
  8 years ago • artch 8 years ago

  4
  4
  Posts
  4.8k
  Views

  8 years ago

  Do visuals posted to all rooms that way only incur a single instance of the serialization cost? Yes, that’s the whole point.
• 

  PTR Changelog 2017-02-21
  8 years ago • artch 8 years ago

  5
  5
  Posts
  4.7k
  Views

  8 years ago

  Helam - you can only ever touch 10 segments. It looks like I have a comment here that is shadowbanned because I was trying to edit it too much. You can set data of segments that are not active on this tick only if you have activated less than 10 memory segments. If you attempt to write to more than 10 memory segments your tick will terminate and the requested memory transaction will be lost. deleting a member of RawMemory.segments has no effect and will prevent error checking. Any resulting error conditions will silently fail. 
• 

  PTR Changelog 2017-02-17
  8 years ago • artch 8 years ago

  24
  24
  Posts
  42.0k
  Views

  8 years ago

  To answer my own questions- * All segments are set as empty strings, so there probably isn't a real way to get a list of segments with length greater than one other than manually checking. * Unavailable segments just return "undefined" * `Object.keys(RawMemory.segments)` sort of works but not really. It returns the values as strings, but an actual int is required in lots of places. There's also a weird "null" value that is returned by Object.keys that needs to be filtered out. To get the real set of available segments- var availableSegments = _.filter(Object.keys(RawMemory.segments).map(Number), function(a){return Number.isInteger(a)})  
• 

  PTR Changelog 2017-02-02
  8 years ago • artch 8 years ago

  7
  7
  Posts
  5.7k
  Views

  8 years ago

  Would be cool to be able to do vertical alignment and rotation too.
• 

  PTR Changelog 2017-02-01
  8 years ago • artch 8 years ago

  16
  16
  Posts
  14.3k
  Views

  8 years ago

  This is amazing! Thank you! Is there an estimate on when it will go live? 
• 

  PTR Changelog 2016-11-25
  8 years ago • artch 8 years ago

  17
  17
  Posts
  14.9k
  Views

  8 years ago

  @kshepard the novice areas are not an automatic feature. The devs are responsible for approving and generating each of them. The reservations are 100% full proof to block reassignment. However, I've been relying on the new sign controller functionality for the past month and it seems to work just as well.
• 

  PTR Changelog 2016-11-11
  8 years ago • artch 8 years ago

  4
  4
  Posts
  3.6k
  Views

  8 years ago

  Nice! I may actually start using more boosts after this, before the cost vs gain wasn't worth the trouble.
• 

  PTR Changelog 2016-10-02
  9 years ago • artch 8 years ago

  28
  28
  Posts
  57.9k
  Views

  8 years ago

  Detect a newly placed flag, save its position into memory, create a visual point at this position (optionally), delete the flag. You don't need even 10 flags if you only use them to point to something via GUI.
• 

  PTR Changelog 2016-11-01
  8 years ago • artch 8 years ago

  12
  12
  Posts
  10.9k
  Views

  8 years ago

  This change doesn't address the unclaim/claim exploit, it's just an inconsistency that should be removed.