Dst Respawn Command

[Louella Kammann]

Im curious if its possible to give a player an item when they respawn (in any location). A hacky solution is to give players items when they return to spawn with a certain score, but that means I can't let players use beds. I want players to only get one item and only when they die. The obvious answer, using a death counter which gets reset right after the player gets their item makes the player get their item while dead only to lose it before they respawn.

I understand how to use a deathCount objective, but for some odd reason that selector works even when the player is dead. As a result, the dead player gets items added to their inventory, and then the items vanish.

If the place where you respawn is a specific location, you could test if the player is standing in that location and they have a minimum death score of 1, and then give them the item. You would have to also make it so that it only gives you the item once, so maybe when you are standing in that spot and you have the death score it will add 1 to another scoreboard constantly, but it only gives you the item when that score is equal to 1.

*edit* i would like to have the possibility to transfer the high command to another specific player after death of commander. ("side" respawn / team switch). perhaps one could accomplish this through chain of command?

i also tried giving the "second" commander his own highcommand-modul and just syncing this second hcm with the subcommand-moduls manually via radiotrigger, after death of first comamnder, but i couldn't get it to work. unfortunately i don't know much about scripting.

i'm currently experimenting with hcRemoveAllGroups and hcSetGroup to toggle command between two commanders. works pretty well. i placed the hc-commander-module and the hc-subordinate-modul and synced them together, but DID NOT SYNC THEM TO A PLAYER.

as mentioned in the wiki doesn't work for me. the group appears under the command, but the number is still white. when you set up the hc-modul with multiple subordinates you get those subgroups with different colors, which is the only real possibility to distinguish between units of similar types.

I am playing in VR and due to the nature of dogfighting, dying on dogfight servers is very frequent. So I bound the "respawn" command on my throttle, that I dont have to fiddle around on my desk for the mouse while being basically blind in VR.

As you can see in my first post, thats the exact command I have bound to my hotas. Also pressing the keyboard shortcut stopped to work on certain servers. Like I said it works fine on some other servers.

I am having difficulty with the start of the game, continuously starving to death because all I can find are sparse bushes of cranberries.

My spawn location is in the middle of some steep mountains with nothing but the occasional patch of birch leaves, and it takes me a bit of time to walk/climb any way I can, just to get to a mildly more manageable plains area. I have attempted to set up a shack with a bed, that has a handful of different trees as well as some clay nearby- but the inevitable starvation leads me back to square one.

Thankfully I have keep inventory enabled, but it means little because I almost end up starving again once I get back to my house, and that's if I don't get jumped by wolves on the way back. Then I end up back in the mountains, either atop a peak or down in a narrow, cramped ravine.

Included is my map- my spawn point is the pink star all the way to the south, and the most suitable living space is the green house all the way to the north. It takes me between five and ten minutes to get back home, depending on where I end up respawning.

I've never used it, though a few of the guys at my work swear by BedRespawnner. It does as you would expect -- whenever you sleep, it resets your spawn to that spot. Won't help wrt starving, but at least you don't have to run home to... whatever it is you are running home to.

For the rare item that sets your spawn temporarily, it depends on what settings you used when creating your world. You can set it to infinite. The default for Standard is 20 times, Exploration is infinite, and Wilderness Survival is 3 times.

Is this something not able to be done anymore? Or perhaps I'm using the command in the wrong spot? I've tried it in the server console and get an error, and I've tried it in world chat but nothing. Is it too good to be true? XD

I've been testing a few invasion wads with friendly AI lately and what irks me is that when I die I either have to bring down the console to resurrect or start a co-op game (which causes a lot of issues, namely the AI wads I'm using not behaving with skulltag et. al) - is there any way to quickly (and hopefully permanently) changing death behaviour to make me respawn instead of restart the level? (inb4 "bind space resurrect" :P)

You can start a co-op game in ZDoom, though, so I'm not sure what's the problem here?

And I'm not sure there's any way that's really quicker than binding a key to resurrect?

But if you want, you can use the buddha cheat code so as to be unkillable. Contrarily to god mode, you'll still take damage, so it's better to test how easy/hard some fights are, but you'll never get below 1% health.

Regarding console commands - and not wanting to start another topic - do console commands carry over to the next time one starts the zdoom exe? For example I wanted to disable translucency several times to test something and wasn't sure if there settings would be "remembered" but my instinct tells me that no, they are not, as that's more something to put in the autoload section of the ini.

Regarding console commands - and not wanting to start another topic - do console commands carry over to the next time one starts the zdoom exe? For example I wanted to disable translucency several times to test something and wasn't sure if there settings would be "remembered" but my instinct tells me that no, they are not, as that's more something to put in the autoload section of the ini.

Commands? No, as there is of course nothing to remember.

Variables, however, is probably what you meant, and it depends entirely on the variable. Practically every setting in ZDoom is a console variable.

R_drawtrans isn't saved deliberately as it's not actually a good idea to disable it, as transparency is generally assumed in most ZDoom features/mods/mapsets, and could make things look horrendous without it.

It also doesn't entirely switch it off anyway. Decals will always have it, as they are basically made of it.

I am getting this error only on console not through ssh or telnet. No error logs in syslog or dmesg. The server is working fine. 1 disk got failed on this disk but after replacing it also getting same error.

There is a line in /etc/inittab that tells init to run the listed command and restart it if it stops for any reason. Now this command keeps dying almost immediately, and after multiple restart attempts, init's safety mechanism is limiting the restart attempts so that the system won't waste all its power trying to restart something that is apparently not going to work.

Is the system supposed to be running something like that? If not, this might be a remnant of some previous software installation that has not been completely uninstalled, and you can safely remove the line from /etc/inittab.

Since the command in inittab is directing all its output to /dev/null, the only way to see any error messages it might produce is to run it manually without the I/O redirections. So please run this command:

If this system should be running an Oracle Cluster or a RAC database, you and your DBA probably should start troubleshooting it. (The database might currently be running just fine, but the failure of the Cluster Synchronization Service might make the cluster unable to recover automatically if something else fails.)

Thanks for the reply.I will try to work on this with my DBA. Have one more query. We have RAID mirroring on all disk. From the day I am getting this error on my console I am also getting Amber LED on my 2 disk. From syslog, dmesg, diskinfo etc.. no error regarding the disk.

If the variable does not exist, you will get no output from the "echo $ORA_CRS_HOME" command. That probably means the product was already removed. If the variable exists but the directory does not exist, it probably means the same thing: the previous sysadmin has already uninstalled the Oracle product (RAC, Cluster or ASM) that caused the /etc/inittab line to be added, but for some reason forgot to remove all the parts.

The "INIT: Command is respawning too rapidly" message indicates the /sbin/init.d/init.cssd script already cannot do its job properly: if the CSSD was required by Oracle or some application, any possible harm to applications is already done. By commenting out the line, you simply stop the system from uselessly trying to start CSSD, as you already know it does not work any more.

to make the init process re-read the inittab file. After reading the modified inittab, the init process will stop trying to restart /sbin/init.d/init.cssd, so the "command is respawning too rapidly" error messages will no longer appear on your console and in /var/adm/syslog/syslog.log.

3a8082e126