Adragonfire shield is an upgraded anti-dragon shield, and one of the best shields in the game behind the elysian spirit shield and Dinh's bulwark. Equipping it requires 75 Defence and having started Dragon Slayer I. It retains the same dragonfire protection as the anti-dragon shield and it also protects against the icy breath of wyverns, like the dragonfire ward, elemental, mind, and ancient wyvern shields.
When uncharged, it is tradeable and offers slightly more defensive bonuses than a mithril sq shield, however, each charge it gains increases melee defensive bonuses and the range defensive bonus by 1 for a total of +50 at maximum those four defensive stats. To charge the shield, dragonfire needs to be absorbed from dragonfire or the icy breath attacks while it is equipped. Bottled dragonbreath can also be used to charge the shield.
Up to a maximum of 50 charges, the shield will absorb one charge per adult dragon dragonfire attack and icy breath attack from wyverns, although it will still discharge dragonfire. Alternatively, the shield can be fully charged by using one bottled dragonbreath on it. Each charge increases its melee and Ranged defensive bonuses by 1, giving a maximum total bonus of +50 to melee and Ranged defensive bonuses on top of the shield's base defensive bonuses. Prior to getting all 50 charges, any dragonfire attack will cause the player to brace behind the shield, stalling the player from doing other actions, but not affecting attacks.
Quickly gaining charges requires a multi-combat zone with multiple metal dragons as they will always use dragonfire when at a distance. The best location for this is the iron and bronze dragons area in the Catacombs of Kourend. Avoid being in melee range and drink an antifire potion to avoid all damage from the dragons. Charging to full with this method will take less than a minute. Elvarg in a practice run of Nightmare Zone may also be used as a free and completely safe alternative.
During Combat, right-click "activate" on the equipped dragonfire shield to expend one charge and unleash a blast of dragonfire at a target, hitting up to 25 damage. This attack has a cooldown of about 1 minute and 56 seconds, has a range of 10 tiles including over obstacles, after which the player will initiate a normal attack if possible.[1] The accuracy roll is based on the player's Defence level, which is rolled against an opponent's Magic defence.[2][3]
Each charge expended reduces the shield's melee and Ranged defensive bonuses by 1. The dragonfire attack mostly follows the standard rules for dragonfire; it will be less effective against a target that has dragonfire protection, such as a player that used an antifire potion and/or an anti-dragon shield. If the target has an anti-dragon shield equipped, the max hit of the dragonfire blast will be reduced to 3 points of damage, and can be reduced even further when combined with a dose of an antifire potion.[4] The use of Protect from Magic does not help mitigate the damage of a dragonfire shield's discharge however.[5]
A dragonfire shield can be drained of all charges at once by right-clicking the shield in the inventory and selecting Empty, releasing it all in a harmless burst. This is useful when selling or trading the shield, as it can only be traded when completely uncharged.
By 1994, higher-speed modems had begun to percolate down from researchlaboratories into the commercial world, and late that year I finallyobtained my own 19.2-kilobit modem. The speed difference was amazing; fora 2008 equivalent, imagine switching from an unstable ADSL connection to adedicated fiber-optic link. Not only were file transfers shortened by anorder of magnitude, but that speed also allowed me to work on a remotecomputer almost as easily as on my own system. The display was notinstantaneous, but reading mail or editing programs was much more tolerablethan it had been; at least I no longer had to wait nearly ten seconds justto view the next page of a file.
Being a bit of a computer music fan, I had amassed a fair collection ofmusic files (modules, or MODs, as they were often called) from various FTPsites. At the suggestion of a friend, and following the Internet principleof sharing, I set up an FTP server on my Amiga, making those filesavailable to anyone who happened across the server.
June rolled around, bringing my high school years to a close. Theswitch from the old VAX to the new Linux system went off reasonablysmoothly, and we shut the VAX down for the last time, ending my firstexperience with multiuser system administration. I had already beenaccepted to Carnegie Mellon University, and I settled back to enjoy mylast two months before entering college. Somehow or other, I managed tosecure continued Internet access through my high school until I left forCarnegie Mellon in late August.
All in all, it was a moderately eventful year, but an interesting onenonetheless, and things were looking up. My first semester of collegeended in mid-December, and I headed home for the holidays, trusting that myLinux server would manage to keep itself running for the month I was away.
As it turned out, the server itself performed just fine on its own. Mydormitory room Ethernet connection, however, did not fare as well,providing me with a bit of a scare in early January when Dragon suddenlybecame unreachable. I initially feared that the server had gone down,which would be a significant problem in terms of service, since I would notbe able to return to the dorm to fix it until the middle of the month. Acall to DataComm, however, revealed the true cause: My connection had beenadministratively disabled in response to a report of a cracking attemptfrom my IP address. The report, it turned out, came from the owner of asystem named
dragon.net.
In contrast to that first month of frustration, the remaining two monthsof summer vacation proved mostly uneventful. Naturally, the bandwidth wasnowhere near enough to support all the sites hosted on Dragonfire; the ISDNline reached its saturation rate of 112kbps for a few hours on the same dayit was connected, even though the updates to the dragonfire.netDNS data had not yet completely propagated. I was able to improveperformance by modifying the HTTP server software to limit the bandwidthused for image files, giving preference to the HTML pages themselves; aftera bit of fine-tuning, I was able to get a 100% response rate on HTML files,though at the cost of rejecting most requests for images. (At this time,many websites were still text-oriented, using graphics for decoration atmost. Doing this sort of throttling on a modern website could easilyrender it unusable.) Nonetheless, new users continued to request accounts,and in August I had to buy an external 4-gigabyte hard disk to augment the4GB of space already installed in the server.
At last, April arrived. I allowed a two-week grace period for those whodid not send payments early, so the transition from a free service was notinstantaneous; but on April 17, over four thousand accounts disappearedfrom the server, and Dragonfire was a free provider no longer.
In the end, I had to raise the basic account fee by about half, from$25 to $40 per year. At least I was able to keep it from jumping asdrastically as my own costs had, but it was still frustrating to feelDragonfire slip farther and farther from the inexpensive provider I hadwanted it to be.
With the addition of the new server and a growing number of serviceprocesses to monitor, I decided to merge my old system status displayprogram with several other short utility scripts I had written, creating afull-fledged monitoringprogram18 whichcould show me the complete status of Dragonfire at a glance:
(Once again, thenumbers19 are frommy personal machines in late 2007, not the actual hardware used byDragonfire.) Aside from having a compact status display, the program wouldbeep at me if it discovered anything untoward, such as a server going down;on one occasion, that woke me in the middle of the night and sent me on a12-hour trek from CMU down to the data center to repair one of the servers.
In November, I received word that I had been accepted to the internshipprogram. That set a firm time limit on when I would have to decide what todo about Dragonfire: I would be departing for Japan the following May,shortly after graduation. I began looking into what would be needed to setup an LLC, a simplified type of corporation, for Dragonfire; but I had notyet decided what I was going to do with the servers themselves.
He was delighted at the opportunity, and over the course of several morediscussions, we finalized an agreement whereby I would turn Dragonfire overto him, and he would pay me a percentage of profits to cover the cost ofthe equipment. And on February 13, I officially left my post asadministrator.
How the Internet has grown! Just 25 years on from running Dragonfireand about half that since first writing this retrospective, much of theworld now lives in an Internet-centric society. Government services areavailable online, and sometimes only online; ride-hailing apps haveovertaken taxi call centers; most people are walking around with abouttwo orders of magnitude more computing power in their pocket thanDragonfire ever had in its data center rack.
I do hold out hope that, since my intuition has proven correct inforecasting the current flood of misinformation, it may also prove correctin predicting that we will eventually learn to move beyond this stage, totruly understand the nature of this instant communication and how we canuse it to build a better society for all rather than simply destroy thatwith which we disagree. I often find myself thinking back on a remark Iwrote as a footnote toward the original end of this piece, on the topic ofmisunderstandings caused by instant communication, which I will quote here:
Dragonfire is the fiery breath used by dragons against their enemies. All adult dragons are able to use it, with the exception of Gorvek, the Revenant dragon, Dragonkin Laboratory celestial dragons and the three bosses of the Dragonkin Laboratory.
3a8082e126