Is the minecraft version you are playing on matching the mod "mc" version?
The SpawnCommands 2.0.0 has that problem but the 2.1.0 does not.
Each time /home or /spawn. is triggered it looks up the home coordinates.
Are you in the overworld(main world) when you try /home?
Are you playing in single player or on a server?
When you put in the latest (v2.1.0) jar file into the /mods folder did you restart the server right after that?
It sound very much like you are using the 2.0.0 version of SpawnCommands.
- Yes I downloaded the mod for 1.8 and I am using MC 1.8
- I am using the 2.1.0 mod file
- I am in the overworld where I try it
- Single player
- Yes , restarted the game completely , several times
- The jar file says 2.1.0
EDIT: Maybe the config file that enable the use of /home got defaulted back to "false" setting after the update ? I forgot to check that. Will check that when I get home tonight and give feedback
EDIT 2: Ok I have double checked the following:
- jar filename is 2.1.0 in the mods folder
- Mod info in-game in the mods list also confirms version 2.1.0
- Everything in config files are enabled , nothing is disabled there
- Yes I downloaded the mod for 1.8 and I am using MC 1.8
- I am using the 2.1.0 mod file
- I am in the overworld where I try it
- Single player
- Yes , restarted the game completely , several times
- The jar file says 2.1.0
EDIT: Maybe the config file that enable the use of /home got defaulted back to "false" setting after the update ? I forgot to check that. Will check that when I get home tonight and give feedback
EDIT 2: Ok I have double checked the following:
- jar filename is 2.1.0 in the mods folder
- Mod info in-game in the mods list also confirms version 2.1.0
- Everything in config files are enabled , nothing is disabled there
/home does nothing , but /spawn. works
I will try to reproduce the problem. I had 1 other response that said that the config file did not update as well. I am checking into both. Thank you for the prompt feedback and details. Im on it.
EDIT: would you copy and paste the misc config file contents to here for my sake?
Looks great! It functions really well with other mods and I had no problem getting it to work with a heavily modded game. But would it be possible to add a command to delete homes?
To clarify: Would this command be the opposite of /spawn! and undefine the bed location in game?
I will try to reproduce the problem. I had 1 other response that said that the config file did not update as well. I am checking into both. Thank you for the prompt feedback and details. Im on it.
EDIT: would you copy and paste the misc config file contents to here for my sake?
1. I had accidentally put the wrong link for the direct download of 2.1.0 to display on the web page correctly but link to the 2.0.0 version. OOPS! fixed now.
2. Version 2.1.0 does NOT update the misc config file from the old to new version. I have changed the source code to work correctly and will release this fix today. I had set each new config option but forgot to set it into the configuration array I store it in. oops. BUT it does set it up correctly if the misc config file is removed. This happens when your server is started or when you enter a single player game.
3. I tested both single player and multiplayer server with /home and /spawn. which should take you to your bed or home location. They both work for me. However they seemed to not work when I accidentally used the 2.0.0 version (see problem 1 above).
4. I tested /sethome and /spawn! and sleeping in a bed as well. when I was actually using 2.1.0 they all worked well. One little forgetfulness and this happens. lol sorry.
Not exactly, I mean something simpler actually; unless I'm not reading your commands correctly, once I create a home through /sethome, I am not able to delete said home. Something like /deletehome mine to delete a home with the name "mine" for example.
I don't know if it's suppose to be like this , but after I have been to the Nether the /home location is messed up.
Everything was working fine , I went to nether. Explored a bit there and returned to the overworld. I returned far from home
and used the /home command. Suddenly I was surrounded by blackness and suffocating. I quickly used /spawn. and that took me home
just in time before I died. After returning home I did /sethome and then /home worked again.
The blackness and suffocating is actually a known problem when teleporting at all. It is even in vanilla Minecraft when you die then respawn.
For understanding of what happens: When you are teleported, such as when you respawn from death or use SpawnCommands, it sets your player location to the new place. Then you have but a short time for the world to load, and in that time it will let you fall when no blocks are loaded. Normally the world around you loads quickly and the game places you back where you belong. BUT if the world takes too long to load it leaves you falling and you end up inside the blocks under where you were supposed to be. You, ofcourse, suffocate inside solid rock and die. I have ended up 5 blocks below my bed and dug out fast with my pick axe. Note that using a pick axe quickly will usually dig out some air space for your head.
Anything that will speed up your world loading will help this problem.
This problem is not part of SpawnCommands but is in Minecraft combined with world load time.
I'm well aware of it and know of nothing I can do about it. Sorry.
Not exactly, I mean something simpler actually; unless I'm not reading your commands correctly, once I create a home through /sethome, I am not able to delete said home. Something like /deletehome mine to delete a home with the name "mine" for example.
Cool, if it were needed.
For better understanding:
Minecraft itself normally keeps track of the coordinates of the main world spawn and your bed location in that world. SpawnCommands keeps track of named locations on its own and is a mod or "addition" for Minecraft.
Any named location created by SpawnCommands /spawn+ or /sethome with a name after it is removable with /spawn- and the same name.
example:
/spawn+ mysouthcastle
or
/sethome mysouthcastle
will create a named location called "mysouthcastle"
/spawn- mysouthcastle
removes it instantly.
Yes, there is not a command called "/sethome-" and no command "/unsethome" either. sorry. But /spawn- works.
/sethome with no name after it sets the Minecraft bed location. People often refer to it as their "home" location which is why I often refer to it as "bed/home" location. There is a config file setting "HomeWithNamedLocations" that allows /sethome to create named locations but normally it only sets your Minecraft bed location.
The bed location, I suppose could be deleted by setting its coordinated to null or something, but I don't see the point in it since you can just ignore it or just set it to a different location. I am interested to understand a reason why one would want to remove it.
Irrelivant but interesting: The minecraft code seems to support bed/home locations in other dimensions if that dimension isSurfaceWorld type that has sky. But vanilla minecraft only comes with 3 dimensions main overworld, the nether, and the end. For mod coders see rule from EntityPlayer.trySleep(BlockPos);
I hope this helps. Please reply again if I am unclear or not answering the question well.
[EDIT] I suppose you could rename the /spawn- command to be /unsethome or something. I dont recommend it though.
I need some help with this mod as I cannot find the config files in the SpawnCommands folder, and when I look at my mods directly on minecraft it will not let me click on 'config'. I also already did the spawn+ enabled.
I need some help with this mod as I cannot find the config files in the SpawnCommands folder, and when I look at my mods directly on minecraft it will not let me click on 'config'. I also already did the spawn+ enabled.
Any advice?
To to clarify and hopefully not make it worse...
Are you in single player or in a multiplayer server trying to find the config files?
If you are in single player then look under your Minecraft folder under the /saves folder then under the folder for your saved game.
If you are in single player starting Minecraft with the vanilla Minecraft launcher, then you need to find your ".minecraft" folder. On different operating systems it is in different locations. On my Windows 7 system it is under C:\Users\myusername\AppData\Roaming\.minecraft and Microsoft hides the "AppData" folder from you normally. In my Ubuntu machine it is located under /home/myusername/.minecraft and is easily accessible. You will need to locate this folder on your system.
if you are in single player using FTB Launcher you first find and open the folder you have the FTB Client installed to. This can be found by starting the FTB Launcher and clicking the large "Options" button at the top of the window and reading the first line there labeled "Install folder..." Open that folder in your computer. Inside that there are folders representing any different mod packs you have installed from FTB. My mod pack was Direwolf20's mod pack version 1.3.1 for Minecraft 1.7.10 and it's folder name was slightly cryptic but recognizable as "direwolf20_17". Inside that I opened the folder there called "minecraft". This the folder minecraft runs in for this mod pack. Under this is where you start looking for config files. So with this example my starting folder path is: C:/users/myusername/desktop/FTB Client/direwolf20_17/ minecraft
If my saved game was called "New World" then my single player SpawnCommands config files for this would likely be in C:/users/myusername/desktop/FTB Client/direwolf20_17/minecraft/saves/New World/SpawnCommands-config-folder. If you have more than one saved game called "new world" then Minecraft adds a "-" to the game name as the folder name. You will have to look under the game name at the list of single player games. This is the answer to your question.
if you are using a multiplayer server, you need to know the starting folder path or folder location of the server. In that folder you will see very similar folders to a single player game. There should be a /mods and a /config folder there in the same way as all Forge servers have. Instead of looking under /saves for single player you need to identify which folder holds your game world. Normally the folder is just called "world" but to be real, open the file there called "server.properties" There is a line in there that defines what the folder name really is for your world. Look for a line starting with "level-name=". This line defines what the folder name is. Inside this folder is where to find the folder named "SpawnCommands-config-folder" which is the answer to your question.
I hope this makes things clearer and not worse.
Short answer: the config file for SpawnCommands are under the appropriate world folder where your game is saved since it relates to that world only and not to minecraft in general.
I know you are saying you can't do anything about the spawning inside blocks and I do understand that is a larger issue but we have the problem constantly on our server. However, it only happens when someone has slept in a bed. Using /sethome and then /home no one on the server has yet to spawn inside any blocks but if we sleep in a bed and use /home it happens nearly every time, even if we are very near to our bed when we do it.
Is it possible to disable the sleeping in a bed setting your home location and only having /sethome? Awhile back I ran a bukkit server and the essentials mod (I think it was called) had this functionality. Sleeping in bed would set where you would go back to on death but only /sethome would actually set your /home location.
I know you are saying you can't do anything about the spawning inside blocks and I do understand that is a larger issue but we have the problem constantly on our server. However, it only happens when someone has slept in a bed. Using /sethome and then /home no one on the server has yet to spawn inside any blocks but if we sleep in a bed and use /home it happens nearly every time, even if we are very near to our bed when we do it.
Is it possible to disable the sleeping in a bed setting your home location and only having /sethome? Awhile back I ran a bukkit server and the essentials mod (I think it was called) had this functionality. Sleeping in bed would set where you would go back to on death but only /sethome would actually set your /home location.
a rambling answer:
as far as spawning inside blocks when using /home, it should function exactly the same as when you die and respawn there. hmmm.
Its almost always due to slow load time of the destination area (bed in this case). it is 100% minecraft code issue. Sleeping in the bed does set your death respawn location in minecraft itself.
This bed location is looked up every time you do a /home to go there. the coordinates are to the head of the bed.
i hear you, but knowing the code i don't see the difference if you sleep in the bed or /sethome.
slow load time is often because your bed chunk is not loaded into minecraft at the time you teleport therefore it has to load that part of the world and the chunks around it. Some interesting but irrelevant beginner information: chunks are 16 blocks wide by 16 and go from bedrock to sky top. also chunk borders can be seen with the F9 key if you have nei mod installed (nei = not enough items).
slow load can be because of the lack of bandwidth for the machine hosting your minecraft server. it can be because that server is under attack (lookup ddos attacks). slowness can be because the server is so busy processing other in game things that it can barely respond to what is needed (see Entity LagFix and Opis). If players are running multiple mining quarries or multiple chunk loaders or spot loaders it can allow lag time as well. Entity LagFix can be installed or uninstalled with no fuss. To check if too many items are being processed in the server try using its /entitycount 99999 command once to get a report about all loaded parts of the world. The 99999 radius essentially means all loaded areas. preferably do that right when you are having the problem. read the 1st post of the Entity LagFix page to help you understand it better. Opis is excellent but more confusing to use. There are good videos on using Opis on youtube.
Ive had multiple servers have problems due to issues detectable by Opis and Entity Lag Fix.
i would look into disabling the sleep in bed but it doesnt make sense at the moment.
I hope this helps at least some.
the bukkit essentials mod was part of my inspiration for spawncommands teleport for forge. =) Its a good mod.
[EDIT PS] "possible to disable the sleeping in a bed setting your home location" possible im sure. i will think about it for a while.
I get "**** is not a player in game right now" when I try to use /ta on my server.
/sethome works fine. I can't seem to figure out what I didn't configure. Any ideas?
When using /ta the player names are case sensitive. It is in mind to make it not case sensative in a later version. Check to see which letters in their user name are capitalized. /ta TheirName is different than /ta theirname for now.
- Yes I downloaded the mod for 1.8 and I am using MC 1.8
- I am using the 2.1.0 mod file
- I am in the overworld where I try it
- Single player
- Yes , restarted the game completely , several times
- The jar file says 2.1.0
EDIT: Maybe the config file that enable the use of /home got defaulted back to "false" setting after the update ? I forgot to check that. Will check that when I get home tonight and give feedback
EDIT 2: Ok I have double checked the following:
- jar filename is 2.1.0 in the mods folder
- Mod info in-game in the mods list also confirms version 2.1.0
- Everything in config files are enabled , nothing is disabled there
/home does nothing , but /spawn. works
I will try to reproduce the problem. I had 1 other response that said that the config file did not update as well. I am checking into both. Thank you for the prompt feedback and details. Im on it.
EDIT: would you copy and paste the misc config file contents to here for my sake?
my published mods
To clarify: Would this command be the opposite of /spawn! and undefine the bed location in game?
my published mods
advancedcommandsenabled=true
allowwithcheatsdisabled=true
homewithnamedlocations=true
Here is what I have found so far:
1. I had accidentally put the wrong link for the direct download of 2.1.0 to display on the web page correctly but link to the 2.0.0 version. OOPS! fixed now.
2. Version 2.1.0 does NOT update the misc config file from the old to new version. I have changed the source code to work correctly and will release this fix today. I had set each new config option but forgot to set it into the configuration array I store it in. oops. BUT it does set it up correctly if the misc config file is removed. This happens when your server is started or when you enter a single player game.
3. I tested both single player and multiplayer server with /home and /spawn. which should take you to your bed or home location. They both work for me. However they seemed to not work when I accidentally used the 2.0.0 version (see problem 1 above).
4. I tested /sethome and /spawn! and sleeping in a bed as well. when I was actually using 2.1.0 they all worked well. One little forgetfulness and this happens. lol sorry.
workin on it...
EDIT:
The misc config should look something like this:
AdvancedCommandsEnabled=false
allowWithCheatsDisabled=false
HomeWithNamedLocations=false
AllowToLeaveTheDragon=false
LimitTheNumberOfNamedLocationsPerPlayer=false
TheNamedLocationsLimitNumber=3
teleportask responseTimeLimitSeconds=45
teleportask requestJustCameInDelaySeconds=1.2
teleportask lastPlayerAskedTimeoutHours=9
my published mods
OFFICIAL RELEASE (quick bugfix) of SpawnCommands Teleport v2.1.1
fixed the misc config file updating to the new version and options.
fixed the links under "download" in this thread top post.
Thank you to those reporting bugs. It helps everyone.
If the previous above message and the 2.1.1 version doesn't fix everything please do post a message here again.
my published mods
/home still doesn't work for me.
/home returns a list of my named locations , basically acting the same as the /spawns command
Edit: Wait a minute , I think my config is set to true for it instead of false. Lemme check on that first
Edit 2: Indeed it was. /home and /sethome works sharp for me now
Thank you for the quick fix
cool!
my published mods
Just when I thought I was done for the day I notice a tiny little itty bitty bug and decided to just get it done...
The feature to optionally limit the number of named locations per player was limiting it off by 1. Minor but fixed. Its nice when it all works!
OFFICIAL RELEASE (minor bug fix) of SpawnCommands v2.1.2 for Minecraft 1.8
(hopefully thats it for changes)
I do plan to port this code for the lower versions of minecraft then release them as well.
my published mods
Not exactly, I mean something simpler actually; unless I'm not reading your commands correctly, once I create a home through /sethome, I am not able to delete said home. Something like /deletehome mine to delete a home with the name "mine" for example.
I don't know if it's suppose to be like this , but after I have been to the Nether the /home location is messed up.
Everything was working fine , I went to nether. Explored a bit there and returned to the overworld. I returned far from home
and used the /home command. Suddenly I was surrounded by blackness and suffocating. I quickly used /spawn. and that took me home
just in time before I died. After returning home I did /sethome and then /home worked again.
The blackness and suffocating is actually a known problem when teleporting at all. It is even in vanilla Minecraft when you die then respawn.
For understanding of what happens: When you are teleported, such as when you respawn from death or use SpawnCommands, it sets your player location to the new place. Then you have but a short time for the world to load, and in that time it will let you fall when no blocks are loaded. Normally the world around you loads quickly and the game places you back where you belong. BUT if the world takes too long to load it leaves you falling and you end up inside the blocks under where you were supposed to be. You, ofcourse, suffocate inside solid rock and die. I have ended up 5 blocks below my bed and dug out fast with my pick axe. Note that using a pick axe quickly will usually dig out some air space for your head.
Anything that will speed up your world loading will help this problem.
This problem is not part of SpawnCommands but is in Minecraft combined with world load time.
I'm well aware of it and know of nothing I can do about it. Sorry.
my published mods
Cool, if it were needed.
For better understanding:
Minecraft itself normally keeps track of the coordinates of the main world spawn and your bed location in that world. SpawnCommands keeps track of named locations on its own and is a mod or "addition" for Minecraft.
Any named location created by SpawnCommands /spawn+ or /sethome with a name after it is removable with /spawn- and the same name.
example:
/spawn+ mysouthcastle
or
/sethome mysouthcastle
will create a named location called "mysouthcastle"
/spawn- mysouthcastle
removes it instantly.
Yes, there is not a command called "/sethome-" and no command "/unsethome" either. sorry. But /spawn- works.
/sethome with no name after it sets the Minecraft bed location. People often refer to it as their "home" location which is why I often refer to it as "bed/home" location. There is a config file setting "HomeWithNamedLocations" that allows /sethome to create named locations but normally it only sets your Minecraft bed location.
The bed location, I suppose could be deleted by setting its coordinated to null or something, but I don't see the point in it since you can just ignore it or just set it to a different location. I am interested to understand a reason why one would want to remove it.
Irrelivant but interesting: The minecraft code seems to support bed/home locations in other dimensions if that dimension isSurfaceWorld type that has sky. But vanilla minecraft only comes with 3 dimensions main overworld, the nether, and the end. For mod coders see rule from EntityPlayer.trySleep(BlockPos);
I hope this helps. Please reply again if I am unclear or not answering the question well.
[EDIT] I suppose you could rename the /spawn- command to be /unsethome or something. I dont recommend it though.
my published mods
OFFICIAL RELEASE of SpawnCommands Teleport version 2.1.4 for Minecraft 1.7.10
this is a very minor update for Minecraft 1.8
This includes the /ta Teleport Ask commands for the 1st time in mc1.7.10
my published mods
Hello.
I need some help with this mod as I cannot find the config files in the SpawnCommands folder, and when I look at my mods directly on minecraft it will not let me click on 'config'. I also already did the spawn+ enabled.
Any advice?
To to clarify and hopefully not make it worse...
Are you in single player or in a multiplayer server trying to find the config files?
If you are in single player then look under your Minecraft folder under the /saves folder then under the folder for your saved game.
If you are in single player starting Minecraft with the vanilla Minecraft launcher, then you need to find your ".minecraft" folder. On different operating systems it is in different locations. On my Windows 7 system it is under C:\Users\myusername\AppData\Roaming\.minecraft and Microsoft hides the "AppData" folder from you normally. In my Ubuntu machine it is located under /home/myusername/.minecraft and is easily accessible. You will need to locate this folder on your system.
if you are in single player using FTB Launcher you first find and open the folder you have the FTB Client installed to. This can be found by starting the FTB Launcher and clicking the large "Options" button at the top of the window and reading the first line there labeled "Install folder..." Open that folder in your computer. Inside that there are folders representing any different mod packs you have installed from FTB. My mod pack was Direwolf20's mod pack version 1.3.1 for Minecraft 1.7.10 and it's folder name was slightly cryptic but recognizable as "direwolf20_17". Inside that I opened the folder there called "minecraft". This the folder minecraft runs in for this mod pack. Under this is where you start looking for config files. So with this example my starting folder path is: C:/users/myusername/desktop/FTB Client/direwolf20_17/ minecraft
If my saved game was called "New World" then my single player SpawnCommands config files for this would likely be in C:/users/myusername/desktop/FTB Client/direwolf20_17/minecraft/saves/New World/SpawnCommands-config-folder. If you have more than one saved game called "new world" then Minecraft adds a "-" to the game name as the folder name. You will have to look under the game name at the list of single player games. This is the answer to your question.
if you are using a multiplayer server, you need to know the starting folder path or folder location of the server. In that folder you will see very similar folders to a single player game. There should be a /mods and a /config folder there in the same way as all Forge servers have. Instead of looking under /saves for single player you need to identify which folder holds your game world. Normally the folder is just called "world" but to be real, open the file there called "server.properties" There is a line in there that defines what the folder name really is for your world. Look for a line starting with "level-name=". This line defines what the folder name is. Inside this folder is where to find the folder named "SpawnCommands-config-folder" which is the answer to your question.
I hope this makes things clearer and not worse.
Short answer: the config file for SpawnCommands are under the appropriate world folder where your game is saved since it relates to that world only and not to minecraft in general.
my published mods
I know you are saying you can't do anything about the spawning inside blocks and I do understand that is a larger issue but we have the problem constantly on our server. However, it only happens when someone has slept in a bed. Using /sethome and then /home no one on the server has yet to spawn inside any blocks but if we sleep in a bed and use /home it happens nearly every time, even if we are very near to our bed when we do it.
Is it possible to disable the sleeping in a bed setting your home location and only having /sethome? Awhile back I ran a bukkit server and the essentials mod (I think it was called) had this functionality. Sleeping in bed would set where you would go back to on death but only /sethome would actually set your /home location.
a rambling answer:
as far as spawning inside blocks when using /home, it should function exactly the same as when you die and respawn there. hmmm.
Its almost always due to slow load time of the destination area (bed in this case). it is 100% minecraft code issue. Sleeping in the bed does set your death respawn location in minecraft itself.
This bed location is looked up every time you do a /home to go there. the coordinates are to the head of the bed.
i hear you, but knowing the code i don't see the difference if you sleep in the bed or /sethome.
slow load time is often because your bed chunk is not loaded into minecraft at the time you teleport therefore it has to load that part of the world and the chunks around it. Some interesting but irrelevant beginner information: chunks are 16 blocks wide by 16 and go from bedrock to sky top. also chunk borders can be seen with the F9 key if you have nei mod installed (nei = not enough items).
slow load can be because of the lack of bandwidth for the machine hosting your minecraft server. it can be because that server is under attack (lookup ddos attacks). slowness can be because the server is so busy processing other in game things that it can barely respond to what is needed (see Entity LagFix and Opis). If players are running multiple mining quarries or multiple chunk loaders or spot loaders it can allow lag time as well. Entity LagFix can be installed or uninstalled with no fuss. To check if too many items are being processed in the server try using its /entitycount 99999 command once to get a report about all loaded parts of the world. The 99999 radius essentially means all loaded areas. preferably do that right when you are having the problem. read the 1st post of the Entity LagFix page to help you understand it better. Opis is excellent but more confusing to use. There are good videos on using Opis on youtube.
Ive had multiple servers have problems due to issues detectable by Opis and Entity Lag Fix.
i would look into disabling the sleep in bed but it doesnt make sense at the moment.
I hope this helps at least some.
the bukkit essentials mod was part of my inspiration for spawncommands teleport for forge. =) Its a good mod.
[EDIT PS] "possible to disable the sleeping in a bed setting your home location" possible im sure. i will think about it for a while.
my published mods
I get "**** is not a player in game right now" when I try to use /ta on my server.
/sethome works fine. I can't seem to figure out what I didn't configure. Any ideas?
When using /ta the player names are case sensitive. It is in mind to make it not case sensative in a later version. Check to see which letters in their user name are capitalized. /ta TheirName is different than /ta theirname for now.
You probably did it right.
Im happy to help in any way that I can. =)
my published mods