TLDR; Current SPF Reform Survey Voting and Results
Hello folks,
Late in December of 2017, I sent a detailed messaged to @Dredd describing my concerns about the state of the SPF, including but not limited to rules that could/should be modified, and improvements that we could do to the management of the SPF (and possibly new sub-forums that may or may not be created depending on community needs).
This is part of the response that @Dredd wrote:
"If you happen to know other posters who would like to see a chance in policy about mod use, please ask them to shoot me a PM and share their thoughts. Some people may not be speaking out due to peer pressure. I'm not here to judge, just to listen."
With this, I want to let everyone know to please message Dredd on changes that you would like to see in the community. Any proposals that you send to Dredd as a PM, will be posted in a private moderator forum which will be discussed with internal staff. As Dredd said, he is here to listen to your suggestions without judgement. Do not feel silenced because some people may not agree with you on your views. Everyone is part of the community and we all deserve our voices to be represented.
The following are the proposals that I sent out to him. Some of these may or may not be accepted. I wanted to post these in here rather than just send it to him privately so that people could see all of the viewpoints out there. I believe it will bring a healthier and more open community.
------------------------
Discussion of Mods
Discussion of mods in the forum should not be banned (But can be placed in a separate sub-forum). Sure PhrozenKeep is the primarily place for mod development, but a lot of the recent mods (Such as Singling's consolidation of FAM) has actually happened because of the many hours and experiences that the player base has been having. Without everyone here, Singling might have been much different or it wouldn't have existed.
Adding Item Level and Fingerprint support to Singling
@GalaXyHaXz has developed a small improvement (That will be added to Singling if it becomes SPF approved) for Singling that allows the user to see the item level. This would not pollute the stats since you will need to press "Shift" or "Ctrl" in order to see it. The "Shift" allows us to develop the display of "Extended attributes" which are really any attributes we want to see. For example, if we want to see the item level and the fingerprint of an item, holding Shift and hovering over the item will allow you to see this information directly inside the game. This feature has also been requested by many Diablo II members around the world.
At the moment the community is forced to use outside applications to do this (ATMA/GoMule).
Allowing trading in all Diablo II versions (Including the previously stopped 1.00-1.11 trading)
Currently the SPF doesn't allow trading in old Diablo II versions (And even versions up to 1.11 I believe) due to the game not having strong anti-dupe features. This lack of security should not prevent, people from trading with each other, and it doesn't make sense. People that are legitimately playing old versions of 1.00 or any other version cannot trade with each other even if they aren't duping themselves. The SPF has aways been an honor system and this should continue to be followed. Not allowing trading effectively kills the pre 1.11 multi-player community which is something that I'm working very hard to build with the Xyinn Network.
Allowing the play of LOD 1.07.41 Beta
The Bliss Complete Collection includes support for version 1.07.41 Beta. This version hasn't really been formally approved (or really mentioned much) by the SPF, but noting it here to bring awareness to this.
Map Seeds
Map seeds should be allowed to be backed up, and used for personal play as the player sees fit. This includes allowing the map seed to be backed up, and recovered when you are muling.
At the moment the SPF only allows the map seeds to be used in case you accidentally lost your map.
However, muling is a good situation where intentionally using the map seed would be beneficial. A lot of people are using GoMule/ATMA muling as a way to bypass this rule so that they don't lose their map. However, not everyone uses GoMule/ATMA, and those people should not be forced to use third party muling applications. It's also not a sustainable model since if Blizzard releases a new version of Diablo II that changes the character format, this might break compatibility with GoMule/ATMA, and thus you won't be able to mule with those apps anymore (Unless you decide to forever, stay on an older version, or wait until someone -maybe- updates GoMule/ATMA to the new version). We already see that those muling applications haven't been actively developed for years.
So to recap:
- Using Map Seeds for recovering your lost map when you mule should be allowed.
- And more generally, Map Seeds should just be allowed to be backed up and used as desired
for personal play. For example, if during your adventure you discover a nice Andy/Meph map,
but you want to go do Baal now, you should be allowed to save that map, go baal (find a good baal map and save that as well), and then when you are done you can go back to your Andy/Meph map.
I actually also don't have a problem if people were to share the map seeds, BUT, if people want to just allow the map seeds to be used as people see fit for _personal play only_, I would definitely be willing to compromise with that.
Most people (including myself now) are against using map seeds. However some exceptions can be made. The current rule in the SPF is that the map seed can be used for recovery purposes (Not sure what this means since I thought it meant if you misclick and lose your map, however people say that isn't allowed). What does the current SPF rule mean?
The other exception is for muling. At the moment people use GoMule/ATMA as a way to:
1. Efficiently mule
2. Bypass them losing their maps since GoMule/ATMA allow you to transfer your items between characters/stashes without you having to make a new LAN game.
Using the map seed for muling purposes only should be allowed since it would allow people that don't use those applications to mule and be on equal grounds with GoMule/ATMA users.
Enabling ladder-only runewords in 1.10
Why are ladder-only runewords allowed in 1.11+ but not in 1.10? Doesn't make sense. We should allow this and make things consistent.
HC to SC item transfers should be banned
Currently the SPF allows HC to SC item transfers. This doesn't make sense and violates the separation between HC and SC. If a HC item started in HC, then it shouldn't be allowed to be moved to SC whether or not the HC character is currently dead or not (Which would violate the HC stripping rule). This rule would only make more sense if dead HC characters could be converted to SC characters which some members in the forum are strictly against even though it doesn't affect HC in any way because -THEY ARE DEAD, AND NOT IN HARDCORE ANYMORE-.
Maybe allow distribution of Classic/LOD 1.00/1.03/1.07 ISOs [Still requires legal CD KEY from user]?
The new Blizzard installer for version 1.12a has an updated MPQ file format. If any players
that want to time travel and play any versions of D2 before 1.12, they won't be able to using
that Diablo II installation because the old versions will think the new MPQs are corrupted.
The solution to this issue is for the player to find an old pair of ISOs and re-install D2 using
the pre 1.12 images. These ISOs would be the exact ISOs found on the CD and they wouldn't be modified in any way. Which means that the installer will still prompt for a CD key. The user must have purchased a copy of D2 from Blizzard in order to install the game. This is the same concept that Microsoft uses for their Windows Vista, 7, 8, and 10 ISOs. Anyone can download and use the ISO, but the installer will prompt for a cdkey on installation.
Removed above since new installer uses 26 length keys rather than 16. Users with new installers and keys will need to find another way on getting the old MPQ files. Maybe grab old discs from eBay?
Solution for this problem has been found.
Allow players within minor versions of a game to play with each other
Currently the SPF considers every single patch a completely separate trade pool. This doesn't make sense. For example, 1.09[a b c d] would segregate the player base 4 times even though those were minor patch versions and all the files are fully compatible. 1.09b and 1.09d players cannot play with each other because of this rule.
1.13[a, b, c, d] also suffers the same type of fragmentation. And actually, there haven't been THAT many changes to the game starting from 1.10, sure we had re-specs in 1.13, but if you look at all of the other minor fixes, it isn't that much. Ubers were introduced in 1.10 and 1.11, but those are bnet only so it doesn't affect us.
Removing this fragmentation will increase the player base. For technical reasons, people should all use the same version, but if someone made a 1.13d character and everyone else decided on 1.13c, than that 1.13d player should be allowed to bring his character back to 1.13c considering it's all within the same patch version and no technical file format changes took place.
I haven't looked at all the forum rules but these are the ones that have caught my attention during my 6 years at the SPF.
Color Rune Mod / Color Gem Mod (Cosmetic Changes)
I don't see what the problem is with coloring runes in 1.07+. Blizzard added this in 1.13, and not having it in 1.07 and other pre 1.13 version doesn't make that particular version any better. Just stresses out your eyes more. You finding a rune and then missing out on that because everything is colored the same color (White) doesn't provide any "additional fun".
Gems can be colored as well since they are a socketable type and something we also look forward to pick up amongst the 100s of white items that drop.
- Jonathan
Hello folks,
Late in December of 2017, I sent a detailed messaged to @Dredd describing my concerns about the state of the SPF, including but not limited to rules that could/should be modified, and improvements that we could do to the management of the SPF (and possibly new sub-forums that may or may not be created depending on community needs).
This is part of the response that @Dredd wrote:
"If you happen to know other posters who would like to see a chance in policy about mod use, please ask them to shoot me a PM and share their thoughts. Some people may not be speaking out due to peer pressure. I'm not here to judge, just to listen."
With this, I want to let everyone know to please message Dredd on changes that you would like to see in the community. Any proposals that you send to Dredd as a PM, will be posted in a private moderator forum which will be discussed with internal staff. As Dredd said, he is here to listen to your suggestions without judgement. Do not feel silenced because some people may not agree with you on your views. Everyone is part of the community and we all deserve our voices to be represented.
The following are the proposals that I sent out to him. Some of these may or may not be accepted. I wanted to post these in here rather than just send it to him privately so that people could see all of the viewpoints out there. I believe it will bring a healthier and more open community.
------------------------
Discussion of Mods
Discussion of mods in the forum should not be banned (But can be placed in a separate sub-forum). Sure PhrozenKeep is the primarily place for mod development, but a lot of the recent mods (Such as Singling's consolidation of FAM) has actually happened because of the many hours and experiences that the player base has been having. Without everyone here, Singling might have been much different or it wouldn't have existed.
Adding Item Level and Fingerprint support to Singling
@GalaXyHaXz has developed a small improvement (That will be added to Singling if it becomes SPF approved) for Singling that allows the user to see the item level. This would not pollute the stats since you will need to press "Shift" or "Ctrl" in order to see it. The "Shift" allows us to develop the display of "Extended attributes" which are really any attributes we want to see. For example, if we want to see the item level and the fingerprint of an item, holding Shift and hovering over the item will allow you to see this information directly inside the game. This feature has also been requested by many Diablo II members around the world.
At the moment the community is forced to use outside applications to do this (ATMA/GoMule).
Allowing trading in all Diablo II versions (Including the previously stopped 1.00-1.11 trading)
Currently the SPF doesn't allow trading in old Diablo II versions (And even versions up to 1.11 I believe) due to the game not having strong anti-dupe features. This lack of security should not prevent, people from trading with each other, and it doesn't make sense. People that are legitimately playing old versions of 1.00 or any other version cannot trade with each other even if they aren't duping themselves. The SPF has aways been an honor system and this should continue to be followed. Not allowing trading effectively kills the pre 1.11 multi-player community which is something that I'm working very hard to build with the Xyinn Network.
Allowing the play of LOD 1.07.41 Beta
The Bliss Complete Collection includes support for version 1.07.41 Beta. This version hasn't really been formally approved (or really mentioned much) by the SPF, but noting it here to bring awareness to this.
Map Seeds
At the moment the SPF only allows the map seeds to be used in case you accidentally lost your map.
However, muling is a good situation where intentionally using the map seed would be beneficial. A lot of people are using GoMule/ATMA muling as a way to bypass this rule so that they don't lose their map. However, not everyone uses GoMule/ATMA, and those people should not be forced to use third party muling applications. It's also not a sustainable model since if Blizzard releases a new version of Diablo II that changes the character format, this might break compatibility with GoMule/ATMA, and thus you won't be able to mule with those apps anymore (Unless you decide to forever, stay on an older version, or wait until someone -maybe- updates GoMule/ATMA to the new version). We already see that those muling applications haven't been actively developed for years.
So to recap:
- Using Map Seeds for recovering your lost map when you mule should be allowed.
- And more generally, Map Seeds should just be allowed to be backed up and used as desired
for personal play. For example, if during your adventure you discover a nice Andy/Meph map,
but you want to go do Baal now, you should be allowed to save that map, go baal (find a good baal map and save that as well), and then when you are done you can go back to your Andy/Meph map.
I actually also don't have a problem if people were to share the map seeds, BUT, if people want to just allow the map seeds to be used as people see fit for _personal play only_, I would definitely be willing to compromise with that.
Most people (including myself now) are against using map seeds. However some exceptions can be made. The current rule in the SPF is that the map seed can be used for recovery purposes (Not sure what this means since I thought it meant if you misclick and lose your map, however people say that isn't allowed). What does the current SPF rule mean?
The other exception is for muling. At the moment people use GoMule/ATMA as a way to:
1. Efficiently mule
2. Bypass them losing their maps since GoMule/ATMA allow you to transfer your items between characters/stashes without you having to make a new LAN game.
Using the map seed for muling purposes only should be allowed since it would allow people that don't use those applications to mule and be on equal grounds with GoMule/ATMA users.
Enabling ladder-only runewords in 1.10
Why are ladder-only runewords allowed in 1.11+ but not in 1.10? Doesn't make sense. We should allow this and make things consistent.
HC to SC item transfers should be banned
Currently the SPF allows HC to SC item transfers. This doesn't make sense and violates the separation between HC and SC. If a HC item started in HC, then it shouldn't be allowed to be moved to SC whether or not the HC character is currently dead or not (Which would violate the HC stripping rule). This rule would only make more sense if dead HC characters could be converted to SC characters which some members in the forum are strictly against even though it doesn't affect HC in any way because -THEY ARE DEAD, AND NOT IN HARDCORE ANYMORE-.
The new Blizzard installer for version 1.12a has an updated MPQ file format. If any players
that want to time travel and play any versions of D2 before 1.12, they won't be able to using
that Diablo II installation because the old versions will think the new MPQs are corrupted.
The solution to this issue is for the player to find an old pair of ISOs and re-install D2 using
the pre 1.12 images. These ISOs would be the exact ISOs found on the CD and they wouldn't be modified in any way. Which means that the installer will still prompt for a CD key. The user must have purchased a copy of D2 from Blizzard in order to install the game. This is the same concept that Microsoft uses for their Windows Vista, 7, 8, and 10 ISOs. Anyone can download and use the ISO, but the installer will prompt for a cdkey on installation.
Removed above since new installer uses 26 length keys rather than 16. Users with new installers and keys will need to find another way on getting the old MPQ files. Maybe grab old discs from eBay?
Solution for this problem has been found.
Allow players within minor versions of a game to play with each other
Currently the SPF considers every single patch a completely separate trade pool. This doesn't make sense. For example, 1.09[a b c d] would segregate the player base 4 times even though those were minor patch versions and all the files are fully compatible. 1.09b and 1.09d players cannot play with each other because of this rule.
1.13[a, b, c, d] also suffers the same type of fragmentation. And actually, there haven't been THAT many changes to the game starting from 1.10, sure we had re-specs in 1.13, but if you look at all of the other minor fixes, it isn't that much. Ubers were introduced in 1.10 and 1.11, but those are bnet only so it doesn't affect us.
Removing this fragmentation will increase the player base. For technical reasons, people should all use the same version, but if someone made a 1.13d character and everyone else decided on 1.13c, than that 1.13d player should be allowed to bring his character back to 1.13c considering it's all within the same patch version and no technical file format changes took place.
I haven't looked at all the forum rules but these are the ones that have caught my attention during my 6 years at the SPF.
Color Rune Mod / Color Gem Mod (Cosmetic Changes)
I don't see what the problem is with coloring runes in 1.07+. Blizzard added this in 1.13, and not having it in 1.07 and other pre 1.13 version doesn't make that particular version any better. Just stresses out your eyes more. You finding a rune and then missing out on that because everything is colored the same color (White) doesn't provide any "additional fun".
Gems can be colored as well since they are a socketable type and something we also look forward to pick up amongst the 100s of white items that drop.
- Jonathan
Last edited: