I need to add four components into my game using unreal engine 4
SIT151 - Assignment 3 Unreal Game Development Worth: 30% of your unit grade Due: Monday,1st of June by 11:59pm (Week 12) Introduction In this assignment you will individually design and develop components for a video game developed using the Unreal Engine 4 game engine. You will first need to complete the instructions for to create the base game covered in the Unreal development tasks in the practicals. The creation of this base game will take place during the first half of the trimester. You then need to design and develop chosen additional features as described below. Tasks Unreal Engine 4 Implementation For this assignment, you must first complete the base game you have created using the in-class Unreal Tutorials. From this base game, you will need to expand it by choosing at least 4 features from the Features section below in this document to add to your base game in Unreal Engine 4. Each component has 2 listed features with a description of the feature’s requirements. This means you could choose to complete: Both (2) features for 2 components (2 components * 2 features = 4 features) OR 1 feature each for 4 different components (4 components * 1 feature each = 4 features) OR Any combination of the above to equal at least 4 features. You may develop more than 4 features, in which event your best 4 will be counted towards your grade. You are encouraged to be as creative as possible in your solutions, with higher marks awarded for interesting and innovative solutions that go beyond the specific skills taught in your practical Unreal tutorials. A great way to create interesting and creative implementations of the components is to think about how they can become more dynamic or reactive to other game objects and components in a way that will surprise the player or encourage more varied gameplay. Your practical teacher will be happy to hear your ideas and provide guidance and feedback on your features. You are also encouraged to discuss your ideas and find solutions to development challenges with your peers both in practicals and using the SIT151 DeakinSync Unreal Development discussion board. However, you must be the only one to have access to your individual game files and implement your solutions. DO NOT SHARE YOUR UNREAL GAME FILES WITH ANY OTHER STUDENT. Note that sharing game files with others or using someone else’s work may be regarded as plagiarism or collusion, and is a breach of the Deakin Academic Integrity Policy. Bonus marks may be awarded in the event of particularly innovative or transformative work; however total assignment marks cannot exceed 40 points (20% of unit grade). Development Documentation To better demonstrate the purpose and development process of your features, you must also provide a development document that describes the way in which your design and implementation satisfied the brief of each of your 4 (or more) chosen features from the Features table later in this document. A template will be provided on DeakinSync. For each feature, you must provide: Description of your design and implementation of the feature. Reasoning for your choices and how your design fulfils the feature description in a creative or interesting way. Screenshots of the relevant blueprints used, together with an explanation of how they work. Gameplay Video A short (<2 minute) screen-capture video of your game in unreal engine demonstrating the features functioning and showing the blueprints. choice of screen-capture recording software is up to you. we suggest using obs studio which is available at deakin and also available to download from deakinsync for your own computer. the video should be solely focused on demonstrating your new features and their blueprints. you can edit this together however you wish to cut unnecessary footage if required. while you may wish to add voice-over, labels or captions remember this is not a promotional trailer and should only require minimal editing. please upload your video to youtube (recommended), vimeo or deakin video and provide the access url in your submission. note on youtube you can make videos ‘unlisted’ so they will not be publicly searchable if you do not wish your video to be viewable by anyone other than the unit staff. submission your submission to the assignment 3 dropbox on the sit151 deakinsync page must contain the following 3 items: an archive (zip file) of your unreal engine project. o ensure you test this prior to submission to avoid any missing files. your archive should simply be a zip of the entire project directory of your unreal game. your development document as a pdf or microsoft word document (.doc or .docx). your gameplay video as a url link with your submission. this can be provided as a text ‘comment’ on your submission. features choose 4 features total from any combination of components. component features and requirements (you must complete at least 4 features total!) new enemy add a new enemy to the game (this could be a boss enemy). feature 1: enemy must move in an interesting way different than the existing enemy. (10 points) feature 2: enemy must react to being attacked by the player in an unique way different from the existing enemy. special weapon add a second weapon for the player. feature 1: special weapon must be able to attack and damage or destroy enemies in a unique way different from the standard weapon. feature 2: special weapon must use limited or recharging ammo, preventing continuous use. power-up add a collectible power-up. feature 1: power-up must be able to be collected by the player for use at a later time or in certain states. feature 2: power-up must enhance player abilities in an interesting way that adds variety to gameplay. environmental hazard add an environmental hazard as an additional challenge. feature 1: environmental hazard must hinder the player in some way, encouraging the player to avoid it. feature 2: the environmental hazard must appear / start and disappear / end so it is not present for the entirety of play. enemy waves add a structured spawning system for enemies. feature 1: enemies must spawn in a wave-based system that waits until all enemies of a wave are destroyed before commencing the new wave. feature 2: enemy spawn points and behaviour must be varied and unique between waves (not just random spawn points). victory condition add a victory condition state for the player to win the game. feature 1: the game must end when the player achieves a certain challenging game state (try and think creatively). feature 2: the player must have real-time feedback during play that provides an indication of how close they are to successfully achieving the victory condition. dynamic difficulty adjustment add a system to regulate challenge in the game. feature 1: the game must evaluate player performance in real-time and judge whether the challenge is too easy, difficult or just right for the player. feature 2: the game must adjust the sources of challenge in response to this evaluation to better balance challenge to player skill. content transformation overhaul the look and sound of the game. feature 1: replace the visual and audio assets including all characters, objects and sound effects or music with assets you have created or sourced online yourself (try and think creatively such as changing the setting or theme of the game, and reference any online sources in your development document). feature 2: create a new, more detailed or interesting hud (heads- up display) including images and dynamic elements. marking rubric the following rubric will be used when marking and providing feedback from your assignment 3. the unit learning objective (ulo) criteria that you need to address in your submission is listed in the left hand column. the level to which you have achieved each criteria will be marked on the corresponding column for your 4 chosen features (10 points per feature). in the event you wish to include more than 4 features, all will be marked but only the 4 highest-scoring will count towards the final assignment grade for a maximum of 40 marks. feedback on all submitted material will be provided in the rubric. please review the tables below to assist you with your assignment. fail pass credit distinction high distinction unit learning outcomes 0-4 points 5 points 6 points 7 points 8-10 points ulo1: investigate computer game designs and articulate their effectiveness using evidence. ulo2: design and develop computer game components and incorporate that into a game. ulo3: employ the terminology used for computer game design and development to communicate ideas and concepts in a professional manner. feature is absent or only partially present with major issues. feature may not fully satisfy the requirements. documentation (including blueprint screenshots and video) of feature may be absent or missing significant information. component may not be present in project archive or may not be functional. both feature implementation in project file and documentation are present. feature is present and functional but may have some issues, bugs or inefficiencies. the feature requirements are generally fulfilled but the chosen design may be very simplistic and lacking creativity and inventiveness. documentation (including blueprint screenshots and video) covers the major required content with some omissions, or unclear points or issues. both feature implementation in project file and documentation are present. feature is present and functional with few issues or bugs and sound logic. the feature requirements are fulfilled but the chosen design may be somewhat simplistic or lacking creativity and inventiveness. documentation (including blueprint screenshots and video) covers the required content with some minor omissions, or unclear points or issues. appropriate terminology is used throughout. both feature implementation in project file and documentation are present. feature is present and functional with effective logic and very few issues or bugs. some evidence of engine or logic features beyond what has been covered in class tutorials minute)="" screen-capture="" video="" of="" your="" game="" in="" unreal="" engine="" demonstrating="" the="" features="" functioning="" and="" showing="" the="" blueprints.="" ="" choice="" of="" screen-capture="" recording="" software="" is="" up="" to="" you.="" we="" suggest="" using="" obs="" studio="" which="" is="" available="" at="" deakin="" and="" also="" available="" to="" download="" from="" deakinsync="" for="" your="" own="" computer.="" ="" the="" video="" should="" be="" solely="" focused="" on="" demonstrating="" your="" new="" features="" and="" their="" blueprints.="" you="" can="" edit="" this="" together="" however="" you="" wish="" to="" cut="" unnecessary="" footage="" if="" required.="" ="" while="" you="" may="" wish="" to="" add="" voice-over,="" labels="" or="" captions="" remember="" this="" is="" not="" a="" promotional="" trailer="" and="" should="" only="" require="" minimal="" editing.="" ="" please="" upload="" your="" video="" to="" youtube="" (recommended),="" vimeo="" or="" deakin="" video="" and="" provide="" the="" access="" url="" in="" your="" submission.="" note="" on="" youtube="" you="" can="" make="" videos="" ‘unlisted’="" so="" they="" will="" not="" be="" publicly="" searchable="" if="" you="" do="" not="" wish="" your="" video="" to="" be="" viewable="" by="" anyone="" other="" than="" the="" unit="" staff.="" submission="" your="" submission="" to="" the="" assignment="" 3="" dropbox="" on="" the="" sit151="" deakinsync="" page="" must="" contain="" the="" following="" 3="" items:="" ="" an="" archive="" (zip="" file)="" of="" your="" unreal="" engine="" project.="" o="" ensure="" you="" test="" this="" prior="" to="" submission="" to="" avoid="" any="" missing="" files.="" your="" archive="" should="" simply="" be="" a="" zip="" of="" the="" entire="" project="" directory="" of="" your="" unreal="" game.="" ="" your="" development="" document="" as="" a="" pdf="" or="" microsoft="" word="" document="" (.doc="" or="" .docx).="" ="" your="" gameplay="" video="" as="" a="" url="" link="" with="" your="" submission.="" this="" can="" be="" provided="" as="" a="" text="" ‘comment’="" on="" your="" submission.="" features="" choose="" 4="" features="" total="" from="" any="" combination="" of="" components.="" component="" features="" and="" requirements="" (you="" must="" complete="" at="" least="" 4="" features="" total!)="" new="" enemy="" add="" a="" new="" enemy="" to="" the="" game="" (this="" could="" be="" a="" boss="" enemy).="" feature="" 1:="" enemy="" must="" move="" in="" an="" interesting="" way="" different="" than="" the="" existing="" enemy.="" (10="" points)="" feature="" 2:="" enemy="" must="" react="" to="" being="" attacked="" by="" the="" player="" in="" an="" unique="" way="" different="" from="" the="" existing="" enemy.="" special="" weapon="" add="" a="" second="" weapon="" for="" the="" player.="" feature="" 1:="" special="" weapon="" must="" be="" able="" to="" attack="" and="" damage="" or="" destroy="" enemies="" in="" a="" unique="" way="" different="" from="" the="" standard="" weapon.="" feature="" 2:="" special="" weapon="" must="" use="" limited="" or="" recharging="" ammo,="" preventing="" continuous="" use.="" power-up="" add="" a="" collectible="" power-up.="" feature="" 1:="" power-up="" must="" be="" able="" to="" be="" collected="" by="" the="" player="" for="" use="" at="" a="" later="" time="" or="" in="" certain="" states.="" feature="" 2:="" power-up="" must="" enhance="" player="" abilities="" in="" an="" interesting="" way="" that="" adds="" variety="" to="" gameplay.="" environmental="" hazard="" add="" an="" environmental="" hazard="" as="" an="" additional="" challenge.="" feature="" 1:="" environmental="" hazard="" must="" hinder="" the="" player="" in="" some="" way,="" encouraging="" the="" player="" to="" avoid="" it.="" feature="" 2:="" the="" environmental="" hazard="" must="" appear="" start="" and="" disappear="" end="" so="" it="" is="" not="" present="" for="" the="" entirety="" of="" play.="" enemy="" waves="" add="" a="" structured="" spawning="" system="" for="" enemies.="" feature="" 1:="" enemies="" must="" spawn="" in="" a="" wave-based="" system="" that="" waits="" until="" all="" enemies="" of="" a="" wave="" are="" destroyed="" before="" commencing="" the="" new="" wave.="" feature="" 2:="" enemy="" spawn="" points="" and="" behaviour="" must="" be="" varied="" and="" unique="" between="" waves="" (not="" just="" random="" spawn="" points).="" victory="" condition="" add="" a="" victory="" condition="" state="" for="" the="" player="" to="" win="" the="" game.="" feature="" 1:="" the="" game="" must="" end="" when="" the="" player="" achieves="" a="" certain="" challenging="" game="" state="" (try="" and="" think="" creatively).="" feature="" 2:="" the="" player="" must="" have="" real-time="" feedback="" during="" play="" that="" provides="" an="" indication="" of="" how="" close="" they="" are="" to="" successfully="" achieving="" the="" victory="" condition.="" dynamic="" difficulty="" adjustment="" add="" a="" system="" to="" regulate="" challenge="" in="" the="" game.="" feature="" 1:="" the="" game="" must="" evaluate="" player="" performance="" in="" real-time="" and="" judge="" whether="" the="" challenge="" is="" too="" easy,="" difficult="" or="" just="" right="" for="" the="" player.="" feature="" 2:="" the="" game="" must="" adjust="" the="" sources="" of="" challenge="" in="" response="" to="" this="" evaluation="" to="" better="" balance="" challenge="" to="" player="" skill.="" content="" transformation="" overhaul="" the="" look="" and="" sound="" of="" the="" game.="" feature="" 1:="" replace="" the="" visual="" and="" audio="" assets="" including="" all="" characters,="" objects="" and="" sound="" effects="" or="" music="" with="" assets="" you="" have="" created="" or="" sourced="" online="" yourself="" (try="" and="" think="" creatively="" such="" as="" changing="" the="" setting="" or="" theme="" of="" the="" game,="" and="" reference="" any="" online="" sources="" in="" your="" development="" document).="" feature="" 2:="" create="" a="" new,="" more="" detailed="" or="" interesting="" hud="" (heads-="" up="" display)="" including="" images="" and="" dynamic="" elements.="" marking="" rubric="" the="" following="" rubric="" will="" be="" used="" when="" marking="" and="" providing="" feedback="" from="" your="" assignment="" 3.="" the="" unit="" learning="" objective="" (ulo)="" criteria="" that="" you="" need="" to="" address="" in="" your="" submission="" is="" listed="" in="" the="" left="" hand="" column.="" the="" level="" to="" which="" you="" have="" achieved="" each="" criteria="" will="" be="" marked="" on="" the="" corresponding="" column="" for="" your="" 4="" chosen="" features="" (10="" points="" per="" feature).="" in="" the="" event="" you="" wish="" to="" include="" more="" than="" 4="" features,="" all="" will="" be="" marked="" but="" only="" the="" 4="" highest-scoring="" will="" count="" towards="" the="" final="" assignment="" grade="" for="" a="" maximum="" of="" 40="" marks.="" feedback="" on="" all="" submitted="" material="" will="" be="" provided="" in="" the="" rubric.="" please="" review="" the="" tables="" below="" to="" assist="" you="" with="" your="" assignment.="" fail="" pass="" credit="" distinction="" high="" distinction="" unit="" learning="" outcomes="" 0-4="" points="" 5="" points="" 6="" points="" 7="" points="" 8-10="" points="" ulo1:="" investigate="" computer="" game="" designs="" and="" articulate="" their="" effectiveness="" using="" evidence.="" ulo2:="" design="" and="" develop="" computer="" game="" components="" and="" incorporate="" that="" into="" a="" game.="" ulo3:="" employ="" the="" terminology="" used="" for="" computer="" game="" design="" and="" development="" to="" communicate="" ideas="" and="" concepts="" in="" a="" professional="" manner.="" feature="" is="" absent="" or="" only="" partially="" present="" with="" major="" issues.="" feature="" may="" not="" fully="" satisfy="" the="" requirements.="" documentation="" (including="" blueprint="" screenshots="" and="" video)="" of="" feature="" may="" be="" absent="" or="" missing="" significant="" information.="" component="" may="" not="" be="" present="" in="" project="" archive="" or="" may="" not="" be="" functional.="" both="" feature="" implementation="" in="" project="" file="" and="" documentation="" are="" present.="" feature="" is="" present="" and="" functional="" but="" may="" have="" some="" issues,="" bugs="" or="" inefficiencies.="" the="" feature="" requirements="" are="" generally="" fulfilled="" but="" the="" chosen="" design="" may="" be="" very="" simplistic="" and="" lacking="" creativity="" and="" inventiveness.="" documentation="" (including="" blueprint="" screenshots="" and="" video)="" covers="" the="" major="" required="" content="" with="" some="" omissions,="" or="" unclear="" points="" or="" issues.="" both="" feature="" implementation="" in="" project="" file="" and="" documentation="" are="" present.="" feature="" is="" present="" and="" functional="" with="" few="" issues="" or="" bugs="" and="" sound="" logic.="" the="" feature="" requirements="" are="" fulfilled="" but="" the="" chosen="" design="" may="" be="" somewhat="" simplistic="" or="" lacking="" creativity="" and="" inventiveness.="" documentation="" (including="" blueprint="" screenshots="" and="" video)="" covers="" the="" required="" content="" with="" some="" minor="" omissions,="" or="" unclear="" points="" or="" issues.="" appropriate="" terminology="" is="" used="" throughout.="" both="" feature="" implementation="" in="" project="" file="" and="" documentation="" are="" present.="" feature="" is="" present="" and="" functional="" with="" effective="" logic="" and="" very="" few="" issues="" or="" bugs.="" some="" evidence="" of="" engine="" or="" logic="" features="" beyond="" what="" has="" been="" covered="" in="" class="">