I have continued bulldozing through the course today, and my silly text RPG now has a magic system as well as a way to get a "Game Over". The application now starts straight into an enemy battle, and the played character has a limited amount of HP/MP, along with the enemy having a limited amount of HP. The application ends when either the player's hp or the enemy's hp reaches 0.
The biggest problem I'm finding is the same thing I bump into learning programming in the past: The further I go into it, the less in control I feel of the code and understanding what it does. All I have been doing mostly is copying almost verbatim the instructors code- although I do seem quick at finding typo errors when it doesn't run properly. I have also made my own changes to the program, such as making the text detailing enemy and player hp/mp stand out more, and giving different colours to the instructor (so text involving magic or MP are universally blue, for example).
I suppose these are the bugbears of learning anything unfamiliar. The thing is I know each of the systems individually and how and why they work. It's just, as a whole, I would have difficulty tracking down how or why a certain part of the code does a certain thing, without spending 30 seconds or so reading through it and remembering what each part of the code does. Still, the fact I can make little changes that work out how I want them to shows I must understand what I am coding on some level?
As usual, the code is available for study at: https://github.com/GlitchWalker/Python-RPG/
Showing posts with label Web development. Show all posts
Showing posts with label Web development. Show all posts
Sunday, 24 September 2017
Python App 2: Adding a Magic and Game Over System
Labels:
Computer Games,
computing,
education,
games programming,
gaming,
github,
programming,
python,
RPG,
scripting,
software,
stackskills,
Technology,
Text editor,
text game,
Video Games,
Web development
Sunday, 22 January 2012
So We Meet Again, Mr Tag
| Some CSS, An Image I Thought I'd Add Even Though I Don't (Yet) Understand It. Image via Wikipedia |
Anyway, here goes...
<DIV>
Used to group elements into blocks for styling purposes.
<BLOCK QUOTE>
Used for large quotes that may need indentation based on the style (although the style doesn't HAVE to indent it, but it'd make sense to). Use CITE to provide a URL citation. e.g:
<blockquote cite="http://gwattsdesign.blogspotcom>Loads more text would usually go here, say a paragraph or a few lines, but because I am just giving an example there is no need for me to randomly write that much off the top of my head</blockquote>
<P>
Represents a paragraph. It is used to "block" text together, and this is the most used block-level element.
<OL>
Creates an ordered list. (Can be preceded by numbering or any other character or image defined in CSS). e.g:
<ol>
<li>line/item 1</li>
<li>line/item2</li>
</ol>
<UL>
Similar to <ol>, bu creates a list with no numerical ordering, but just bullet points (or whatever is defined in CSS) e.g:
<ul>
<li>line/item</li>
<li>another line/item</li>
</ul>
<LI>
Stands for List Item. Should only be used in a list with <ol> or <ul>
<NAV>
Navigation element; contains links used to navigate the website. e.g:
<nav>
<ul>
<li>Home</li>
<li>Away</li>
<li>About</li>
<li>Links</li>
</ul>
</nav>
<MENU>
Creates an unordered list. The difference is whereas <ul> solely displays items, <menu> acts as an interactive menu with items that are activated or interactive in some way (like in a window's menubar). It can also contain nested <menu>'s, or menus within menus (which presumably would display on mouse-over). e.g.:
<menu type="toolbar">
<li>
<menu label="file">
<button type="button" onclick="new()">New...</button>
<button type="button" onclick="save()">Save...</button>
</menu>
</li>
<li>
<menu label="empty">
</menu>
</li>
</menu>
<SPAN>
Used for styling purposes. Similar to <div>, but is used in-line within a block, rather than acting as a block itself. (A little like when you put text in italics or bold in word processing, it doesn't necessarily act on the whole block/paragraph but only on a word, a few words or a line...?) e.g.:
<p>this <span>here</span> has just used the span tag</p>
<TIME>
Represents the time and/or date of an event, whether external (like a concert) or part of the website (like the creation of an article, or update of a page). It doesn't magically do anything on its own, but it is machine readable (using, for example, something like Google Calendar or a Feed Reader) so an application can use the date to update a calendar or order news stories. Information can be internal to the tag, or surrounded by the tag, depending on whether you want to the user to see the extra information or not respectively as part of the page. e.g.:
<p>Let's meet up at <time>19:00</time>
<article>
<p>This here article was made on <time pubdate>2011-01-02</time></p>
</article>
<p>The comedy show took place on <time datetime="2001-05-15 17:00">May 15 2001</time>
<Q>
Indicates the included text is a quote. e.g.
<p>Gary said <q>Gee whiz, that is so funny!</q>.</p>
<IMG>
Represents an image. e.g.:
<img src="a_pic.png" height="800" width="600" alt="What a pic!/>
Based on the P2P University activity at http://p2pu.org/en/groups/webmaking-101-html-hunting-in-the-world-around-you/content/some-tags-for-you-to-meet/
Related articles
- HTML5 context menus in Firefox (Screencast and Code) (hacks.mozilla.org)
- [How To] Enable Ubuntu's Global Menu in Xubuntu 11.10 (omgubuntu.co.uk)
- Why Good Website Navigation Is Important ? (olgalf.wordpress.com)
Labels:
Cascading Style Sheets,
Clients,
CSS,
Google,
Google Calendar,
HTML,
HTML element,
Hyperlink,
Open Web Foundation,
P2PU,
Protocols,
Span and div,
Watty Design,
Web development
Location:
Lincoln, UK
Saturday, 21 January 2012
%$@&! P2PU Is Down!
Just as I was about to start work on the next P2PU course, I go on it and get a message that the site is down for maintenance! I would have thought this would be one of the worst times to do (scheduled) maintenance, as not only is it prime-time for European web browsing but I would have thought peak time isn't too far off in the US too...
Oh well, I think it's time for a Thomas The Tank Engine Youtube Poop.... (most likely NSFW)
Oh well, I think it's time for a Thomas The Tank Engine Youtube Poop.... (most likely NSFW)
Labels:
Not safe for work,
NSFW,
P2PU,
primetime,
Watty Design,
Web browser,
Web development,
YouTube
Location:
Lincoln, UK
Friday, 2 December 2011
Just a Box. I mean, test.
Just a test, in order to complete my first task on P2PU. The task is available at
And hi, everyone!
Labels:
HTTP,
Open Web Foundation,
Protocols,
Watty Design,
Web development,
Web page
Location:
Lincoln, UK
Subscribe to:
Posts (Atom)