That would be lovely! Well for example the commands /back can be exploited to get fairly easy to the place of death. Some Servers don't want that, and it woul dbe really cool if a Admin could just deactivate the command for all other regular players. The same could be done with other commands like /spawn and /home. This would give servers the free choice to use all or just a certain amount of your commands for regular players. Thanks a lot
Cool. I will add a config file to be able to set each command to: all, enabled, op, or no. Where all would be available to all users anytime. Where enabled would require the "/spawn+ enable" to allow it on the server. Where op would only allow operators to use it. And no would be that the command will not be available at all. file: commandPermissions.config
A thought I had is just using the config file and not using the "/spawn+ enable" at all. I might do this as well. If i do, I'll put in a custom message about the config file, if someone tries to use the enable command. This would ofcourse eliminate the "enabled" option above.
I have been thinking it might be nice to be able to rename any command using a config file. I'll put some thought into that as well. This might be useful for resolving command conflicts or even for other languages. file: commandNames.config
Any additional thoughts or suggestions are welcome.
I plan to work on this soon.
EDIT: In progress (September 25th, 2014)
EDIT: Much progress has been made. Getting there. (October 3rd, 2014)
I have to review the code for the working updated (not yet released) version of SpawnCommands Teleport. Then I need to apply the chanes to the minecraft 1.7.2 and 1.6.4 versions of this mod. Then I will release them. =)
The most significant changes are as follows: (remember not yet released)
1. every command and sub command can be configured with permissions: no, op, enabled, and all. Where no is totally disabled. Op is operator only. enabled is it requires the enabled flag to be set. All is open to all users.
2. every command can be changed to a different word or command. As in you could change the /spawn to something like /gothere if you wanted.
3. now SpawnCommands Teleport stores all locations and configuration in the world folder of the appropriate game. It used to have one set of spawn locations and configuration for all games you played in single player mode. Now it recognizes which game you are playing and also knows which folder to use whether it is a unique singleplayer game or if its a dedicated server. (finally got this bit right lol)
4. shared locations are fully functional. operators may create named teleport locations with an @ sign ahead of the name and all shared locations are listed at the beginning of the /spawns list of locations with their @sign names. The idea being there may be common needed locations like @mainspawn or @tradecenter or @communitycastle and such.
A minor addition: When in single player with cheats disabled you are unable to have operator status. This would normally prevent you from enabling and disabling advanced commands in the mod. Now there is a misc config option to allow this mod to think you are an op in singleplayer despite the no cheats allowed option at game creation. You can ofcourse just edit the config files anyway. They are created automatically the first time you enter a game.
Well thats whats coming just around the corner. All this is 100% working and tested in my not-yet-released code. I will release it all after I review the code then convert it for minecraft 1.7.2 and 1.6.4.
Thats the news so far.
EDIT: (october 5th,2014) I've swept my code for derpiness. It looks good now. I will make versions for mc 1.7.2 and 1.6.4 next. The new release will be right after that.
EDIT: (October 8th, 2014) Officially released. See the first post change log for the final changes in this version.
I am playing offline and I am getting 'This is an op only command. You are not an op.' for /spawn+ enable. Meaning I can only set one home, which is annoying for moving house Any ideas how to fix this? I am playing offline, can only use the basic settings.
Yes. The config file .minecraft/saves/yourWorldName/SpawnCommands-config-folder/_miscellaneous.config has a setting called allowWithCheatsDisabled that needs set to true. This is the most likely solution to making the /spawn+ enable to work. Also the AdvancedCommandsEnabled can be manually set here as well. Any change to this file should be immediately available in game without restarting the game.
If this does not work I am very happy to help resolve this. Please let me know if this worked for you.
EDIT:
I looked over the default settings in the misc config file. This setting (allowWithCheatsDisabled) defaults to false. The thought behind this is that if you have your single player game created with "cheats disabled" it makes sense to have the advanced commands disabled. BUT *grin* myself having had the problem you have now, I created this config option. =) This solution should work.
I am certain I am missing something here so perhaps you guys can lead me through my ignorance to the light.
I would like to enable /spawn <named location> for all users while preventing users from creating the named locations (I will create them using shared locations). This is for a Pixelmon server. The problem is, I have no idea what the name of the config file should be to make the system use it nor am I certain what the entries for the permission assignments should be. I tried naming it Permissions and entered "spawn *: all" as a shot in the dark and obviously it did not work.
I would like to enable /spawn <named location> for all users while preventing users from creating the named locations (I will create them using shared locations).
Yes easily.
In your server folder under your world folder in the folder "SpawnCommands-config-folder" is the config file "_commandPermissions.config" edit this.
// This file is checked each time a command in this mod is used.
// command=[all|enabled|op|no]
// example: back=op
The red settings above you need to set as shown for what you asked for.
spawnName allows all players to use the /spawn command with a name after it such as /spawn @townhall
Each of the /spawn+ and /spawn- commands and sub-commands should be set to op for your use, as they control adding and removing locations.
The blue settings above I suggest you set to "op" if you don't want players setting their bed location and teleporting to it. Also the "/back" command is very powerful and will take players back to their last death point if they have not teleported since their death. I suggest "op" for it as well. Your choice.
The green settings above are probably already set to what you need as "all" players.
An unlikely situation: If you are using SpawnCommands Teleport 2.0.0 or up and not changed any settings, the above should work well. But If you have changed the misc. setting "homewithnamedlocations" to true you should change it back to false for what you want.
In short: set the red ones above =)
PS: Be sure you are using version 2.0.0 or up of SpawnCommands Teleport for these features to work.
Where are the config files located when you add this to your server????
Config files location: in the appropriate world folder
Single Player: in the .minecraft/saves/YourSavedWorldNameHere
Multiplayer: in the server folder under the world name as specified in the server.properties file. example: myDW20server/world
The folder you are looking for in that location should be named "SpawnCommands-config-folder"
If you forget where they are, a SpawnCommands.config file in the forge standard /config/ folder contains a mesage reminding you where to look for them.
Side Notes:
You should be able to edit the files with any plain text editor such as notepad or gedit.
If you totally screw up the config files, do not worry, just erase them and restart the server. They will be recreated with the default settings when the server starts.
Also you may add or remove the SpawnCommands Teleport mod at any time without harming your server. It does not affect any blocks or items.
Hey, when i type /spawn+ Piratebay it comes up with: Named locations are not enabled for spawncommands.
How do i fix this?
In chat type:
/spawn+ enable
If you are op (server operator) or in single player with cheats enabled you will be able to use the /spawn+ Piratebay immediately after that.
The mod starts with simple commands by default, but doing the above will enable everything.
If you are in a single player game with no cheats enabled.then there is still a save. Message 27 above this one explains. Its a matter of changing one line in the misc. config file for this mod to "allowWithCheatsDisabled=true".
Happy to help. Have fun.
EDIT: I just remembered! If at all possible make sure you are using SpawnCommands Teleport version 2.0.0 or up. The /spawn+ enable should work either way but the config file solution is only for version 2.0.0 and up.
An adjustment for Railcraft for Minecraft 1.7.10 in the Direwolf20 mod pack is needed.
Aparently Railcraft creates a temporary invisible block at player's locations called "residual heat". This fools SpawnCommands into thinking that there is something in the way almost everywhere you teleport to. An easy fix is to add the following line into the "_canSpawnInsideBlockNameList.config" config file for SpawnCommands.
Railcraft:tile.railcraft.residual.heat
Incidentally I also added this line for convenience:
TConstruct:decoration.stonetorch
This immediately cleared up the symptom of the jump/fall effect when you teleport to a named location in the Direwold20 pack with SpawnCommands installed.
I am now working on updating this for Minecraft 1.8 now that MineraftForge for 1.8 is out. yea!
EDIT (March 3, 2015): coding for 1.8 seems done. some singleplayer testing seems to work well. Next is full testing in singleplayer then on a test SMP server. Then after that release it for Minecraft 1.8.
EDIT (March 5th, 2015): Officially released SpawnCommands Teleport for Minecraft 1.8. Yea!
Great mod - enjoying it on my forge only server. Tired of fighting with Bukkit/Cauldron/Spigot stuff. I want to just do forge. Now I just need a mod that implements a user friendly Grief Protection for a Forge only server.
Are you asking if players can be limited to a specific number of locations they can create for themselves?
Are you thinking that players can create locations that everyone can access?
Please give me an example if possible?
Adding a config entry is easy. What I think you are asking may be unnecessary or even easy to setup. Please give and example and explain why... Thanks
Yes, I am wanting the feature whereby players are limited in the number of locations they can create for themselves.
No, I'm not referring to shared locations.
Feature Request: can you add something similar to the /tpa command from ForgeEssentials that allows a player to do /tpa <playername> which will send a teleport request to said player and if they accept the player issuing the request will be teleported to the target player? I know you have something similar but it isn't the same thing. It doesn't ask for permission.
Following is left-field for you but maybe not, who knows.
Could you make a companion mod or feature in this mod whereby portals can be crafted, and if so crafted those would be shared by default and furthermore said crafted portals allow the power to exceed the limitations imposed by my request above.
I only ask because Portal Gates 2 has a serious flaw in it that if the amulet of teleportation is used up the network you made previously forgets you and you can't get it back.
Yes, I am wanting the feature whereby players are limited in the number of locations they can create for themselves.
No, I'm not referring to shared locations.
Feature Request: can you add something similar to the /tpa command from ForgeEssentials that allows a player to do /tpa which will send a teleport request to said player and if they accept the player issuing the request will be teleported to the target player? I know you have something similar but it isn't the same thing. It doesn't ask for permission.
Following is left-field for you but maybe not, who knows.
Could you make a companion mod or feature in this mod whereby portals can be crafted, and if so crafted those would be shared by default and furthermore said crafted portals allow the power to exceed the limitations imposed by my request above.
I only ask because Portal Gates 2 has a serious flaw in it that if the amulet of teleportation is used up the network you made previously forgets you and you can't get it back.
Feature: set a maximin number of named locations regular players can create in the misc config will be easy and i will add this. (i work slowly due to life) For my understanding please tell me what you beilieve a maximum number would be set to and why? Examples are good.
Feature: /tpa: I have thought about this and it seems like it will be easy to impliment. As I envision it a person would /tpa destination-player-name,meaning "teleport ask player" then the destination player could type /tpa which means "teleport accept" or type /tpd meaning "teleport deny". Just some thoughts. This would work well with my existing command /back. Just fyi: any command in SpawnCommands may be fully disabled or renamed. This should be easy to code as well.
Feature: function similar to Portal Gates 2. This needs discussion and detail, both for my understanding and because there are a variety of ways to handle portals or gates or pads or simple teleport points, and many options for such including effects or restrictions or costs or free etc. So in short: explain more please lol
Also, I took a good look at the documentation for ForgeEssentials (FE) and at the Portal Gates 2. I love the FE and like the Portal Gates as well. In FE i found nothing relating to telporting except 2 things: 1. the setting of the main spawn points in different worlds (very nice!) and their /jump command. I really love Forge Essentials. I need to look into the Portal Gates a little more and wish to consider other ways of setting up transport points. I do not wish to offend the other modders and I really dont this this will. Please do explain more, I am interested.
[EDIT] You said "said crafted portals allow the power to exceed the limitations imposed by my request above" I have no idea what you mean by this.
PS: unrelated: this message editor was terrible to begin with now its even worse!!! every time i edit this message and add color to some of the print it changes my words to say "undefined". Its maddening.
Cool. I will add a config file to be able to set each command to: all, enabled, op, or no. Where all would be available to all users anytime. Where enabled would require the "/spawn+ enable" to allow it on the server. Where op would only allow operators to use it. And no would be that the command will not be available at all. file: commandPermissions.config
A thought I had is just using the config file and not using the "/spawn+ enable" at all. I might do this as well. If i do, I'll put in a custom message about the config file, if someone tries to use the enable command. This would ofcourse eliminate the "enabled" option above.
I have been thinking it might be nice to be able to rename any command using a config file. I'll put some thought into that as well. This might be useful for resolving command conflicts or even for other languages. file: commandNames.config
Any additional thoughts or suggestions are welcome.
I plan to work on this soon.
EDIT: In progress (September 25th, 2014)
EDIT: Much progress has been made. Getting there. (October 3rd, 2014)
my published mods
I have to review the code for the working updated (not yet released) version of SpawnCommands Teleport. Then I need to apply the chanes to the minecraft 1.7.2 and 1.6.4 versions of this mod. Then I will release them. =)
The most significant changes are as follows: (remember not yet released)
1. every command and sub command can be configured with permissions: no, op, enabled, and all. Where no is totally disabled. Op is operator only. enabled is it requires the enabled flag to be set. All is open to all users.
2. every command can be changed to a different word or command. As in you could change the /spawn to something like /gothere if you wanted.
3. now SpawnCommands Teleport stores all locations and configuration in the world folder of the appropriate game. It used to have one set of spawn locations and configuration for all games you played in single player mode. Now it recognizes which game you are playing and also knows which folder to use whether it is a unique singleplayer game or if its a dedicated server. (finally got this bit right lol)
4. shared locations are fully functional. operators may create named teleport locations with an @ sign ahead of the name and all shared locations are listed at the beginning of the /spawns list of locations with their @sign names. The idea being there may be common needed locations like @mainspawn or @tradecenter or @communitycastle and such.
A minor addition: When in single player with cheats disabled you are unable to have operator status. This would normally prevent you from enabling and disabling advanced commands in the mod. Now there is a misc config option to allow this mod to think you are an op in singleplayer despite the no cheats allowed option at game creation. You can ofcourse just edit the config files anyway. They are created automatically the first time you enter a game.
Well thats whats coming just around the corner. All this is 100% working and tested in my not-yet-released code. I will release it all after I review the code then convert it for minecraft 1.7.2 and 1.6.4.
Thats the news so far.
EDIT: (october 5th,2014) I've swept my code for derpiness. It looks good now. I will make versions for mc 1.7.2 and 1.6.4 next. The new release will be right after that.
EDIT: (October 8th, 2014) Officially released. See the first post change log for the final changes in this version.
my published mods
Yea!
See change log on first post.
my published mods
Yes. The config file .minecraft/saves/yourWorldName/SpawnCommands-config-folder/_miscellaneous.config has a setting called allowWithCheatsDisabled that needs set to true. This is the most likely solution to making the /spawn+ enable to work. Also the AdvancedCommandsEnabled can be manually set here as well. Any change to this file should be immediately available in game without restarting the game.
AdvancedCommandsEnabled=true
allowWithCheatsDisabled=true
HomeWithNamedLocations=false
If this does not work I am very happy to help resolve this. Please let me know if this worked for you.
EDIT:
I looked over the default settings in the misc config file. This setting (allowWithCheatsDisabled) defaults to false. The thought behind this is that if you have your single player game created with "cheats disabled" it makes sense to have the advanced commands disabled. BUT *grin* myself having had the problem you have now, I created this config option. =) This solution should work.
my published mods
my published mods
I would like to enable /spawn <named location> for all users while preventing users from creating the named locations (I will create them using shared locations). This is for a Pixelmon server. The problem is, I have no idea what the name of the config file should be to make the system use it nor am I certain what the entries for the permission assignments should be. I tried naming it Permissions and entered "spawn *: all" as a shot in the dark and obviously it did not work.
Any help would be greatly appreciated!
Yes easily.
In your server folder under your world folder in the folder "SpawnCommands-config-folder" is the config file "_commandPermissions.config" edit this.
// This file is checked each time a command in this mod is used.
// command=[all|enabled|op|no]
// example: back=op
spawn=all
spawnName=all
spawn.=all
spawn!=all
spawn?=all
back=enabled
spawn+=op
spawn+enable=op
spawn+@sharedlocation=op
spawn+name=op
spawn+nameWithCoordinates=op
spawn-=op
spawn-name=op
spawn-@sharedlocation=op
spawns=all
home=all
sethome=all
spawnhelp=all
The red settings above you need to set as shown for what you asked for.
spawnName allows all players to use the /spawn command with a name after it such as /spawn @townhall
Each of the /spawn+ and /spawn- commands and sub-commands should be set to op for your use, as they control adding and removing locations.
The blue settings above I suggest you set to "op" if you don't want players setting their bed location and teleporting to it. Also the "/back" command is very powerful and will take players back to their last death point if they have not teleported since their death. I suggest "op" for it as well. Your choice.
The green settings above are probably already set to what you need as "all" players.
An unlikely situation: If you are using SpawnCommands Teleport 2.0.0 or up and not changed any settings, the above should work well. But If you have changed the misc. setting "homewithnamedlocations" to true you should change it back to false for what you want.
In short: set the red ones above =)
PS: Be sure you are using version 2.0.0 or up of SpawnCommands Teleport for these features to work.
my published mods
Config files location: in the appropriate world folder
Single Player: in the .minecraft/saves/YourSavedWorldNameHere
Multiplayer: in the server folder under the world name as specified in the server.properties file. example: myDW20server/world
The folder you are looking for in that location should be named "SpawnCommands-config-folder"
If you forget where they are, a SpawnCommands.config file in the forge standard /config/ folder contains a mesage reminding you where to look for them.
Side Notes:
You should be able to edit the files with any plain text editor such as notepad or gedit.
If you totally screw up the config files, do not worry, just erase them and restart the server. They will be recreated with the default settings when the server starts.
Also you may add or remove the SpawnCommands Teleport mod at any time without harming your server. It does not affect any blocks or items.
my published mods
Andrenoel you are a pretty awesome modder to take requests so seriously. Very cool.
In chat type:
/spawn+ enable
If you are op (server operator) or in single player with cheats enabled you will be able to use the /spawn+ Piratebay immediately after that.
The mod starts with simple commands by default, but doing the above will enable everything.
If you are in a single player game with no cheats enabled.then there is still a save. Message 27 above this one explains. Its a matter of changing one line in the misc. config file for this mod to "allowWithCheatsDisabled=true".
Happy to help. Have fun.
EDIT: I just remembered! If at all possible make sure you are using SpawnCommands Teleport version 2.0.0 or up. The /spawn+ enable should work either way but the config file solution is only for version 2.0.0 and up.
my published mods
Aparently Railcraft creates a temporary invisible block at player's locations called "residual heat". This fools SpawnCommands into thinking that there is something in the way almost everywhere you teleport to. An easy fix is to add the following line into the "_canSpawnInsideBlockNameList.config" config file for SpawnCommands.
Railcraft:tile.railcraft.residual.heat
Incidentally I also added this line for convenience:
TConstruct:decoration.stonetorch
This immediately cleared up the symptom of the jump/fall effect when you teleport to a named location in the Direwold20 pack with SpawnCommands installed.
my published mods
EDIT (March 3, 2015): coding for 1.8 seems done. some singleplayer testing seems to work well. Next is full testing in singleplayer then on a test SMP server. Then after that release it for Minecraft 1.8.
EDIT (March 5th, 2015): Officially released SpawnCommands Teleport for Minecraft 1.8. Yea!
my published mods
Yea!!
If you have any problems at all please notify me immediately here.
A "secret" command has been snuck into the mc1.8 version of this. See the changes spoiler in post #1 if you really want to.
Have fun! I love to hear from you all. Feedback is nice.
my published mods
Can you add an option in the config to limit the named locations that a player can make?
Please clarify:
Are you asking if players can be limited to a specific number of locations they can create for themselves?
Are you thinking that players can create locations that everyone can access?
Please give me an example if possible?
Adding a config entry is easy. What I think you are asking may be unnecessary or even easy to setup. Please give and example and explain why... Thanks
my published mods
Yes, I am wanting the feature whereby players are limited in the number of locations they can create for themselves.
No, I'm not referring to shared locations.
Feature Request: can you add something similar to the /tpa command from ForgeEssentials that allows a player to do /tpa <playername> which will send a teleport request to said player and if they accept the player issuing the request will be teleported to the target player? I know you have something similar but it isn't the same thing. It doesn't ask for permission.
Following is left-field for you but maybe not, who knows.
Could you make a companion mod or feature in this mod whereby portals can be crafted, and if so crafted those would be shared by default and furthermore said crafted portals allow the power to exceed the limitations imposed by my request above.
I only ask because Portal Gates 2 has a serious flaw in it that if the amulet of teleportation is used up the network you made previously forgets you and you can't get it back.
Feature: set a maximin number of named locations regular players can create in the misc config will be easy and i will add this. (i work slowly due to life) For my understanding please tell me what you beilieve a maximum number would be set to and why? Examples are good.
Feature: /tpa: I have thought about this and it seems like it will be easy to impliment. As I envision it a person would /tpa destination-player-name,meaning "teleport ask player" then the destination player could type /tpa which means "teleport accept" or type /tpd meaning "teleport deny". Just some thoughts. This would work well with my existing command /back. Just fyi: any command in SpawnCommands may be fully disabled or renamed. This should be easy to code as well.
Feature: function similar to Portal Gates 2. This needs discussion and detail, both for my understanding and because there are a variety of ways to handle portals or gates or pads or simple teleport points, and many options for such including effects or restrictions or costs or free etc. So in short: explain more please lol
Also, I took a good look at the documentation for ForgeEssentials (FE) and at the Portal Gates 2. I love the FE and like the Portal Gates as well. In FE i found nothing relating to telporting except 2 things: 1. the setting of the main spawn points in different worlds (very nice!) and their /jump command. I really love Forge Essentials. I need to look into the Portal Gates a little more and wish to consider other ways of setting up transport points. I do not wish to offend the other modders and I really dont this this will. Please do explain more, I am interested.
[EDIT] You said "said crafted portals allow the power to exceed the limitations imposed by my request above" I have no idea what you mean by this.
PS: unrelated: this message editor was terrible to begin with now its even worse!!! every time i edit this message and add color to some of the print it changes my words to say "undefined". Its maddening.
my published mods