DEPARTMENT OF COMPUTER APPLICATIONS

T. JOHN COLLEGE
(Affiliated to Bangalore University & Approved to AICTE)
Gottigere, Bengaluru – 560 083.

ANDROID ATTENDANCE SYSTEM

A project report submitted to the Bangalore University in the partial fulfilment
of the requirements for the award of the degree of

BACHELORS OF COMPUTER APPLICATIONS

Submitted by
ANTHONY JAYRAJ F

(Reg.No.U03ML21S0003)

Under the guidance of

Dr .P. FELCY JUDITH
(Assistant Professor, Department of Computer Applications)
 DEPARTMENT OF COMPUTER APPLICATIONS

T. JOHN COLLEGE
(Affiliated to Bangalore University & Approved to AICTE)
Gottigere, Bengaluru – 560 083.

PROJECT WORK

ANDROID ATTENDANCE SYSTEM

Bonafide Work Done by
ANTHONY JAYRAJ F

(Reg.No.U03ML21S0003)

The project submitted in partial fulfilment of the requirements for the award
of Bachelors of Computer Applications, of Bangalore University, Bengaluru.

GUIDE HEAD OF THE DEPARTMENT

Submitted for the Viva-Voce Examination held on

INTERNAL EXAMINER EXTERNAL EXAMINER

 DECLARATION

I, ANTHONY JAYRAJ F (Reg No. U03ML21S0003) hereby declare that the

project entitled ANDROID ATTENDANCE SYSTEM is my project work carried out
during the final year BCA at T. John College, Bengaluru, under the guidance of Dr .
P. FELCY JUDITH
Assistant Professor, Department of Computer Applications, T. John College and
has not submitted previously for the award of any other degree or diploma by me to
any institution or university according to the best of my knowledge.

SIGNATURE OF THE CANDIDATE

Place: Bengaluru
Date:
 ACKNOWLEDGEMENT

The project titled Android Attendance App has been successfully completed with
the help of our Principal , HOD and Guide. I thank them for providing great tips that I have
incorporated in this project.

I would express my sincere thanks to Dr. SRINIVASA HP, Principal, T. John

College for his valuable advice, co-operation and support and for providing all the faculties
for the construction of the project.

I am thankful to Dr. S. DINAKARAN, Head of Department of Computer

Applications for his valuable advice and co-operation.

I am thankful to Dr. P. FELCY JUDITH, Assistant Professor Department of

Computer Applications for his valuable advice and co-operation.

Last but not the least I also like to thank our friends and family for their valuable
support and encouragement.
 CONTENTS

SL TITLE PAGE No
NO
SYNOPSIS

1 INTRODUCTION
1.1 About the Project 01
2 SYSTEM STUDY AND ANALYSIS
2.1 Existing System 02
2.1.1 Disadvantages of the Existing System 02
2.2 Proposed System 03
2.2.1 Advantages of the Proposed System 03
3 SYSTEM CONFIGURATION
3.1 Hardware specification 03
3.2 Software specification 04
3.2.1 Front end 04
3.2.2 Back end 13
4 SYSTEM DESIGN AND DEVELOPMENT
4.1 Input Design 18
4.2 Output Design 20
4.3 Database Design 21
4.3.1 Data Flow Diagram 25
4.3.2 Entity Relationship Diagram 26
4.3.3 Class Diagram 28
4.3.4 Sequence Diagram

5 SYSTEM TESTING AND IMPLEMENTATION

5.1 System Testing 29
5.2 System Implementation 33
5.3 Project Life Cycle 34
6 CONCLUSION 36
7 FUTURE SCOPE OF THE PROJECT 37
8 BIBLIOGRAPHY 38
9 APPENDIX

9.1 Output 39
9.2 Source Code
44
 Synopsis

Introduction

The project Attendance Management System has been developed for World User for android
market and college user. The Application is mainly focused on College Administration in mobile
application.
It helps the users to maintain theirs various details. The main advantage of using this application
is it reduces the time of generating time table to all over the classes and staff’s details are maintained.
The process in this project is to be organized to College Staff and Subject, Class batch wise, And Also
Maintained by Student Attendance details organized by staff directly Responsibility of the vision of my
captured Student details, Class based Attendance hour wise organized mobile application. The Project
Coding is based Several Tools is used to develop the this mobile application (java jdk ) are so well
connected that the protect resembles to the computerization of the Web services operation of the firm.
The database design and coding techniques has highly enhanced and optimized. This makes the
application an overall user friendly and easy for naive users.
The tools constitutes Android SDK development, Java Jdk ,Eclipse in mobile applications
which will be displayed when authorized person uses the software and developed on Linux
environment which is platform dependent in mobility application. The back end tool constitutes Sql lite
database and developed on windows environment which is platform independent.

It helps the clients to keep up theirs different points of interest. The principle favorable position of
utilizing this application is it decreases the season of producing time table to everywhere throughout the
classes and staff's subtle elements are kept up. The procedure in this undertaking is to be sorted out to
College Staff and Subject and Class cluster savvy ,And Also Maintained by Student Attendance subtle
elements composed by staff specifically Responsibility of the vision of my caught Student points of
interest ,Class based Attendance hour wise, Staff login maintained Timetable vision For Staff wise
Generated Report displayed and Class ,Department Wise Reports are displayed based on User Login
Preference’s composed versatile application

1 | Page
Problem Statement

Educational institutions and workplaces often struggle with managing attendance using traditional
methods, such as paper registers or manual digital entries. These methods are time-consuming, prone to
human error, and inconvenient, leading to inefficiencies in tracking attendance and maintaining records.
There is a pressing need for a modern, automated solution that simplifies attendance management,
reduces errors, and saves time. The proposed solution is to develop an Attendance App that automates
the process of recording attendance, enhances accuracy, and provides real-time reporting. This app aims
to be user-friendly for both administrators and attendees and integrate seamlessly with existing systems.
Key features of the app include secure user authentication to ensure data privacy, QR code scanning for
quick and easy attendance marking, and an optional facial recognition feature for hands-free attendance.
The app will also provide real-time data synchronization to keep attendance records up-to-date and
notifications to alert attendees about missed sessions or the need to confirm their attendance.
Additionally, the app will offer comprehensive reporting and analytics, giving administrators valuable
insights into attendance patterns and trends. Multi-platform support will ensure accessibility across iOS,
Android, and web browsers, while an offline mode will allow attendance to be recorded without internet
connectivity and synced later. The development of this Attendance App addresses several challenges,
including data security, the accuracy of recognition technologies, and compatibility with various
existing systems. By automating and streamlining the attendance tracking process, the app will
significantly reduce manual effort and errors, enhance efficiency, and provide a seamless user
experience. Success will be measured by the reduction in time spent on attendance management,
decreased attendance-related errors, positive user feedback, and successful integration with institutional
systems. This Attendance App represents a significant advancement in attendance management,
promising to improve administrative efficiency and data accuracy.

Objectives

The objective of developing an Attendance App is to create a modern, automated solution that
revolutionizes attendance management for educational institutions and workplaces. Traditional methods,
such as paper registers or manual digital entries, are fraught with inefficiencies, including time
consumption, human error, and inconvenience, leading to inaccurate and incomplete attendance records.
This app aims to streamline the process of recording attendance, ensuring greater accuracy and saving
valuable time for both administrators and attendees. By integrating secure user authentication, the app
will protect sensitive data and provide a safe environment for users. QR code scanning will facilitate

2 | Page
quick and efficient attendance marking, while an optional facial recognition feature will offer a hands-
free alternative, enhancing convenience and minimizing contact. Real-time data synchronization will
ensure that attendance records are always up-to-date, allowing administrators to access accurate
information instantly. The app will also send automated notifications to attendees about missed sessions
or the need to confirm their attendance, improving communication and accountability. Comprehensive
reporting and analytics will provide administrators with valuable insights into attendance patterns and
trends, aiding in better decision-making and resource allocation. With support for multiple platforms,
including iOS, Android, and web browsers, the app will be accessible to a wide range of users, ensuring
flexibility and ease of use. An offline mode will enable attendance recording even without internet
connectivity, with data syncing once connectivity is restored. The app aims to address critical challenges
such as data security, accuracy of recognition technologies, and compatibility with existing systems. By
automating and optimizing the attendance tracking process, the app will reduce manual effort and errors,
enhance operational efficiency, and deliver a seamless user experience. The success of this initiative will
be measured by the reduction in time spent on attendance management, decreased errors, positive user
feedback, and successful integration with institutional systems, ultimately transforming attendance
management into a more efficient and accurate process.

Scope

The scope of the Attendance App encompasses developing a comprehensive solution to

streamline attendance tracking and management for educational institutions and workplaces.
The app will feature secure user authentication to protect sensitive data and ensure authorized
access.Real-time data synchronization will maintain up-to-date records, enabling
administrators to access accurate information instantly. The app will include automated
notifications to alert attendees about missed sessions or the need to confirm their attendance,
enhancing communication and accountability.The app will be designed for multi-platform
support, including iOS, Android. An offline mode will allow attendance recording without
internet connectivity, with data syncing when the connection is restored. The app will address
challenges such as data security, accuracy of recognition technologies, and compatibility with
existing systems. By automating and optimizing the attendance process, the app aims to
reduce manual effort and errors, enhance efficiency, and deliver a seamless user experience,
ultimately transforming attendance management into a more efficient and accurate process.

3 | Page
System Design

The system design for the Attendance App includes a multi-tier architecture encompassing
user interfaces, application logic, and a centralized database. The user interface will be developed for
multiple platforms, including iOS, Android, and web browsers, ensuring broad accessibility. The app
will utilize secure user authentication protocols to protect sensitive data and ensure authorized access.
System Testing and Implementation

Additionally, the app will include an offline mode, allowing attendance recording without
internet connectivity, with data syncing once the connection is restored. Ensuring data security,
accuracy of recognition technologies, and compatibility with existing systems will be key
considerations. This system design aims to automate and optimize attendance management,
enhancing efficiency and accuracy while providing a seamless user experience.

System Testing

The system coding and testing phase represents a critical stage in the development of our
meticulously designed website, which serves as a centralized hub for college activities and
administrative tasks. During this phase, the development team translates the conceptual design and
functional requirements into actual code, implementing features such as project information
dissemination, batch division, and seamless communication among stakeholders. This process
involves writing and debugging software code, adhering to coding standards and best practices to
ensure robustness and maintainability. Additionally, comprehensive testing procedures are carried out
to validate the functionality, reliability, and performance of the system. This includes unit testing,
integration testing, and system testing, where different modules and components are evaluated
individually and collectively to identify and rectify any defects or discrepancies. Through rigorous
coding and testing efforts, we aim to deliver a high-quality web application that optimizes student
project management and administrative tasks, providing substantial benefits to both students and
college authorities.
During the coding phase, developers translate the system design and requirements into
executable code, implementing the functionalities and features outlined in the system specifications.
This involves writing code in programming languages such as Java, Python, or JavaScript, depending
on the technology stack chosen for the development of the system. Developers adhere to coding
standards and best practices to ensure readability, maintainability, and scalability of the codebase.

4 | Page
 Additionally, they may leverage frameworks, libraries, and third-party APIs to expedite development
and enhance system functionality.Once the coding phase is complete, the system undergoes rigorous
testing to identify and rectify any defects or issues before deployment.
Testing encompasses various levels, including unit testing, integration testing, system testing,
and acceptance testing, each focusing on different aspects of the system's functionality and
performance. Unit testing involves testing individual components or modules in isolation to verify
their correctness. Integration testing validates the interactions between different modules to ensure
they work together seamlessly. System testing evaluates the system as a whole, validating its
compliance with requirements and assessing its overall functionality. Finally, acceptance testing
involves validating the system against user requirements and obtaining feedback from stakeholders to
ensure it meets their needs and expectations.

System Implementation

The implementation of our website, serving as a centralized hub for college activities and
administrative tasks, begins with setting up the necessary software development environment. This
includes configuring integrated development environments (IDEs), version control systems, and
project management tools to facilitate efficient collaboration among team members. Frontend
development follows, where the user interface (UI) components are created using HTML, CSS, and
JavaScript, translating design mockups into functional elements.
Concurrently, backend development focuses on implementing server-side logic and database
management using programming languages like Python or Java, and database systems such as
MySQL or MongoDB. Once frontend and backend components are developed, they are integrated to
enable seamless interaction between UI and server-side functionality, incorporating features like
project information dissemination, batch division, and communication tools. This phase involves
coding, configuration, and integration of various system components, modules, and functionalities.
Developers utilize programming languages, frameworks, and tools to build the system's
architecture, user interfaces, and backend logic according to the established design principles and
requirements. Additionally, database systems are set up and configured to store and manage the
system's data effectively. Throughout the implementation process, adherence to coding standards,
version control practices, and continuous integration techniques ensures the integrity and
maintainability of the codebase furthermore, implementation encompasses deployment, where the
developed system is deployed to production environments for use by end-users.

5 | Page
Project Life Cycle

1. Initiation: Defining project scope and objectives.

2. Planning: Developing detailed project plans and schedules.
3. Execution: Developing the game according to the plan.
4. Testing: Conducting thorough testing to ensure quality.
5. Deployment: Implementing the game and transitioning it to users.
6. Maintenance: Providing ongoing support and updates.

Conclusion

In concluding our online grievance redressal system project, it's evident that we've taken a
significant step towards promoting transparency, accountability, and stakeholder satisfaction. By
leveraging digital technologies to streamline the grievance handling process, we've empowered
individuals to voice their concerns easily and receive timely resolutions. Throughout this project,
we've prioritized user experience, ensuring that the platform is intuitive, accessible, and responsive to
diverse needs. By implementing robust mechanisms for tracking grievances, assigning
responsibilities, and monitoring progress, we've established a foundation for efficient and effective
grievance management.
Looking ahead, the success of our online grievance redressal system will depend on continued
engagement, feedback, and adaptation. We must remain vigilant in addressing emerging challenges,
refining processes, and incorporating technological advancements to enhance the system's
functionality and relevance. Ultimately, our goal is not only to resolve grievances but also to foster
trust, collaboration, and constructive dialogue within our community or organization. By embracing
innovation and a commitment to continuous improvement, we can ensure that our online grievance
redressal system remains a cornerstone of integrity and accountability for years to come.

6 | Page
Future Scope

Looking towards the future, several enhancements can be implemented to further improve our online
grievance redressal system:
 Implementing artificial intelligence (AI) and chatbots can automate initial grievance intake,
provide instant responses to common queries, and escalate complex issues to human agents
when necessary. This would streamline the process, reduce response times, and enhance user
satisfaction.
 Introducing multilingual support for the platform can cater to a more diverse user base and
ensure that individuals from different linguistic backgrounds can access and navigate the
system with ease.
 Incorporating advanced data analytics capabilities can provide insights into trends, patterns,
and recurring issues. This data-driven approach can enable proactive identification of
systemic
 Strengthening security measures such as encryption, multi-factor authentication, and regular
security audits can safeguard sensitive information and ensure the integrity of the grievance
redressal process. This is particularly crucial for maintaining trust and compliance with data
protection regulations.
 Establishing integrations with external platforms such as social media channels, email
services, or customer relationship management (CRM) systems can facilitate seamless
communication and data exchange, enabling swift resolution of grievances and better
coordination with relevant stakeholders.
 Implementing feedback mechanisms and conducting regular user satisfaction surveys can
provide valuable insights into the effectiveness of the grievance redressal system. This
feedback loop will enable continuous improvement based on user input and evolving needs.
 This will promote inclusivity and broaden the reach of the grievance redressal system. This
feedback loop will enable continuous improvement based on user input and evolving needs.
 Integrations with external platforms such as social media channels, email services, or
customer relationship management systems can facilitate seamless communication and data
exchange, enabling swift resolution of grievances and better coordination with relevant
stakeholders.
 With Multilingual support for the platform can cater to a more diverse user base and ensure
that individuals from different linguistic backgrounds can access and navigate the system with

7 | Page
 ease. This will promote inclusivity and broaden the reach of the grievance redressal system.
 This data-driven approach can enable proactive identification of systemic problems, informed
decision-making, and targeted interventions to address underlying issues effectively.

INTRODUCTION

1.1 About the project

An online grievance redressal system is an essential project for any college aiming to
enhance transparency and efficiency in addressing student concerns. By implementing
such a system, colleges can streamline the process of lodging, tracking, and resolving
grievances, thereby fostering a conducive environment for learning and development.
This project encompasses the development of a user- friendly web-based platform that
allows students to submit grievances, track their status, and receive timely updates on
the resolution process The primary objective of this project is to provide a centralized
platform where students can voice their grievances regarding various aspects of college
life, including academics, infrastructure, and administration.

Through the online grievance redressal system, students can submit their complaints
securely and confidentially, ensuring that their concerns are addressed promptly and

8 | Page
effectively. Additionally, the system facilitates communication between students and
college authorities, promoting accountability and responsiveness in addressing
grievances By leveraging technology to automate the grievance redressal process,
colleges can streamline administrative tasks and allocate resources more efficiently.
Moreover, the implementation of an online grievance redressal system demonstrates the
institution's commitment to promoting transparency, accountability, and student
welfare. Overall, this project not only enhances the college's reputation but also
contributes to creating a supportive and conducive environment for all stakeholders
involved.

This project encompasses the development of a user- friendly web-based platform that
allows students to submit grievances, track their status, promoting accountability and
responsiveness in addressing grievances By leveraging technology to automate the
grievance redressal process, colleges can streamline administrative tasks and allocate
resources more efficiently. Moreover, online grievance redressal systems often feature
automated workflows and escalation mechanisms, which facilitate prompt resolution of
issues.

One of the key advantages of online grievance redressal systems is their ability to
enhance transparency and accountability in addressing public concerns. Through these
platforms, users can submit their grievances along with supporting documents, ensuring
a clear record of complaints and resolutions. This transparency fosters trust between
citizens and authorities, as it allows for scrutiny and monitoring of the grievance
resolution process. Moreover, online grievance redressal systems often feature
automated workflows and escalation mechanisms, which facilitate prompt resolution of
issues. Upon submission, grievances are routed to the relevant authorities or
departments, reducing delays and bureaucratic hurdles. Additionally, these systems can
prioritize urgent matters and marginalized or remote communities who may face
barriers to accessing traditional grievance mechanisms

Furthermore, online grievance redressal systems facilitate greater transparency and

accountability in government operation through these platforms, citizens can track the

9 | Page
status of their complaints in realtime, ensuring visibility into the redressal process.
Additionally, authorities can analyze data collected through these systems to identify
recurring issues, improve service delivery, and enhance governance practices. Overall,
online grievance redressal systems play a vital role in promoting citizen engagement,
enhancing public trust, and fostering responsive governance in the digital age.

10 | Page
 2 SYSTEM STUDY AND ANALYSIS

2.1 Existing System

The current state of online grievance redressal systems presents several challenges and
shortcomings.
Firstly, many existing systems lack comprehensive integration and integrity with organizational
databases and processes, leading to inefficiencies and duplication of efforts. This disjointed approach
often results in delays in addressing, grievances and fails to provide a seamless user experience.
Moreover, limited accessibility remains a significant issue, as certain demographics face barriers such as
inadequate internet access or digital literacy, hindering their ability to utilize online grievance redressal
platform effectively.
Secondly, bureaucratic hurdles and procedural complexities contribute to the sluggishness of
grievance redressal processes. Lengthy approval chains, convoluted workflows, and excessive paperwork
create bottlenecks that impede the timely resolution of complaints. This bureaucratic inertia not only
frustrates complainants but also erodes trust in the efficacy and responsiveness of the system
Furthermore, the lack of transparency exacerbates these concerns, as many systems fail to provide clear
visibility into the status of complaints, the actions taken by the authorities, and the decision-making
rationale, fostering perceptions of opacity and arbitrariness.
Lastly, inadequate feedback mechanisms undermine the ability of grievance redressal systems to
evolve and improve over time. Without robust mechanisms for soliciting, analyzing, and acting upon user
feedback, organizations miss valuable opportunities to identify systemic issues, address user concerns,
and enhance the overall effectiveness of the system. This deficiency in feedback loops perpetuates a cycle
of inefficiency and dissatisfaction, further undermining the credibility and trustworthiness of online
grievance redressal mechanisms.

2.1.1 Disadvantages of the Existing System

Insufficient Transparency:
 Transparency is crucial for fostering trust and accountability in grievance redressal mechanisms.
Limited Accessibility:
 Despite the availability of online platforms, accessibility remains a significant challenge for
certain demographics, including those with limited internet access, digital literacy, or disabilities.
11 | Page
  Time-consuming process.
Lack of Integration:
In many cases, online grievance redressal systems are not fully integrated with other organizational
databases or systems.

2.1 PROPOSED SYSTEM

"Mastery Maze" is designed to address the shortcomings of traditional educational methods and
existing educational games. It aims to provide an engaging, interactive, and comprehensive
learning experience for students pursuing a Bachelor of Computer Applications (BCA). By
integrating game-based learning, interactive puzzles, and AI-powered teaching, the proposed
system enhances understanding, retention, and practical application of core BCA subjects.

2.2.1 Advantages of the Proposed System

1. Active Learning:
○ Interactive Gameplay: Students actively participate in the learning process through
interactive gameplay, which enhances engagement and motivation.
○ Problem-Solving: The game includes puzzles and challenges that require critical
thinking and problem-solving, promoting a deeper understanding of concepts.
2. Enhanced Retention:
○ Reinforcement Learning: Players receive rewards and feedback, which reinforce
learning and improve retention of information.
○ Contextual Learning: Concepts are taught in a contextual manner, helping students
understand and remember the material better.
3. Practical Application:
○ Real-World Scenarios: The game includes practical exercises and real-world
scenarios that allow students to apply their knowledge in a meaningful way.
○ Hands-On Experience: Students gain hands-on experience through interactive
puzzles and challenges, bridging the gap between theory and practice.

12 | Page
 4. System Configuration

To address the limitations of existing online grievance redressal systems, a proposed solution must focus
on integration, accessibility, transparency, efficiency, and user feedback mechanisms Firstly, a centralized
and fully integrated online grievance redressal system would streamline the process by connecting various
organizational databases.This seamless integration would enable authorities to track complaints in real
time, allocate resources efficiently, and coordinate responses effectively, thereby enhancing the overall
responsiveness.
Secondly, the proposed system should prioritize accessibility by ensuring compatibility with
diverse devices, browsers, and assistive technologies. By designing user- friendly interfaces, providing
multilingual support, and offering alternative channels for submission, such as phone hotlines or physical
kiosks, the system would cater to the needs of diverse demographics, including those with limited internet
access or digital literacy. This inclusive approach would empower marginalized communities to
participate in the grievance redressal process, fostering equity and social justice.
Thirdly, transparency is paramount for building trust and accountability in grievance redressal
mechanisms. The proposed system would enhance transparency by providing stakeholders with clear
visibility into the status of complaints, the actions taken by authorities, and the decision-making process.
Through comprehensive dashboards, automated notifications, and publicly accessible reports, users
would have greater confidence in the fairness impartiality, and integrity of the system, thereby
strengthening public trust and engagement.
Fourthly, the proposed system would prioritize efficiency by automating routine tasks,
streamlining workflows, and reducing bureaucratic hurdles. By implementing intelligent case
management algorithms, prioritization criteria. The system would ensure that complaints are promptly
routed to the appropriate authorities and resolved in a timely manner. This inclusive approach would
empower marginalized communities to participate in the grievance redressal process, fostering equity and
social justice.
The proposed system advantages are-

Enhances Accessibility:
By offering multiple channels for submitting complaints and ensuring compatibility with various
devices and assistive technologies, the system will enhance accessibility, allowing a broader range of
users to participate in the grievance redressal process. Improved data storage, organization, and security

13 | Page
 for enhanced data integrity.
Streamlined process:
 The proposed online grievance redressal system will streamline.
 The process of submitting and managing complaints.
 The reducing bureaucratic hurdles.
 The technologies and the system will enhance accessibility
Transparency and Accountability:
Real time updates and transparent reporting will provide stakeholders with clear visibility into the
status of their complaints and the actions taken by authorities, fostering trust and accountability in the
grievance redressal process.
Improved Efficiency:
Automation and intelligent algorithms will optimize workflow management, ensuring that complaints are
promptly routed to the appropriate authorities and resolved in a timely manner, thereby improving overall
efficiency.

3.1 Hardware Specification

Processor : Intel i3 and above Processor

RAM : 16GB
Hard Disk : 512 GB

1. Target Machines :
○ Processor: Intel Core i3 or AMD Ryzen 3 (or higher)
○ RAM: 4 GB (8 GB recommended)
○ Storage: HDD or SSD with at least 100 GB free space
○ Display: HD (1280x720) resolution (Full HD recommended)

14 | Page
 About Web Development

HTML:
HTML served as the backbone of our web application, providing the structural framework for
content presentation. Through semantic markup and proper element hierarchy, we ensured accessibility
and readability across various devices and browsers. HTML also allows for the creation of hyperlinks,
enabling users to navigate between different web pages or sections within a page. By using the <a> tag,
developers can define anchor points and link them to other documents or resources on the web.
Additionally, HTML supports the inclusion of multimedia content, forms for user input, and semantic
markup for improved accessibility and search engine optimization

CSS:
CSS played a pivotal role in enhancing the visual appeal and layout of our platform. By
implementing responsive design principles and leveraging CSS frameworks like Bootstrasp, we achieved
consistency in styling and layout, offering users a cohesive experience irrespective of their device or
screen size. One of the key features of CSS is its ability to apply styles to HTML elements selectively,
based on various criteria such as element type, class, ID, or hierarchical relationships. This allows
developers to target specific elements or groups of elements and customize their appearance according to
design requirements.
For example, CSS can be used to change the color and font size of headings (<h1>), style links (<a>), or
create responsive layouts that adapt to different screen sizes and devices.CSS also supports inheritance
and cascading, where styles applied to parent elements are inherited by their children, and conflicting
styles are resolved based on specificity and order of declaration. This enables developers to create
modular and maintainable stylesheets, where common styles can be defined once and reused across
multiple elements or pages.

JavaScript:
JavaScript was instrumental in adding interactivity and dynamic functionality to our web
application. From form validation to asynchronous data retrieval, JavaScript empowered us to create a
responsive and engaging user interface, facilitating seamless navigation and interaction. Moreover,
JavaScript facilitates client-side scripting, where code is executed within the user's web browser, reducing
the need for server-side processing and improving performance. With the advent of modern JavaScript

15 | Page
 frameworks and libraries such as React, Angular, and Vue.js, developers can build complex web

applications more efficiently, leveraging reusable components and modular code.Additionally, JavaScript
is increasingly being used beyond the browser environment, with frameworks like Node.js enabling server-
side development, allowing developers to build full-stack applications using JavaScript across both client
and server layers. This ecosystem expansion has led to the emergence of isomorphic or universal
JavaScript applications, where code can be shared between client and server, enhancing code reusability
and developer productivity.
Overall, JavaScript is a powerful and versatile programming language that empowers developers
to create rich, interactive, and responsive web applications, driving innovation and creativity on the
modern web. Its widespread adoption and continuous evolution make it an essential skill for web
developers seeking to build dynamic and engaging online experiences.
Bootstrap:
Bootstrap emerged as a cornerstone in expediting front-end development and ensuring cross
browser compatibility. By leveraging Bootstrap's extensive component library and grid system, we
expedited the UI development process, while adhering to responsive design principles for optimal user
experience across devices. Moreover, Bootstrap includes a wide range of reusable UI components such as
buttons, forms, navigation bars, dropdowns, and modals, which can be easily customized and integrated
into web applications. These components follow best practices in web design and accessibility, providing
a consistent and user-friendly experience for website visitors.Additionally, Bootstrap offers extensive
documentation.
For examples, and starter templates to help developers get started quickly and efficiently. Its modular and
scalable architecture allows developers to customize and extend the framework according to their project
requirements, ensuring flexibility and maintainability in the long run.Overall, Bootstrap is a valuable tool
for web developers, offering a robust foundation for building responsive and mobile-friendly web
applications with ease. Its popularity and widespread adoption make it a go-to choice for developers
looking to streamline their development process and deliver high-quality user experiences on the web
applications more efficiently, leveraging reusable components and modular code.Additionally, JavaScript
is increasingly being used beyond the browser environment, with frameworks like Node.js enabling
server- side development, allowing developers to build full-stack applications using JavaScript across
both client and server layers. This ecosystem expansion has led to the emergence of isomorphic or
universal JavaScript applications, where code can be shared between client and server, enhancing code
reusability and developer productivity.
Overall, JavaScript is a powerful and versatile programming language that empowers developers

16 | Page
to create rich, interactive, and responsive web applications, driving innovation and creativity on the
modern web. Its widespread adoption and continuous evolution make it an essential skill for web
developers seeking to build dynamic and engaging online experiences.
PHP:
PHP formed the backbone of our server-side logic, enabling dynamic content generation and
database interactions. Leveraging PHP frameworks and libraries, we implemented robust authentication
mechanisms, data processing functionalities, and server-side validation, ensuring data integrity and
security throughout the platform. PHP is a server-side language, meaning that PHP code is executed on
the server before being sent to the client's web browser. This provides greater security for sensitive
operations such

17 | Page
1. System Design and Development

System design for an online grievance redressal system involves the process of conceptualizing and
structuring the components, functionalities, and interactions of the system to effectively address
user grievances in a digital environment. This phase of development lays the foundation for the
implementation of the system, defining its architecture, user interfaces, databases, and integration
with other systems. By carefully designing the system, developers aim to ensure its usability,
reliability, scalability, and security while meeting the specific requirements and objectives of
grievance redressal processes. This section will outline the key considerations and principles
guiding the design of an online grievance redressal system to optimize its effectiveness and user
experience.
The system design process begins with a thorough analysis of requirements gathered from
stakeholders, including complainants, administrators, and regulatory bodies, to understand their
needs and expectations. Based on these requirements, the system architecture is conceptualized,
encompassing various components such as the user interface, database management, workflow
automation, and reporting mechanisms. The design also considers factors such as scalability,
security, and compliance with relevant regulations to ensure the system's robustness and integrity.
Moreover, the user experience is a key focus of the system design, with emphasis placed on
creating intuitive interfaces, clear navigation pathways, and accessible features to accommodate
users with diverse backgrounds and technological proficiencies. Iterative prototyping and usability
testing are employed to refine the design and address any usability issues or pain points identified
by users. Ultimately, the system design serves as the foundation for the development and
implementation phases, guiding the creation of a comprehensive Online Grievance Redressal
System that meets the needs of its stakeholders while promoting transparency, accountability, and
trust in the grievance resolution process.

18 | Page
 4.3 Database Design

Database design involves structuring data to ensure efficient storage and retrieval. Key
aspects include:

4.3.1 Data Flow Diagram (DFD)

A Data Flow Diagram illustrates how data moves through the system. Key components
include:

● Entities: Players, Game Levels

● Processes: game progress tracking, puzzle solving, hint generation
● Data Stores: Player profiles, game state
● Data Flows: Input commands, game state updates, feedback

DFD LEVEL 0:

4.3.2 Entity Relationship Diagram (ERD)

19 | Page
An Entity Relationship Diagram maps out the relationships between different entities in the
database:

● Entities: Player, GameLevel, Puzzle

● Relationships:
○ A Player interacts with multiple GameLevels
○ Each GameLevel contains multiple Puzzles

4.3.3 Class Diagram

A Class Diagram provides a blueprint of the system’s classes and their relationships:

● Classes: Player, GameLevel, Puzzle, UI

● Attributes: Player (name, score, progress), GameLevel (level number, difficulty),
Puzzle (question, options, correct answer), UI (display elements)
● Methods: Player (login, answerPuzzle), GameLevel (loadLevel, saveProgress), Puzzle
(checkAnswer, provideHint)

4.3.4 Use Case Diagram

A Use Case Diagram outlines the interactions between users and the system:

● Actors: Player, Administrator

● Use Cases:
○ Player: Register, Login, Select Game Mode, Navigate Maze, Solve Puzzle,
Receive Hint, View Progress
○ Administrator: Manage Content, Update Game, View Statistics

4.3.5 Sequence Diagram

A Sequence Diagram shows the order of operations in a particular scenario:

20 | Page
 ● Scenario: Solving a puzzle
○ Player selects puzzle
○ System presents puzzle
○ Player submits answer
○ System checks answer
○ System provides feedback (correct/incorrect)
○ Player views hint

5. System Testing and Implementation

5.1 System Testing

System testing ensures the game functions correctly and meets user requirements. Types of
testing include:

● Unit Testing: Testing individual components (e.g., puzzle logic, AI hints)

● Integration Testing: Ensuring components work together (e.g., AI hint generation
during gameplay)
● System Testing: Testing the complete system in a simulated environment
● User Acceptance Testing (UAT): Gathering feedback from real users to validate the
game’s functionality and usability

5.2 System Implementation

System implementation involves deploying the game for use:

21 | Page
 ● Deployment Plan:
○ Preparation: Setting up servers, databases, and necessary infrastructure
○ Installation: Deploying the game on target machines
○ Configuration: Setting up initial game settings and user accounts
○ Training: Providing documentation and training for users and administrators

5.3 Project Life Cycle

The project life cycle includes the following phases:

● Initiation: Defining project scope and objectives

● Planning: Developing detailed project plans, schedules, and resource allocations
● Execution: Developing the game according to the plan, with continuous monitoring
and control
● Testing: Conducting thorough testing to ensure quality
● Deployment: Implementing the game and transitioning it to users
● Maintenance: Providing ongoing support and updates based on user feedback

6. Conclusion

22 | Page
The 3D Quiz Game project aimed to blend educational content with an interactive gaming
experience to create a compelling platform for learning. By employing the Godot Engine, the
project showcases how game development can be used to enhance educational tools.

The game leverages 3D graphics and a dungeon setting to create an immersive environment,
increasing engagement compared to traditional educational tools and making learning more
enjoyable. The focus on aptitude questions related to basic programming and data structures
and algorithms (DSA) effectively reinforces academic concepts through repeated interaction
and practice. Players must solve at least five questions to advance through levels, providing a
clear goal and incentive for learning. The immediate feedback system for incorrect answers
encourages players to learn from their mistakes and try again, reinforcing knowledge
retention.

Utilizing the Godot Engine and GD Script, the project demonstrates the effective use of
modern game development tools. The game architecture includes well-defined components
for question management, user interaction, and game state control. The game underwent
rigorous testing, including unit testing, integration testing, and user testing. Feedback from
playtesters was used to refine the game mechanics and improve the overall user experience.

One of the primary challenges was maintaining a balance between educational content and
engaging gameplay. The project addressed this by designing questions that were challenging
yet approachable and integrating them seamlessly into the game mechanics. Developing a 3D
game with interactive elements posed several technical challenges, which were overcome
through iterative development, extensive testing, and continuous learning and application of
best practices in game development.

The project provided a deep dive into the Godot Engine, enhancing skills in game
development, 3D modeling, and scripting. Understanding the principles of educational game
design and applying them effectively was a significant learning outcome. The project
highlighted the importance of user engagement, feedback mechanisms, and content
integration in educational tools.

7. Future Scope of the Project

23 | Page
Future enhancements could include:

● Expanding Subject Coverage: Including additional subjects beyond BCA

● Advanced AI Features: Implementing more sophisticated AI techniques for
personalized learning
● Multiplayer Mode: Allowing students to collaborate and compete with peers
● Mobile Version: Developing a mobile version of the game for broader accessibility
● Continuous Updates: Regularly updating content and features based on user feedback
and advancements in educational technology

24 | Page
 8. Bibliography

Websites:

● Godot Engine Documentation, docs.godotengine.org.

● Stack Overflow, "Game Development Questions," stackoverflow.com.
● "Blender 3D Modeling and Animation," blender.org.

Educational Platforms:

● Udemy, "Complete Godot Developer 4.0," udemy.com.

Online Tutorials and Videos:

● YouTube, "Godot Engine Tutorials," youtube.com.

● "Blender Guru," Blender tutorials, youtube.com/user/AndrewPPrice.
● GDQuest, "Godot Tutorials," gdquest.com.

Software and Tools:

● Godot Engine, godotengine.org.

● Blender, blender.org.
● GitHub, "Version Control and Collaboration," github.com.

9. Appendix

9.1 Output:
25 | Page
26 | Page
27 | Page
28 | Page
29 | Page
30 | Page
31 | Page
32 | Page
33 | Page
9.2 Source Code:

Player.gd:

extends CharacterBody3D
class_name Player
@onready var minimap_camera
=$"../SubViewportContainer/SubViewport/MiniMapCam"
@onready var portal=$"../Protal"
@export var spawn_areas_container: Node3D

# TODO: Add descriptions for each value

#@export var portal_scene: PackedScene
@export_category("Character")
@export var base_speed : float = 3.0
@export var sprint_speed : float = 6.0
@export var crouch_speed : float = 1.0

@export var acceleration : float = 10.0

@export var jump_velocity : float = 4.5
@export var mouse_sensitivity : float = 0.1
@export var immobile : bool = false
@export_file var default_reticle

@export_group("Nodes")
@export var HEAD : Node3D
@export var CAMERA : Camera3D

34 | Page
@export var HEADBOB_ANIMATION : AnimationPlayer
@export var JUMP_ANIMATION : AnimationPlayer
@export var CROUCH_ANIMATION : AnimationPlayer
@export var COLLISION_MESH : CollisionShape3D

@export_group("Controls")
# We are using UI controls because they are built into Godot Engine so they can be
used right away
@export var JUMP : String = "ui_accept"
@export var LEFT : String = "ui_left"
@export var RIGHT : String = "ui_right"
@export var FORWARD : String = "ui_up"
@export var BACKWARD : String = "ui_down"
@export var PAUSE : String = "ui_cancel"
@export var CROUCH : String = "crouch"
@export var SPRINT : String = "sprint"
@export_group("Feature Settings")
@export var jumping_enabled : bool = true
@export var in_air_momentum : bool = true
@export var motion_smoothing : bool = true
@export var sprint_enabled : bool = true
@export var crouch_enabled : bool = true
@export_enum("Hold to Crouch", "Toggle Crouch") var crouch_mode : int = 0
@export_enum("Hold to Sprint", "Toggle Sprint") var sprint_mode : int = 0
@export var dynamic_fov : bool = true
@export var continuous_jumping : bool = true
@export var view_bobbing : bool = true
@export var jump_animation : bool = true

35 | Page
@export var pausing_enabled : bool = true

# Member variables
var speed : float = base_speed
var current_speed : float = 0.0
# States: normal, crouching, sprinting
var state : String = "normal"
var low_ceiling : bool = false # This is for when the cieling is too low and the player
needs to crouch.
var was_on_floor : bool = true
var correct_answer_count = 0
var death_count = 0

var RETICLE : Control

# Get the gravity from the project settings to be synced with RigidBody nodes
var gravity : float = ProjectSettings.get_setting("physics/3d/default_gravity") # Don't
set this as a const, see the gravity section in _physics_process
#signal
# Declare the signal

func _ready():
Input.mouse_mode = Input.MOUSE_MODE_CAPTURED

HEAD.rotation = rotation
rotation = Vector3.ZERO

if default_reticle:
change_reticle(default_reticle)

36 | Page
 # Reset the camera position
HEADBOB_ANIMATION.play("RESET")
JUMP_ANIMATION.play("RESET")
CROUCH_ANIMATION.play("RESET")

check_controls()
randomize()

func check_controls(): # If you add a control, you might want to add a check for it here.
if !InputMap.has_action(JUMP):
push_error("No control mapped for jumping. Please add an input map control.
Disabling jump.")
jumping_enabled = false
if !InputMap.has_action(LEFT):
push_error("No control mapped for move left. Please add an input map
control. Disabling movement.")
immobile = true
if !InputMap.has_action(RIGHT):
push_error("No control mapped for move right. Please add an input map
control. Disabling movement.")
immobile = true
if !InputMap.has_action(FORWARD):
push_error("No control mapped for move forward. Please add an input map
control. Disabling movement.")
immobile = true
if !InputMap.has_action(BACKWARD):
push_error("No control mapped for move backward. Please add an input map
control. Disabling movement.")
immobile = true
37 | Page
 if !InputMap.has_action(PAUSE):
push_error("No control mapped for move pause. Please add an input map
control. Disabling pausing.")
pausing_enabled = false
if !InputMap.has_action(CROUCH):
#push_error("No control mapped for crouch. Please add an input map control.
Disabling crouching.")
crouch_enabled = false
if !InputMap.has_action(SPRINT):
#push_error("No control mapped for sprint. Please add an input map control.
Disabling sprinting.")
sprint_enabled = false

func change_reticle(reticle):
if RETICLE:
RETICLE.queue_free()

RETICLE = load(reticle).instantiate()
RETICLE.character = self
$UserInterface.add_child(RETICLE)

func _physics_process(delta):
current_speed = Vector3.ZERO.distance_to(get_real_velocity())
$UserInterface/DebugPanel.add_property("Speed", snappedf(current_speed, 0.001),
1)
#$UserInterface/DebugPanel.add_property("Target speed", speed, 2)
var cv : Vector3 = get_real_velocity()

38 | Page
 var vd : Array[float] = [
snappedf(cv.x, 0.001),
snappedf(cv.y, 0.001),
snappedf(cv.z, 0.001)
]
var readable_velocity : String = "X: " + str(vd[0]) + " Y: " + str(vd[1]) + " Z: " +
str(vd[2])
#$UserInterface/DebugPanel.add_property("Velocity", readable_velocity, 3)

# Gravity
#gravity = ProjectSettings.get_setting("physics/3d/default_gravity") # If the gravity
changes during your game, uncomment this code
if not is_on_floor():
velocity.y -= gravity * delta

handle_jumping()

var input_dir = Vector2.ZERO

if !immobile:
input_dir = Input.get_vector(LEFT, RIGHT, FORWARD, BACKWARD)
handle_movement(delta, input_dir)

low_ceiling = $CrouchCeilingDetection.is_colliding()

handle_state(input_dir)
if dynamic_fov:
update_camera_fov()

if view_bobbing:

39 | Page
 headbob_animation(input_dir)

if jump_animation:
if !was_on_floor and is_on_floor(): # Just landed
match randi() % 2:
0:
JUMP_ANIMATION.play("land_left", 0.25)
1:
JUMP_ANIMATION.play("land_right", 0.25)

was_on_floor = is_on_floor() # This must always be at the end of

physics_process

func handle_jumping():
if jumping_enabled:
if continuous_jumping:
if Input.is_action_pressed(JUMP) and is_on_floor() and !low_ceiling:
if jump_animation:
JUMP_ANIMATION.play("jump", 0.25)
velocity.y += jump_velocity
else:
if Input.is_action_just_pressed(JUMP) and is_on_floor() and !
low_ceiling:
if jump_animation:
JUMP_ANIMATION.play("jump", 0.25)
velocity.y += jump_velocity

40 | Page
func handle_movement(delta, input_dir):
var direction = input_dir.rotated(-HEAD.rotation.y)
direction = Vector3(direction.x, 0, direction.y)
move_and_slide()

if in_air_momentum:
if is_on_floor():
if motion_smoothing:
velocity.x = lerp(velocity.x, direction.x * speed, acceleration *
delta)
velocity.z = lerp(velocity.z, direction.z * speed, acceleration *
delta)
else:
velocity.x = direction.x * speed
velocity.z = direction.z * speed
else:
if motion_smoothing:
velocity.x = lerp(velocity.x, direction.x * speed, acceleration * delta)
velocity.z = lerp(velocity.z, direction.z * speed, acceleration * delta)
else:
velocity.x = direction.x * speed
velocity.z = direction.z * speed

func handle_state(moving):
if sprint_enabled:
if sprint_mode == 0:
if Input.is_action_pressed(SPRINT) and state != "crouching":
if moving:

41 | Page
 if state != "sprinting":
enter_sprint_state()
else:
if state == "sprinting":
enter_normal_state()
elif state == "sprinting":
enter_normal_state()
elif sprint_mode == 1:
if moving:
# If the player is holding sprint before moving, handle that
cenerio
if Input.is_action_pressed(SPRINT) and state == "normal":
enter_sprint_state()
if Input.is_action_just_pressed(SPRINT):
match state:
"normal":
enter_sprint_state()
"sprinting":
enter_normal_state()
elif state == "sprinting":
enter_normal_state()

if crouch_enabled:
if crouch_mode == 0:
if Input.is_action_pressed(CROUCH) and state != "sprinting":
if state != "crouching":
enter_crouch_state()
elif state == "crouching" and !$CrouchCeilingDetection.is_colliding():
enter_normal_state()

42 | Page
 elif crouch_mode == 1:
if Input.is_action_just_pressed(CROUCH):
match state:
"normal":
enter_crouch_state()
"crouching":
if !$CrouchCeilingDetection.is_colliding():
enter_normal_state()

# Any enter state function should only be called once when you want to enter that state,
not every frame.

func enter_normal_state():
#print("entering normal state")
var prev_state = state
if prev_state == "crouching":
CROUCH_ANIMATION.play_backwards("crouch")
state = "normal"
speed = base_speed

func enter_crouch_state():
#print("entering crouch state")
var prev_state = state
state = "crouching"
speed = crouch_speed
CROUCH_ANIMATION.play("crouch")

func enter_sprint_state():

43 | Page
 #print("entering sprint state")
var prev_state = state
if prev_state == "crouching":
CROUCH_ANIMATION.play_backwards("crouch")
state = "sprinting"
speed = sprint_speed

func update_camera_fov():
if state == "sprinting":
CAMERA.fov = lerp(CAMERA.fov, 85.0, 0.3)
else:
CAMERA.fov = lerp(CAMERA.fov, 75.0, 0.3)

func headbob_animation(moving):
if moving and is_on_floor():
var use_headbob_animation : String
match state:
"normal","crouching":
use_headbob_animation = "walk"
"sprinting":
use_headbob_animation = "sprint"

var was_playing : bool = false

if HEADBOB_ANIMATION.current_animation == use_headbob_animation:
was_playing = true

HEADBOB_ANIMATION.play(use_headbob_animation, 0.25)

44 | Page
 HEADBOB_ANIMATION.speed_scale = (current_speed / base_speed) * 1.75
if !was_playing:
HEADBOB_ANIMATION.seek(float(randi() % 2)) # Randomize the
initial headbob direction
# Let me explain that piece of code because it looks like it does the
opposite of what it actually does.
# The headbob animation has two starting positions. One is at 0 and the
other is at 1.
# randi() % 2 returns either 0 or 1, and so the animation randomly starts
at one of the starting positions.
# This code is extremely performant but it makes no sense.

else:
HEADBOB_ANIMATION.play("RESET", 0.25)
HEADBOB_ANIMATION.speed_scale = 1

func _process(delta):
$UserInterface/DebugPanel.add_property("FPS",
Performance.get_monitor(Performance.TIME_FPS), 0)
var status : String = state
if !is_on_floor():
status += " in the air"
#$UserInterface/DebugPanel.add_property("State", status, 4)
$UserInterface/DebugPanel.add_property("Correct Answers",
correct_answer_count,3)
#$UserInterface/DebugPanel.add_property("Death", death_count, 6)
if pausing_enabled:
if Input.is_action_just_pressed(PAUSE):
if Input.mouse_mode == Input.MOUSE_MODE_CAPTURED:
45 | Page
 Input.mouse_mode = Input.MOUSE_MODE_VISIBLE
elif Input.mouse_mode == Input.MOUSE_MODE_VISIBLE:
Input.mouse_mode = Input.MOUSE_MODE_CAPTURED

HEAD.rotation.x = clamp(HEAD.rotation.x, deg_to_rad(-90), deg_to_rad(90))

if correct_answer_count == 1 and not $"../SubViewportContainer".visible:

$"../SubViewportContainer".visible = true
if$"../SubViewportContainer".visible:
minimap_camera.global_transform.origin = global_transform.origin +
Vector3(0, 50, 0)# Adust offset as needed
if correct_answer_count == 2 and not $"../Protal".visible:
$"../Protal".visible = true

func die():
# Implement your player death logic here
print("Player died!")
death_count += 1
get_tree().call_group("QuizArea", "reset_quiz_area")

# For example:queue_free() # Remove the player node

# Or:

respawn()
#get_tree().reload_current_scene()

func respawn():
correct_answer_count = 0

46 | Page
 # Reset other player properties if needed
velocity = Vector3.ZERO
state = "normal"
speed = base_speed
# 1. Get all spawn areas from the container
var spawn_areas = spawn_areas_container.get_children()

# 2. Choose a random spawn area

var random_spawn_area = spawn_areas[randi() % spawn_areas.size()]

# 3. Get the chosen area's extents (rest of the code is the same as before)
var min_pos = random_spawn_area.global_transform.origin -
random_spawn_area.scale / 2
var max_pos = random_spawn_area.global_transform.origin +
random_spawn_area.scale / 2

# 4. Calculate random position within the chosen area

var random_x = randf_range(min_pos.x, max_pos.x)
var random_z = randf_range(min_pos.z, max_pos.z)
var new_position = Vector3(random_x, min_pos.y, random_z)

# 5. Set the player's new position

global_transform.origin = new_position
get_tree().call_group("QuizAreas", "reset_quiz")
# 4. Reset other player properties if needed
# (e.g., velocity, health, etc.)

47 | Page
func _unhandled_input(event):
if event is InputEventMouseMotion and Input.mouse_mode ==
Input.MOUSE_MODE_CAPTURED:
HEAD.rotation_degrees.y -= event.relative.x * mouse_sensitivity
HEAD.rotation_degrees.x -= event.relative.y * mouse_sensitivity

Area3d.gd:

extends Area3D

@export var quiz_ui: NodePath

@export var question_resource: QuestionData # Use the QuestionData resource type

var question_shown: bool = false

func _on_body_entered(body):
if body.is_in_group("Player") and not question_shown:
print("Player entered quiz area")
show_question()

func show_question():
if question_resource != null:
var quiz_ui_instance = get_node_or_null(quiz_ui)
if quiz_ui_instance:
quiz_ui_instance.set_question(
question_resource.question,
question_resource.answers,
question_resource.correct_answer
)
quiz_ui_instance.show_ui()
48 | Page
 question_shown = true
else:
print("Error: QuizUI node not found.")
else:
print("No question resource assigned")

func _on_body_exited(body):
if body.is_in_group("Player"):
print("Player exited quiz area")
var quiz_ui_instance = get_node_or_null(quiz_ui)
if quiz_ui_instance:
quiz_ui_instance.hide_ui()
Input.mouse_mode = Input.MOUSE_MODE_CAPTURED

func reset_quiz():
question_shown = false
func _ready():
if question_resource == null:
print("No question resource assigned.")
elif not (
question_resource.question != "" and
question_resource.answers.size() > 0 and
question_resource.correct_answer != ""
):
push_error("Question data is incomplete.")
add_to_group("QuizAreas")

49 | Page
QuizUI.gd:

extends Control

var question = ""

var answers = []
var correct_answer = ""

func set_question(new_question: String, new_answers: Array, new_correct_answer: String):

question = new_question
answers = new_answers
correct_answer = new_correct_answer

var question_label = $Panel.get_node_or_null("Label")

if question_label:
question_label.text = question

# Disconnect any existing signals and connect the new ones

for i in range(answers.size()):
var button = $Panel.get_node("Button" + str(i + 1))
button.text = answers[i]
button.disabled = false
if button.is_connected("pressed", Callable(self, "_on_button_1_pressed")):
button.pressed.disconnect(_on_button_1_pressed)
button.pressed.connect(_on_button_1_pressed.bind(i))

func show_ui():
self.visible = true

50 | Page
 self.set_focus_mode(FOCUS_ALL) # or FOCUS_CLICK depending on your needs
self.grab_focus()
Input.mouse_mode = Input.MOUSE_MODE_VISIBLE

func hide_ui():
self.visible = false
Input.mouse_mode = Input.MOUSE_MODE_CAPTURED

# Check if signals exist before disconnecting

for i in range(answers.size()):
var button = $Panel.get_node("Button" + str(i + 1))
if button.is_connected("pressed", Callable(self, "_on_button_1_pressed")):
button.pressed.disconnect(_on_button_1_pressed)

func _ready():
hide_ui()

func _on_button_1_pressed(button_index: int):

# Immediately disable all buttons after one is pressed
for i in range(answers.size()):
var button = $Panel.get_node("Button" + str(i + 1))
button.disabled = true

if answers[button_index] == correct_answer:
display_feedback("Correct!")
var player_node = get_tree().get_first_node_in_group("Player") # Find the
player node
if player_node:
player_node.correct_answer_count += 1
else:
display_feedback("Wrong!")

51 | Page
 get_tree().call_group("Player", "die")

func display_feedback(message):
var feedback_label = $Panel.get_node_or_null("FeedbackLabel")
if feedback_label:
feedback_label.text = message
feedback_label.visible = true
if message == "Correct!":
feedback_label.modulate = Color.GREEN
else:
feedback_label.modulate = Color.RED

await get_tree().create_timer(1.0).timeout # 2-second delay

feedback_label.visible = false
hide_ui() # Hide the UI after feedback is shown

52 | Page
53 | Page
54 | Page