**Feature summary** (what you would like to be able to do and where):
When placing a global account block, also adding an underlying global ip block should be optionalThe on-wiki overrides for messages used by the #GlobalBlocking extension need to be updated to reflect that you can now globally block accounts.
**Use case(s)** (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
In some cases a user needs to be globally blocked, but they are on a dynamic IP address, such as a mobile provider, and there is not also a need to block the underlying IP.This has caused confusion (because it mentions blocking an IP address), Currently placing an autoblock force-places the underlying IP block according to the block result output page.
**Benefits** (why should this be implemented?):
All of the same use cases that apply to local blocks that need to not block the underlying IP can be applicable hereso updating these messages is more urgent.