Page MenuHomeSchine - Phabricator
Create Task
Maniphest T1559

Starmade | Core spontaneously overheats
Closed, RejectedPublic
Actions

Description

Might be related to T468

Player's ship spontaneously overheated, no related combat for this player, although about two galaxies over another player was taking down a pirate station at about the same time.

[2016-06-13 23:08:32] Shield hit with effect 'piercing': 36912.765625 -> 36912.765625 R(0.88131315); S(0.0)
[2016-06-13 23:08:32] [SERVER] SPAWNING BONUS IN sector: Sector[15245](-404, 2, -168); amount: 0
[2016-06-13 23:08:32] [AI] Setting callback Server(0) Ship[Station_Piratestation Eta_-403_2_-168_14649384805011](15246) Executing send callback: true
[2016-06-13 23:08:32] [SERVER] MAIN CORE STARTED DESTRUCTION: in 60 seconds - started 1465859312327
[2016-06-13 23:08:32] [SREVER] FACTION BLOCK REMOVED FROM Ship[Station_Piratestation Eta_-403_2_-168_14649384805011](15246); resetting faction !!!!!!!!!!!!!!
[2016-06-13 23:08:32] Shield hit with effect 'ioneffect': 358534.125 -> 482119.75109666213 R(0.68939394); S(0.5)
[2016-06-13 23:08:32] [SERVER] Ship[X16-leopardM2 2781-2](15341) Failed Activating 2 Blocks
[2016-06-13 23:08:32] [SERVER] Ship[X16-leopardM2 2781-2](15341) ADDING NEW INVENTORY (14, 9, 9)
....
[2016-06-13 23:08:38] [SERVER][READTAG] WARNING: org.schema.game.server.controller.GameServerController@2d029ab READING tag: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.ent;  took long: 61ms
[2016-06-13 23:08:38] [SERVER] Ship[AES_Acclimator_Star Destroyer1462969988318](15396) loaded activation state: ActBuffer 0; Delay 2; DelayNR 0
[2016-06-13 23:08:38] [SERVER][SECTOR][LOADING_ENTITY] WARNING: Sector[15391](4168, 4079, 86) loading entity: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318 took long: 63ms
[2016-06-13 23:08:38] [AI] Setting callback Server(0) Ship[AES_Acclimator_Star Destroyer1462969988318](15396) Executing send callback: true
[2016-06-13 23:08:38] [SERVER] MAIN CORE STARTED DESTRUCTION: in 60 seconds - started 1465859318873
...
[2016-06-13 23:09:29] [SERVER] SPAWNING BONUS IN sector: Sector[15291](-402, 2, -168); amount: 0
[2016-06-13 23:09:29] [AI] Setting callback Server(0) Ship[MOB_SIM_X16-swallowM3R_2781_4rl1](15344) Executing send callback: true
[2016-06-13 23:09:29] [SERVER] MAIN CORE STARTED DESTRUCTION: in 60 seconds - started 1465859369323
...
[2016-06-13 23:09:38] [SERVER] CORE OVERHEATED COMPLETELY: KILLING ALL SHIP CREW
[2016-06-13 23:09:38] [SEGMENTCONTROLLER] ENTITY Ship[AES_Acclimator_Star Destroyer1462969988318](15396) HAS BEEN DESTROYED...
[2016-06-13 23:09:38] [AI] Setting callback Server(0) Ship[AES_Acclimator_Star Destroyer1462969988318](15396) Executing send callback: true
[2016-06-13 23:09:38] [SERVER] MAIN CORE STARTED DESTRUCTION: in 60 seconds - started 1465859378904
[2016-06-13 23:09:38] [ENTITIES] removed object from loaded state Ship[AES_Acclimator_Star Destroyer1462969988318](15396); 15396
[2016-06-13 23:09:38] [DELETE][Server(0)] Sendable 15396(Ship[AES_Acclimator_Star Destroyer1462969988318](15396)) Physically DELETING DONE and Notified!
[2016-06-13 23:09:38] [SERVER] WRITING ENTITY TAG: Ship[AES_Acclimator_Star Destroyer1462969988318](15396) to ./server-database/world0/ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.ent
[2016-06-13 23:09:38] [SERVER] WARNING: WRITING ENTITY TAG: Ship[AES_Acclimator_Star Destroyer1462969988318](15396) FINISHED: 48ms -> tagcreate: 1; tagwrite: 45; rename: 0; delete: 1; DB: 1
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.ent
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.-1.0.-1.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.0.0.-1.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.1.0.-1.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.-1.-1.0.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.0.-1.0.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.1.-1.0.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.-1.0.0.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.0.0.0.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.1.0.0.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.-1.-1.1.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.0.-1.1.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.1.-1.1.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.-1.0.1.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.0.0.1.smd2 (exists: true)
[2016-06-13 23:09:38] [SERVER][SEGMENTCONTROLLER] PERMANENTLY DELETING ENTITY DATA: ENTITY_SHIP_AES_Acclimator_Star Destroyer1462969988318.1.0.1.smd2 (exists: true)

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
Single and Multi
Reproducible
uncertain
Category
Engine
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
uncertain
Steps to reproduce

Server logs and packet trace both available. Player is trying to replicate, but has not been successful yet.

Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>

Related Objects

Event Timeline

Restricted Application added a project: Issue Navigation. · View Herald TranscriptJun 14 2016, 3:10 AM
erthparadine added a comment.Jun 14 2016, 3:35 AM

More info from ongoing discussions

2016/06/14 - 03:23:08 [KillaKrazy]: My ship took some damage this morning, about 5% damage to systems
2016/06/14 - 03:23:31 [KillaKrazy]: I went and added about 200k shield caps and recharges without rebooting the system
2016/06/14 - 03:23:50 [KillaKrazy]: I'm curious if that played a part in this bug happening
2016/06/14 - 03:24:08 [ErthParadine]: Could have - did you just lump those onto the ship?
2016/06/14 - 03:24:57 [KillaKrazy]: Yea I put them inside it. Depending on how long the timer was, that may have triggered the bug
2016/06/14 - 03:33:25 [KillaKrazy]: I'm thinking that adding more systems to a damaged ship may have dropped the hp level below 50% without showing or triggered the overheat
SmilingDemon shifted this object from the S1 Public space to the S3 Starmade space.Jun 14 2016, 6:33 PM
SmilingDemon changed the visibility from "Custom Policy" to "Public (No Login Required)".
SmilingDemon changed the edit policy from "Task Author" to "Starmade (Project)".
SmilingDemon changed Affected Gamemode(s) from none/unspecified to Single and Multi.
SmilingDemon changed Category from none/unspecified to Engine.
SmilingDemon claimed this task.
SmilingDemon triaged this task as High priority.
Restricted Application added a subscriber: AndyP. · View Herald TranscriptJun 14 2016, 6:34 PM
SmilingDemon added a comment.Jun 14 2016, 6:35 PM

-Feedback-

did the player in question got a warning to reboot before placing the new blocks ?
did he actually reboot before placing them?
did he maybe relog without rebooting and didnt got the warning?

if he simply did ignore the warning ... then this was intended behaviour and will be rejected

erthparadine added a comment.Jun 14 2016, 6:38 PM

According to logs, he was logging-in at the moment the server set a 60-second countdown. So I'm going with the assumption he didn't see any sort of warning/reboot message.

erthparadine added a comment.Jun 14 2016, 6:46 PM

Results of command: grep KillaKrazy serverlog.txt.0 (replaced IPs with xx)

[2016-06-13 13:51:35] [LOGIN] logged in RegisteredClient: KillaKrazy (4) [KillaKrazy]connected: true (/xx:57115)
[2016-06-13 14:13:17] [UPLOAD] KillaKrazy started to upload: KillaKrazy_upload_tmp.zip
[2016-06-13 14:16:00] [UPLOAD] PlS[KillaKrazy [KillaKrazy]*; id(1102)(4)f(10404)] finished BLUEPRINT upload: KillaKrazy_upload_tmp.zip:
[2016-06-13 14:16:07] [BLUEPRINT] KillaKrazy: IMPORT OF BLUEPRINT DONE: TIER1-ArtemisNavalShipyards2_0
[2016-06-13 14:17:51] [BLUEPRINT][BUY] KillaKrazy bought blueprint from metaItem: "TIER1-AllianceSuperCity" as "Rendili Hyperworks"; Price: 281987514; to sector: (4168, 4079, 86) (loadTime: 128ms, spawnTime: 10ms)
[2016-06-13 14:17:58] [SPAWN] KillaKrazy spawned new ship: "KillaKrazy_1465827482140"
[2016-06-13 14:20:19] [DISCONNECT] Client 'RegisteredClient: KillaKrazy (4) [KillaKrazy]connected: true' IP(/xx:57115) HAS BEEN DISCONNECTED . PROBE: false; ProcessorID: 167
[2016-06-13 14:20:19] [LOGOUT] logging out client ID RegisteredClient: KillaKrazy (4) [KillaKrazy]connected: true
[2016-06-13 23:08:37] [AUTH] authenticating KillaKrazy; useAuth: true; requireAuth: true
[2016-06-13 23:08:38] [AUTH] Protection status of KillaKrazy is ProtectedUplinkName [username=KillaKrazy, timeProtected=1465825895438] -> protected = true
[2016-06-13 23:08:38] [AUTH] PROTECTING USER killakrazy under uplink id KillaKrazy
[2016-06-13 23:08:38] [LOGIN] logged in RegisteredClient: KillaKrazy (63) [KillaKrazy]connected: true (/xx:57915)
[2016-06-13 23:13:39] [DISCONNECT] Client 'RegisteredClient: KillaKrazy (63) [KillaKrazy]connected: true' IP(/xx:57915) HAS BEEN DISCONNECTED . PROBE: false; ProcessorID: 2151
[2016-06-13 23:13:39] [LOGOUT] logging out client ID RegisteredClient: KillaKrazy (63) [KillaKrazy]connected: true

Logs also do not reflect any evidence of another player in any nearby sector during this time.

SmilingDemon added a comment.Jun 14 2016, 7:40 PM

03:23:08 [KillaKrazy]: My ship took some damage this morning, about 5% damage to systems
2016/06/14 - 03:23:31 [KillaKrazy]: I went and added about 200k shield caps and recharges without rebooting the system

i totally did oversee that ... intended behaviour ... you cant save your ship in combat by placing aditional blocks without rebooting first ... this will insta kill your ship. pretty sure that is what happenend.

question is .. had it been damaged earlier and he didnt got the warning when he did log in again and placed those new blocks the next time ... or did he simply ignore the warning.

please ask him

erthparadine added a comment.EditedJun 14 2016, 7:49 PM

I didn't get the impression he was trying to save the ship during combat, just adding shield modules after returning to his homebase and then logging-out. He logged-back in about 9 hours later, and his ship began a destruction countdown immediately upon his login.

As for a warning - I'll ask when I see him on again. Although if you look at the timing of his login, and when the ship destruction began, there's less than a 1-second difference. I doubt he was able to see any sort of warning during that stage of the login process.

SmilingDemon added a comment.Jun 14 2016, 8:08 PM

you do get that warning if you try to place blocks on a damaged ship.
(easy to test core-hull-3xsystem block - kill one system block and then add two more while ignoring the warning -> overheat)

so he must have ignored that when he did place them before l0oging out ...
and on login the server spawned his ship with < 50% system health and started the overheating then. ... it would have happened sonner if he hadnt logged out ... maybe it was lagging behind and didnt kick in earlier

SmilingDemon closed this task as Rejected.Jun 23 2016, 8:57 PM

-Rejected-

concluded to be a player error

Restricted Application edited projects, added Starmade; removed Issue Navigation. · View Herald TranscriptJun 23 2016, 8:57 PM
Restricted Application removed a subscriber: AndyP. · View Herald Transcript
AndyP moved this task from Unclassed to Archived on the Starmade board.Aug 26 2016, 10:32 AM
Restricted Application added a project: Engine. · View Herald TranscriptMar 10 2017, 6:12 PM