Jump to content

Custom Map Crash - most likely invalid Card Id spawn


Recommended Posts

I tried to play my old map "Random Unit" today. Everything worked for quite some time, but then a crash occured for all players.

My guess is, that it tried to spawn a unit for which the id isnt valid anymore.

How can I find out, if that is indeed the case and what changed with the ids?

According to the mapscript, those unit ids are used:

local unit_id = {255, 287, 289, 290, 302, 304, 364, 374, 379, 380, 386, 387, 388, 402, 405, 407, 408, 413, 414, 415, 417, 418, 419, 420, 421, 426, 431, 434, 443, 444, 507, 526, 527, 529, 534, 548, 549, 550, 552, 560, 561, 562, 563, 564, 661, 664, 677, 682, 683, 703, 707, 708, 709, 718, 719, 720, 778, 784, 786, 1021, 1029, 1030, 1031, 1032, 1033, 1034, 1035, 1117, 1119, 1120, 1124, 1128, 1171, 1183, 1193, 1194, 1195, 1196, 1198, 1199, 1200, 1201, 1202, 1203, 1219, 1220, 1225, 1226, 1227, 1228, 1235, 1238, 1289, 1240, 1262, 1263, 1264, 1265, 1267, 1274, 1275, 1276, 1277, 1278, 1279, 1286, 1293, 1296, 1297, 1299, 1300, 1316, 1317, 1318, 1319, 1325, 1327, 1330, 1331, 1333, 1624, 1544, 1343, 1344, 1345, 1346, 1347, 1348, 1361, 1375, 1382, 1385, 1391, 1409, 1410, 1411, 1413, 1414, 1415, 1428, 1429, 1416, 1434, 1436, 1438, 1442, 1443, 1449, 1450, 1451, 1465, 1472, 1474, 1477, 1482, 1484, 1487, 1489, 1505, 1531, 1532, 1533, 1538, 1540, 1544, 1545, 1555, 1558, 1561, 1562, 1563, 1564, 1565, 1567, 1573, 1574, 1585, 1607, 1624}

 

Last lines of log file, where the error occured:

    20:45:46.763 DEBUG 14588 from_server::game::GameMessage_AnnounceCommandNotification:8
received msg: 0x5:b AnnounceCommandNotification { match_id: 66209, sequence_number: 5087, step: 4065, command: GroupAttack { player: 332, squads: [1274], target: CGdTarget { version: 1, targets: [Target { category: 1, sub_category: 0, uid: 1258, x: 202.84523, y: 176.96764 }] }, force_attack: 0 } }
    20:45:46.763 DEBUG 14588 from_server::game::GameMessage_AnnounceCommandNotification:8
received msg: 0x5:b AnnounceCommandNotification { match_id: 66209, sequence_number: 5088, step: 4065, command: GroupGoto { player: 330, squads: [1278], positions: [(181.85175, 178.59972)], walk_mode: 2, run_or_orientation: 1, orientation: 0.0 } }
    20:45:47.008 ERROR 17108 proxy::logging:74
src="SYS" message="d:\\project\\battleforge\\release\\beta\\code\\gd\\GdEntity.h\n[351]\n: error: Assertion failed!\n\n\nMessage: invalid call, no jobmanager\n"
    20:45:53.303 DEBUG 14588 from_server::game::GameMessage_PlayerLeftGameNotification:8
received msg: 0x5:7 PlayerLeftGameNotification { match_id: 66209, sequence_number: 5155, player: 4537, map_cluster: 0 }
    20:45:53.364 DEBUG 14588 from_server::game::GameMessage_AnnounceCommandNotification:8
received msg: 0x5:b AnnounceCommandNotification { match_id: 66209, sequence_number: 5156, step: 4131, command: PlayerSurrender { player: 333 } }
    20:45:57.671 INFO 17108 proxy::networking::connect:280
destroying
    20:45:57.671 INFO 17108 proxy::networking::open_ssl_wrapper:157
disconnecting
    20:45:57.671 DEBUG 14588 proxy::networking::connect:389
sf; target="threading::forge_send_messages_to_server"
    20:45:57.671 ERROR 14588 proxy::networking::connect:395
FP->S no msg
    20:45:57.672 INFO 17108 proxy::networking::open_ssl_wrapper:172
disconnected
    20:45:57.672 ERROR 14588 proxy::networking::connect:375
P->BF no msg
    20:45:57.672 INFO 17108 proxy::networking::connect:282
destroyed
    20:45:57.672 ERROR 14588 proxy::networking::connect:541
MP->S no msg
    20:45:57.682 INFO 17108 proxy::logging:72
src="PREGAME" message="CharacterRemote deletion."
    20:45:57.749 ERROR 17108 proxy::logging:74
src="BASE" message="Unhandled exception error. Crash dump written."
    20:45:57.749 ERROR 17108 proxy::logging:74
src="BASE" message=""

Edited by Kaldra
Link to post
Share on other sites
20 hours ago, LEBOVIN said:

afaik only the id of fire sphere was changed (in fact duplicated so the old and the new one continue to work)

Hmmm...then I don’t see why it would crash. The map only spawns units by card id. Nothing else.

And it was playable for quite some time before it crashed, right when a new unit should’ve been spawned.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use