llyrios

Igne'onn's eyes read over the letter. He cannot help but feel something indescribable as he realises he has lost his Father, his creator. He shakes his head "Maybe death itself is what you needed Father, your life was one worth living. You touched so many with your grace. May your soul rest peacefully for eternity."

Post is visible again!

"Sorry Father, they were lost in travel." he'd say to his creator as he scratched his head.

[!] As you walk the road you stumble across a torn scroll weighed down by an old coin, you pick up the scroll and read it. "To those of the guild who seek a place to speak easy, to have a break from the guards, fence off some unwanted goods that other traders will not buy or simply a place to conduct business you may not conduct in a normal tavern, visit Thirsty Hollow. If you wish to quench your thirst, use the map and visit the cabin, fill a bucket from the cauldron in the cellar." As you turn the note over a detailed map has been sketched onto it. Perhaps this note was lost, not meant for your eyes, perhaps it was... You now decide whether to visit. OOC Vrakai on the map indicates Belvitz for those who do not know, head to the marker labelled Cabin, please do not break blocks whilst you are there or play with the redstone (I'm fed up of griefing). If you are having trouble finding it, the co-ordinates are x:-360 z:660. This is a speakeasy, a tavern for villainy rp type characters or to just get away from the normal tavern rp that is ruled by laws/guards. If you have a shady character this could be the place for you. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[!] A small piece of parchment is pinned to a tree, there's writing on it which reads "The Lavana guard force is hiring men to protect its people, are you in need of work and care about this great town? Do you want to keep your family and friends safe? There's plenty of benefits they include: additional military training and free housing, free equipment and a great group of brothers in arms. Join Now! Find Valentino al-Zabaan in Lavana to enquire about joining. Usually found at the guard post." [OOC] Application: Minecraft username: Character Name: Character Race: Character Age: Previous military/guard history: Why are you suitable for the job: Discord Tag:

OOC Username: llyrios How active are you usually?: Most of the day You ok with using Skype?: Yes IC Name: Valentino al-Zabaan Age: 24 Race and Culture: Human (Farfolk) Gender: Male Social Status: Peasant Military History: None to date

Username: llyrios Character Name: Galather of Veris Race: Human Age:27

Yes.

I can provide examples soon, thanks

Serinus takes out the piece of fine parchment from his coat pocket and slid it into the box, the letter reads: "I have left this note in regards to the position opening at your tavern. I am a businessman who is a tailor by trade however I have ran a tavern before, in fact it was the Viridian Tavern in Johannesburg before it came to its end. I am well experienced and educated in trade and business. If you wish to talk more come find me in Karlsburg. Kind regards - Serinus Vagan" Skype: xgamersxtv IGN: llyrios

Conquest Pack as well as a shader mod.

[!] *You find a small note on the floor, below it reads:* I am selling my home. It is located in Krakow, which is in Pasnia, near Ostwick. I am selling it for 500 Minas but the price is negotiable. It is currently serving as my traders and tailor as well as a workshop and home. So it is pretty cramped, however with appropriate simple work it can be made spacious. It is based in a lovely expanding town, that is filled with wonderful people and has cheap tax. It has an attic space - which is currently serving as a bedroom, a ground floor and a second floor along with a spacious kitchen with a large basement area and a big area for storage as well as another big bedroom and an en suite washroom with a working shower and bath. Contact me Serinus Vagan for anymore information, I can be found in Pasnia or Ostwick. *Below you can see detailed sketches* ((Click on the images to expand))

how the structure and design of a game can assist in maintenance and capacity for extension Comments When creating a game it is important to completely map out and design how the game will function before starting development. Methods such as pseudo code and other program design techniques can aid in creating a more sustainable program. This means that rushing into development will allow big areas for error and the base code of the game could affect the performance and ease of any future development. Even when writing the code after designing the program for the game you can leave small notes or also knows as comments to help remind you. These are ignored when running the program as you differentiate them from the rest of the code, you can do this with a //before text for example. This can be seen in the image. Despite how useful they can be, overusing them everywhere can make code messy and pointlessly long, making it harder to read and this can lead to problems, if it is a strain on the eyes, and a problem does occur it can be hard to find it in amongst all the code. Using them to describe brief segments or just generally using them when it is needed, or if you are to remove them later. If you are using them to explain something, such as a function, use it to explain a complex function, instead of a simple one that the reader should already be able understand just from the code itself. When creating a larger game and a team in involved, these comments are especially helpful when working on the same code. They help to explain the needed functionality, and to plan out where certain sections of code will be placed. As you can see in the image the comments (marked with //) care used to categorise the code (config). Variables Some might think Variable names are not important, seeing as some are only used once. However variable with a more suitable name can save a lot time when referring to it in later code, this can mean you can use less comments, as stated on the previous slide, less comments leave cleaner code. By using better names for your variables you do not need a comment to describe what it does, just use a more direct name. For example, say you had a variable storing the names of character you could call it “CharacterNames” instead of just “Names”. It is only slightly longer yet save you a lot of time and effort. However, you might have to retype this name many times throughout your code, so length is still a secondary concern but a variable name should not sacrifice its descriptiveness for shortness. Using simple conventions when naming stuff is great if you’re working in a team. If everyone kept to the convention and use say “TheWeapons” and “TheBuildings” instead of just “Weapons” & “Buildings” it helps in stopping the code from becoming harder to read. Using the same prefix defines it from other variables. The hard part is getting everyone to stick to it. Layout The layout and physical structure of the code is code is very important when improving its readability and for making any future extensions much easier to integrate into the already existing code. It also helps a programmer spot any simple mistakes such as missing brackets or semicolons. It is important that the same style is maintained throughout the code, otherwise the readability of the code will be affected. Below is an image showing what an organised layout looks like compared to a disorganised layout. Modularisation This is the process of separating code into smaller individual modules. It generally has no improvement to the performance of how the code runs, in fact, if you use another file to modularise, there can actually be a slight decrease in performance because of the time it takes to open another file. This would not a big concern as it would only be a few milliseconds. So the main advantage of doing this is the productivity gains from separating the code up into more manageable sections. It is similar to Object Orientated Programming but there are a few main differences. The main one being that Object Orientated Programming uses classes and objects to separate things, whereas modularisation uses methods and functions. One of key benefits of modularising code is that if a problem does occur, it should be a lot easier to narrow down where the problem happened. Modularisation in Teams & in development programs When working in teams multiple programmers can work on the code at the same time. When using just one file there is a lot more danger of corruption or accidental deletion if several people are trying to edit the file, but with modularisation all the modules can be their own files, so the corruption problem is not an issue. Doing so can mean there is a reduced chance of breaking the current version when expanding. This is because if new content is being created, it will be stored in its own new modules. When using other programs such as GameMaker, some are modular by design, as is GameMaker. Therefor All objects, sounds, sprites, etc are all contained in their own modules/files. This makes it very easy to debug a problem when it does occur as GameMaker’s error message tells me which module is responsible. In a triple A game title where the code base can be more than 100,000 lines of code long, modularisation is vital. To the right is n example of one of these games; Sid Meier’s Civilization V. It is however, hard to show an example of the modularisation used in this game as most of the code is encrypted. But as you can see all the texture files and assets are not, so the modularisation can be seen here.

Holy **** look who it is...