New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scripts bug out after restarting in dev game #54
Comments
I'm not sure if it was every really documented anymore than the sticky post on the forum. I haven't had any contact with the original developers in years. I just maintain the engine part occasionally. |
Oh. That seems a little bad, all developers seperating apart. Do you by any chance know where to find all classnames or at least for HP and armor ? |
starting at line 104: is that what you a re looking for ? or https://github.com/rtcwcoop/rtcwcoop/blob/32ad2b2fd35b477c317e50ce53ebf9c6d13a7a0f/code/game/g_spawn.c starting line 423 |
If you failed to load, look some wrong script line in .ai and .script, it's never give you any error message. Some script mechanic don't work in COOP, rewrite script carefuly. All classnames and their properties you can found just install any version of Radiant what support RtCW, and after use it for COOP. |
But that happens for any map I try. Tried 3 of them. |
removeentity gives "action unknown" and I tried the "target_kill" and with "target_relay" but doesn't work. |
Dear developer,
I recently noticed a bug that is annoying when I was converting SP map to COOP. As usually, I am using /coopdevmap for it but whenever I call a vote and map restarts, the game fails to load any map files (.ents, .coop.ai, .coop.scripts). After making arena file and running the map from "Create Server" menu, after map restart it works normally. Since I am unable to use cheats there, it will be hard to test reinforcements. Tried 1.0.1 version and same thing.
Since the forums for RTCWCOOP are dead, I would like to ask you for all scripting commands if possible. I would like to kill an entity but don't know how.
Sincerly,
Yuki.
The text was updated successfully, but these errors were encountered: