I have known about Wizardry a long time, but for what is likely a bunch of reasons, I never played it. The game, and the series have always existed somewhere in my awareness as quality (certainly anything with seven sequels must be at least ‘okay’) but I never really had a chance to play it closer to its release date and haven’t really looked into playing it, until I stumbled upon the anime of the same name, based on the game and that was enough of an impetus for me to start playing it.
You can find lots of things on that video site…
The anime was excellent, basically like a D&D dungeon crawl in an hour. I really enjoyed it and decided that I really should try the game. I have no knowledge of the game aside from what I gleaned from the anime (not much) and what I have read in memes (incredibly hard difficulty, easy death). I am playing the NES version, largely for ease, and my intention is to not save-scum, so I can really enjoy the misery way old games were. Since the game has several dozen hours of playtime, this will be largely screenshots.
Thanks for the welcome…My first character. Creation is fairly simple, 5 races, several classes (including some progress-classes, that require additional statistics – I can see the space for them, but only managed to make one – Wizard – so far), and a choice of good-evil-neutral alignment. Here is my first character and that bonus is huge, which I learned when making my subsequent characters…Here is the crew: Shithead the human fighter, Paladin the human fighter, Healbot the human cleric, Burgler the hobbit thief, Pothead the elf wizard, and Blaster the elf mage. They are ready to take a dive into the dungeon.Navigating the dungeon (there is only one) is done in first-person perspective and is quite basic. Combat is done on the above table system. Things going well so far!This is the navigation view and it doesn’t get too much more exciting than this.
On the topic of navigating the game: there is no automap. Either the player must map it out manually, keep in their mind where they are (very difficult), or get totally lost (or use maps found online, I guess). I am making my own maps and it is part of the fun, but it definitely slows things down.
This is the same fight – it shows something I really like about the game: the player is not always aware of what creatures they are fighting, sometimes a round or two is required to figure out what kind of ‘slime’ or ‘small humanoid’ they are fighting.Treasures! Almost all boxes seem to have traps and makes me glad I brought along a thief.Magic spells in the game all have unique names that require the player to learn what they do through trial and error (or using a wiki, but I am going with trial and error).Well, taht sucks. My early exploration was halted by this setback as the crew ran back to town to resurrect Paladin.…and Healbot gets killed very soon after we re-enter the dungeon. Going is quite difficult and I had several deaths. I had to make a few other characters: Goon the fighter as well as Beggar, Bandit, and Blimp the thieves. I tried to raise Burgler after he was killed, but he was turned to ash. RIP, I guess. Regaining health is difficult. Gaining levels requires sleep. Lost statistics?! Madness. Shithead gains in power and most of the crew’s jaunts are pure grinding.Beggar was permanently paralyzed by a trap. Life is hard.One of the story elements of the game, we also found a key in this room.From the anime I learned that the dungeon has 10 levels, and I finally reached the end of the first.
That’s it for the first entry in this playthrough. The crew is fairly stabilized now with all characters being on level 3 or 4. We have found some better equipment, but nothing too special yet.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
You can find more information in our Cookie Policy and .
You must be logged in to post a comment.