Do you need anything to be nullified? - then read this closely.
1. How To Create a Correct Retail Thread
Do a search to see if the retail script you want to supply has not already been released by our group.
By creating the thread make sure you include the name, version and a good description of the item.
EXAMPLE:
THREAD:
Release Name
Description
Changes
THREAD FIELDS:
Developer :
Website : (without http or https)
Version :
Release Date:
Official Release / Internal Release (your decision) :
This means :
Official Release (only for Special Groups)
Internal Relase (only TeamDGT Members)
2. Attaching Files
Please only supply us with files straight downloaded from the members area,
because it makes it easier for us to identify watermarks.
Dont Rename the Attached Files.
As we know about the high sensibility of retails, we ask you to
Attach your files either in the particular thread or attach it in a private message to the
DGT NULLiNG SQUAD:
SNap!
TRiPL
Currently the maximum file size for you to upload is: 100 MB
For Security Reasons the Retail Section are Protected, this means,
You can only show your own created Threads. Never upload some Retail to the Retail Request Section.
Attached files are only viewable by DGT NULLiNG SQUAD, and it will only be worked on them within our Group.
3. Encoded Scripts
At the moment we are only accepting scripts encoded with
CodeLock
SourceCop
CNCrypto
PHP LockIt!
TrueBug PHP Encoder
PHTML Encoder
Custom gzinflate,
str_rot13, base64 etc.
any other non-bitcode protection.
Do NOT attach scripts encoded with Zend, ionCube or SourceGuardian.
Several reasons:
1.We still have many dezended scripts in queue, because the debugging process takes too much time.
2.We already got enough encoded scripts which need to be decoded.
3.We have nearly-none people in our group who are technical experienced to work with decoding and debugging.
4.Right now it is only possible for us to decode Zend-encoded scripts without paying.
4. Public Release?
After the script went through our nullify and testing processing, it will be packed and released to the public.
Private releases are available if so desired, please add a notice or contact us directly: SNap! or TRiPL !
5. Forbidden Retail Scripts
The following list contain all the Retail Scripts we don't want to see here.
XFileSharing Pro or any other Script from sibsoft.net.
All In One Tools for XenForo from xenvn.com.
Any Scrips of xendev.ru.
Any Scrips or Skins of XenTR.net
1. How To Create a Correct Retail Thread
Do a search to see if the retail script you want to supply has not already been released by our group.
By creating the thread make sure you include the name, version and a good description of the item.
EXAMPLE:
THREAD:
Release Name
Description
Changes
THREAD FIELDS:
Developer :
Website : (without http or https)
Version :
Release Date:
Official Release / Internal Release (your decision) :
This means :
Official Release (only for Special Groups)
Internal Relase (only TeamDGT Members)
2. Attaching Files
Please only supply us with files straight downloaded from the members area,
because it makes it easier for us to identify watermarks.
Dont Rename the Attached Files.
As we know about the high sensibility of retails, we ask you to
Attach your files either in the particular thread or attach it in a private message to the
DGT NULLiNG SQUAD:
SNap!
TRiPL
Currently the maximum file size for you to upload is: 100 MB
For Security Reasons the Retail Section are Protected, this means,
You can only show your own created Threads. Never upload some Retail to the Retail Request Section.
Attached files are only viewable by DGT NULLiNG SQUAD, and it will only be worked on them within our Group.
3. Encoded Scripts
At the moment we are only accepting scripts encoded with
CodeLock
SourceCop
CNCrypto
PHP LockIt!
TrueBug PHP Encoder
PHTML Encoder
Custom gzinflate,
str_rot13, base64 etc.
any other non-bitcode protection.
Do NOT attach scripts encoded with Zend, ionCube or SourceGuardian.
Several reasons:
1.We still have many dezended scripts in queue, because the debugging process takes too much time.
2.We already got enough encoded scripts which need to be decoded.
3.We have nearly-none people in our group who are technical experienced to work with decoding and debugging.
4.Right now it is only possible for us to decode Zend-encoded scripts without paying.
4. Public Release?
After the script went through our nullify and testing processing, it will be packed and released to the public.
Private releases are available if so desired, please add a notice or contact us directly: SNap! or TRiPL !
5. Forbidden Retail Scripts
The following list contain all the Retail Scripts we don't want to see here.
XFileSharing Pro or any other Script from sibsoft.net.
All In One Tools for XenForo from xenvn.com.
Any Scrips of xendev.ru.
Any Scrips or Skins of XenTR.net
