<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Feature Request: More event types]]></title><description><![CDATA[<p>Could you guys please add more event types to <code>Room.getEventLog</code>? like creep enter room, structure decayed, creep spawned, etc.</p>
]]></description><link>http://screeps.com/forum/topic/2959/feature-request-more-event-types</link><generator>RSS for Node</generator><lastBuildDate>Mon, 09 Nov 2026 18:10:27 GMT</lastBuildDate><atom:link href="http://screeps.com/forum/topic/2959.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 27 Apr 2020 10:52:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Feature Request: More event types on Invalid Date]]></title><description><![CDATA[<p>Could you guys please add more event types to <code>Room.getEventLog</code>? like creep enter room, structure decayed, creep spawned, etc.</p>
]]></description><link>http://screeps.com/forum/post/15000</link><guid isPermaLink="true">http://screeps.com/forum/post/15000</guid><dc:creator><![CDATA[Liu233w]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Reply to Feature Request: More event types on Invalid Date]]></title><description><![CDATA[<p>I personally think it's best to keep the event log to things that you cannot neccessarily detect through code. Keeps things lean. I'm not 100% sure why we have <code>EVENT_OBJECT_DESTROYED</code> as I can't think why that can't be detected through code, so maybe the devs don't have the same philosophy here.</p>
]]></description><link>http://screeps.com/forum/post/15001</link><guid isPermaLink="true">http://screeps.com/forum/post/15001</guid><dc:creator><![CDATA[Tigga]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Reply to Feature Request: More event types on Invalid Date]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="http://screeps.com/forum/uid/138">@tigga</a> It is true that events like STRUCTURE_DECAYED and CREEP_SPAWNED can be detected by user's code without too much cpu cost. However, I really cannot image how to detect an invader entering a room in an O(1) time complexity.</p>
]]></description><link>http://screeps.com/forum/post/15002</link><guid isPermaLink="true">http://screeps.com/forum/post/15002</guid><dc:creator><![CDATA[Liu233w]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Reply to Feature Request: More event types on Mon, 27 Apr 2020 13:41:29 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="http://screeps.com/forum/uid/4177">@liu233w</a> said in <a href="/forum/post/15002">Feature Request: More event types</a>:</p>
<blockquote>
<p><a class="plugin-mentions-user plugin-mentions-a" href="http://screeps.com/forum/uid/138">@tigga</a> It is true that events like STRUCTURE_DECAYED and CREEP_SPAWNED can be detected by user's code without too much cpu cost. However, I really cannot image how to detect an invader entering a room in an O(1) time complexity.</p>
</blockquote>
<p><code>room.find(FIND_HOSTILE_CREEPS).length</code> should be good enough. That'll almost always return 0. When it doesn't, checking them against exit tiles is easy enough. Yeah, it scales with number of hostile creeps as find has a clone inside, but parsing the event log is also not free.</p>
<p>EDIT: I guess you could mean O(1) in tick count. That's fair enough. Cost is about 0.001 CPU though. I guess if you're already parsing the event log every tick (which I guess is more expensive than 0.001 CPU...) then maybe an event would save you a tiny amount of CPU.</p>
]]></description><link>http://screeps.com/forum/post/15003</link><guid isPermaLink="true">http://screeps.com/forum/post/15003</guid><dc:creator><![CDATA[Tigga]]></dc:creator><pubDate>Mon, 27 Apr 2020 13:41:29 GMT</pubDate></item><item><title><![CDATA[Reply to Feature Request: More event types on Mon, 27 Apr 2020 14:15:14 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="http://screeps.com/forum/uid/138">@tigga</a> I just read the <a href="https://github.com/screeps/engine/blob/f02d16a44a00c35615ae227fc72a3c9a07a6a39a/src/game/game.js#L273" rel="nofollow">source code</a> of how Room.find works and found that the result of <code>Room.find(FIND_HOSTILE_CREEPS)</code> (and other structures) are constructed every tick no mater whether I read it or not... Maybe it's not a good idea to parse the event log instead of just looping through the result of find <img
      src="http://screeps.com/forum/plugins/nodebb-plugin-emoji/emoji/android/1f61e.png?v=a1k070tfs06"
      class="not-responsive emoji emoji-android emoji--disappointed"
      title=":("
      alt="😞"
    /></p>
]]></description><link>http://screeps.com/forum/post/15004</link><guid isPermaLink="true">http://screeps.com/forum/post/15004</guid><dc:creator><![CDATA[Liu233w]]></dc:creator><pubDate>Mon, 27 Apr 2020 14:15:14 GMT</pubDate></item><item><title><![CDATA[Reply to Feature Request: More event types on Invalid Date]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="http://screeps.com/forum/uid/138">@tigga</a> pretty sure the destroyed event was put in to identify specifically which creep made the kill, which would not be able to be identified in code 100%. I remember that discussion when events were new.</p>
]]></description><link>http://screeps.com/forum/post/15010</link><guid isPermaLink="true">http://screeps.com/forum/post/15010</guid><dc:creator><![CDATA[SemperRabbit]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Reply to Feature Request: More event types on Invalid Date]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="http://screeps.com/forum/uid/77">@semperrabbit</a> it's not really possible to say who or what killed a creep due to how it's being calculated. Consequently, <code>EVENT_OBJECT_DESTROYED</code> can't expose that data.</p>
]]></description><link>http://screeps.com/forum/post/15014</link><guid isPermaLink="true">http://screeps.com/forum/post/15014</guid><dc:creator><![CDATA[o4kapuk]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>